June 2006 - Ietf-types - alvestrand.no

Preliminary Community Review: text/json
by Douglas Crockford 15 Apr '07

15 Apr '07

This is notice of a potential media type registration. The details may be found here: http://www.ietf.org/internet-drafts/draft-crockford-jsonorg-json-02.txt

10 11

Request for review of 9 MIME type for 3GPP SA4
by Magnus Westerlund 29 Mar '07

29 Mar '07

Hi, attached is a word document with a proposal for 9 MIME type that will go into the 3GPP Technical Specification 26.346 and when present in that be requested to registered. Most of these media types are for XML formats, although not all of them. Please review them, comments received within a week can be directly addressed at the 3GPP SA4 meeting. TS 26.346 can in its latest form be fetched here: http://www.3gpp.org/ftp/Specs/archive/26_series/26.346/26346-610.zip However some of the references in the chapter relate to text that are being specified and added. They are available in the following document: http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/TSGS4_36/Docs/S4-050514.zip Thanks Magnus Westerlund Multimedia Technologies, Ericsson Research EAB/TVA/A ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund(a)ericsson.com

3 8

W3C Last Call and Media Type request for comments: XQuery and XQueryX
by Liam Quin 18 Jan '07

18 Jan '07

[ Notes: (1) - I'm trying to follow a new procedure here. Becasue not everything is in place, the documents I refer to probably don't have perfect wording. The documentation on the process was released after the documents were frozen for Last Call, but we can make any needed changes for the next round of publication. I see that we failed to define the correct syntax for parameters, and would welcome comments on any other areas wheer we need to improve. (2) The following text will be inserted in the next published versions of the documents: This registration is for community review and will be (or has been) submitted to the IESG for review, approval, and registration with IANA. (3) We are using Bugzilla to track comments on these documents; comments on these MIME-related pats of the documents may be made on the ietf-types mailing list or in Bugzilla. See the individual documents and their respective "Status of this Document" sections for further information. - Liam ] In accordance with the draft Media Type Specifications and Registration Procedures [1], and on behalf of the W3C XML Query Working Group [2], I hereby give notice that W3C has published two specifications at the stage "Last Call Working Draft" which each incorporate definitions of a standards-tree MIME media type, as allowed for in section 3.1 of [1], and request comments on these definitions. The types and subtypes are application/xquery defined in "XQuery 1.0: An XML Query Language" [3] optional parameter: charset application/xquery+xml defined in "XML Syntax for XQuery 1.0 (XQueryX)" [4] optional parameter: charset **** Registration for application/xquery also at [3] I The application/xquery Media Type (Non-Normative) --------------------------------------------------- This Appendix specifies the media type for XQuery Version 1.0. XQuery is a language for querying over collections of data from XML data sources, as specified in the main body of this document. I.1 Introduction ---------------- This document, together with its normative references, defines the language XQuery Version 1.0. This Appendix provides information about the application/xquery media type, which is intended to be used for transmitting queries written in the XQuery language. This document was prepared by members of the W3C XML Query Working Group. Please send comments to public-qt-comments [at] w3.org, a public mailing list with archives at http://lists.w3.org/Archives/Public/public-qt-comments. I.2 Registration of MIME Media Type application/xquery ------------------------------------------------------ MIME media type name: application MIME subtype name: xquery Required parameters: none Optional parameters: charset The syntax of XQuery is expressed in Unicode but may be written with any Unicode-compatible character encoding, including UTF-8 or UTF-16, or transported as US-ASCII or Latin-1 with Unicode characters outside the range of the given encoding represented using an XML-style ෝ syntax. I.2.1 Interoperability Considerations None known. I.2.2 Applications Using this Media Type The public XQuery Web page lists more than two dozen implementations of the XQuery language, both proprietary and open source. This new media type is being registered to allow for deployment of XQuery on the World Wide Web. I.2.3 File Extensions The most common file extensions in use for XQuery are .xq and .xquery. The appropriate Macintosh file type code is TEXT. I.2.4 Intended Usage The intended usage of this media type is for interchange of XQuery expressions. I.2.5 Author/Change Controller XQuery was produced by, and is maintained by, the World Wide Web Consortium's XML Query Working Group. The W3C has change control over this specification. I.3 Encoding Considerations For use with transports that are not 8-bit clean, quoted-printable encoding is recommended since the XQuery syntax itself uses the US-ASCII-compatible subset of Unicode. An XQuery document may contain an encoding declaration as part of its version declaration: xquery version "1.0" encoding "utf-8"; If an XQuery document contains an encoding declaration, it overrides the default encoding specified by the MIME charset parameter. I.4 Recognizing XQuery Files An XQuery file may have the string xquery version "V.V" near the beginning of the document, where "V.V" is a version number. Currently the version number, if present, must be "1.0". I.5 Charset Default Rules XQuery documents use the Unicode character set and, by default, the UTF-8 encoding. I.6 Security Considerations Queries written in XQuery may cause arbitrary URIs to be dereferenced. Therefore, the security issues of [Uniform Resource Locators (URL)] Section 6 should be considered. In addition, the contents of file: URIs can in some cases be accessed, processed and returned as results. Furthermore, because the XQuery language permits extensions, it is possible that application/xquery may describe content that has security implications beyond those described here. The XML Query Working group is working on a facility to allow XQuery expressions to be used to create and update persistent data. Untrusted queries should not be given write access to data. **** Registration for application/xquery+xml also at [4] C The application/xquery+xml Media Type (Non-Normative) ------------------------------------------------------- This Appendix specifies the media type for XQueryX Version 1.0. XQueryX is the XML syntax of a language, XQuery, for querying over data from XML data sources, as specified in [XQuery 1.0: An XML Query Language]. C.1 Introduction ---------------- This document, together with its normative references, defines the XML syntax for the XML Query language XQuery Version 1.0. This Appendix specifies the application/xquery+xml media type, which is intended to be used for transmitting queries expressed in the XQueryX syntax. This document was prepared by members of the W3C XML Query Working Group. Please send comments to public-qt-comments [at] w3.org, a public mailing list with archives at http://lists.w3.org/Archives/Public/public-qt-comments. C.2 Registration of MIME Media Type application/xquery+xml MIME media type name: application MIME subtype name: xquery+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]. C.2.1 Encoding Considerations The considerations as specified in RFC 3023 [XMLMIME] also hold for 'application/xquery+xml'. C.2.2 Fragment Identifiers For documents labeled as 'application/xquery+xml', fragment identifiers are handled as specified in RFC 3023 [XMLMIME]. C.2.3 Restrictions on usage The intended usage of this media type is for interchange of XQueryX expressions. C.2.4 Security Considerations Queries written in XQueryX may cause arbitrary URIs to be dereferenced. Therefore, the security issues of [Uniform Resource Locators (URL)] Section 6 should be considered. In addition, the contents of file: URIs can in some cases be accessed, processed and returned as results. Furthermore, because the XQuery language (and thus the XQueryX language) permits extensions, it is possible that application/xquery+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 arise. The XML Query Working group is working on a facility to allow XQuery (and thus XQueryX) expressions to be used to create and update persistent data. Untrusted queries should not be given write access to data. C.2.5 Interoperability Considerations See Section 5 ConformanceXQ. C.2.6 Applications That Use This Media Type The public XQuery Web page lists more than two dozen implementations of the XQuery language, both proprietary and open source. Some of these are known to support XQueryX. This new media type is being registered to allow for deployment of XQueryX on the World Wide Web. There is no experimental, vendor specific, or personal tree predecessor to "application/xquery+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 XQueryX 1.0 on the World Wide Web, as a first class XML application. C.2.7 Additional Information C.2.7.1 Recognizing XQuery Files ("Magic Numbers") Although no byte sequences can be counted on to consistently identify XQueryX, XQueryX documents will have the sequence "http://www.w3.org/yyyy/mm/XQueryX" to identify the XQueryX namespace (where "yyyy" is exactly four decimal digits and "mm" is exactly two decimal digits). This sequence will normally be found in a namespace attribute of the first element in the document. C.2.7.2 File Extensions The most common file extension in use for XQueryX is .xqx. C.2.7.3 Macintosh File Type Code(s) The appropriate Macintosh file type code is TEXT. C.2.8 Person and Email Address to Contact For Further Information Jim Melton, Oracle Corp., jim.melton [at] oracle.com C.2.9 Intended Usage COMMON C.2.10 Author/Change Controller XQuery was produced by, and is maintained by, the World Wide Web Consortium's XML Query Working Group. The W3C has change control over this specification. [1] http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-02.txt [2] http://www.w3.org/XML/Query [3] http://www.w3.org/TR/2005/WD-xquery-20050404/#id-mime-type [4] http://www.w3.org/TR/2005/WD-xqueryx-20050404/#xqueryx-id-mime-type -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/

