2335 2005-10-10 14:11:51 +0000 Add {context} property to type definitions 2006-03-15 01:30:42 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.1 only PC Windows XP RESOLVED FIXED http://www.w3.org/XML/Group/2005/09/xml-schema-ftf-minutes#d0e159 resolved P2 normal --- 2337 2338 1 ht ht www-xml-schema-comments oldest_to_newest 6669 0 ht 2005-10-10 14:12:01 +0000 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> 8127 1 ht 2006-02-06 19:01:16 +0000 The minutes have used 'context types' where 'content types' is meant, I think The prose above corrects all the resulting bugs. 8728 2 cmsmcq 2006-03-15 01:30:42 +0000 The two part-specific items having been resolved (2337 in October 2005, 2338 on 10 February 2006), this umbrella issue can now be closed.