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

Editorial LC comments on XOP

From: Jacek Kopecky <jacek.kopecky@deri.at>
Date: Fri, 18 Jun 2004 18:28:58 +0200
To: XMLP Comments <xmlp-comments@w3.org>
Message-Id: <1087576138.3043.50.camel@Kalb>

Hi, here are my editorial comments on the XOP LC draft:

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

2) in 1.1, drop second reference to XML InfoSet

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.
 
4) Section 1.2, [media type] link should be filled in

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

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

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.

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

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

10) consolidate spacing in references rfcxxxx and rfc xxxx (with/out
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

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

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

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.

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

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

17) Section 6.1 contains unbalanced parenthesis

Best regards,

Jacek
Received on Friday, 18 June 2004 12:29:05 GMT

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