8 16

Request preliminary check of 8 personal media types
by Damian Dollahite 24 Sep '06

24 Sep '06

I would like to request a preliminary check of 8 media types collected in this document: http://purl.org/int-fiction/ifmi/documents/mediatypes/ This document is not a registration form or specification, rather it is a discussion of issues that need to be addressed so that these formats can be registered. It does include examples of how the registration forms might be filled out, however. Currently, these file formats are being transferred using "x-" prefixed types; I'm fairly certain that none of the controllers are aware that the prs. tree is open to everyone, or else they just assume that registration will involve too much paperwork to bother with. I plan to contact them and present them with this document, as well as volunteering to handle the paperwork for them. Once I've discussed these types with the format controllers, I'll submit them for another review before proceeding with registration; at this point all I need is a quick look-over to make sure I won't be giving the format controllers bad advice. The thing that especially concerns me is my use of a "+blorb" suffix on some of the types. I realize "+" suffixes are discouraged, but something of that nature is needed to allow correct dispatch of Blorb files. If "+blorb" is simply not appropriate, I'd appreciate suggestions on how else to solve the problem; I do not believe a "." or "-" facet is semantically correct here. Thank you, M.D. Dollahite

2 2

Request for review of application/xspf+xml media type
by Lucas Gonze 01 Jul '06

