Re: Thank you!

Re: Hi

Incoming message

Forum notify

Re: Yahoo!

Notification

Site changes

Submission of the application/soap_xop+xml Media Mype

All,
The media type is defined in the W3C Last Call Working Draft of
"SOAP Message Transmission Optimization Mechanism" [1]
Below is a full text version for convenience. [2]
Please direct comments to xmlp-comments <at> w3.org.
Best regards,

[1] http://www.w3.org/TR/soap12-mtom/#media_type
[2]
A The application/soap_xop+xml Media Type
A.1 Introduction

SOAP version 1.2 ([SOAP Part 1] and [SOAP Part 2]) is a lightweight 
protocol intended for exchange of structured information between peers in 
a decentralized, distributed environment. It defines an extensible 
messaging framework that contains a message construct based on XML 
technologies that can be exchanged over a variety of underlying protocols.

The XML-binary Optimized Packaging Mechanism [XOP] is an alternate 
serialization of the XML Infoset, intended to make processing and 
representation of certain types of content (specifically, that which is 
base64-encoded) more efficient. Such serializations, when free-standing, 
are called XOP Packages; the portion of the XOP Package that represents 
the structure and non-optimized content of the Infoset are called XOP 
Documents, and are serialized as XML.

This appendix defines the media type application/soap_xop+xml which can be 
used to identify SOAP 1.2 message envelopes that have been serialized as 
XOP Documents using XML 1.0 ([XML 1.0]).

The application/soap_xop+xml media type explicitly identifies the XOP 
Document portion of a SOAP 1.2 message envelope, serialized as XML 1.0. In 
other words, it identifies the serialized XML after the extraction of any 
content into the XOP Package; it does not identify the package itself.

XOP Documents not serialized as XML 1.0 or representing message envelopes 
with a different SOAP namespace version MUST NOT use it.
A.2 Registration

     *

       MIME media type name:

       application.
     *

       MIME subtype name:

       soap_xop+xml
     *

       Required parameters:

       none
     *

       Optional parameters:
           o

             "charset":

             This parameter has identical semantics to the charset 
parameter of the application/xml media type as specified in RFC 3023 [RFC 
3023].
           o

             "action":

             This optional parameter can be used to specify the URI that 
identifies the intent of the message. In SOAP 1.2, it serves a similar 
purpose as the SOAPAction HTTP header field did in SOAP 1.1. Namely, its 
value identifies the intent of the message.

             The value of the action parameter is an absolute URI-reference 
as defined by RFC 2396 [RFC 2396]. SOAP places no restrictions on the 
specificity of the URI or that it is resolvable. Although the purpose of 
the action parameter is to indicate the intent of the SOAP message there 
is no mechanism for automatically computing the value based on the SOAP 
envelope. In other words, the value has to be determined out of band.

             It is recommended that the same value be used to identify sets 
of message types that are logically connected in some manner, for example 
part of the same "service". It is strongly RECOMMENDED that the URI be 
globally unique and stable over time.

             The presence and content of the action parameter MAY be used 
by servers such as firewalls to appropriately filter SOAP messages and it 
may be used by servers to facilitate dispatching of SOAP messages to 
internal message handlers etc. It SHOULD NOT be used as an insecure form 
of access authorization. Use of the action parameter is OPTIONAL. SOAP 
Receivers MAY use it as a hint to optimize processing, but SHOULD NOT 
require its presence in order to operate.
     *

       Encoding considerations:

       Identical to those of application/xml as described in RFC 3023 [RFC 
3023], section 3.2, as applied to the SOAP envelope Infoset.
     *

       Security considerations:

       Because SOAP can carry application defined data whose semantics is 
