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

error in Table 1 of Schema primer

From: Gignac Donald A CRBE <GignacDA@nswccd.navy.mil>
Date: Mon, 23 Jul 2001 09:34:12 -0400
Message-ID: <1F9F67162ADED3119F18009027A8F404C604DA@crbeex03.dt.navy.mil>
To: "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
Cc: "Westbrook Evelyn 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>
This is with reference to the entry "(0, 1) 37,  -" in the "Elements (minoccurs, maxoccurs) fixed, default" column in Table 1 "Occurrence Constraints for Elements and Attributes" in the Schema Primer. The corresponding entry in the "Notes" column is "element\attribute must occur once, if it does appear its value must be 37, if it does not appear its value is 37".

The "it" refers to an element or attribute. However, "if does not appear its value is 37" does not seem to be true for an element in view of a previous paragraph 

	The schema processor treats defaulted elements slightly differently. When an element is declared with a default value, the 	value of the element is whatever value appears as the element's content in the instance document; if the element appears 	without any content, the schema processor provides the element with a value equal to that of the default attribute. 	However, if the element does not appear in the instance document, the schema processor does not provide the element 	all. In summary, the differences between element and attribute defaults can be stated as: Default attribute values apply 	when attributes are missing, and default element values apply when elements are empty. 

in clause 2.2.1 "Occurrence Constraints".

Donald Gignac	"gignacda@nswccd.navy.mil"	301-227-3348
Received on Monday, 23 July 2001 09:34:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:12:51 GMT