This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Minor point #1 in http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008Mar/0001.html 'document' as defined in the XML spec. is a character sequence -- this seems unnecessarily restrictive -- surely a reference to the Infoset spec. would be more appropriate here?
Resolution in F2F meeting on 3/31: The SML WG doesn't want to change our definition. Record our intent not to change the substance of the spec and instruct the editors to draft a non-normative note for review. The note should clarify the relation between the XML document (character stream) and the non-character representations (SAX or DOM). Editors should submit the non-normative note for review by the WG. The change in status should cause email to be sent to the originator of this issue, to whom the following request is addressed. Please review the current LC text and let us know if you agree with this resolution of your issue, by adding a comment to the issue record. Or, if you do not agree with this resolution, please add a comment explaining why. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.
resolution (conf call on 4/17/2008): remove the 'decided' keyword because the 2 week response period has elapsed (see comment# 1).
I have looked extensively, and cannot find any change in the 3 March draft which addresses this issue. . .
Sorry, Comment 1 had some incorrect boilerplate text. The non-normative note is being drafted and we'll update this bug with a link to the note when it is ready
Proposal: Add the following text section 2.1 Notational Conventions: This specification refers to terms such as XML document, element, attribute, etc. for the sake of brevity. The alternative would be to use terms like XML document or a synthetic infoset [link to infoset spec], element information item [link], attribute information item [link], etc. at each place. This would make the specification excessively verbose without adding to or changing the meaning of the existing text. The use of the concise terms is not intended to exclude other XML representations. The concepts defined in this specification apply to all forms of XML representations.
resolution (5/15 conf call): add the proposed text as mentioned in comment# 5. The SML WG believes that the resolution addresses this issue fully. I'm changing its status accordingly. The change in status should cause email to be sent to the originator of this issue, to whom the following request is addressed. Please review the proposed text and let us know if you agree with this resolution of your issue, by adding a comment to the issue record. Or, if you do not agree with this resolution, please add a comment explaining why. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.
Resolution in 5/29 call - fix as per Comment #5
fixed per comment# 5.
I am happy that the text which has been added addresses my concern