independent from that of any MIME wrapper (or context within which the 
MIME wrapper is used), one should not expect to be able to understand the 
semantics of the SOAP message based on the semantics of the MIME wrapper 
alone. Therefore, whenever using the application/soap_xop+xml media type, 
it is strongly RECOMMENDED that the security implications of the context 
within which the SOAP message is used is fully understood. The security 
implications are likely to involve both the specific SOAP binding to an 
underlying protocol as well as the application-defined semantics of the 
data carried in the SOAP message (though one must be careful when doing 
this, as discussed in SOAP 1.2 Part 1 [SOAP Part 1], 7.3.1 Binding to 
Application-Specific Protocols.

       Also, see SOAP 1.2 Part 1 [SOAP Part 1], 7. Security Considerations.

       In addition, as this media type uses the "+xml" convention, it 
shares the same security considerations as described in RFC 3023 [RFC 
3023], section 10.
     *

       Interoperability considerations:

       There are no known interoperability issues.
     *

       Published specification:

       SOAP 1.2 Part 1 [SOAP Part 1], SOAP 1.2 Part 2, [SOAP Part 2], and 
XOP [XOP].
     *

       Applications which use this media type:

       No known applications currently use this media type.
     *

       Additional information:
           o

             File extension:

             SOAP messages are not required or expected to be stored as 
files.
           o

             Fragment identifiers:

             Identical to that of application/xml as described in RFC 3023 
[RFC 3023], section 5.
           o

             Base URI:

             As specified in RFC 3023 [RFC 3023], section 6. Also see SOAP 
1.2 Part 1 [SOAP Part 1], 6. Use of URIs in SOAP.
           o

             Macintosh File Type code:

             TEXT
     *

       Person and email address to contact for further information:

       Mark Nottingham <mnot <at> pobox.com>
     *

       Intended usage:

       COMMON
     *

       Author/Change controller:

       The SOAP 1.2 specification set is a work product of the World Wide 
Web Consortium's XML Protocol Working Group. The W3C has change control 
over these specifications.

--

-- 
Yves Lafon - W3C
"Baroula que barouleras, au tiéu toujou t'entourneras."

Request for comments for Media Type registration of application/ccxml+xml

*This message was transferred with a trial version of CommuniGate(tm) Pro*

This is a request for comments on the registration of the
application/ccxml+xml mime type. The request is published as part of the
CCXML 1.0 specification and is copied below. The url of the request is:

    http://www.w3.org/TR/ccxml/#ccxml-mime-definition

Please send any comments on this request to rj <at> voxeo.com

Thanks,

    RJ

Appendix I - CCXML Media Type

This appendix registers a new MIME media type, "application/ccxml+xml".

I.1 Registration of MIME media type application/ccxml+xml
MIME media type name:

application
MIME subtype name:

ccxml+xml
Required parameters:

None.
Optional parameters:
charset

This parameter has identical semantics to the charset parameter of the
application/xml media type as specified in [RFC3023].
Encoding considerations:

By virtue of CCXML content being XML, it has the same considerations when
sent as "application/ccxml+xml" as does XML. See RFC 3023, section 3.2.
Security considerations:

Several CCXML instructions may cause arbitrary URIs to be referenced. In
this case, the security issues of RFC1738, section 6, should be considered.

In addition, because of the extensibility features for CCXML, it is possible
that "application/ccxml+xml" may describe content that has security
implications beyond those described here. However, if the processor follows
only the normative semantics of this specification, this content will be
ignored. Only in the case where the processor recognizes and processes the
additional content, or where further processing of that content is
dispatched to other processors, would security issues potentially arise. And
in that case, they would fall outside the domain of this registration
document.
Interoperability considerations:

This specification describes processing semantics that dictate behavior that
must be followed when dealing with, among other things, unrecognized
elements.

Because CCXML is extensible, conferment "application/ccxml+xml" processors
can expect that content received is well-formed XML, but it cannot be
guaranteed that the content is valid CCXML or that the processor will
recognize all of the elements and attributes in the document.
Published specification:

This media type registration is for CCXML documents as described by this
specification.
Additional information:
Magic number(s):

There is no single initial octet sequence that is always present in CCXML
documents.
File extension(s):

CCXML documents are most often identified with the extensions ".ccxml".
Macintosh File Type Code(s):

TEXT
Person & email address to contact for further information:

RJ Auburn, <rj <at> voxeo.com>.
Intended usage:

COMMON
Author/Change controller:

The CCXML specification is a work product of the World Wide Web Consortium's
Voice Browser Working Group. The W3C has change control over these
specifications.

Submission: "The 'application/ssml+xml' Media Type" : ietf-xml-mime

Resending through spamtrap

From: Paul Hoffman / IMC <phoffman <at> imc.org>
Subject: Re: Submission: "The 'application/ssml+xml' Media Type" : ietf-xml-mime
Date: 2004-07-17 18:23:14 GMT

>  >From owner-ietf-xml-mime Mon Jul 12 04:35:35 2004
>Received: from homer.w3.org (homer.w3.org [18.29.0.30])
>	by above.proper.com (8.12.11/8.12.9) with ESMTP id i6CBZ54p013996
>	for <ietf-xml-mime <at> imc.org>; Mon, 12 Jul 2004 04:35:35 -0700 (PDT)
>	(envelope-from mf <at> w3.org)
>Received: from jetlag (homer.w3.org [18.29.0.30])
>	by homer.w3.org (Postfix) with ESMTP id 90C1C4F16F;
>	Mon, 12 Jul 2004 07:35:05 -0400 (EDT)
>To: internet-drafts <at> ietf.org
>Cc: ietf-xml-mime <at> imc.org, martin <at> w3.org, w3t-archive <at> w3.org
>Subject: Submission: "The 'application/ssml+xml' Media Type"Sender: 
>Max Froumentin <mf <at> w3.org>
>From: Max Froumentin <mf <at> w3.org>
>Organization: W3C
>Date: Mon, 12 Jul 2004 13:35:10 +0200
>Message-ID: <87hdsda26p.fsf <at> w3.org>
>User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux)
>MIME-Version: 1.0
>Content-Type: multipart/mixed; boundary="=-=-="
>
>--=-=-=
>
>Dear editor,
>
>Please find below the updated submission for a media type registation
>"ssml+xml". This document updates an expired submission at [2].
>
>The document was earlier sent to ietf-types [1] and was revised for
>this submission.
>
>
>[1] 
>http://eikenes.alvestrand.no/pipermail/ietf-types/2003-December/000134.html
>[2] http://www.mail-archive.com/all-ietf <at> loki.ietf.org/msg12940.html
>
>Max Froumentin
>W3C
>
>
>--=-=-=
>Content-Disposition: attachment;
>   filename=draft-froumentin-ssml-media-reg.txt
>
>
>
>Network Working Group                                      M. Froumentin
>Internet-Draft                                             July 12, 2004
>Expires: January 10, 2005
>
>
>                  The 'application/ssml+xml' Media Type
>                  draft-froumentin-ssml-media-reg-01.txt
>
>Status of this Memo
>
>    This document is an Internet-Draft and is in full conformance with
>    all provisions of Section 10 of RFC2026.
>
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as
>    Internet-Drafts.
>
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
>
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
>
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
>
>    This Internet-Draft will expire on January 10, 2005.
>
>Copyright Notice
>
>    Copyright (C) The Internet Society (2004).  All Rights Reserved.
>
>Abstract
>
>    This document defines the 'application/ssml+xml' media type for the
>    Speech Synthesis based markup language.
>
>
>
>
>
>
>
>
>
>
>
>
>
>Froumentin              Expires January 10, 2005                [Page 1]
>
>Internet-Draft    The 'application/ssml+xml' Media Type        July 2004
>
>
>Table of Contents
>
>    1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
>    2.   Registration of MIME media type application/ssml+xml . . . . . 4
>      2.1  MIME media type name . . . . . . . . . . . . . . . . . . . . 4
>      2.2  MIME subtype name  . . . . . . . . . . . . . . . . . . . . . 4
>      2.3  Required parameters  . . . . . . . . . . . . . . . . . . . . 4
>      2.4  Optional parameters  . . . . . . . . . . . . . . . . . . . . 4
>        2.4.1  charset  . . . . . . . . . . . . . . . . . . . . . . . . 4
>      2.5  Encoding considerations  . . . . . . . . . . . . . . . . . . 4
>      2.6  Fragment identifiers . . . . . . . . . . . . . . . . . . . . 4
>      2.7  Security Considerations  . . . . . . . . . . . . . . . . . . 4
>      2.8  Interoperability considerations  . . . . . . . . . . . . . . 5
>      2.9  Published specification  . . . . . . . . . . . . . . . . . . 5
>      2.10   Applications which use this media type . . . . . . . . . . 5
>      2.11   Additional information . . . . . . . . . . . . . . . . . . 5
>        2.11.1   Magic number(s)  . . . . . . . . . . . . . . . . . . . 5
>        2.11.2   File extension(s)  . . . . . . . . . . . . . . . . . . 5
>        2.11.3   Macintosh File Type Code(s)  . . . . . . . . . . . . . 5
>      2.12   Person & email address to contact for further
>             information  . . . . . . . . . . . . . . . . . . . . . . . 5
>      2.13   Intended usage . . . . . . . . . . . . . . . . . . . . . . 5
>      2.14   Author/Change controller . . . . . . . . . . . . . . . . . 5
>    3.   References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
>         Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6
>         Intellectual Property and Copyright Statements . . . . . . . . 7
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Froumentin              Expires January 10, 2005                [Page 2]
>
>Internet-Draft    The 'application/ssml+xml' Media Type        July 2004
>
>
>1.  Introduction
>
>    Speech Synthesis Markup Language is an XML based markup language for
>    assisting the generation of synthetic speech in web and other
>    applications.  The essential role of the markup language is to give
>    authors of synthesizable content a standard way to control aspects of
>    speech output such as pronunciation, volume, pitch, rate and etc.
>    across different synthesis-capable platforms.
>
>    Feedback or discussion about this draft should be directed to the
>    Voice Browser Working Group public mailing list, www-voice <at> w3.org
>    with archives at http://lists.w3.org/Archives/Public/www-voice/.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Froumentin              Expires January 10, 2005                [Page 3]
>
>Internet-Draft    The 'application/ssml+xml' Media Type        July 2004
>
>
>2.  Registration of MIME media type application/ssml+xml
>
>2.1  MIME media type name
>
>    application
>
>2.2  MIME subtype name
>
>    ssml+xml
>
>2.3  Required parameters
>
>    None.
>
>2.4  Optional parameters
>
>2.4.1  charset
>
>    This parameter has identical semantics to the charset parameter of
>    the application/xml media type as specified in [RFC3023].
>
>2.5  Encoding considerations
>
>    By virtue of SSML content being XML, it has the same considerations
>    when sent as "application/ssml+xml" as does XML.  See [RFC3023],
>    section 3.2.
>
>2.6  Fragment identifiers
>
>    For documents labeled as 'application/ssml+xml', the fragment
>    identifier notation is exactly that for application/xml, as specified
>    in [RFC3023].
>
>2.7  Security Considerations
>
>    Several SSML instructions may cause arbitrary URIs to be
>    dereferenced.  In this case, the security issues of [RFC1738],
>    section 6, should be considered.
>
>    In addition, because of the extensibility features of SSML, it is
>    possible that "application/ssml+xml" may describe content that has
>    security implications beyond those described here.  However, if the
>    processor follows only the normative semantics of this specification,
>    this content will be ignored.  Only in the case where the processor
>    recognizes and processes the additional content, or where further
>    processing of that content is dispatched to other processors, would
>    security issues potentially arise.  And in that case, they would fall
>    outside the domain of this registration document.
>
>
>
>Froumentin              Expires January 10, 2005                [Page 4]
>
>Internet-Draft    The 'application/ssml+xml' Media Type        July 2004
>
>
>2.8  Interoperability considerations
>
>    Because SSML is extensible, conformant "application/ssml+xml"
>    processors can expect that content received is well-formed XML, but
>    it cannot be guaranteed that the content is valid SSML or that the
>    processor will recognize all of the elements and attributes in the
>    document.
>
>2.9  Published specification
>
>    This media type registration is for SSML documents as described by
>    the W3C SSML specification at [SSML].
>
>2.10  Applications which use this media type
>
>    There is no experimental, vendor specific, or personal tree
>    predecessor to "application/ssml+xml", reflecting the fact that no
>    applications currently recognize it.  This new type is being
>    registered in order to allow for the expected deployment of SSML on
>    the World Wide Web, as a first class XML application.
>
>2.11  Additional information
>
>2.11.1  Magic number(s)
>
>    There is no single initial octet sequence that is always present in
>    SSML documents.  See [RFC3023] for information pertaining to the
>    identification of XML media types.
>
>2.11.2  File extension(s)
>
>    SSML documents are most often identified with the extensions ".ssml".
>
>2.11.3  Macintosh File Type Code(s)
>
>    TEXT
>
>2.12  Person & email address to contact for further information
>
>    Max Froumentin, <mf <at> w3.org>
>
>2.13  Intended usage
>
>    COMMON
>
>2.14  Author/Change controller
>
>    The SSML specification is a work product of the World Wide Web
>
>
>
>Froumentin              Expires January 10, 2005                [Page 5]
>
>Internet-Draft    The 'application/ssml+xml' Media Type        July 2004
>
>
>    Consortium's Voice Browser Working Group.  The W3C has change control
>    over these specifications.
>
>3  References
>
>    [RFC1738]  Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform
>               Resource Locators (URL)", RFC 1738, December 1994.
>
>    [RFC3023]  Murata, M., St. Laurent, S. and D. Kohn, "XML Media
>               Types", RFC 3023, January 2001.
>
>    [SSML]     Burnett, D., Walker, M. and A. Hunt, "Speech Synthesis
>               Markup Language Version 1.0 Candidate Recommendation",
>               December 2003.
>
>
>Author's Address
>
>    Max Froumentin
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Froumentin              Expires January 10, 2005                [Page 6]
>
>Internet-Draft    The 'application/ssml+xml' Media Type        July 2004
>
>
>Intellectual Property Statement
>
>    The IETF takes no position regarding the validity or scope of any
>    intellectual property or other rights that might be claimed to
>    pertain to the implementation or use of the technology described in
>    this document or the extent to which any license under such rights
>    might or might not be available; neither does it represent that it
>    has made any effort to identify any such rights.  Information on the
>    IETF's procedures with respect to rights in standards-track and
>    standards-related documentation can be found in BCP-11.  Copies of
>    claims of rights made available for publication and any assurances of
>    licenses to be made available, or the result of an attempt made to
>    obtain a general license or permission for the use of such
>    proprietary rights by implementors or users of this specification can
>    be obtained from the IETF Secretariat.
>
>    The IETF invites any interested party to bring to its attention any
>    copyrights, patents or patent applications, or other proprietary
>    rights which may cover technology that may be required to practice
>    this standard.  Please address the information to the IETF Executive
>    Director.
>
>
>Full Copyright Statement
>
>    Copyright (C) The Internet Society (2004).  All Rights Reserved.
>
>    This document and translations of it may be copied and furnished to
>    others, and derivative works that comment on or otherwise explain it
>    or assist in its implementation may be prepared, copied, published
>    and distributed, in whole or in part, without restriction of any
>    kind, provided that the above copyright notice and this paragraph are
>    included on all such copies and derivative works.  However, this
>    document itself may not be modified in any way, such as by removing
>    the copyright notice or references to the Internet Society or other
>    Internet organizations, except as needed for the purpose of
>    developing Internet standards in which case the procedures for
>    copyrights defined in the Internet Standards process must be
>    followed, or as required to translate it into languages other than
>    English.
>
>    The limited permissions granted above are perpetual and will not be
>    revoked by the Internet Society or its successors or assignees.
>
>    This document and the information contained herein is provided on an
>    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
>    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
>    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
>
>
>
>Froumentin              Expires January 10, 2005                [Page 7]
>
>Internet-Draft    The 'application/ssml+xml' Media Type        July 2004
>
>
>    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
>    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>
>
>Acknowledgment
>
>    Funding for the RFC Editor function is currently provided by the
>    Internet Society.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Froumentin              Expires January 10, 2005                [Page 8]
>
>
>--=-=-=--

The message above was not sent to the mailing list because, as an anti-spam
measure, the list software prevents people whose exact address is not on any
mailing list we run from posting to lists. I have now permanently added the
above address to the "OK to post" list. Please send your message to the list
again.