This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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>
The minutes have used 'context types' where 'content types' is meant, I think The prose above corrects all the resulting bugs.
The two part-specific items having been resolved (2337 in October 2005, 2338 on 10 February 2006), this umbrella issue can now be closed.