01 Jul '06

See http://xspf.org/specs/draft-gonze-media-type-xspf. ... Type name application Subtype name xspf+xml Required parameters none Optional parameters charset. Same as charset parameter of application/xml as specified in [RFC3023]. Encoding considerations Same as encoding considerations of application/xml as specified in [RFC3023]. Security considerations The XML-based media type being registered has all of the security considerations described in [RFC3023] plus additional considerations. Playlist authors who publish documents containing local filesystem paths should take care to not reveal confidential information contained in those strings. The registration does not employ active content. Interoperability considerations Versions 0 and 1 are compatible except for a range of dates which cannot exist in practice. Published specification http://xspf.org/xspf-v1 (version 1) http://xspf.org/xspf-v0 (version 0) Applications that use this media type Gnomoradio, Webjay.org, Musicplayer, Playr, Yahoo Music Engine, Videolan Client, AmaroK, BMPx, I/ON, (others) Additional information Magic number(s) none, but see section 3.1 of [RFC3023]. File extension(s) .xspf Macintosh file type code(s) "TEXT" Fragment/anchor identifiers see [RFC3023]. Person & email address to contact for further information Lucas Gonze <lucas(a)gonze.com> Intended usage COMMON Restrictions on usage none Author/change controller The XSPF specification is a work product of the Xiph.org Foundation's XSPF Group homed at http://xspf.org. The specification was edited by Lucas Gonze <lucas(a)gonze.com>, Matthias Friedrich <matt(a)mafr.de>, and Robert Kaye <rob(a)eorbit.net> XML namespace http://xspf.org/ns/0 Base URIs see [RFC3023]. BOM see [RFC3023]. References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.

2 3

Revised draft of Last Call document (draft-miller-media-type-cellml)
by Andrew Miller 29 Jun '06

29 Jun '06

Hi all, Please find attached a revised draft of the CellML Media type registration, which is in Last Call for Informational status until 19th of July 2006. The draft has been submitted to the IETF secretariat, but will not appear until on or after Monday, Jule 10 at 9:00 AM ET, due to the upcoming IETF meeting. The revised draft differs from the previous one in the following respects: 1) It fixes a few minor ID nits: a) Minor formatting changes such as fixing a 73 character line, b) Changes a "recommended" to "RECOMMENDED", and a may to "can" to avoid confusion with MAY. 2) The draft now explicitly states that utf-8 is the only acceptable character set. This has always been in the CellML Umbrella Format, but now it is in the draft as well, for clarity. 3) The Abstract is no longer redundant with the Introduction, and the Discussion section has been merged into the Introduction. 4) An ambiguous use of the word "registry" (between the IANA types registry and the CellML Umbrella Format registry) has been fixed. Please CC any comments regarding this draft to ak.miller(a)auckland.ac.nz Best regards, Andrew Miller Internet Draft draft-miller-media-type-cellml-04.txt Intended Status: Network Working Group A. K. Miller Request for Comments: nnnn The University of Auckland Informational May 2006 CellML Media Type Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document standardises a new media type -- application/cellml+xml -- for use in exchanging mathematical models represented in a CellML Umbrella 1.0 compliant markup language. Miller Informational [Page 1] RFCnnnn CellML Media Type 24 May 2006 1. Introduction CellML Umbrella format is a standardised markup meta-language for the interchange of mathematical models. CellML Umbrella Format provides a common base which is supported by a number of specific formats used in the interchange of mathematical models. CellML Umbrella Format provides enough information to determine which specific language is used to express the model. The syntax and semantics of the CellML Umbrella format are defined by [CELLML-UMBRELLA]. CellML Umbrella format is an actual media format. Although CellML Umbrella documents contain elements in namespaces defined by other specifications such as [RDF] and [MATHML], the information in these namespaces do not contain sufficient information to define a mathematical model, and so CellML provides the information required to interconnect the different CellML components, as well as the information required to link CellML components to their metadata. As such, CellML Umbrella documents are more than just a collection of entities defined elsewhere, and so a new media type is required to identify CellML. As all well-formed CellML Umbrella documents are also well-formed XML documents, the convention described in Section 7 of [RFC3023] has been observed by use of the +xml suffix. The information in CellML Umbrella documents cannot be interpreted without understanding the semantics of the XML elements used to mark up the model structure. Therefore, the application top-level type is used instead of the text top-level type. 2. Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. The terms "element" and "document element" in this document are to be interpreted as in [XML]. The term "XML namespace" is to be interpreted as in [NAMESPACES]. 3. Media Type Registration for CellML Umbrella MIME media type name: application MIME subtype name: cellml+xml Mandatory parameters: none Optional parameters: charset The charset parameter of application/cellml+xml is handled in Miller Informational [Page 2] RFCnnnn CellML Media Type 24 May 2006 the same fashion as for application/xml, as specified in Section 3.2 of [RFC3023]. However, per conformance rule 4 of [CELLML-UMBRELLA], valid CellML Umbrella documents MUST be in the UTF-8 character set. If the charset parameter is present it MUST take the value "utf-8". CellML processing software SHOULD check the charset field, and if it is present but not equal to "utf-8", MAY attempt to recover from the error by processing the document in the specified character set. Encoding considerations: As per Section 3.2 of [RFC3023]. Security considerations: As per Section 5 of this document. Interoperability considerations: As per Section 4.1 of this document. Published specification: CellML Umbrella Specification[CELLML-UMBRELLA]. Applications which use this media type: As per Section 4.2 of this document. Additional information: Magic number(s): None. XML processing software can identify CellML Umbrella documents as XML documents which contain a document element with local name "model". File extension(s): The RECOMMENDED file extension for CellML Umbrella documents is .cellml Some older software uses the file extension .xml. Software vendors have also used the non-standard extension .cml. In contexts where the MIME type is available, or where the type has already been determined as CellML, implementations SHOULD allow files to be opened regardless of the extension. Implementations transferring models to an environment which uses file extensions SHOULD use the .cellml extension. Macintosh File Type Code(s): "TEXT" Person & email address to contact for further information: See the Author's Address section of this document. Intended usage: COMMON Author/Change controller: The CellML Umbrella 1.0 specification was authored by Andrew Miller. The CellML Umbrella 1.0 specification itself will not change. Miller Informational [Page 3] RFCnnnn CellML Media Type 24 May 2006 However, the umbrella specification defines the process for new specific formats to be registered. The Bioengineering Institute at The University of Auckland, with input from the CellML Community via the cellml-discussion(a)cellml.org mailing list, has control over the CellML Umbrella Format Registry. 4. Interoperability and usage 4.1. Interoperability Considerations The interoperability considerations in Section 3.1 of [RFC3023] also apply to CellML Umbrella documents. CellML Umbrella documents contain XML elements defined by each specific format, all of which are published specifications. In addition to the ability to parse XML, user agents require software support for the semantics of [RDF] and/or part or all of a specific format. As efforts are made to keep the number of specific formats small, user agents SHOULD implement all specific formats listed in the CellML Umbrella Format Registry at the time they were developed. 4.2. Applications which use CellML Umbrella Format CellML Umbrella is device-, platform-, and vendor-neutral and is supported by a wide range of CellML processing tools, including those designed to validate, edit, and/or visualise CellML models, extract MathML or RDF, translate to or from other related specifications, evaluate mathematics and ordinary differential equations, fit parameters to models, and serve, archive and annotate models. 5. Security Considerations As CellML Umbrella is an XML based markup language, all the security considerations presented in section 10 of [RFC3023] also apply to CellML Umbrella. Some types of CellML Umbrella documents can refer to other Uniform Resource Locators (URLs) in a number of places: i) References to XML document type definitions or schemas. ii) References to other models using the import features of some specific formats. iii) References to other documents embedded in user-defined data. Some types of CellML processing software may then automatically attempt to access the URL and retrieve the document. This retrieval could have several consequences, specifically, i) if a CellML document is transferred via e-mail, the fact that the recipient has opened the CellML document could be disclosed to the sender without the recipient's knowledge or consent. Miller Informational [Page 4] RFCnnnn CellML Media Type 24 May 2006 ii) where the recipient of a document transfers the document to another location using the MIME type defined in this document, the original author of the document may be notified of the second address by the attempted retrieval of further documents. iii) by performing requests on the recipient's behalf, the CellML processing software may cause actions to be performed with privileges granted to the recipient, without the recipient's knowledge or consent. CellML processing software can mitigate this threat when running in an environment where it is a concern by requiring explicit confirmation from the user before attempting to load any external documents. 6. IANA Considerations This document specifies a new media type. IANA will add this media type to the media types registry as specified in [RFC4288]. 7. References 7.1. Normative References [CELLML-UMBRELLA] Miller, A.K., "CellML Umbrella Specification 1.0", 20 April 2006, <http://www.cellml.org/specifications/ cellml_umbrella_1.0> [NAMESPACES] Bray, T., et. al., "Namespaces in XML 1.1", 4 February 2004, <http://www.w3.org/TR/xml-names11> [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997 [RFC3023] Murata, M., Simon, S.L., Kohn, D., "XML Media Types", RFC 3023, January 2001 [XML] Bray, T., et. al., "Extensible Markup Language (XML) 1.0 (Third Edition)", 4 February 2004, <http://www.w3.org/TR/REC-xml/> 7.2. Informative References [MATHML] Ion, P. and Miner, R.(editors) "Mathematical Markup Language (MathML) 1.01 Specification", 7 July 1999, <http://www.w3.org/TR/REC-MathML/> [RDF] Beckett, D.(editor) "RDF/XML Syntax Specification (Revised)", 10 February 2004, <http://www.w3.org/TR/rdf-syntax-grammar/> Miller Informational [Page 5] RFCnnnn CellML Media Type 24 May 2006 [RFC4288] Freed, N. and Klensin, J.C., "Media Type Specifications and Registration Procedures", RFC 4288, BCP 13, December 2005 Author's Address Andrew Miller The Bioengineering Institute at The University of Auckland Level 6, 70 Symonds St Auckland Central Auckland E-mail: ak.miller(a)auckland.ac.nz Full Copyright Statement Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. 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 assigns. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Miller Informational [Page 6]

