1、 Access to Additional Content for ECMA 388, Dated: June 2009 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the Copyright holder of t
2、his document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. ECMA 388 Extra Files Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer S SHOULD; O OPTIONAL) and a unique rule number of th
3、e form m.n, where m and n are positive integers, all enclosed in brackets (). Example: M1.2 is a MUST requirement, S2.4 is a SHOULD requirement, and O3.9 is a MAY requirement. end example For convenient reference, these rules are collected in Annex F. 2.2 Implementation Conformance This Standard inc
4、ludes the implementation requirements that systems processing OpenXPS content must satisfy in order to achieve conforming interoperability. An implementation is a consumer, or a producer, or both a consumer and a producer. In order for a consumer to be considered conformant, the following rules appl
5、y: It MUST interpret and process the contents of OpenXPS Document instances in a manner conforming to this Standard M0.1. A consumer is NOT REQUIRED to interpret or process all of the content in an OpenXPS Document instance M0.2. It SHOULD instantiate an error condition when OpenXPS Document content
6、 not conforming to this Standard is encountered S0.1. It MUST NOT instantiate an error condition in response to OpenXPS Document content conforming to this Standard M0.3. When “OPTIONAL” or “RECOMMENDED” features contained within OpenXPS Document instances are accessed by a consumer, the consumer MU
7、ST interpret and process those features in a manner conforming to this Standard M0.4. In order for a producer to be considered conformant, the following rules apply: 2. Conformance ECMA-388 4 First Edition, June 2009 Any OpenXPS Document instances it creates MUST conform to this Standard M0.5. It MU
8、ST NOT introduce any non-conforming OpenXPS Document content when modifying an OpenXPS Document instance M0.6. When a producer chooses to use an “OPTIONAL” or “RECOMMENDED” feature in an OpenXPS Document instance, then the producer MUST create or modify that feature in a manner conforming to this St
9、andard M0.7. 2.3 Instantiating Error Conditions OpenXPS Documents are intended to address the requirements of a wide range of scenarios. The methods and effects of instantiated error conditions in response to conformance rule violations are implementation-defined. Note: Implementers are encouraged t
10、o instantiate error conditions to indicate non-conformant OpenXPS Documents where users can be expected to be able to act on the error information. Implementers are strongly encouraged to fail gracefully when processing non-compliant OpenXPS Documents to ensure that non-compliant OpenXPS Document in
11、stances, and non-compliant OpenXPS producers, do not proliferate. end note ECMA-388 3. Normative References First Edition, June 2009 5 3. Normative References The following normative documents contain provisions, which, through reference in this text, constitute provisions of this Standard. For date
12、d references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references
13、, the latest edition of the normative document referred to applies. Members of ISO and IEC maintain registers of currently valid International Standards. BNF of Generic URI Syntax. World Wide Web Consortium. http:/www.w3.org/Addressing/URL/5_URI_BNF.html ECMA-376, 1stedition, Office Open XML File Fo
14、rmats (December 2006), Part 2, “Open Packaging Conventions“, which is commonly referred to as OPC. ECMA-376, 1stedition, Office Open XML File Formats (December 2006), Part 5, “Markup Compatibility and Extensibility“. Extensible Markup Language (XML) 1.0 (Fourth Edition). Bray, Tim, Eve Maler, Jean P
15、aoli, C. M. Sperberg-McQueen, and Franois Yergeau (editors). World Wide Web Consortium. 2006. http:/www.w3.org/TR/2006/REC-xml-20060816/ HTML 4.01 Specification. Jacobs, Ian, Arnaud Le Hors, and Dave Raggett (editors). World Wide Web Consortium. 1999. http:/www.w3.org/TR/1999/REC-html401-19991224/ I
16、CC.1:2001-04 File Format for Color Profiles. International Color Consortium. 2001. http:/www.color.org/ICC_Minor_Revision_for_Web.pdf IEC 61966:1999, Multimedia systems and equipment - Colour measurement and management - Part 2-1: Colour management - Default RGB colour space - sRGB IEC 61966:2003, M
17、ultimedia systems and equipment - Colour measurement and management - Part 2-2: Colour management - Extended RGB colour space - scRGB ISO 15076-1:2005, Image technology colour management Architecture, profile format, and data structure Part 1: Based on ICC.1:2004-10 ISO/IEC 2382-1:1993, Information
18、technology Vocabulary Part 1: Fundamental terms. ISO/IEC 10646:2003 (all parts), Information technology Universal Multiple-Octet Coded Character Set (UCS). ISO/IEC 14496-22:2007 Information technology Coding of audio-visual objects Part 22: Open Font Format ISO/IEC 19775-1:2008 Information technolog
19、y Computer graphics and image processing Extensible 3D (X3D) Part 1: Architecture and base components. ISO/IEC 19776-1:2005 Information technology Computer graphics and image processing Extensible 3D (X3D) encodings Part 1: XML encoding. 3. Normative References ECMA-388 6 First Edition, June 2009 IS
20、O/IEC 19776-2:2008 Information technology Computer graphics and image processing Extensible 3D (X3D) encodings Part 2: Classic VRML encoding. ISO/IEC 19776-3:2007 Information technology Computer graphics, image processing and environmental representation Extensible (X3D) encodings Part 3: Compressed
21、 binary encoding. ITU-T T.81, ISO/IEC 10918-1 ITU-T (former CCITT) Recommendation Information technology - Digital compression and coding of continuous-tone still images Requirements and Guidelines) ITU-T T.832 Information technology JPEG XR Image Coding Specification Part 2: Image coding specificat
22、ion Note: This standard is technically aligned to ISO/IEC IS 29199-2:2009 Part 2: JPEG XR image coding specification, which is currently under ballot. end note JEITA CP-3451, Exchangeable image file format for digital still cameras; Exif Version 2.2, April, 2002. http:/www.jeita.or.jp Namespaces in
23、XML 1.0 (Second Edition). Bray, Tim, Dave Hollander, Andrew Layman, and Richard Tobin (editors). World Wide Web Consortium. 2006. http:/www.w3.org/TR/2006/REC-xml-names-20060816/ Portable Network Graphics (PNG) Specification. Duce, David (editor). Second Edition. World Wide Web Consortium. 2003. htt
24、p:/www.w3.org/TR/2003/REC-PNG-20031110 RFC 2045, Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. Borenstein, N., and N. Freed. The Internet Society. 1996. http:/www.ietf.org/rfc/rfc2045.txt. RFC 2119 Key words for use in RFCs to Indicate Requirement Levels.
25、Bradner, S. The Internet Society. 1997. http:/www.ietf.org/rfc/rfc2119.txt RFC 3066 Tags for the Identification of Languages. Alvestrand, H. The Internet Society. 2001. http:/www.ietf.org/rfc/rfc3066.txt RFC 4234 Augmented BNF for Syntax Specifications: ABNF.Crocker, D. (editor). The Internet Societ
26、y. 2005. http:/www.ietf.org/rfc/rfc4234.txt TIFF, Revision 6.0. Adobe Systems Incorporated. 1992. http:/ Unicode Character Database, Revision 4.0.0. Davis, Mark and Ken Whistler. The Unicode Consortium. 2003. http:/www.unicode.org/Public/4.0-Update/UCD-4.0.0.html The Unicode Standard, Version 4.0. T
27、he Unicode Consortium. Boston, MA: Addison-Wesley, 2003, ISBN 0-321-18578-1. XML Base. Marsh, Jonathan. World Wide Web Consortium. 2001. http:/www.w3.org/TR/2001/REC-xmlbase-20010627/ XML Schema Part 1: Structures, Second Edition. Beech, David, Murray Maloney, Noah Mendelsohn, and Henry S. Thompson
28、(editors). World Wide Web Consortium. 2004. http:/www.w3.org/TR/2004/REC-xmlschema-1-20041028/ XML Schema Part 2: Datatypes, Second Edition. Biron, Paul V. and Ashok Malhotra (editors). World Wide Web Consortium. 2004. http:/www.w3.org/TR/2004/REC-xmlschema-2-20041028/ ECMA-388 4. Definitions First
29、Edition, June 2009 7 4. Definitions For the purposes of this Standard, the following definitions apply. Terms explicitly defined in this Standard are not to be presumed to refer implicitly to similar terms defined elsewhere. alpha blending Blending two elements when rendering. consumer A piece of so
30、ftware or a device that interprets and processes OpenXPS packages. content structure The set of markup elements that allow expression of well-understood semantic blocks, such as paragraphs, tables, lists, and figures. content type Describes the type of content stored in a part. Content types define
31、a media type, a subtype, and an optional set of parameters, as defined in RFC 2045. coordinate space, effective The default coordinate space (X,Y in the upper-left corner, units of 1/96“) as modified by any RenderTransform or Transform attributes of the current element and any ancestor elements. con
32、tour intersection point The intersection of the flat line ending a dash and the contour of the shape. device A piece of hardware, such as a printer or scanner, that performs a single function or a set of functions. digital signature, broken A digital signature that conforms to the OpenXPS Document s
33、igning rules but does not meet the digital signature validity. digital signature, compliant A digital signature that conforms to the signing rules described in the OpenXPS Document signing policy, regardless of signature validity. digital signature, incompliant A digital signature that does not conf
34、orm to the OpenXPS Document signing rules. digital signature, questionable A compliant digital signature for which a problem arises during validation of that signature. (Digital signatures may be represented as questionable when the implementation cannot contact the certificate authority to validate
35、 its authenticity, or when the markup contains markup compatibility elements and attributes that can change the representation of the signed content.) digital signature, valid A compliant digital signature that is not a broken digital signature or questionable digital signature. document content A d
36、ocument structural concept that identifies each block of individually readable content in an OpenXPS Document. document outline A document structural concept that contains a structured index of the content in an OpenXPS Document, much like a table of contents. driver A producer that has specific kno
37、wledge of the consumer of the OpenXPS Document. fixed payload A payload that is rooted with a FixedDocumentSequence part. fixed payload root The root of a fixed payload is the FixedDocumentSequence part. 4. Definitions ECMA-388 8 First Edition, June 2009 FixedDocument part A common, easily indexed r
38、oot for all pages within an OpenXPS Document. FixedDocumentSequence part The part that assembles a set of FixedDocument parts within the fixed payload. FixedPage part The part that contains all of the visual elements to be rendered on a page. implementation-defined behavior Behavior specified by eac
39、h implementation and not by this Standard. named color An industry-defined color specification that identifies a particular color in a well-defined color system, usually for purposes of printing. named element An element in the document structure markup that refers to an element in the fixed-page ma
40、rkup with a specified name. OpenXPS Document A package that contains a discoverable fixed payload and is a format for storing paginated documents defined by the OpenXPS Standard. OpenXPS Document StartPart relationship The specific relationship type that identifies the root of a fixed payload within
41、 an OpenXPS Document. package A logical entity that holds a collection of parts. package model Defines a package abstraction that holds a collection of parts. package relationship A relationship whose target is a part and whose source is the package as a whole. Package relationships are found in the
42、 package relationships part named “/_rels/.rels”. part A stream with a MIME content type and associated common properties. Typically corresponds to a file (as on a file system) or a resource (as in an HTTP URI). part name A part name is used to refer to a part in the context of a package, typically
43、as part of a URI. By definition, the part name is the path component of a pack URI. payload A complete collection of interdependent parts and relationships within a package. physical model Defines the mapping between the components of the package model to the features of a particular physical format
44、 based on the ZIP specification. piece A portion of a part. Pieces of different parts can be interleaved together. The individual pieces are named using a unique mapping from the part name. Pieces are not addressable in the package model. primary fixed payload root The fixed payload root that is ref
45、erenced by the OpenXPS package StartPart relationship. PrintTicket part A PrintTicket part provides the settings used when a package is printed. PrintTicket parts can be attached to the entire package and/or at lower levels in the structure, such as individual pages. producer A piece of software or
46、a device that creates or modifies OpenXPS packages. property A characteristic of a markup element. ECMA-388 4. Definitions First Edition, June 2009 9 property attribute An OpenXPS Document property value, commonly expressed or referenced using XML attribute syntax. property element An OpenXPS Docume
47、nt property value, commonly expressed or referenced using XML child element syntax. property value The value of a property, expressed as an XML attribute, an XML child element, or an entry in the resource dictionary. relationships A relationship represents a connection between a source part and a ta
48、rget part in a package. Relationships make the connections between parts directly discoverable without looking at the content in the parts, and without altering the parts themselves. See also, package relationship. relationships part A part containing an XML representation of relationships. required
49、 part A part, such as an image or font, that is referenced from other parts, and is required for valid processing of the referencing part. resource definition A shareable property value, with a name, defined within a resource dictionary. Any property value definable by fixed page markup can be held in a resource dictionary. Each resource
