RE: Schema for schemas bugs?

Thanks Henry. We are now all waiting for the Errata. The following 2
issues is for clarification and commonality, please comment for any

First thing ~~~~~~~~~~~~~
You have memtioned that renaming of anySimpleType or anyType is. Will
there be an errata for this? Below is a mail from you from 11/01.

>> 1.
>> <xs:schema xmlns:xs="" >
>>       <xs:simpleType name="ct1">
>>             <xs:restriction base="xs:anyType" />
>>       </xs:simpleType>
>> </xs:schema>

>Yes, invalid.

>> 2.
>> <xs:schema xmlns:xs="" >
>>       <xs:simpleType name="ct2">
>>             <xs:restriction base="xs:anySimpleType" />
>>       </xs:simpleType>
>> </xs:schema>

>Yes, invalid.

>> 3.
>> <xs:schema xmlns:xs="" >
>>       <xs:complexType name="ct4">
>>             <xs:simpleContent>
>>                   <xs:restriction base="xs:anySimpleType" />
>>             </xs:simpleContent>
>>       </xs:complexType>
>> </xs:schema>

>Yes, invalid.

>But you raise an interesting point -- the above don't actually attempt 
>a restriction, just a private renaming.  There's no reason we shouldn't
>allow this.  The third case in particular, if it contained attributes,
is >something people might reasonably wish to do.

>I'll raise a potential erratum on this.

In short, I think we will need the following 2 points in errata.
(1) allow renaming of anyType or AST
(2) Restriction with facets on anySimpleType is not allowed unless the
restriction is build-in dataTypes (to satisfy SfS).

Scond thing:~~~~~~~~~~~~~~~~~~~~~
I agree that 'xmlns:xml=""' is
interpreted differently as allowed by some implementors and not the
others due to the vagueness of the spec, but it is explicit that this
declaration is not required. Therefore the common denominator is to NOT
specify it. In a standard spec like XSD, I think we should not specify
it to satisfy all parties.


-----Original Message-----
From: Henry S. Thompson [] 
Sent: Tuesday, April 23, 2002 1:28 AM
To: Aung Aung
Subject: Re: Schema for schemas bugs?

"Aung Aung" <> writes:

> The issues with the  xsd4xsd in MSXML are, 
> 1. There were some confusion in the beginning about the usage of
> anySimpleType. After some clarification, we allow anySimpleType as a
> type name. However,  the spec also said "simple *ur-type definition*
> <>  must not be
> named as the *base type definition*
> definition>  of any user-defined simple types: as it has no
> facets, this would be incoherent." So, how are all the primitive data
> types have restriction facets on anySimpleType. Spes does not say how
> allows it. Do we have to special-case all primitive dataType as
> restrict-able from anySimpleType exclusive to for parsing xsd4xsd (for
> such confusing issue, spec should implicit about how to approach it.)?

Sorry for the confusion -- you're right that the inclusion in the
sForS of the 'information only' definitions of the builtin primitive
datatypes is problematic.  I would note in our defense that the quote
above says you can't have anySimpleType as the {base type def} of and
_user-defined_ types, but I agree that taken as a user schema doc.,
the published sForS violates this constraint.

The _reason_ these defns are there is so that for _all_ builtin types
there is a well-grounded URL of the form

but with hindsight we perhaps should have buried all these defns
inside <xs:documentation>.

> 3. Explicit declaration such as
> xmlns:xml= is now allowed by the
> namespace spec. It is explicitly stated in the xml spec that xml:lang
> ( is a special
> attribute to allow language specification in XML, it need not
> declaration.  
> [2] 
> PrefixedAttName
> ::= 
> 'xmlns:' NCName
> [ 
> NSC: Leading "XML"
> ed>  ]
> Namespace Constraint: Leading "XML"
> Prefixes beginning with the three-letter sequence x, m, l, in any case
> combination, are reserved for use by XML and XML-related

Microsoft has consistently maintained that this prose allows parsers
to raise an error when confronted by the correct declaration
'xmlns:xml=""'.  Most of the rest
of the implementor community have read it as allowing _only_ this
declaration for that prefix, while not requiring it.  I believe there
will soon be an erratum clarifying this.

> 4. should remove the trailing space in version [version="Id:
> XMLSchema.xsd,v 1.48 2001/04/24 18:56:39 ht Exp "]. Because it is
> as toke, which cannot have trailing space.

It's not a token at all -- this is just a bug and will be fixed.

> 5. Some group reference that already mentioned in other threads.


  Henry S. Thompson, HCRC Language Technology Group, University of
          W3C Fellow 1999--2002, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail:
 [mail really from me _always_ has this .sig -- mail without it is
forged spam]

Received on Tuesday, 23 April 2002 13:37:51 UTC