headers
Felix Sasaki | 6 Dec 2006 07:12
Picon
Favicon

Request for comments on Media Type section of "Web Services Policy 1.5 - Framework" W3C Working Draft

Hello,

this is a request for comments on the Media Type section of the "Web
Services Policy 1.5 - Framework" W3C Last Call Working Draft. The
section is at
http://www.w3.org/TR/2006/WD-ws-policy-20061117/#media-type and as plain
text below.

Thank you very much. Regards,

Felix Sasaki

A. The application/wspolicy+xml Media Type
This appendix defines the "application/wspolicy+xml" media type which
can be used to describe Web Services Policy documents serialized as XML.
Either wsp:Policy or wsp:PolicyAttachment could be the root element of
such a document.

A.1 Registration
MIME media type name:

        application

MIME subtype name:

        wspolicy+xml

Required parameters:

        none
(Continue reading)

Permalink | Reply | 6 comments |
headers
Mark Baker | 6 Dec 2006 14:22
Picon
Favicon
Gravatar

Re: Request for comments on Media Type section of "Web Services Policy 1.5 - Framework" W3C Working Draft

Felix,

Other than the Mac file type code - which, AIUI, should be "TEXT" - it
looks good to me.

You might also want to explicitly state that you're following the
alternate media type registration procedure; not in the template
necessarily (though I suppose that would be ok too), but just in this
discussion so that potential reviewers aren't surprised.

Mark.

On 12/6/06, Felix Sasaki <fsasaki <at> w3.org> wrote:
> Hello,
>
> this is a request for comments on the Media Type section of the "Web
> Services Policy 1.5 - Framework" W3C Last Call Working Draft. The
> section is at
> http://www.w3.org/TR/2006/WD-ws-policy-20061117/#media-type and as plain
> text below.
>
> Thank you very much. Regards,
>
> Felix Sasaki
>
>
> A. The application/wspolicy+xml Media Type
> This appendix defines the "application/wspolicy+xml" media type which
> can be used to describe Web Services Policy documents serialized as XML.
> Either wsp:Policy or wsp:PolicyAttachment could be the root element of
(Continue reading)

Permalink | Reply | 2 comments |
headers
Felix Sasaki | 6 Dec 2006 17:57
Picon
Favicon

Re: Request for comments on Media Type section of "Web Services Policy 1.5 - Framework" W3C Working Draft

Thank you for looking at this and catching the error, Mark. We will fix
that in the draft and send the new version to this list soon.

On Wed, 2006-12-06 at 08:22 -0500, Mark Baker wrote:
> Felix,
> 
> Other than the Mac file type code - which, AIUI, should be "TEXT" - it
> looks good to me.
> 
> You might also want to explicitly state that you're following the
> alternate media type registration procedure; not in the template
> necessarily (though I suppose that would be ok too), but just in this
> discussion so that potential reviewers aren't surprised.

Thank you again for mentioning that. I hereby state that we are
following that alternate registration procedure described at
http://www.w3.org/2002/06/registering-mediatype "
1. New Procedure: Registration template in spec, no RFC".

Felix

> 
> Mark.
> 
> On 12/6/06, Felix Sasaki <fsasaki <at> w3.org> wrote:
> > Hello,
> >
> > this is a request for comments on the Media Type section of the "Web
> > Services Policy 1.5 - Framework" W3C Last Call Working Draft. The
> > section is at
(Continue reading)

Permalink | Reply | 1 comment |
headers
Magnus Westerlund | 14 Dec 2006 15:17
Picon
Favicon

Request for review update of media types audio/3gpp and video/3gpp

Hi,

The two media types audio/3gpp and video/3gpp was defined in RFC 3839:
ftp://ftp.rfc-editor.org/in-notes/rfc3839.txt

With the publication of the codecs parameters in RFC 4281
(ftp://ftp.rfc-editor.org/in-notes/rfc4281.txt) these two media types 
should be updated to include this parameter. This 3GPP defined file 
format has also got a few more features, one include the capability of 
embedding other binary objects to be used in scene presentations created 
by SMIL or SVG to achieve self contained units. Due to this the RFC 
authors and 3GPP document editor has also proposed to add another 
parameter similar to codecs that identifies the type of binary objects 
embedded in the file.

When performing this update it is also intended to move the Media Type 
definitions from the RFC into the file format specification document in 
3GPP. The current file format specification is 3GPP TS 26.244:
http://www.3gpp.org/ftp/Specs/archive/26_series/26.244/26244-700.zip

So please review the following document containing the proposed Media 
Types.
http://www.denstore.se/IETF/3GP-mime-reg.pdf

We appreciate comments by Monday the 8th of January.

Cheers

Magnus Westerlund
(Continue reading)

Permalink | Reply | 1 comment |
headers
Felix Sasaki | 19 Dec 2006 06:53
Picon
Favicon

Re: Request for comments on Media Type section of "Web Services Policy 1.5 - Framework" W3C Working Draft

Hello Mark, all,

The Web Services Policy Working Group decided to make a change to the
Media Type section of "Web Services	Policy 1.5 - Framework" W3C Working
Draft, see the start of this thread for the initial request.

The change is related to the description of the base URI.

Old text:
[[Base URI:
As specified in RFC 3023, section 6.]]

New text:
[[Base URI:
As specified in IETF RFC 3023, section 6. Also see section 4.6 Use of
IRIs in Policy Expressions in this document and section 3.5 Use of IRIs
in Policy Attachment in the Web Services Policy 1.5 - Attachment.]]

The link for section 4.6 in the editors copy of the document is
http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;charset=utf-8#IRI_Policy_Expressions

The link for section 3.5 in the editors copy of the document is
http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-attachment.html?content-type=text/html;charset=utf-8#IRI_Policy_Attachment

The complete revised version of the Media Type section is below.

A. The application/wspolicy+xml Media Type

This appendix defines the "application/wspolicy+xml" media type which
can be used to describe Web Services Policy documents serialized as XML.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane