- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 13 Jul 2008 15:53:31 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5862 Summary: Please retain redefine as well as override Product: XML Schema Version: 1.1 only Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Structures: XSD Part 1 AssignedTo: cmsmcq@w3.org ReportedBy: abcoates@londata.com QAContact: www-xml-schema-comments@w3.org I know that redefine isn't widely used, largely because of flaky implementations in the early days of XML Schema 1.0. However, an increasingly common approach for enterprise data modelling is to define a "core" data model that contains all possible fields, and then allow individual groups to customise data types *by restriction*, so that all customisations are held in sync by their common ancestor. While redefine was too restrictive in the past (because sometimes you do want to just override), redefine allows you to prove that you are using a restriction, not an extension, and to manage the use of extension versus restriction across sets of Schemas derived from a core set of Schemas. It's possible that as people move to Schema 1.1, and start to experiment with all of the features that they aren't currently using now with 1.0, they may revisit "redefine" and its uses. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 13 July 2008 15:54:04 UTC