W3C home > Mailing lists > Public > public-powderwg@w3.org > December 2008

Re: Re: Request for two new media types submitted

From: Eric Prud'hommeaux <eric@w3.org>
Date: Tue, 2 Dec 2008 17:27:38 -0500
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: Phil Archer <phil@philarcher.org>, ietf-types@iana.org, Public POWDER <public-powderwg@w3.org>
Message-ID: <20081202222738.GG4209@w3.org>
* Bjoern Hoehrmann <derhoermi@gmx.net> [2008-12-02 18:36+0100]
> * Phil Archer wrote:
> >On behalf of the W3C POWDER Working Group I have have today submitted 
> >two registration requests for Media Types. As cited in those requests, 
> >the key documentation is section 4 of Protocol for Web Description 
> >Resources (POWDER): Description Resources [1]. Although this is formally 
> >published as a working draft, we are close to reaching our Candidate 
> >Recommendation exit criteria and therefore expect to seek transition to 
> >Proposed Recommendation later this month.
> >[1] http://www.w3.org/TR/powder-dr/#assoc
> As per RFC 4288
>    As stated previously, standards tree registrations for media types
>    defined in documents produced by other standards bodies MUST be
>    described by a formal standards specification produced by that body.
>    Such specifications MUST contain an appropriate media type
>    registration template taken from Section 10.
> I could not find such a template in the document. Also, given that
> some http://www.w3.org/TR/webarch/#xml-media-types in the W3C think
>   In general, a representation provider SHOULD NOT assign Internet
>   media types beginning with "text/" to XML representations.
> A registration request for text/powder+xml from the W3C should not
> come without some form of justification for this choice.

Phil, meet Bjoern. Bjoern is lint for W3C and IETF specs.

I propose that POWDER register application/powder+xml for POWDER, and
use application/rdf+xml for POWDER-S.

I think it's handy to include the media type registration in the spec,
à al http://www.w3.org/TR/rdf-sparql-query/#mediaType .

Following http://www.w3.org/2002/06/registering-mediatype , and
assuming you have no preference above being good netizens, I have
created a template for both (powder+xml and powder-s+xml) with
, i.e. using application/ instead of text/:

Type name:

Subtype name:

Required parameters:

Optional parameters:
  "charset": This parameter has identical semantics to the charset
             parameter of the "application/xml" media type as
             specified in [RFC3023], section 3.2.

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 [RFC3986]) and IRIs (Section 8 of [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:

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 [RFC3023], section 3.2.

File extension(s):

Fragment identifiers:
  Identical to that of "application/xml" as described in RFC 3023
  [RFC3023], section 5.

Base URI:
  As specified in [RFC3023], section 6.

Macintosh file type code(s):

Person & email address to contact for further information:
  Phil Archer <public-powderwg@w3.org>

Intended usage:

Restrictions on usage:

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.


[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types",
          RFC 3023, January 2001.

[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
          Resource Identifier (URI): Generic Syntax", STD 66, RFC
          3986, January 2005.

[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource
          Identifiers (IRIs)", RFC 3987, January 2005.


office: +1.617.258.5741 32-G528, MIT, Cambridge, MA 02144 USA
mobile: +1.617.599.3509

Feel free to forward this message to any list for any purpose other than
email address distribution.

Received on Tuesday, 2 December 2008 22:28:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:06:04 UTC