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

And here's the record of the submission for application/powder-s+xml.


-------- Original Message --------
Subject: [IANA #208576] AutoReply: Request for MIME media type 
Application/Standards Tree -
Date: Mon, 1 Dec 2008 13:07:29 +0000
From: IANA MIME Requests via RT <iana-mime@icann.org>
Reply-To: iana-mime@icann.org
To: phil@philarcher.org
References: <RT-Ticket-208576@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 208576. 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 #208576]

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 : Application

MIME subtype name : Standards Tree -powder-s+xml

Required parameters :

Optional parameters :

Encoding considerations : 7bit

Security considerations :
RFC 3023, section 10, reviews the security considerations for XML Media 
Types in general. application/powder-s+xml does not add to or subtract 
from such considerations.

Interoperability considerations :
POWDER-S documents are OWL ontologies and as such have a good deal of 
content related to semantics alongside the actual data. The new media 
type is necessary to identify that POWDER extends the formal semantics 
of RDF. If processed by RDF/OWL tools that do not implement the 
extension, the data will be largely meaningless, but not harmful.

Published specification :
Protocol for Web Description Resources (POWDER): Description Resources
(http://www.w3.org/TR/powder-dr/). See Section 4. Protocol for Web 
Description Resources (POWDER): Formal Semantics 
(http://www.w3.org/TR/powder-formal/) specifies the semantic extension 
referred to in answer to  question 7.

Applications which use this media :
Any RDF/OWL application will be able to process the data up to a point. 
An application that implements the semantic extension for full 
processing is nearing completion at http://transonto.sourceforge.net/. 
This uses a small amount of custom-written code but depends largely on 
established tools: Jena and Pellet.

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 application/powder-s+xml, we are also 
submitting a request to register text/powder+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)
Public Mailing list: public-powderwg@w3.org


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

Received on Monday, 1 December 2008 13:10:13 UTC