Re: Media Type Request for comments: WS-CDL 1.0
Martin Duerst <duerst@it.aoyama.ac.jp> Fri, 18 November 2005 10:34 UTC
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id jAIAYBYa083183; Fri, 18 Nov 2005 02:34:11 -0800 (PST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id jAIAYBTq083182; Fri, 18 Nov 2005 02:34:11 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from scmailgw1.scop.aoyama.ac.jp (scmailgw1.scop.aoyama.ac.jp [133.2.251.194]) by above.proper.com (8.12.11/8.12.9) with ESMTP id jAIAY9CL083154 for <ietf-xml-mime@imc.org>; Fri, 18 Nov 2005 02:34:10 -0800 (PST) (envelope-from duerst@it.aoyama.ac.jp)
Received: from scmse1.scbb.aoyama.ac.jp (scmse1 [133.2.253.16]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id jAIAXsu25600; Fri, 18 Nov 2005 19:33:54 +0900 (JST)
Received: from (133.2.210.1) by scmse1.scbb.aoyama.ac.jp via smtp id 1174_d1662474_581e_11da_9324_0030482533a1; Fri, 18 Nov 2005 19:33:53 +0900
Received: from EBOSHIIWA.it.aoyama.ac.jp (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.13.1/8.13.1) with ESMTP id jAIAVKJv008769; Fri, 18 Nov 2005 19:33:04 +0900
Message-Id: <6.0.0.20.2.20051118174702.07983df0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Fri, 18 Nov 2005 17:54:52 +0900
To: Yves Lafon <ylafon@w3.org>, ietf-types@iana.org, ietf-xml-mime@imc.org
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: Media Type Request for comments: WS-CDL 1.0
In-Reply-To: <Pine.GSO.4.63.0511151627070.13927@gnenaghyn.vaevn.se>
References: <Pine.GSO.4.63.0511151627070.13927@gnenaghyn.vaevn.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format="flowed"
Content-Transfer-Encoding: 7bit
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>
Hello Yves, Some comments below. At 00:35 05/11/16, Yves Lafon wrote: >[ > Notes: > > We slipped up in not sending this along with the Last Call > announcement; please accept our apologies. > > Comments on the MIME-related part of the document may be made > on the ietf-types mailing list or in the > public-ws-chor-comments@w3.org mailing list.. See the > "Status of this Document" section for further information. > > We are following > http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-05.txt > here, and the text is written to be part of a larger document. > > Finally, as WS-CDL is a description format and not something directly > executable, the Working Group didn't identify any need for a > specific security section. You need a security section, even just to describe why you think there are no security issues, and to document that you actually thought this through. >] >The current specification is at: > http://www.w3.org/TR/2005/CR-ws-cdl-10-20051109/ > >The MIME Type template at > http://www.w3.org/TR/ws-cdl-10/#Mime-Type-definition That's good info, but it needs to be *inside* the registration template. That may make the registration template in the spec look a bit weird (explicitly referring to the document itself in textual form inside the document), but is absolutely necessary to allow the template to be taken out and stand on its own. >One typo already spotted, in the Author/Change controller, http://www.w3.org/2002/ws/chor/ should be a link with a text value of "Web Services Choreography Working Group". >Thanks, > >Registration of MIME Media Type application/cdl+xml >--------------------------------------------------- >MIME media type name: > > application Whatever kind of formatting you use, please make sure that the empty line comes between the field value and the next field name, not between the field name and the associated value. >MIME subtype name: > > cdl+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 RFC 3023 [RFC 3023]. > >Encoding considerations: > > Identical to those of "application/xml" as described in RFC 3023 [RFC 3023], section 3.2. >Security considerations: > > WS-CDL has the same security considerations described in RFC3023 [RFC 3023], section 10. >Interoperability considerations: > > There are no known interoperability issues. >Published specification: > > This document This is where you have to provide full and explicit information, both the title and the URI of the document. Providing the title Providing the title of the document will also help people understand what CDL stands for. Regards, Martin. >Applications which use this media type: > > No known applications currently use this media type. >Additional information: > > File extension: > > CDL > Fragment identifiers: > > Identical to that of "application/xml" as described in RFC 3023 [RFC 3023], section 5. > Base URI: > > As specified in RFC 3023 [RFC 3023], section 6. > Macintosh File Type code: > > TEXT > >Person and email address to contact for further information: > > Yves Lafon <ylafon@w3.org> >Intended usage: > > COMMON >Author/Change controller: > > The WS-CDL 1.0 specification is a work product of the World Wide Web Consortium's http://www.w3.org/2002/ws/chor/. The W3C has change control over this specification. > >-------------------------------------------------------------- > > > >-- >Yves Lafon - W3C >"Baroula que barouleras, au ti騏 toujou t'entourneras."
- Re: Media Type Request for comments: WS-CDL 1.0 Martin Duerst