W3C home > Mailing lists > Public > xmlschema-dev@w3.org > June 2007

RE: Discrepancies in the W3C Schema docs?

From: Michael Kay <mike@saxonica.com>
Date: Mon, 11 Jun 2007 15:41:43 +0100
To: "'Dan Maharry'" <dan@mcd.coop>, <xmlschema-dev@w3.org>
Message-ID: <00c701c7ac36$a4030020$6401a8c0@turtle>

> My point was that the NMTOKENS type *is* defined explicitly 
> as non-zero-length in the schema doc while the NMTOKEN type 
> is not. As you say, it is only defined as non-zero-length in 
> the grammar rules in the XML 1.0 spec and not in the schema 
> docs which is my issue. 
> 
> "Any property identified as a having a set, subset or *list* 
> value may have an empty value unless this is explicitly ruled 
> out: this is not the same as absent." Says the schema doc. I 
> imply from that it must be ruled out in the schema doc.

Well, firstly, NMTOKEN isn't a set, subset, or list, it's a string.

Secondly, a normative reference from the Schema specification to the XML
specification has the same force as spelling out the rules in the schema
specification.

Thirdly, it is in fact spelt out in the schema specification: the definition
of the xs:NMTOKEN data type in the schema for schemas has <xs:pattern
value="\c+" id="NMTOKEN.pattern">. (Search in XML Schema Part 2 for
'simpleType name="NMTOKEN"' to find it).
> 
> > for minor comments like these, the best approach is to enter a bug
> report 
> > - one per problem - in the bugzilla database.
> 
> Where is the bugzilla database to do this?
> 
http://www.w3.org/Bugs/Public/query.cgi

Michael Kay
http://www.saxonica.com/
Received on Monday, 11 June 2007 14:41:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:59 GMT