Dale said that there is a need for a clear specification in UBL that the schema-validated instance will always be taken to be the definitive document. I'm not sure that'd be enough; I think two normative statements would be needed. - All UBL-compliant document instances MUST contain information about the location and version (if the latter is relevant) of the schema to be used to validate said document - Only the infoset produced by document validation is canonical wrt said document Or, alternatively, one normative sentence would to the trick ;-) - No defaulted attributes are allowed in UBL schemas. Eve L. Maler wrote: > >> From: McKay, Dale R. <
DMCKAY@northropgrumman.com> >> To: 'Eve L. Maler' <
eve.maler@sun.com> >> Subject: Defaults >> Date: Wed, 9 Jan 2002 08:14:31 -0800 >> X-Mailer: Internet Mail Service (5.5.2650.21) >> >> Here's a draft of Section A9. As noted, I really didn't have enough to >> go on >> from our legal authority, so have winged it to a considerable extent. >> Comments? >> >> -Dale >> >> > -- > Eve Maler +1 781 442 3190 > Sun Microsystems XML Technology Center eve.maler @ sun.com > DefaultDetails.doc > > Content-Type: > > application/msword > Content-Encoding: > > BASE64 > > > ------------------------------------------------------------------------ > Part 1.3 > > Content-Type: > > text/plain > > -- Eduardo Gutentag e-mail:
eduardo.gutentag@Sun.COM XML Technology Center Phone: (510) 986-3651 x73651 Sun Microsystems Inc.