- From: Martin Gudgin <mgudgin@microsoft.com>
- Date: Tue, 13 Jul 2004 03:23:21 -0700
- To: <fujisawa.jun@canon.co.jp>
- Cc: <xmlp-comments@w3.org>
Fujisawa-san, You raised an issue, number 483[1] regarding langauge in section 1 of the XOP specification[2]. The working group agrees that it is not clear from the context why attribute content cannot be optimized. The reason, that an element is used to indicate where content has been optimized, is present in Paragraph 2 of Section 1, but the language you refer to is in Paragraph 5. The two intervening paragraphs make the context unclear. The Working Group will remove the text 'As a result,' from Section 5 so that it reads: "Only element content can be optimized; attributes, non-base64-compatible character data, and data not in the canonical representation of the base64Binary datatype cannot be successfully optimized by XOP." I hope my explanation is clear and that this resolution is acceptable to you. If this resolution is NOT acceptable to you please let the working group know as soon as possible. Regards Martin Gudgin For the XMLP Working Group [1] http://www.w3.org/2000/xp/Group/xmlp-lc-issues#x482 [2] http://www.w3.org/TR/2004/WD-xop10-20040608/
Received on Tuesday, 13 July 2004 06:23:57 UTC