RE: XML Schema WG Comments on Last Call Draft

Thanks for the comment, and sorry to take so long to respond.

The use of the term "already" in this instance doesn't seem to the WG to be terribly misleading in the case you've pointed out.  In this case, willful misinterpretation might imply that infinite recursion should be used to create a list of the include history that is infinitely long, but we don't feel implementers are likely to get this wrong.

We don't plan to make a change at this point.  If you disagree, please let us know promptly.

________________________________________
From: www-xml-xinclude-comments-request@w3.org [mailto:www-xml-xinclude-comments-request@w3.org] On Behalf Of Biron,Paul V
Sent: Monday, May 24, 2004 11:58 AM
To: 'www-xml-xinclude-comments@w3.org'
Cc: w3c-xml-schema-ig; Jonathan Marsh
Subject: Re: XML Schema WG Comments on Last Call Draft

> From: Jonathan Marsh <jmarsh@microsoft.com> 
> Date: Mon, 29 Mar 2004 13:19:48 -0800 
> To: "C. M. Sperberg-McQueen" <cmsmcq@acm.org> 
> Cc: "Ashok Malhotra" <ashokma@microsoft.com>, <www-xml-xinclude-comments@w3.org>, <w3c-xml-schema-ig@w3.org> 
> 
> The XML Core WG has accepted your request to provide a place for the 
> xi:include elements in the resulting infoset.  Here is a draft of the 
> significant part of the text I'm proposing to replace the Boolean 
> [included] property: 
> 
> -------------- 
> The inclusion history of each top-level included item is recorded in the 
> extension property [include history]. The [include history] property is 
> a list of element information items, representing the xi:include 
> elements for recursive levels of inclusion. If an [include history] 
> property already appears on a top-level included item, the xi:include 
> element information item is prepended to the list. If no [include 
> history] property exists, then this property is added with the single 
> value of the xi:include element information item. 
> -------------- 
> 
> We note that we don't expect to see implementation fully exposing this 
> property in our upcoming CR, but that's no worse a match with current 
> implementations than the previous [included] property. 
Thank you for your reply to our further request [1], we appologize for the delay in responding.  The working has discussed this response and are happy with the result.
Some members of the WG noted, however, that the term "already" in the sentence "If an [include history] property already appears on a top-level included item..." above implies a time axis in the construction of the result infoset.  That is, if a includes b includes c, which include happens first?  We appologize if this aspect is covered elsewhere in the XInclude CR [2] but a quick perusal of section 4 Processing Model [3] did not turn anything up.  
While it is not necessary to address the above in order to satisfy the Schema WG in response to our previous comments you might want to consider addressing it to prevent future questions of this nature.
thank you, 
pvb (for the XML Schema WG) 
[1] http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/2004Feb/0021.html 
[2] http://www.w3.org/TR/2004/CR-xinclude-20040413 
[3] http://www.w3.org/TR/2004/CR-xinclude-20040413/#processing 
p.s. For the record, our original comment on the Last Call is here [4] and your response to that comment is here [5] 
[4] http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/2004Jan/0015.html 
[5] http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/2004Feb/0011.html

Received on Wednesday, 7 July 2004 16:46:38 UTC