1 0

Request for review of audio/amr and audio/amr-wb media types
by Colin Perkins 29 Jun '06

29 Jun '06

The AVT working group requests media type review for the audio/amr and audio/amr-wb media types, defined in section 8.1 and 8.2 of draft- ietf-avt-rtp-amr-bis-04.txt. This draft is currently in working group last call to obsolete RFC 3267. We would be grateful if any comments could be made by 21st July 2006. Thanks, Colin Perkins (AVT co-chair)

1 0

Fwd: Last Call: 'CellML Media Type' to Informational RFC (draft-miller-media-type-cellml)
by Lisa Dusseault 22 Jun '06

22 Jun '06

FYI Begin forwarded message: > From: The IESG <iesg-secretary(a)ietf.org> > Date: June 21, 2006 2:46:33 PM PDT > To: IETF-Announce <ietf-announce(a)ietf.org> > Subject: Last Call: 'CellML Media Type' to Informational RFC > (draft-miller-media-type-cellml) > Reply-To: iesg(a)ietf.org > > The IESG has received a request from an individual submitter to > consider the > following document: > > - 'CellML Media Type ' > <draft-miller-media-type-cellml-03.txt> as an Informational RFC > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send any comments to the > iesg(a)ietf.org or ietf(a)ietf.org mailing lists by 2006-07-19. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-miller-media-type- > cellml-03.txt > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce(a)ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce

