- From: Ashok Malhotra <ashokma@microsoft.com>
- Date: Fri, 9 Jan 2004 09:55:26 -0800
- To: <www-xml-xinclude-comments@w3.org>
- Cc: <w3c-xml-schema-ig@w3.org>
- Message-ID: <EDB607C8AC991F40BE646533A1A673E8F8DBF1@RED-MSG-42.redmond.corp.microsoft.com>
These comments on the XInclude Last Call draft dated November 10, 2003 are on behalf of the XML Schema WG The XML Schema WG congratulates the XML Core WG for the good work it has done in producing the last call draft for XInclude. We find this draft much improved over earlier versions. We also note that most of our comments on earlier versions have been addressed. Consequently we have only minor comments on this version of the draft. 1. XInclude now works as an Infoset transformation. If the documents/fragments have been Schema validated the PSVI decorations are removed before the inclusion takes place and the resulting Infosets have to be re-validated if so needed. We find your description of the inclusion process under this constraint consistent and correct but we are disappointed that you did not choose to step up to the challenge of inclusions based on PSVIs. 2. In our comments on the last draft we said : "(3) We consider it a mistake to erase all record that XInclude processing has occurred. This damages the usability of this specification for many applications, such as distributed editing, document packaging, and so on." Your reaction to this comment was to point out that most of the Infoset properties were optional and implementations were free to maintain such information if they wished. We would prefer a better architected solution to this issue. 3. Section 5 discusses support for IRIs. Since the IRI proposal is not a recommendation yet, you say you expect to issue an erratum with possible changes when the IRI proposal becomes a recommendation. This is reasonable. But, it's is a pity that the IRI support has to be handled in this manner. Do you have a projected date for the erratum? All the best, Ashok
Received on Friday, 9 January 2004 13:00:17 UTC