W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > July to September 2001

Comments on Appendix C of the Schema Primer

From: Gignac Donald A CRBE <GignacDA@nswccd.navy.mil>
Date: Thu, 30 Aug 2001 09:47:41 -0400
Message-ID: <1F9F67162ADED3119F18009027A8F404C6054F@crbeex03.dt.navy.mil>
To: "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
Cc: "Westbrook E L (Lori) CRBE" <WestbrookEL@nswccd.navy.mil>, "Junod L J (John) II CRBE" <JunodLJ@nswccd.navy.mil>, "Garner F J (Joe) CRBE" <GarnerFJ@nswccd.navy.mil>
1. Appendix C of the Schema Primer contains the text
	Note that when this instance document is processed, the entity will be dereferenced before schema validation takes place. 
While the meaning of "dereferenced" is clear from the context, the usual "resolved" terminology would be more appropriate.

2. The approach used in the example "Using an element instead of an entity in an instance" begs the question. The non-keyboard character (for the US English keyboard) "eacute" itself  is provided as the value of the "fixed" attribute on the "xsd:element" tag defining the "eacute" element type, e.g.

	<xsd:element name="eacute" type="xsd:token" fixed=""/>

If I can directly enter (i.e., from the keyboard) this "eacute" character as the value of the "fixed" attribute, why not just type it in the content of the "city" element and not go through this unneeded procedure? How would this approach handle the other non-keyboard characters such as the degree sign, Greek letters, mathematical symbols, etc.?

3. The "city" element
should be rewritten as
since the XML specification (http://www.w3.org/TR/2000/REC-xml-20001006#sec-starttags) recommends (for operability) that the empty-element tag be used only for EMPTY element types.

Donald Gignac	"gignacda@nswccd.navy.mil"	1-301-227-3348
Received on Thursday, 30 August 2001 09:48:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:08:53 UTC