W3C home > Mailing lists > Public > xmlp-comments@w3.org > July 2004

Issue 483 closed

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Tue, 13 Jul 2004 03:23:21 -0700
Message-ID: <DD35CC66F54D8248B6E04232892B633802B04631@RED-MSG-43.redmond.corp.microsoft.com>
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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:28 GMT