Re: Media Type Registration request for POWDER and POWDER-S

Phil Archer <phil@philarcher.org> Thu, 22 January 2009 11:12 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0MBCTvV053689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Jan 2009 04:12:29 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n0MBCSIm053688; Thu, 22 Jan 2009 04:12:28 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from mtaout02-winn.ispmail.ntl.com (mtaout02-winn.ispmail.ntl.com [81.103.221.48]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0MBCGq6053638 for <ietf-xml-mime@imc.org>; Thu, 22 Jan 2009 04:12:27 -0700 (MST) (envelope-from phil@philarcher.org)
Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090122111215.YVJN4080.mtaout02-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com>; Thu, 22 Jan 2009 11:12:15 +0000
Received: from [86.12.217.99] by aamtaout02-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090122111214.QOYM21638.aamtaout02-winn.ispmail.ntl.com@[86.12.217.99]>; Thu, 22 Jan 2009 11:12:14 +0000
Message-ID: <4978548D.1080604@philarcher.org>
Date: Thu, 22 Jan 2009 11:12:13 +0000
From: Phil Archer <phil@philarcher.org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: ietf-types@iana.org
CC: ietf-xml-mime@imc.org, Public POWDER <public-powderwg@w3.org>
Subject: Re: Media Type Registration request for POWDER and POWDER-S
References: <493D3127.1080904@philarcher.org>
In-Reply-To: <493D3127.1080904@philarcher.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Cloudmark-Analysis: v=1.0 c=1 a=JvociZDhN3IA:10 a=zgnTKQX5KOQA:10 a=S89q9SsuAAAA:8 a=SSmOFEACAAAA:8 a=RFp60smDAAAA:8 a=vOyFs-Gt2QM4L5hM1bQA:9 a=l4_FmH1SqDKH7sTCvkoA:7 a=KZzjVydg05LF2WC4bAPA6C5_guwA:4 a=DFZ4TeuG6JwA:10 a=rUGnz4CYuSoA:10 a=e6IU-BRPPdS6bXfZ:21 a=x6U-xavQM-XC5ABG:21
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

To whom it may concern,

This request was submitted on 8th December last year, archived at [1], 
and effectively replaced the requests sent previously that were 
incorrect for various reasons [2].

As the POWDER WG makes its final preparations for a transition request 
for W3C Proposed Recommendation status, I realise that there has been no 
acknowledgement of the corrected requests, still less a resolution.

The W3C Recommendations Track document that includes the registration 
details is available with W3C member access at [3]. The text is not 
expected to change before PR transition is requested (apart from 
removing diff marks etc.).

Can I ask you to look into the matter please?

Thank you.

Phil Archer
On behalf of the POWDER WG.



[1] http://www.alvestrand.no/pipermail/ietf-types/2008-December/002122.html
[2] http://www.alvestrand.no/pipermail/ietf-types/2008-December/002117.html
[3] http://www.w3.org/2007/powder/Group/powder-dr/20090120-diff.html#appB



Phil Archer wrote:
> To whom it may concern,
> 
> This e-mail is sent in line with "How to Register an Internet Media Type 
> for a W3C Spec" [1] and follows an earlier attempt to follow the IANA 
> process (see 2, 3).
> 
> Having taken advice [4], the W3C POWDER Working Group requests that 
> consideration be given to registering two Media types for POWDER and 
> POWDER-S documents.
> 
> POWDER: application/powder+xml
> ==============================
> 
> POWDER is a constrained dialect of XML that transports RDF properties 
> and objects that can be associated with multiple subjects. The media 
> type details are included in Appendix B of POWDER: Description Resources 
> [5] which has just completed its (second) Last Call period. The version 
> cited here includes changes made in response to last call comments and 
> is not yet published, however, it is the one (or very close to the one) 
> the working group will present as the Proposed Recommendation. It is 
> anticipated that this happen within the next 2 weeks. The relevant 
> section of the Description Resources document is as follows:
> 
> Appendix B: POWDER Internet Media Type and Macintosh File Type
> 
> The following Media Type has been submitted to the IESG for review, 
> approval, and registration with IANA
> 
> contact:
>   Phil Archer or Matt Womer
> 
> See also:
>   How to Register a Media Type for a W3C Specification
>   Internet Media Type registration, consistency of use
>   TAG Finding 3 June 2002 (Revised 4 September 2002)
> 
> The Internet Media Type / MIME Type for POWDER is "application/powder+xml".
> 
> It is recommended that POWDER files use the file extension of .xml (all 
> lowercase) on all platforms.
> 
> It is recommended that POWDER files stored on Macintosh HFS file systems 
> be given a file type of "TEXT".
> 
> Type name:
>   application
> 
> Subtype name:
>   powder+xml
> 
> Required parameters:
>   None
> 
> Optional parameters:
>   None
> 
> Encoding considerations:
>   Identical to those of "application/xml" as specified in [RFC3023],
>   section 3.2.
> 
> Security considerations:
>   POWDER is used to make assertions, sometimes socially sensitive, about
>   web resources. Consumers of POWDER should be aware of the source and
>   chain of custody of this data. Security considerations for URIs
>   (Section 7 of RFC 3986 [RFC3986]) and IRIs (Section 8 of RFC 3987
>   [RFC3987]) apply to the extent that describing resources in POWDER may
>   prompt consumers to retrieve those resources.
> 
> Interoperability considerations:
>   There are no known interoperability issues.
> 
> Published specification:
>   http://www.w3.org/TR/powder-dr/
> 
> Applications which use this media type:
>   No known applications currently use this media type.
> 
> Additional information:
> Magic number(s):
>  As specified for "application/xml" in RFC 3023 [RFC3023], section 3.2.
> 
> File extension(s):
>   .xml
> 
> Fragment identifiers:
>   Identical to that of "application/xml" as described in RFC 3023
>   [RFC3023], section 5.
> 
> Base URI:
>   As specified in RFC 3023 [RFC3023], section 6.
> 
> Macintosh file type code(s):
>   "TEXT"
> 
> Person & email address to contact for further information:
>   public-powderwg@w3.org
> 
> Intended usage:
> COMMON
> 
> Restrictions on usage:
>   None
> 
> Author/Change controller:
>   The POWDER specification is a work product of the World Wide Web
>   Consortium's Protocol for Web Description Resources (POWDER) Working
>   Group. The W3C has change control over these specifications.
> 
> POWDER-S: application/powder-s+xml
> ==================================
> 
> Semantic POWDER, or POWDER-S, is typically generated by performing a 
> transformation on a POWDER document. Each POWDER-S document is an OWL 
> ontology from which properties and values can be inferred for a given 
> resource. In order for inferences to be drawn, however, OWL tools must 
> implement a semantic extension (defined separately) and it is for this 
> reason that a new media type is requested, rather than using the 
> existing RDF/OWL media types. A POWDER-S document is valid RDF/OWL but 
> is essentially meaningless without the semantic extension.
> 
> The media type details are included in Appendix C of POWDER: Description 
> Resources [5] as follows:
> 
> Appendix C: POWDER-S Internet Media Type and Macintosh File Type
> 
> The following Media Type has been submitted to the IESG for review, 
> approval, and registration with IANA
> 
> contact:
>   Phil Archer or Matt Womer
> 
> See also:
>   How to Register a Media Type for a W3C Specification
>   Internet Media Type registration, consistency of use
>   TAG Finding 3 June 2002 (Revised 4 September 2002)
> 
> The Internet Media Type / MIME Type for POWDER-S is 
> "application/powder-s+xml".
> 
> It is recommended that POWDER-S files use the file extension of .rdf 
> (all lowercase) on all platforms.
> 
> It is recommended that POWDER-S files stored on Macintosh HFS file 
> systems be given a file type of "TEXT".
> 
> Type name:
>   application
> 
> Subtype name:
>   powder-s+xml
> 
> Required parameters:
>   None
> 
> Optional parameters:
>   None
> 
> Encoding considerations:
>  Identical to those of "application/xml" as specified in [RFC3023],
>   section 3.2.
> 
> Security considerations:
>   POWDER-S is used to make assertions, sometimes socially sensitive,
>   about web resources. Consumers of POWDER should-S be aware of the
>   source and chain of custody of this data. Security considerations for
>   URIs (Section 7 of RFC 3986 [RFC3986]) and IRIs (Section 8 of RFC 3987
>   [RFC3987]) apply to the extent that describing resources in POWDER-S
>   may prompt consumers to retrieve those resources.
> 
> Interoperability considerations:
>   There are no known interoperability issues.
> 
> Published specification:
>   http://www.w3.org/TR/powder-dr/
> 
> Applications which use this media type:
>   No known applications currently use this media type.
> 
> Additional information:
> 
> Magic number(s):
>   As specified for "application/xml" in RFC 3023 [RFC3023], section 3.2.
> 
> File extension(s):
>   .rdf
> 
> Fragment identifiers:
>   Identical to that of "application/xml" as described in RFC 3023
>   [RFC3023], section 5.
> 
> Base URI:
>   As specified in RFC 3023 [RFC3023], section 6.
> 
> Macintosh file type code(s):
>   "TEXT"
> 
> Person & email address to contact for further information:
>   public-powderwg@w3.org
> 
> Intended usage:
>   COMMON
> 
> Restrictions on usage:
>   None
> 
> Author/Change controller:
>   The POWDER-S specification is a work product of the World Wide Web
>   Consortium's Protocol for Web Description Resources (POWDER) Working
>   Group. The W3C has change control over these specifications.
> 
> Please advise if there is any missing or incorrect information in this 
> request.
> 
> Yours faithfully
> 
> Phil Archer
> POWDER WG Chair.
> 
> 
> [1] http://www.w3.org/2002/06/registering-mediatype
> [2] http://lists.w3.org/Archives/Public/public-powderwg/2008Dec/0001.html
> [3] http://lists.w3.org/Archives/Public/public-powderwg/2008Dec/0002.html
> [4] For example 
> http://lists.w3.org/Archives/Public/public-powderwg/2008Dec/0026.html 
> and http://lists.w3.org/Archives/Public/public-powderwg/2008Dec/0012.html
> [5] http://www.w3.org/2007/powder/Group/powder-dr/20081205.html
> 
> 
> 

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