Re: Issue 483 closed

Hi Martin,

At 3:23 AM -0700 04.7.13, Martin Gudgin wrote:
>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'm happy with this resolution.

-- 
Jun Fujisawa
<mailto:fujisawa.jun@canon.co.jp>

Received on Tuesday, 13 July 2004 12:09:43 UTC