idnits 2.17.1 draft-miller-media-type-cellml-05.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 297. ** 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 : ---------------------------------------------------------------------------- No issues found here. 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 (May 2006) is 6557 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: 8 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-05.txt 4 Intended Status: 5 Network Working Group A. K. Miller 6 Request for Comments: nnnn The University of Auckland 7 Informational May 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 47 the interchange of mathematical models. CellML Umbrella format 48 provides a common base which is supported by a number of specific 49 formats used in the interchange of mathematical models. CellML 50 Umbrella format provides enough information to determine which 51 specific language is used to express the model. The syntax and 52 semantics of the CellML Umbrella format are defined by 53 [CELLML-UMBRELLA]. 55 CellML Umbrella format is an actual media format. Although 56 CellML Umbrella documents contain elements in namespaces defined by 57 other specifications such as [RDF] and [MATHML], the information in 58 these namespaces do not contain sufficient information to define a 59 mathematical model, and so CellML provides the information required 60 to interconnect the different CellML components, as well as the 61 information required to link CellML components to their metadata. As 62 such, CellML Umbrella documents are more than just a collection of 63 entities defined elsewhere, and so a new media type is required to 64 identify CellML. 66 As all well-formed CellML Umbrella documents are also well-formed 67 XML documents, the convention described in Section 7 of [RFC3023] 68 has been observed by use of the +xml suffix. 70 The information in CellML Umbrella documents cannot be interpreted 71 without understanding the semantics of the XML elements used to mark 72 up the model structure. Therefore, the application top-level type is 73 used instead of the text top-level type. 75 2. Notational Conventions 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in [RFC2119]. 81 The terms "element" and "document element" in this document are to be 82 interpreted as in [XML]. 84 The term "XML namespace" is to be interpreted as in [NAMESPACES]. 86 3. Media Type Registration for CellML Umbrella 88 MIME media type name: application 90 MIME subtype name: cellml+xml 92 Mandatory parameters: none 94 Optional parameters: charset 96 The charset parameter of application/cellml+xml is handled in 97 the same fashion as for application/xml, as specified in Section 98 3.2 of [RFC3023]. However, per conformance rule 4 of 99 [CELLML-UMBRELLA], valid CellML Umbrella documents MUST be in the 100 UTF-8 character set. If the charset parameter is present it MUST 101 take the value "utf-8". CellML processing software SHOULD check 102 the charset field, and if it is present but not equal to "utf-8", 103 MAY attempt to recover from the error by processing the document 104 in the specified character set. 106 Encoding considerations: As per Section 3.2 of [RFC3023]. 108 Security considerations: As per Section 5 of this document. 110 Interoperability considerations: As per Section 4.1 of this 111 document. 113 Published specification: 115 CellML Umbrella Specification[CELLML-UMBRELLA]. 117 Applications which use this media type: As per Section 4.2 of this 118 document. 120 Additional information: 122 Magic number(s): None. 123 XML processing software can identify CellML Umbrella documents 124 as XML documents which contain a document element with local 125 name "model". 127 File extension(s): 128 The RECOMMENDED file extension for CellML Umbrella documents is 129 .cellml 131 Some older software uses the file extension .xml. Software 132 vendors have also used the non-standard extension .cml. In 133 contexts where the MIME type is available, or where the type has 134 already been determined as CellML, implementations SHOULD allow 135 files to be opened regardless of the extension. Implementations 136 transferring models to an environment which uses file extensions 137 SHOULD use the .cellml extension. 139 Macintosh File Type Code(s): "TEXT" 141 Person & email address to contact for further information: 142 See the Author's Address section of this document. 144 Intended usage: COMMON 146 Author/Change controller: The CellML Umbrella 1.0 specification 147 was authored by Andrew Miller. 149 The CellML Umbrella 1.0 specification itself will not change. 151 However, the umbrella specification defines the process for new 152 specific formats to be registered. The Bioengineering Institute 153 at The University of Auckland, with input from the CellML 154 Community via the cellml-discussion@cellml.org mailing list, 155 has control over the CellML Umbrella Format Registry. 157 4. Interoperability and usage 158 4.1. Interoperability Considerations 159 The interoperability considerations in Section 3.1 of [RFC3023] 160 also apply to CellML Umbrella documents. CellML Umbrella documents 161 contain XML elements defined by each specific format, all of which 162 are published specifications. In addition to the ability to 163 parse XML, user agents require software support for the semantics of 164 [RDF] and/or part or all of a specific format. As efforts are made 165 to keep the number of specific formats small, user agents SHOULD 166 implement all specific formats listed in the CellML Umbrella Format 167 Registry at the time they were developed. 169 4.2. Applications which use CellML Umbrella format 170 CellML Umbrella is device-, platform-, and vendor-neutral and is 171 supported by a wide range of CellML processing tools, including 172 those designed to validate, edit, and/or visualise CellML models, 173 extract MathML or RDF, translate to or from other related 174 specifications, evaluate mathematics and ordinary differential 175 equations, fit parameters to models, and serve, archive and annotate 176 models. 178 5. Security Considerations 180 As CellML Umbrella is an XML based markup language, all the security 181 considerations presented in section 10 of [RFC3023] also apply to 182 CellML Umbrella. 184 Some types of CellML Umbrella documents can refer to other Uniform 185 Resource Locators (URLs) in a number of places: 186 i) References to XML document type definitions or schemas. 187 ii) References to other models using the import features of some 188 specific formats. 189 iii) References to other documents embedded in user-defined data. 191 Some types of CellML processing software may then 192 automatically attempt to access the URL and retrieve the document. 193 This retrieval could have several consequences, specifically, 194 i) if a CellML document is transferred via e-mail, the fact that 195 the recipient has opened the CellML document could be 196 disclosed to the sender without the recipient's knowledge or 197 consent. 199 ii) where the recipient of a document transfers the document to 200 another location using the MIME type defined in this 201 document, the original author of the document may be notified 202 of the second address by the attempted retrieval of further 203 documents. 204 iii) by performing requests on the recipient's behalf, the CellML 205 processing software may cause actions to be performed with 206 privileges granted to the recipient, without the recipient's 207 knowledge or consent. 209 CellML processing software can mitigate this threat when running in 210 an environment where it is a concern by requiring explicit 211 confirmation from the user before attempting to load any external 212 documents. 214 6. IANA Considerations 216 This document specifies a new media type. IANA will add this media 217 type to the media types registry as specified in [RFC4288]. 219 7. References 220 7.1. Normative References 222 [CELLML-UMBRELLA] Miller, A.K., "CellML Umbrella Specification 1.0", 223 20 April 2006, 224 227 [NAMESPACES] Bray, T., et. al., "Namespaces in XML 1.1", 228 4 February 2004, 229 231 [RFC2119] Bradner, S., "Key words for use in RFCs to 232 Indicate Requirement Levels", RFC 2119, BCP 14, 233 March 1997 235 [RFC3023] Murata, M., Simon, S.L., Kohn, D., "XML Media 236 Types", RFC 3023, January 2001 238 [XML] Bray, T., et. al., "Extensible Markup Language 239 (XML) 1.0 (Third Edition)", 4 February 2004, 240 242 7.2. Informative References 243 [MATHML] Ion, P. and Miner, R.(editors) "Mathematical 244 Markup Language (MathML) 1.01 Specification", 7 245 July 1999, 247 [RDF] Beckett, D.(editor) "RDF/XML Syntax Specification 248 (Revised)", 10 February 2004, 249 251 [RFC4288] Freed, N. and Klensin, J.C., "Media Type 252 Specifications and Registration Procedures", 253 RFC 4288, BCP 13, December 2005 255 Author's Address 257 Andrew Miller 258 The Bioengineering Institute at The University of Auckland 259 Level 6, 70 Symonds St 260 Auckland Central 261 Auckland 263 E-mail: ak.miller@auckland.ac.nz 265 Full Copyright Statement 267 Copyright (C) The Internet Society (2006). 269 This document is subject to the rights, licenses and restrictions 270 contained in BCP 78, and except as set forth therein, the authors 271 retain all their rights. 273 This document and translations of it may be copied and furnished 274 to others, and derivative works that comment on or otherwise 275 explain it or assist in its implementation may be prepared, copied, 276 published and distributed, in whole or in part, without 277 restriction of any kind, provided that the above copyright notice 278 and this paragraph are included on all such copies and derivative 279 works. However, this document itself may not be modified in any 280 way, such as by removing the copyright notice or references to the 281 Internet Society or other Internet organizations, except as needed 282 for the purpose of developing Internet standards in which case the 283 procedures for copyrights defined in the Internet Standards 284 process must be followed, or as required to translate it into 285 languages other than English. 287 The limited permissions granted above are perpetual and will not 288 be revoked by the Internet Society or its successors or assigns. 290 This document and the information contained herein 291 are provided on an "AS IS" basis and THE CONTRIBUTOR, THE 292 ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE 293 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 294 ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO 295 ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 296 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 297 OR FITNESS FOR A PARTICULAR PURPOSE.