- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 11 Feb 2006 01:42:24 +0000
- To: www-xml-schema-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2842
Summary: RQ-134 Origin of inherited portions of content model
(scd-origin-inheritance)
Product: XML Schema
Version: 1.1 only
Platform: Other
OS/Version: All
Status: NEW
Keywords: needsDrafting
Severity: normal
Priority: P2
Component: Structures: XSD Part 1
AssignedTo: ht@w3.org
ReportedBy: cmsmcq@w3.org
QAContact: www-xml-schema-comments@w3.org
This issue was originally reported by Asir Vedamuthu, Mary Holstege.
Today, there is no mechanism to trace back the origin of some of the
components that were assembled via compiling a complex/simple type
definition. Suppose one type extends another type by adding
additional terms to a sequence. In the schema component model there is
no direct way to determine which terms in the sequence come from the
base type: the inheritance is "compiled out" as it were.
How does this issue apply to Simple Type Definition? via Simple Type
Definition.{facets} property. This property is a union of the set of
Facets components resolved to by the facet [children] merged with
{facets} from {base type definition}, subject ..
See
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0222.html
See also
http://www.w3.org/TR/2003/WD-xmlschema-ref-20030109/#issue_derived_cm_not_manifest
This item was classified as Req in the meeting of 2004-03-11
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Mar/0026.html).
This item was discussed, and phase-1 agreement was reached, in the
meeting of 2004-04-02
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Apr/0041.html).
According to the requirements document, phase-1 agreement has been reached.
Received on Saturday, 11 February 2006 01:42:26 UTC