2 1

Re: Last Call: 'CellML Media Type' to Informational RFC (draft-miller-media-type-cellml)
by Mark Baker 22 Jun '06

22 Jun '06

Yah, we (ietf-types) reviewed this one pretty thoroughly a few weeks ago, and -03 reflects the results of that review. http://www.alvestrand.no/pipermail/ietf-types/2006-March/date.html http://www.alvestrand.no/pipermail/ietf-types/2006-April/date.html http://www.alvestrand.no/pipermail/ietf-types/2006-May/date.html Mark. On 6/22/06, Lisa Dusseault <lisa(a)osafoundation.org> wrote: > > FYI > > Begin forwarded message: > > From: The IESG <iesg-secretary(a)ietf.org> > Date: June 21, 2006 2:46:33 PM PDT > To: IETF-Announce <ietf-announce(a)ietf.org> > Subject: Last Call: 'CellML Media Type' to Informational RFC > (draft-miller-media-type-cellml) > Reply-To: iesg(a)ietf.org > > > The IESG has received a request from an individual submitter to consider the > following document: > > - 'CellML Media Type ' > <draft-miller-media-type-cellml-03.txt> as an > Informational RFC > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send any comments to the > iesg(a)ietf.org or ietf(a)ietf.org mailing lists by 2006-07-19. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-miller-media-type-cellml-03.txt > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce(a)ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > >

1 0

Registration of media type application/sparql-results+json
by Elias Torres 16 Jun '06

16 Jun '06

see also http://www.w3.org/2001/sw/DataAccess/json-sparql/#mediaType Type name: application Subtype name: sparql-results+json Required parameters: None Optional parameters: None Encoding considerations: The encoding considerations of the SPARQL Query Results JSON Format is identical to those of the "application/json" as specified in [JSON-IETF-DRAFT] Security considerations: SPARQL query results uses URIs. See Section 7 of [RFC3986]. SPARQL query results uses IRIs. See Section 8 of [RFC3987]. The security considerations of the SPARQL Query Results JSON Format is identical to those of the "application/json" as specified in [JSON-IETF-DRAFT] Interoperability considerations: There are no known interoperability issues. Published specification: http://www.w3.org/2001/sw/DataAccess/json-sparql/ Applications which use this media type: No known applications currently use this media type. Additional information: Magic number(s): n/a File extension(s): ".srj" Macintosh file type code(s): "TEXT" Person & email address to contact for further information: Kendall Clark, Elias Torres, Lee Feigenbaum <public-rdf-dawg-comments(a)w3.org> Intended usage: COMMON Restrictions on usage: None Author/Change controller: The SPARQL specification is a work product of the World Wide Web Consortium's RDF Data Access Working Group. The W3C has change control over these specifications. References [JSON-IETF-DRAFT] JavaScript Object Notation (JSON), Internet Draft, D. Crockford, http://www.ietf.org/internet-drafts/draft-crockford-jsonorg-json-04.txt Regards, Elias Torres Member of RDF Data Access Working Group W3C/IBM

2 1