W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2000

RE: Ability to BLOCK redefinition ( .. priority feedback)

From: Fuchs, Matthew <matthew.fuchs@commerceone.com>
Date: Tue, 21 Nov 2000 15:16:49 -0800
Message-ID: <4C4A7BE77CE1D311A1D200508BA38C1202F352AF@venus.commerceone.com>
To: "'Asir S Vedamuthu'" <asirv@webMethods.com>, "Www-Xml-Schema-Comments@W3. Org" <www-xml-schema-comments@w3.org>
Cc: W3c-Xml-Schema-Ig <w3c-xml-schema-ig@w3.org>
I agree completely with Asir's treatment of this issue.  It is not clear to
me that "redefine" is not a likely winner of the first deprecated feature
award, and therefore it is very wise to be able to turn it off.  In fact,
there should be a schema-level default (I hate schema level defaults) so
that the default value is to disallow this.

Matthew

> -----Original Message-----
> From: Asir S Vedamuthu [mailto:asirv@webMethods.com]
> Sent: Monday, November 20, 2000 6:00 AM
> To: Www-Xml-Schema-Comments@W3. Org
> Cc: W3c-Xml-Schema-Ig
> Subject: Ability to BLOCK redefinition ( .. priority feedback)
> 
> 
> I raised this issue at the F2F meeting on November 13th, 
> 2000. This e-mail
> provides a full explanation of the issue.
> 
> ISSUE: 'including modified component definitions' is a VERY 
> VERY powerful
> feature without proper checks and balances: ability to block 
> redefinition.
> Reference,
> http://www.w3.org/TR/2000/CR-xmlschema-1-20001024/#modify-schema
> 
> Why?
> 
> [1] If the block feature does not exists, there isn't an 
> obvious mechanism
> to validate or invalidate schema re-definitions
> 
> [2] Authors (schema authors) do not have a facility to 
> express their intent
> to processors and end-users using XML Schema surface syntax
> 
> [3] Absent a mechanism to block redefinitions, standards 
> (expressed using
> XML Schema) may splinter under the 'embrace and redefine' method of
> undermining and controlling the standard. Example, Asir's 
> Schema For Schemas
> by redefining one or more attribute / model groups
> 
> [4] Practically, I would like to divide my schema into two parts:
> redefinable and non-redefinable. Example, 'UserArea' is 
> redefinable and
> others aren't.
> 
> Proposed solutions,
> 
> [Option a] provide a facility to block redefinitions
> [Option b] eliminate 'including modified component 
> definitions' feature
> 
> All the best,
> 
> Asir S Vedamuthu
> webMethods, Inc.
> (Phone) 703-460-2513 (Fax) 703-460-2513 (E-mail) asirv@webmethods.com
> URL: http://www.webmethods.com
> 
Received on Tuesday, 21 November 2000 18:17:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:12:49 GMT