Network Working Group A. Miller
Request for Comment: 4708 The University of Auckland
Category: Informational October 2006
Network Working Group A. Miller
Request for Comment: 4708 The University of Auckland
Category: Informational October 2006
CellML Media Type
CellML媒体类型
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（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.
本文档标准化了一种新的媒体类型——application/cellml+xml，用于交换cellml伞形1.0兼容标记语言中表示的数学模型。
The CellML Umbrella format is a standardised markup meta-language for the interchange of mathematical models. The CellML Umbrella format provides a common base that is supported by a number of specific formats used in the interchange of mathematical models. The 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伞形格式是用于数学模型交换的标准化标记元语言。CellML伞形格式提供了一个公共基础，由数学模型交换中使用的许多特定格式支持。CellML伞形格式提供了足够的信息来确定使用哪种特定语言来表示模型。CellML伞形格式的语法和语义由[CellML-Umbrella]定义。
The 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 elements 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.
CellML伞形格式是一种实际的媒体格式。尽管CellML伞形文档包含由[RDF]和[MATHML]等其他规范定义的名称空间中的元素，但这些名称空间中的元素不包含足够的信息来定义数学模型，因此CellML提供了互连不同CellML组件所需的信息，以及将CellML组件链接到其元数据所需的信息。因此，CellML伞形文档不仅仅是在别处定义的实体集合，因此需要一种新的媒体类型来识别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.
由于所有格式良好的CellML伞形文档也是格式良好的XML文档，因此使用+XML后缀遵守了[RFC3023]第7节中描述的约定。
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.
如果不理解用于标记模型结构的XML元素的语义，就无法解释CellML伞形文档中的信息。因此，将使用应用程序顶级类型而不是文本顶级类型。
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].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The terms "element" and "document element" in this document are to be interpreted as in [XML].
本文档中的术语“元素”和“文档元素”应解释为[XML]。
The term "XML namespace" is to be interpreted as in [NAMESPACES].
术语“XML名称空间”应解释为[名称空间]。
MIME media type name: application
MIME媒体类型名称：应用程序
MIME subtype name: cellml+xml
MIME子类型名称：cellml+xml
Mandatory parameters: none
强制参数：无
Optional parameters: charset
可选参数：字符集
The charset parameter of application/cellml+xml is handled in 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.
application/cellml+xml的字符集参数的处理方式与application/xml相同，如[RFC3023]第3.2节所述。但是，根据[CELLML-UMBRELLA]的一致性规则4，有效的CELLML UMBRELLA文档必须使用UTF-8字符集。如果存在字符集参数，则必须取值“utf-8”。CellML处理软件应检查字符集字段，如果该字段存在但不等于“utf-8”，则可通过在指定字符集中处理文档来尝试从错误中恢复。
Encoding considerations: As per Section 3.2 of [RFC3023].
编码注意事项：根据[RFC3023]第3.2节。
Security considerations: As per Section 5 of this document.
安全注意事项：根据本文件第5节。
Interoperability considerations: As per Section 4.1 of this document.
互操作性注意事项：根据本文件第4.1节。
Published specification:
已发布的规范：
CellML Umbrella Specification [CELLML-UMBRELLA].
CellML雨伞规格[CellML-UMBRANGE]。
Applications that use this media type: As per Section 4.2 of this document.
使用此介质类型的应用程序：根据本文件第4.2节。
Additional information:
其他信息：
Magic number(s): None. XML processing software can identify CellML Umbrella documents as XML documents that contain a document element with the local name "model".
幻数：无。XML处理软件可以将CellML伞形文档识别为包含本地名为“model”的文档元素的XML文档。
File extension(s): The RECOMMENDED file extension for CellML Umbrella documents is .cellml
文件扩展名：CellML伞形文档的建议文件扩展名为.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 that uses file extensions SHOULD use the .cellml extension.
一些较旧的软件使用文件扩展名.xml。软件供应商也使用了非标准扩展名.cml。在MIME类型可用的上下文中，或者该类型已被确定为CellML的上下文中，实现应允许打开文件，而不考虑扩展名。将模型传输到使用文件扩展名的环境的实现应使用.cellml扩展名。
Macintosh File Type Code(s): "TEXT"
Macintosh文件类型代码：“文本”
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.
作者/变更控制器：CellML雨伞1.0规范由Andrew Miller编写。
The CellML Umbrella 1.0 specification itself will not change. 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@cellml.org mailing list, has control over the CellML Umbrella Format Registry.
CellML 1.0规范本身不会改变。但是，伞形规范定义了注册新的特定格式的过程。奥克兰大学生物工程研究所，通过CYLML从CelML社区输入discussion@cellml.org邮件列表，控制CellML伞形格式注册表。
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
[RFC3023]第3.1节中的互操作性注意事项也适用于CellML伞形文件。CellML伞形文档包含由每个特定格式定义的XML元素，所有这些都是发布的规范。除了解析XML的能力外，用户代理还需要软件支持[RDF]和/或特定格式的部分或全部的语义。由于努力保持
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.
特定格式的数量很小，用户代理应该在开发CellML伞形格式注册表时实现所有列出的特定格式。
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.
CellML Umbrella与设备、平台和供应商无关，并由一系列CellML处理工具支持，包括用于验证、编辑和/或可视化CellML模型、提取MathML或RDF、转换为其他相关规范或从其他相关规范转换、评估数学和常微分方程的工具，将参数拟合到模型，并为模型提供服务、存档和注释。
As CellML Umbrella is an XML-based markup language, all the security considerations presented in Section 10 of [RFC3023] also apply to CellML Umbrella.
由于CellML Umbrella是一种基于XML的标记语言，[RFC3023]第10节中介绍的所有安全注意事项也适用于CellML Umbrella。
Some types of CellML Umbrella documents can refer to other Uniform Resource Locators (URLs) in a number of places:
某些类型的CellML伞形文档可以在多个位置引用其他统一资源定位器（URL）：
i) References to XML document type definitions or schemas.
i) 对XML文档类型定义或架构的引用。
ii) References to other models using the import features of some specific formats.
ii）参考使用某些特定格式的导入功能的其他模型。
iii) References to other documents embedded in user-defined data.
iii）用户定义数据中嵌入的其他文件的参考。
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,
某些类型的CellML处理软件可能会自动尝试访问URL并检索文档。这种检索可能会产生几个后果，特别是，
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.
i) 如果通过电子邮件传输CellML文档，则接收方已打开CellML文档的事实可能会在接收方不知情或不同意的情况下披露给发送方。
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.
ii）如果文件接收人使用本文件中定义的MIME类型将文件转移到另一个位置，可通过尝试检索其他文件通知文件的原始作者第二个地址。
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.
iii）通过代表接收方执行请求，CellML处理软件可能会导致在接收方不知情或不同意的情况下，以授予接收方的权限执行操作。
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.
CellML处理软件在环境中运行时，需要用户在加载任何外部文档之前进行明确确认，从而可以减轻这种威胁。
This document specifies a new media type. IANA has added this media type to their media types registry as specified in [RFC4288].
此文档指定了一种新的媒体类型。IANA已按照[RFC4288]中的规定将此媒体类型添加到其媒体类型注册表中。
[CELLML-UMBRELLA] Miller, A.K., "CellML Umbrella Specification 1.0",
20 April 2006, <http://www.cellml.org/
specifications/cellml_umbrella_1.0>
[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>
[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", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.
[RFC3023]Murata，M.，St.Laurent，S.，和D.Kohn，“XML媒体类型”，RFC 3023，2001年1月。
[XML] Bray, T., et. al., "Extensible Markup Language
(XML) 1.0 (Fourth Edition)", 29 September 2006,
<http://www.w3.org/TR/REC-xml/>
[XML] Bray, T., et. al., "Extensible Markup Language
(XML) 1.0 (Fourth Edition)", 29 September 2006,
<http://www.w3.org/TR/REC-xml/>
[MATHML] Ion, P. and Miner, R.(editors) "Mathematical Markup
Language (MathML) 1.01 Specification", 7 July 1999,
<http://www.w3.org/TR/REC-MathML/>
[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/>
[RDF] Beckett, D.(editor) "RDF/XML Syntax Specification
(Revised)", 10 February 2004,
<http://www.w3.org/TR/rdf-syntax-grammar/>
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005.
[RFC4288]Freed，N.和J.Klensin，“介质类型规范和注册程序”，BCP 13，RFC 4288，2005年12月。
Author's Address
作者地址
Andrew Miller The Bioengineering Institute at The University of Auckland Level 6, 70 Symonds St Auckland Central Auckland
Andrew Miller奥克兰大学生物工程学院6, 70级西蒙兹圣奥克兰奥克兰中心
EMail: ak.miller@auckland.ac.nz
EMail: ak.miller@auckland.ac.nz
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（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.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。