[Fwd: [IANA #208572] AutoReply: Request for MIME media type Text/Standards Tree -]

For the POWDER public record, I have submitted the request to IANA to 
register text/powder+xml as a Media Type.

-------- Original Message --------
Subject: [IANA #208572] AutoReply: Request for MIME media type 
Text/Standards Tree -
Date: Mon, 1 Dec 2008 12:56:55 +0000
From: IANA MIME Requests via RT <iana-mime@icann.org>
Reply-To: iana-mime@icann.org
To: phil@philarcher.org
References: <RT-Ticket-208572@icann.org> 

To whom it may concern:

This is an automatically generated message to notify you that we have
received your request, and it has been recorded in our ticketing
system with a reference number of 208572. To check the status
of your request, please see:


If you have any problems accessing this page, please contact

There is no need to reply to this message right now. IANA staff will
review your message shortly.

If this message is in reply to a previously submitted ticket, it is
possible that the previous ticket has been marked as closed. As we
review this ticket, we will also review previous correspondence and
take appropriate action.

To expedite processing, and ensure our staff can view the full history
of this request, please make sure you include the follow exact text in
the subject line of all future correspondence on this issue:

          [IANA #208572]

You can also simply reply to this message, as this tag is already in
the subject line.

Thank you,

The Internet Assigned Numbers Authority

Name : Phil Archer

Email : phil@philarcher.org

MIME media type name : Text

MIME subtype name : Standards Tree -powder+xml

Required parameters :

Optional parameters :

Encoding considerations : 7bit

Security considerations :
RFC 3023, section 10, reviews the security considerations for XML Media 
Types in general. text/powder+xml does not subtract from such 
considerations. However, the structure of a POWDER document is highly 
constrained with child elements from external namespaces prohibited for 
many elements. Thus we do not consider POWDER to present any addition 
security consideration.

Interoperability considerations :
The text top level media type is used in accordance with RFC2046, 
section 3(1) which says that "... software must not be required in order 
to get the general idea of the content." We contend that the structure 
of a POWDER document, whilst not desigend first and foremost to be 
human-readable, is simple enough for this requirement to be met. 
Therefore interoperability with systems that only render text is supported.

Published specification :
Protocol for Web Description Resources (POWDER): Description Resources
(http://www.w3.org/TR/powder-dr/). See Section 4.

Applications which use this media :
The POWDER Working Group is releasing two conformant POWDER processors. 
One is already available at http://keg.icra.org/cgi-bin/processor.cgi

Additional information :

1. Magic number(s) : None
2. File extension(s) : None (.xml is sufficient)
3. Macintosh file type code : None
4. Object Identifiers: None

The current draft of the relevant document is at Last Call but the WG is 
not expecting to make a separate call for implementations, preferring to 
seek transition to W3C Proposed Recommendation later this month. In 
addition to this request for text/powder+xml, we are also submitting a 
request to register application/powder-s+xml and the registration of 
'describedby' as a relationship type to be included at 

Person to contact for further information :

1. Name : Phil Archer
2. Email : phil@philarcher.org

Intended usage : Common

Author/Change controller : Phil Archer, POWDER WG chair;
Matt Womer, W3C Team Contact (mdw@w3.org)


Phil Archer
w. http://philarcher.org/

Received on Monday, 1 December 2008 13:09:41 UTC