W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2012

[whatwg] FW: [[IANA #598351] Request for MIME media type Application/Standards Tree - xhtml+xml]

From: Michael[tm] Smith <mike@w3.org>
Date: Mon, 22 Oct 2012 17:11:51 +0900
To: Ian Hickson <ian@hixie.ch>
Message-ID: <20121022081150.GQ23069@sideshowbarker>
Cc: whatwg@whatwg.org
Hixie,

Comments from IANA review of the application/xhtml+xml mime type. (Note
that I never got an actual response back -- only this and a previous
reminder, so forwarding this to you as-is instead.)

  --Mike

----- Forwarded message from Amanda Baber via RT <iana-mime@iana.org> -----

Subject: [IANA #598351] Request for MIME media type Application/Standards Tree - xhtml+xml
From: Amanda Baber via RT <iana-mime@iana.org>
To: mike@w3.org
Date: Fri, 19 Oct 2012 21:29:21 +0000

Dear Michael,

This is a reminder that IANA needs your response by 2 November.

Thanks in advance,

Amanda Baber
ICANN/IANA

On Wed Oct 03 19:32:46 2012, amanda.baber wrote:
> Hi Michael,
> 
> The IESG-designated expert has reviewed your application and returned 
> the inline comments below. Please reply to this email within 30 days 
> (i.e. by 2 November) with a revised application. 
> 
> If you have any questions, please don't hesitate to contact us.
> 
> As of this writing, four of your requests are still with the expert. 
> 
> Best regards,
> 
> Amanda Baber
> IANA Analyst
> ICANN
> 
> ===
> 
> > Name : Michael[tm] Smith
> 
> > Email : mike@w3.org
> 
> > MIME media type name : Application
> 
> > MIME subtype name : Standards Tree - xhtml+xml
> 
> > Required parameters : Same as for application/xml [RFC3023]
> 
> This needs to change to "N/A". Application/xml has no required
> parameters, so this is a pointer to nothing. And in the highly unlikely
> event a required parameter was ever added to application/xml, you most
> certainly would not want to inherit it automatically.
> 
> > Optional parameters :
> > Same as for application/xml [RFC3023]
> 
> This really isn't a good way to specify the charset parameter for this
> type, since in the event that parameters were added to application/xml
> this type could be seen as inheriting them, which you probaby don't want.
> 
> I would suggest instead listing the charset parameter and then referring
> to RFC 3023 for its definition.
> 
> > Encoding considerations : 8bit
> 
> This implies that xhtml is never encoded using utf-16. I am doubtful
> that is true. If it isn't, this needs to change to binary.
> 
> 
> > Security considerations :
> > Same as for application/xml [RFC3023]
> 
> This isn't even close to sufficient, since HTML has massive security
> considerations XML in general does not have.
> 
> In discussing the security considerations for a media type it is
> necessary to cover at least these points:
> 
> (1) State whether or not the media type contains active or executable
>     content. If the media type does contain executable content explain
>     what measures have been taken to insure that it can be executed
>     safely, e.g. a sandbox, safe operation set, signed content, etc.
> 
> (2) State whether or not the information contained in the media type
>     needs privacy or integrity services.
> 
> (3) If the answer to (2) is yes, elaborate on any privacy or integrity
>     services the media type itself provides.
> 
> These points all need to be covered briefly and ideally pointers to more
> specific security considerations for HTML will also be given.
> 
> > Interoperability considerations :
> 
> 
> > Published specification :
> > Labeling a resource with the application/xhtml+xml type asserts that the
> > resource is an XML document that likely has a root element from the HTML
> > namespace. Thus, the relevant specifications are the XML specification,
> > the Namespaces in XML specification, and the HTML5 specification:
> 
> > http://www.w3.org/TR/html5/iana.html#application-xhtml-xml
> 
> > Applications which use this media :
> > Same as for application/xml [RFC3023]
> 
> Er, no, that's rather obviously not true. Plenty of applications use
> XML that have no use for HTML, and vice versa.
> 
> I suggest just leaving this blank since XHTML is a very general thing
> and trying to list all the applications is pointless.
> 
> > Additional information :
> 
> > 1. Magic number(s) : Same as for application/xml [RFC3023]
> > 2. File extension(s) : "xhtml" and "xht" are sometimes used
> > 3. Macintosh file type code : TEXT
> > 4. Object Identifiers: [none]
> 
> 
> 
> > Person to contact for further information :
> 
> > 1. Name : Michael[tm] Smith
> > 2. Email : mike@w3.org
> 
> > Intended usage : Common
> 
> 
> > Author/Change controller : Author:
> > Ian Hickson <ian at hixie.ch>
> 
> > Change controller:
> > W3C





----- End forwarded message -----

-- 
Michael[tm] Smith http://people.w3.org/mike
Received on Monday, 22 October 2012 08:12:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:11 GMT