INTERNET DRAFT Tom Hastings
<draft-mcdonald-cip4-jdf-mime-00.txt> Xerox
Ira McDonald
[Target Category: Informational] High North
Expires 25 July 2003 25 January 2003
The MIME application/vnd.cip4-jdf+xml Content-Type
<draft-mcdonald-cip4-jdf-mime-00.txt>
Copyright (C) The Internet Society (2003). All Rights Reserved.
Status of This Memo
This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. 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."
To view the list of Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html.
Abstract
The International Cooperation for the Integration of Processes in Prepress, Press, and Postpress (CIP4) is an international worldwide standards body located in Switzerland. The purpose of CIP4 is to encourage computer based integration of all processes that have to be considered in the graphic arts industry. CIP4 has defined two document formats that are encoded in W3C Extensible Markup Language (XML):
This document defines two new MIME sub-types for IANA registration:
1. Introduction ............................................... 3 2. Terminology and Conventions ................................ 3 3. Registration of JDF MIME Sub-type .......................... 4 4. Registration of JMF MIME Sub-type .......................... 6 5. IANA Considerations ........................................ 8 6. Internationalization Considerations ........................ 8 7. Security Considerations .................................... 8 8. Normative References ....................................... 9 9. Informative References ..................................... 9 10. Acknowledgments ........................................... 10 11. Authors Addresses ......................................... 10 12. Full Copyright Statement .................................. 11 13. Appendix X - Change History ............................... 12
[[RFC Editor: Please replace the string 'RFC xxxx' with the assigned RFC number when this document is published as an Informational RFC]]
[CIP4-ORG] has defined the Job Definition Format (JDF) Specification [CIP4-JDF], an open standard for integration of all computer aided business and production processes around print media.
This document defines two new MIME sub-types for IANA registration:
This document follows the procedures for registration of new MIME types described in [RFC2048]. See the IANA registry at [IANA-MIME].
Please send comments directly to the authors (see section 11).
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 BCP 14 [RFC2119].
To: ietf-types@iana.org
Subject: Registration of MIME type 'application/vnd.cip4-jdf+xml'
MIME media type name: application
MIME subtype name: vnd.cip4-jdf+xml (Vendor Tree)
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].
Although listed as an optional parameter, the use of the charset
parameter is STRONGLY RECOMMENDED, since this information can be
used by XML processors to determine authoritatively the character
encoding of the XML MIME entity. The charset parameter can also
be used to provide protocol-specific operations, such as charset-
based content negotiation in HTTP. "utf-8" [RFC2279] is the
RECOMMENDED value, representing the UTF-8 charset. UTF-8 is
supported by all conforming processors of W3C XML/1.0.
Encoding considerations:
Each 'application/vnd.cip4-jdf+xml' entity is a well-formed and
valid XML document encoded in UTF-8 [RFC2279] or UTF-16 [RFC2781].
See XML Media Types [RFC3023] for further encoding information.
Per the JDF Specification (see URL below), each JDF document SNOULD
contain a JDF 'Version' element. So 'application/vnd.cip4-jdf+xml'
may be correctly used to label any future version of JDF content.
Security considerations:
See section 7 'Security Considerations' of this document.
Interoperability considerations:
See section 1.4.2 'Conformance Requirements for JDF Entities' in
the JDF Specification (see URL below).
For maximum interoperability, the use of validating XML processors
is STRONGLY RECOMMENDED. Although non-validating XML processors
may be more efficient, they are not required to handle all features
of XML.
Published specification:
The MIME application/vnd.cip4-jdf+xml Content-Type (RFC xxxx)
JDF Specification, Release 1.1, Revision A, September 2002.
<http://www.cip4.org/documents/jdf_specifications/JDF1.1a.pdf>
Applications which use this media type:
Graphic arts industry prepress, press, and postpress applications
and printing and finishing devices.
Additional information:
Magic number(s): none
No initial byte sequence that is always present for JDF files.
See XML Media Types [RFC3023] for further information.
File extension(s): .jdf or .xml
Use of the '.jdf' file extension is RECOMMENDED.
Macintosh File Type Code(s): "TEXT"
Person & email address to contact for further information:
Tom Hastings
Xerox Corporation
737 Hawaii St
El Segundo, CA 90245
Phone: +1 310-333-6413
Fax: +1 310-333-5514
EMail: hastings@cp10.es.xerox.com
Ira McDonald
High North Inc
221 Ridge Ave
Grand Marais, MI 49839
USA
Phone: +1 906-494-2434
Email: imcdonald@sharplabs.com
Intended usage: LIMITED USE
Author/Change controller:
The JDF Specification is a work product of the International
Cooperation for the Integration of Processes in Prepress, Press,
and Postpress (CIP4) and is periodically revised and enhanced.
See <http://www.cip4.org> for further information.
To: ietf-types@iana.org
Subject: Registration of MIME type 'application/vnd.cip4-jmf+xml'
MIME media type name: application
MIME subtype name: vnd.cip4-jmf+xml (Vendor Tree)
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].
Although listed as an optional parameter, the use of the charset
parameter is STRONGLY RECOMMENDED, since this information can be
used by XML processors to determine authoritatively the character
encoding of the XML MIME entity. The charset parameter can also
be used to provide protocol-specific operations, such as charset-
based content negotiation in HTTP. "utf-8" [RFC2279] is the
RECOMMENDED value, representing the UTF-8 charset. UTF-8 is
supported by all conforming processors of W3C XML/1.0.
Encoding considerations:
Each 'application/vnd.cip4-jmf+xml' entity is a well-formed and
valid XML document encoded in UTF-8 [RFC2279] or UTF-16 [RFC2781].
See XML Media Types [RFC3023] for further encoding information.
Per the JDF Specification (see URL below), each JMF document SNOULD
contain a JMF 'Version' element. So 'application/vnd.cip4-jmf+xml'
may be correctly used to label any future version of JMF content.
Security considerations:
See section 7 'Security Considerations' of this document.
Interoperability considerations:
See section 1.4.2 'Conformance Requirements for JDF Entities' in
the JDF Specification (see URL below).
For maximum interoperability, the use of validating XML processors
is STRONGLY RECOMMENDED. Although non-validating XML processors
may be more efficient, they are not required to handle all features
of XML.
Published specification:
The MIME application/vnd.cip4-jdf+xml Content-Type (RFC xxxx)
JDF Specification, Release 1.1, Revision A, September 2002.
<http://www.cip4.org/documents/jdf_specifications/JDF1.1a.pdf>
Applications which use this media type:
Graphic arts industry prepress, press, and postpress applications
and printing and finishing devices.
Additional information:
Magic number(s): none
No initial byte sequence that is always present for JMF files.
See XML Media Types [RFC3023] for further information.
File extension(s): .jmf or .xml
Use of the '.jmf' file extension is RECOMMENDED.
Macintosh File Type Code(s): "TEXT"
Person & email address to contact for further information:
Tom Hastings
Xerox Corporation
737 Hawaii St
El Segundo, CA 90245
Phone: +1 310-333-6413
Fax: +1 310-333-5514
EMail: hastings@cp10.es.xerox.com
Ira McDonald
High North Inc
221 Ridge Ave
Grand Marais, MI 49839
USA
Phone: +1 906-494-2434
Email: imcdonald@sharplabs.com
Intended usage: LIMITED USE
Author/Change controller:
The JDF Specification is a work product of the International
Cooperation for the Integration of Processes in Prepress, Press,
and Postpress (CIP4) and is periodically revised and enhanced.
See <http://www.cip4.org> for further information.
This document defines two new MIME sub-types for IANA registration after public review:
CIP4 JDF and JMF files [CIP4-JDF] are XML documents [W3C-XML] that are encoded in human-readable text, usually in the UTF-8 charset [RFC2279]. All CIP4 JDF and JMF files SHOULD contain an internal 'charset' label in the XML declaration (first line of text), naming a 'charset' from the IANA registry [IANA-CHAR].
Therefore, CIP4 JDF and JMF files conform to the "IETF Policy on Character Sets and Languages" [RFC2277].
The security considerations for 'application/vnd.cip4-jdf+xml' and 'application/vnd.cip4-jmf+xml' are the same considerations as those specified for 'application/xml' in [RFC3023].
In addition, because of the extensibility features of JDF provided for in the JDF Specification [CIP4-JDF], it may also be possible that 'application/vnd.cip4-jdf+xml' or 'application/vnd.cip4-jmf+xml' may describe content that has security implications beyond those described here.
[CIP4-JDF] CIP4 Job Definition Format (JDF) Specification, Release
1.1, Revision A, September 2002.
<http://www.cip4.org/documents/jdf_specifications/JDF1.1a.pdf>
[CIP4-JMF] CIP4 Job Messaging Format (JMF) - see chapter 5 'JDF Messaging with the Job Messaging Format' of [CIP4-JDF].
[CIP4-ORG] The International Cooperation for the Integration of
Processes in Prepress, Press, and Postpress (CIP4) is an international
worldwide standards body located in Switzerland.
<http://www.cip4.org>
[RFC2119] Bradner. Key words for use in RFCs to Indicate Requirement Levels, RFC 2119, March 1997.
[RFC2279] Yergeau. UTF-8, a Transformation Format of ISO 10646, RFC 2279, January 1998.
[RFC2781] Hoffman, Yergeau. UTF-16, an encoding of ISO 10646, RFC 2781, February 2000.
[RFC3023] Murata, St. Laurent, Kohn. XML Media Types, RFC 3023, January 2001.
[W3C-XML] Bray, Paoli, Sperberg-McQueen. Extensible Markup Language
(XML) 1.0, W3C XML, October 2000.
<http://www.w3.org/TR/REC-xml>
[IANA-CHAR] IANA Registry of Character Sets
ftp://ftp.iana.org/assignments/charset-reg/...
[IANA-MIME] IANA Registry of MIME Media Types
ftp://ftp.iana.org/assignments/media-types/...
[RFC2048] Freed, Klensin, Postel. MIME Part Four: Registration Procedures, RFC 2048, November 1996.
[RFC2277] Alvestrand. IETF Policy on Character Sets and Languages, RFC 2277, January 1998.
The authors wish to acknowledge the very significant contributions of Rainer Prosi (Heidelberg Digital) during the development of this document.
Please send comments directly to the authors (see below).
Tom Hastings Xerox Corporation 737 Hawaii St El Segundo, CA 90245 Phone: +1 310-333-6413 Fax: +1 310-333-5514 EMail: hastings@cp10.es.xerox.com Ira McDonald High North Inc 221 Ridge Ave Grand Marais, MI 49839 USA Phone: +1 906-494-2434 Email: imcdonald@sharplabs.com
Copyright (C) The Internet Society (2003). All Rights Reserved.
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 is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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."
[[RFC Editor: Please delete this section before RFC publication]]
25 January 2003 - draft-mcdonald-cip4-jdf-mime-00.txt
- Initial version - following guidelines in RFC 2048.