idnits 2.17.1 draft-miller-media-type-cellml-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 292. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 2006) is 6615 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'CELLML-UMBRELLA' -- Possible downref: Non-RFC (?) normative reference: ref. 'NAMESPACES' ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' -- Obsolete informational reference (is this intentional?): RFC 4288 (Obsoleted by RFC 6838) Summary: 9 errors (**), 0 flaws (~~), 2 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft 2 draft-miller-media-type-cellml-02.txt 4 Intended Status: 5 Network Working Group A. K. Miller 6 Request for Comments: nnnn The University of Auckland 7 Standards Track March 2006 9 CellML Media Type 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other documents 25 at any time. It is inappropriate to use Internet-Drafts as 26 reference material or to cite them other than as "work in progress. 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/1id-abstracts.html 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html 34 Copyright Notice 36 Copyright (C) The Internet Society (2006). 38 Abstract 40 This document standardises a new media type -- 41 application/cellml+xml -- for use in exchanging mathematical models 42 represented in a CellML Umbrella 1.0 compliant markup language. 44 1. Introduction 46 CellML Umbrella format is a standardised markup meta-language for the 47 interchange of mathematical models. CellML Umbrella Format provides 48 a common base which is supported by a number of specific formats 49 used in the interchange of mathematical models. CellML Umbrella 50 Format provides enough information to determine which specific 51 language is used to express the model. The syntax and semantics of 52 the CellML Umbrella format are defined by [CELLML-UMBRELLA]. 54 This document standardises a new media type -- 55 application/cellml+xml -- for use in exchanging mathematical models 56 represented in a specific CellML Umbrella compliant language. 58 2. Notational Conventions 60 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 61 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 62 document are to be interpreted as described in [RFC2119]. 64 The terms "element" and "document element" in this document are to be 65 interpreted as in [XML]. 67 The term "XML namespace" is to be interpreted as in [NAMESPACES]. 69 3. Discussion 71 CellML Umbrella is an XML-based markup meta-language for the 72 interchange of mathmatical models. 74 CellML Umbrella format is an actual media format. Although 75 CellML Umbrella documents contain elements in namespaces defined by 76 other specifications such as [RDF] and [MATHML], the information in 77 these namespaces do not contain sufficient information to define a 78 mathematical model, and so CellML provides the information required 79 to interconnect the different CellML components, as well as the 80 information required to link CellML components to their metadata. As 81 such, CellML Umbrella documents are more than just a collection of 82 entities defined elsewhere, and so a new media type is required to 83 identify CellML. 85 As all well-formed CellML Umbrella documents are also well-formed 86 XML documents, the convention described in Section 7 of [RFC3023] 87 has been observed by use of the +xml suffix. 89 The information in CellML Umbrella documents cannot be interpreted 90 without understanding the semantics of the XML elements used to mark 91 up the model structure. Therefore, the application top-level type is 92 used instead of the text top-level type. 94 4. Media Type Registration for CellML Umbrella 96 MIME media type name: application 98 MIME subtype name: cellml+xml 100 Mandatory parameters: none 102 Optional parameters: charset 104 The charset parameter of application/cellml+xml is handled in 105 the same fashion as for application/xml, as specified in Section 106 3.2 of [RFC3023]. 108 Encoding considerations: As per Section 3.2 of [RFC3023]. 110 Security considerations: As per Section 6 of this document. 112 Interoperability considerations: As per Section 5.1 of this 113 document. 115 Published specification: 117 CellML Umbrella Specification[CELLML-UMBRELLA]. 119 Applications which use this media type: As per Section 5.2 of this 120 document. 122 Additional information: 124 Magic number(s): None. 125 XML processing software may identify CellML Umbrella documents 126 as XML documents which contain a document element with local 127 name "model". 129 File extension(s): 130 The recommended file extension for CellML Umbrella documents is 131 .xml 133 Some older software still uses the obsolete file extension .cml 135 Macintosh File Type Code(s): "TEXT" 137 Person & email address to contact for further information: 138 See the Author's Address section of this document. 140 Intended usage: COMMON 142 Author/Change controller: The CellML Umbrella 1.0 specification 143 was authored by Andrew Miller. 145 The CellML Umbrella 1.0 specification itself will not change. 146 However, the umbrella specification defines the process for new 147 specific formats to be registered. The Bioengineering Institute 148 at The University of Auckland, with input from the CellML 149 Community via the cellml-discussion@cellml.org mailing list, 150 has control over the CellML Umbrella Format Registry. 152 5. Interoperability and usage 153 5.1. Interoperability Considerations 154 The interoperability considerations in Section 3.1 of [RFC3023] 155 also apply to CellML Umbrella documents. CellML Umbrella documents 156 contain XML elements defined by each specific format, all of which 157 are published specifications. In addition to the ability to 158 parse XML, user agents require software support for the semantics of 159 [RDF] and/or part or all of a specific format. As efforts are made 160 to keep the number of specific formats small, user agents SHOULD 161 implement all specific formats listed in the registry at the time 162 they were developed. 164 5.2. Applications which use CellML Umbrella Format 165 CellML Umbrella is device-, platform-, and vendor-neutral and is 166 supported by a wide range of CellML processing tools, including 167 those designed to validate, edit, and/or visualise CellML models, 168 extract MathML or RDF, translate to or from other related 169 specifications, evaluate mathematics and ordinary differential 170 equations, fit parameters to models, and serve, archive and annotate 171 models. 173 6. Security Considerations 175 As CellML Umbrella is an XML based markup language, all the security 176 considerations presented in section 10 of [RFC3023] also apply to 177 CellML Umbrella. 179 Some types of CellML Umbrella documents can refer to other Uniform 180 Resource Locators (URLs) in a number of places: 181 i) References to XML document type definitions or schemas. 182 ii) References to other models using the import features of some 183 specific formats. 184 iii) References to other documents embedded in user-defined data. 186 Some types of CellML processing software may then 187 automatically attempt to access the URL and retrieve the document. 188 This retrieval could have several consequences, specifically, 189 i) if a CellML document is transferred via e-mail, the fact that 190 the recipient has opened the CellML document could be 191 disclosed to the sender without the recipient's knowledge or 192 consent. 194 ii) where the recipient of a document transfers the document to 195 another location using the MIME type defined in this 196 document, the original author of the document may be notified 197 of the second address by the attempted retrieval of further 198 documents. 199 iii) by performing requests on the recipient's behalf, the CellML 200 processing software may cause actions to be performed with 201 privileges granted to the recipient, without the recipient's 202 knowledge or consent. 204 CellML processing software can mitigate this threat when running in 205 an environment where it is a concern by requiring explicit 206 confirmation from the user before attempting to load any external 207 documents. 209 7. IANA Considerations 211 This document specifies a new media type. IANA will add this media 212 type to the media types registry as specified in [RFC4288]. 214 8. References 215 8.1. Normative References 217 [CELLML-UMBRELLA] Miller, A.K., "CellML Umbrella Specification 1.0", 218 20 April 2006, 219 222 [NAMESPACES] Bray, T., et. al., "Namespaces in XML 1.1", 223 4 February 2004, 224 226 [RFC2119] Bradner, S., "Key words for use in RFCs to 227 Indicate Requirement Levels", RFC 2119, BCP 14, 228 March 1997 230 [RFC3023] Murata, M., Simon, S.L., Kohn, D., "XML Media 231 Types", RFC 3023, January 2001 233 [XML] Bray, T., et. al., "Extensible Markup Language 234 (XML) 1.0 (Third Edition)", 4 February 2004, 235 237 8.2. Informative References 238 [MATHML] Ion, P. and Miner, R.(editors) "Mathematical 239 Markup Language (MathML) 1.01 Specification", 7 240 July 1999, 242 [RDF] Beckett, D.(editor) "RDF/XML Syntax Specification 243 (Revised)", 10 February 2004, 244 246 [RFC4288] Freed, N. and Klensin, J.C., "Media Type 247 Specifications and Registration Procedures", 248 RFC 4288, BCP 13, December 2005 250 Author's Address 252 Andrew Miller 253 The Bioengineering Institute at The University of Auckland 254 Level 6, 70 Symonds St 255 Auckland Central 256 Auckland 258 E-mail: ak.miller@auckland.ac.nz 260 Full Copyright Statement 262 Copyright (C) The Internet Society (2006). 264 This document is subject to the rights, licenses and restrictions 265 contained in BCP 78, and except as set forth therein, the authors 266 retain all their rights. 268 This document and translations of it may be copied and furnished 269 to others, and derivative works that comment on or otherwise 270 explain it or assist in its implementation may be prepared, copied, 271 published and distributed, in whole or in part, without 272 restriction of any kind, provided that the above copyright notice 273 and this paragraph are included on all such copies and derivative 274 works. However, this document itself may not be modified in any 275 way, such as by removing the copyright notice or references to the 276 Internet Society or other Internet organizations, except as needed 277 for the purpose of developing Internet standards in which case the 278 procedures for copyrights defined in the Internet Standards 279 process must be followed, or as required to translate it into 280 languages other than English. 282 The limited permissions granted above are perpetual and will not 283 be revoked by the Internet Society or its successors or assigns. 285 This document and the information contained herein 286 are provided on an "AS IS" basis and THE CONTRIBUTOR, THE 287 ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE 288 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 289 ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO 290 ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 291 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 292 OR FITNESS FOR A PARTICULAR PURPOSE.