On Thursday, July 22, 2004, 7:03:48 AM, Larry wrote:
LM> These comments are as much about the general "IETF MIME type
LM> registration from W3C recommendation" as they are about this
LM> particular registration:
LM> -------------
LM> It might be helpful if the registration template explained
LM> that "ccxml" stood for "Call Control eXtensible Markup Language"
LM> for use in voice browser applications, and that the registration
LM> is in a document intended to become a W3C recommendation.
I agree that this sort of context, although obvious when the W3C
document as a whole is studies, is fairly opaque when a single appendix
is extracted and sent as an email message.
Prepending the 'Abstract' of the specification, and giving a link to the
full specification, would be helpful.
LM> I'm not sure this is necessary, but since we're getting
LM> W3C recommendations registering MIME types, I wondered
LM> if making the registration template just a little bit
LM> more explanatory would be useful.
Certainly.
LM> Your translation from HTML to ASCII left out line breaks
LM> before heading lines, which made your template hard
LM> to read.
LM> Specific comments:
this case, the security issues of RFC1738, section 6, should
be considered.
LM> RFC 1738 has been superseded quite a while ago, by 2396.
When citing an RFC abcd, it is useful to do a Google search for
"Obsoletes: abcd" and "Updates: abcd" because RFCs do not have 'latest
version' URIs (or indeed canonical URIs at all).
Published specification:
This media type registration is for CCXML documents as
described by this specification.
'This specification' should be a link to the main page of the document,
even if that is a link to itself for a short document, and inline URIs
should be indicated in the ascii text version by a numbered link [1]
[1] http://example.org/like/this
A conversion to text can be obtained for any W3C document by appending
,text to the URI (before any fragment) for example
http://www.w3.org/TR/ccxml/,text#ccxml-mime-definition
which is redirected to (watch out for line
wrapping):
http://cgi.w3.org/cgi-bin/html2txt?url=http://www.w3.org/TR/ccxml/#ccxml-mime-definition
LM> I'm not 100% sure if this is necessary, but I'd expect
LM> if the template were to appear elsewhere to see
LM> a bibliographic citation, e.g.,
LM> "Voice Browser Call Control: CCXML Version 1.0", W3C
LM> Working Draft, 30 April 2004, W3C, <http://www.w3.org/TR/ccxml/>
I agree.
LM> Is "this specification" (or the whole specification) precise
LM> enough?
Not when the appendix is transmitted separately, no.
LM> In some other cases, a single W3C recommendation defines
LM> many different data types. Perhaps it would be useful to
LM> say, somewhere, e.g., that the MIME type refers to XML bodies that
LM> conform to the DTD/Schema referenced in Appendix B and C and
LM> interpreted by the rules in the cited specification.
Additional information:
Magic number(s):
There is no single initial octet sequence that is always
present in CCXML documents.
LM> While this section is titled "Magic number", I think
LM> what we're seeing in MIME registrations for XML content
LM> is a description of how to recognize CCXML if it isn't
LM> labeled. It would be useful here to identify the namespace
LM> expected and the likely root XML element name(s).
Yes, I agrre that this is current good practice. The text in this
registration is fine, but it should add something like:
This media type is expected to be handled by an XML processor, as
indicated by "+xml". XML processors may detect ccXML by its namespace
URI, http://www.w3.org/2001/vxml
Hmm the revision to RFC 3023 should probably supply suggested
boilerplate for this and, indeed, perhaps a registration template with
the common items for all +xml types.
Person & email address to contact for further information:
RJ Auburn, <rj(_at_)voxeo(_dot_)com>.
LM> Should there be a W3C contact as well?
The person listed is the W3C Editor of the specification. The fact that
they are the document editor should be noted since its not apparent from
the appendix in isolation.
Intended usage:
COMMON
Author/Change controller:
The CCXML specification is a work product of the World Wide Web
LM> Consortium's
Voice Browser Working Group. The W3C has change control over these
specifications.
LM> Or perhaps the W3C contact address should be listed here.
LM> Larry
--
Chris Lilley mailto:chris(_at_)w3(_dot_)org
Chair, W3C SVG Working Group
Member, W3C Technical Architecture Group