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

Issue 476 closed

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Fri, 16 Jul 2004 09:37:57 -0700
Message-ID: <DD35CC66F54D8248B6E04232892B633802BE7951@RED-MSG-43.redmond.corp.microsoft.com>
To: <xmlp-comments@w3.org>, <jacek.kopecky@deri.at>

Jacek,

You raised an issue 476[1] on the XOP specification[2]. The editors have
made the following changes(reflected in latest editors copy[4])

> 1) just before 1.1, decapitalize the section numbers in the overview -
> instead of Section Four say Section four.

Changed to use Section 4 rather than Section Four ( see[3] )

> 2) in 1.1, drop second reference to XML InfoSet

Done.

> 3) xop:Includeelement add space, in multiple places in the spec, same
> with hrefattribute in multiple places and other similar spacing
problems
> - suggest searching for the pair >< in the XML or for a letter and <
> with no space in between, I guess.

Done.
 
> 4) Section 1.2, [media type] link should be filled in

Done. 

> 5) Section 1.3 add spacing and/or padding to table to make it more
> readable

Done. Made the table 3 columns wide.

> 6) Section 2 heading: XOP Infosets Constructs - drop first plural -
XOP
> Infoset Constructs

Done

> 7) Sections 2.1, 2.2, xop:Include element MUST have the name of
Include?
> Oh, please! 8-) I suggest taking the approach from Representation
header
> spec.

Done.

> 8) Section 2.1 third bullet: ... It MUST NOT change the semantics...
> "it" is ambiguous, I suggest using "the element"

Fixed. 

> 9) Section 2.1 fourth bullet: hrefattribute information items - space
> missing, drop 's' at the end (plural items)

Fixed.

> 10) consolidate spacing in references rfcxxxx and rfc xxxx (with/out
> space)

Done. ( They now always have a space )

> 11) also, I believe some references are not properly pointing to their
> destinations (rfc reference in 2.2, third bullet), may be related to
the
> problem above

Fixed.

> 12) Section 2.2 fourth bullet: its owner must be a xop:include
element.
> period.

Done.

> 13) Section 3 heading: XOP's processing model - drop possessive -> 
> "XOP processing model"

Fixed.

> 14) Section 3.2 ... has as its [children] a xop:Include... - mismatch
of
> plural [children] and singular element, suggest a bit more verbose
> version that says that is the only child.

Language amended.

> 15) Section 3.2: ... replace its [children] with a char info items ...
-
> drop indefinite article 'a'

Langage amended.

> 16) Section 4.1 says the media type of the root part must be specific
to
> XOP encoding of the actual data, 5 mentions application/soap_xop+xml,
> the example in 1.2 uses text/xml though, should use
> application/soap_xop+xml

Fixed.

> 17) Section 6.1 contains unbalanced parenthesis

Fixed.

Regards

Martin Gudgin
For the XMLP Working Group

[1] http://www.w3.org/2000/xp/Group/xmlp-lc-issues#476
[2] http://www.w3.org/TR/2004/WD-xop10-20040608/
[3] http://webster.commnet.edu/grammar/numbers.htm
[4] http://www.w3.org/2000/xp/Group/3/06/Attachments/xop.xml 
Received on Friday, 16 July 2004 12:38:21 GMT

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