- From: Biron,Paul V <Paul.V.Biron@kp.org>
- Date: Tue, 10 Apr 2001 15:34:33 -0700
- To: "'Jeff Lowery'" <jlowery@scenicsoft.com>, "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
> -----Original Message----- > From: Jeff Lowery [SMTP:jlowery@scenicsoft.com] > Sent: Saturday, April 07, 2001 11:22 PM > To: 'www-xml-schema-comments@w3.org' > Subject: Part 2: Datatypes > > Couple of minor corrections (excuse the bad element names): > > <2.4.2.6 whiteSpace> > "whiteSpace is applicable to all atomic and list datatypes. For all atomic > datatypes other than string (and types derived by restriction from it) the > value of whiteSpace is collapse and cannot be changed by a schema > author;..." > Actually, the whitespace value for normalizedString (derived from string) > is > "replace"; token collapses it. > </2.4.2.6 whiteSpace> > normalizedString is covered by the "...(and types derived by restriction from it)..." clause. IOW, the whiteSpace is collapse for all PRIMITIVE types other than string. Would it help if we added the word "primitive"? > <Datatypes Schema> > Near the bottom of the ENTITIES definition it says: > <xs:minLength value="1" id="ENTITES.minLength"/> > Missing the "I" in ENTITIES.minLength; hard to see, I know. > </Datatypes Schema> > Thank you catching this one. We'll fix it. > P. S. > Sorry, I'm sure this has been asked several times already: > Committee-endorsed XML Schema namespace prefix convention: xs:? xsd:? > both? > other? none? > None. The WG hasn't "endorsed" any specific prefix. And, speaking just for myself, the WG should NOT endorse any specific prefix. pvb
Received on Tuesday, 10 April 2001 18:44:59 UTC