- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 10 Oct 2005 14:12:02 +0000
- To: www-xml-schema-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2335
Summary: Add {context} property to type definitions
Product: XML Schema
Version: 1.1
Platform: PC
URL: http://www.w3.org/XML/Group/2005/09/xml-schema-ftf-
minutes#d0e159
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: XSD Part 1: Structures
AssignedTo: ht@w3.org
ReportedBy: ht@inf.ed.ac.uk
QAContact: www-xml-schema-comments@w3.org
Back off from {scope} for S and C TDs, use {context} instead, has a value
(always a component) iff TD is anonymous. By cases (see minutes ref):
element types: the element declaration.
attribute types: the attribute declaration.
union members: the union.
list items: the list.
simple content type (B in xmpl below) of complex types: the complex type (C).
base types (A in xmpl below) of simple content type of complex types: the
content type (B) of the complex type. (This could be viewed as an instance of
anonymous base of simple restricted type (below).)
type O redefined by type N: O.context set to N.
anonymous base (X) of simple restricted type: the restricted type (Y)
<complexType name="C">
<simpleContent>
<restriction base="my:D">
<simpleType><!--* call this simple type A *-->
...
</simpleType>
... facets ...
<!--* apply these facets to A; call the result B *-->
</restriction>
</simpleContent>
</complexType>
<simpleType name="Y">
<restriction>
<simpleType> <!-- call this X -->
<list itemType="xs:string"/>
</simpleType>
... facets ...
</restriction>
</simpleType>
Received on Monday, 10 October 2005 14:12:13 UTC