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