1、BSI Standards PublicationBS ISO/IEC 29500-3:2015Information technology Document description andprocessing languages OfficeOpen XML File FormatsPart 3: Markup Compatibility andExtensibilityBS ISO/IEC 29500-3:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO/I
2、EC29500-3:2015. Together with BS ISO/IEC 29500-1, BS ISO/IEC 29500-2and BS ISO/IEC 29500-4 it supersedes BS ISO/IEC 29500 PARTS 1-4:2012, which will be withdrawn upon publication of the remaining parts.The UK participation in its preparation was entrusted to Technical Committee IST/41, Document desc
3、ription and processing language.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institut
4、ion 2015.Published by BSI Standards Limited 2015ISBN 978 0 580 85467 5 ICS 35.060; 35.240.30 Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 July 2015.Amendme
5、nts/corrigenda issued since publicationDate T e x t a f f e c t e dBS ISO/IEC 29500-3:2015Reference numberISO/IEC 29500-3:2015(E)ISO/IEC 2015INTERNATIONAL STANDARDISO/IEC29500-3Fourth edition2015-07-01Information technology Document description and processing languages Office Open XML File Formats P
6、art 3: Markup Compatibility and Extensibility Technologies de linformation Description des documents et langages de traitement Formats de fichier “Office Open XML“ Partie 3: Compatibilit et extensibilit du balisage BS ISO/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2
7、015 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be reque
8、sted from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2015 All rights reservedBS IS
9、O/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) ISO/IEC 2015 All rights reserved i Contents Foreword .iii Introduction .v 1 Scope 1 2 Normative References . 2 3 Terms and Definitions 3 4 Notational Conventions . 4 5 General Description . 5 6 Overview . 6 7 MCE Elements and Attributes . 8 7.1 Introduction
10、8 7.2 Ignorable Attribute 8 7.3 ProcessContent Attribute 9 7.4 MustUnderstand Attribute . 9 7.5 AlternateContent Element 10 7.6 Choice Element . 11 7.7 Fallback Element . 11 8 Application-Defined Extension Elements .13 9 Semantic Definitions and Reference Processing Model 15 9.1 Overview . 15 9.2 St
11、ep 1: Processing the Ignorable and ProcessContent Attributes 16 9.3 Step 2: Processing the AlternateContent, Choice and Fallback Elements 17 9.4 Step 3: Processing the MustUnderstand Attribute and Creating the Output Document . 18 Annex A (informative) Examples .22 A.1 Syntactic Examples 22 A.1.1 Ge
12、neral 22 A.1.2 Ignorable Attribute: Multiple Prefixes Bound to a Namespace 22 A.1.3 Ignorable Attribute: Non-conformant Use . 22 A.1.4 ProcessContent Attribute: Multiple Prefixes Bound to a Namespace 23 A.1.5 ProcessContent Attribute: Non-conformant Use . 23 A.1.6 MustUnderstand Attribute: Non-confo
13、rmant Use . 23 A.1.7 AlternateContent Element: Future Extensibility . 24 A.2 Semantic Examples . 24 A.2.1 General 24 A.2.2 Ignorable Attribute . 24 A.2.3 Ignorable and ProcessContent Attributes. 25 A.2.4 Non-Ignorable and Non-Understood Namespace 27 A.2.5 MustUnderstand Attribute . 27 BS ISO/IEC 295
14、00-3:2015ISO/IEC 29500-3:2015(E) ii ISO/IEC 2015 All rights reserved A.2.6 AlternateContent Element 28 A.2.7 Ignorable Content Inside Application-Defined Extension Elements . 29 Annex B (informative) Validation Using NVDL 31 Bibliography .33 BS ISO/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) ISO/IEC 201
15、5 All rights reserved iii Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of Internationa
16、l Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with I
17、SO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical comm
18、ittee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75% of the national bodies casting a vote. Attention is drawn to th
19、e possibility that some of the elements of this standard may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 29500-3 was prepared by ISO/IEC JTC 1, Information technology, Subcommittee SC 34, Document description and p
20、rocessing languages. This fourth edition cancels and replaces the third edition (ISO/IEC 29500-3:2012). The major changes from the previous edition include: Specification of the core semantics in one place, and the interactions among semantic constructs and/or the processing model. Removal of the sp
21、ecification of namespace subsumption Expansion of examples, in particular, by providing output documents The intended semantics remains the same as long as namespace subsumption is not used. The major changes in the third edition included: Removed all traces of the concept of markup editor Removed t
22、he attributes PreserveAttributes and PreserveElements There were no major changes in the second edition. ISO/IEC 29500 consists of the following parts, under the general title Information technology Document description and processing languages Office Open XML File Formats: BS ISO/IEC 29500-3:2015IS
23、O/IEC 29500-3:2015(E) iv ISO/IEC 2015 All rights reserved Part 1: Fundamentals and Markup Language Reference Part 2: Open Packaging Conventions Part 3: Markup Compatibility and Extensibility Part 4: Transitional Migration Features BS ISO/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) ISO/IEC 2015 All right
24、s reserved v Introduction ISO/IEC 29500 specifies a family of XML schemas, collectively called Office Open XML, that define the XML vocabularies for word-processing, spreadsheet, and presentation office documents, as well as the packaging of office documents that conform to these schemas. The goal i
25、s to enable the implementation of the Office Open XML formats by the widest set of tools and platforms, fostering interoperability across office productivity applications and line-of-business systems, as well as to support and strengthen document archival and preservation, all in a way that is fully
26、 compatible with the existing corpus of Microsoft Office documents. BS ISO/IEC 29500-3:2015BS ISO/IEC 29500-3:2015INTERNATIONAL STANDARD ISO/IEC 29500-3:2015(E) ISO/IEC 2015 All rights reserved 1 Information technology Document description and processing languages Office Open XML File Formats Part 3
27、: Markup Compatibility and Extensibility (MCE) 1 Scope This Part of ISO/IEC 29500 defines a set of conventions for forward compatibility of markup specifications, applicable not only to Office Open XML specifications as described in Parts 1 and 4 of this Standard, but also to other markup specificat
28、ions. These conventions allow XML documents created by applications of later versions or extensions to be handled by applications of earlier versions. BS ISO/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) 2 ISO/IEC 2015 All rights reserved 2 Normative References The following referenced standards are indis
29、pensable for the application of this standard. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced standard (including any amendments) applies. XML, Tim Bray, Jean Paoli, Eve Maler, C. M. Sperberg-McQueen, and Franois Yergeau (editors).
30、Extensible Markup Language (XML) 1.0, Fifth Edition. World Wide Web Consortium. 2008. http:/www.w3.org/TR/2008/PER-xml-20080205/. Note: Implementations of this Part of ISO/IEC 29500 are not required to support features of XML introduced by the Fifth Edition. end note XML Base, Marsh, Jonathan. XML B
31、ase. World Wide Web Consortium. 2009. http:/www.w3.org/TR/2009/REC-xmlbase-20090128/ XML Information Set, John Cowan and Richard Tobin (editors). XML Information Set (Second Edition), 4 February 2004. World Wide Web Consortium. http:/www.w3.org/TR/2004/REC-xml-infoset-20040204/ XML Namespaces, Tim B
32、ray, Dave Hollander, Andrew Layman, and Richard Tobin (editors). Namespaces in XML 1.0 (Third Edition), 8 December 2009. World Wide Web Consortium. http:/www.w3.org/TR/2009/REC-xml-names-20091208/ BS ISO/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) ISO/IEC 2015 All rights reserved 3 3 Terms and Definitio
33、ns For the purposes of this standard, the following terms and definitions apply: 3.1 application configuration set of names of understood namespaces 3.2 application-defined extension element element defined by a markup specification, the attributes and content of which are not to be processed by an
34、MCE processor 3.3 markup configuration set of expanded names of application-defined extension elements 3.4 markup specification XML-based format specification that allows the use of elements and attributes in the MCE namespace 3.5 MCE processor software used to process XML documents containing MCE e
35、lements and attributes 3.6 mismatch incompatibility between the constraints specified by MCE elements and attributes, and the namespaces specified by an application configuration 3.7 understood namespace namespace, the elements and attributes of which a consuming application is able to process BS IS
36、O/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) 4 ISO/IEC 2015 All rights reserved 4 Notational Conventions The following typographical conventions are used in ISO/IEC 29500: 1) The first occurrence of a new term is written in italics. Example: The text in ISO/IEC 29500 is divided into normative and infor
37、mative categories. end example 2) The tag name of an XML element is written using a distinct style and typeface. Example: The bookmarkStart and bookmarkEnd elements specify end example 3) The name of an XML attribute is written using a distinct style and typeface. Example: The dropCap attribute spec
38、ifies end example 4) The value of an XML attribute is written using a constant-width style. Example: The attribute value of auto specifies end example Except for whole clauses or annexes that are identified as being informative, informative text that is contained within normative text is indicated i
39、n the following ways: 1) Example: code fragment, possibly with some narrative end example 2) Note: narrative end note 3) Rationale: narrative end rationale 4) Guidance: narrative end guidance BS ISO/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) ISO/IEC 2015 All rights reserved 5 5 General Description This
40、 clause is informative This Part of ISO/IEC 29500 is divided into the following subdivisions: Front matter (Clauses 15); Overview (Clause 6); Main body (Clauses 79); Annexes Examples are provided to illustrate possible forms of the constructions described. References are used to refer to related cla
41、uses. Notes are provided to give advice or guidance to implementers or programmers. The following form the normative pieces of this Part of ISO/IEC 29500: Clauses 14, and 79 The following make up the informative pieces of this Part of ISO/IEC 29500: Foreword Introduction Clauses 5 and 6 All annexes
42、All notes and examples End of informative text BS ISO/IEC 29500-3:2015ISO/IEC 29500-3:2015(E) 6 ISO/IEC 2015 All rights reserved 6 Overview This clause is informative This Part of ISO/IEC 29500 describes a set of XML elements and attributes, called MCE elements and attributes, the purpose of which i
43、s to enable producing applications to guide consuming applications in their handling of any XML elements and attributes in namespaces not understood by the consuming applications. MCE elements and attributes are intended to enable producing applications to use features added in new versions or exten
44、sions of a markup specification in the production of new documents, which nevertheless remain interoperable with consuming applications that do not understand these features. A producing application includes MCE elements and attributes in documents to indicate to a consuming application how it can a
45、djust the content of the document to exclude those features that are not compatible with the version of the markup specification that it understands, while at the same time allowing consuming applications that do understand these features to make full use of them. MCE elements and attributes define
46、particular types of compatibility and extension constructs, as summarized below: Namespaces can be declared to be ignorable, indicating that all elements and attributes in those namespaces can be disregarded by consuming applications as if they were not present in the input document, enabling gracef
47、ul degradation of the document functionality. This allows implementations to identify some markup as not core to the document content. Elements in ignorable namespaces can be marked for their content to be processed that would otherwise be ignored. This allows producing applications to prevent loss
48、of content nested within an element in an ignorable namespace when processed by consuming applications that do not understand that namespace but do understand the namespace(s) of the nested content. Namespaces can be declared that must be understood by consuming applications in order to process the
49、document. This allows producing applications to set minimum compatibility requirements for consuming applications. Alternative representations of document content can be specified. This allows producing applications to include content alternatives for consuming applications with differing sets of understood namespaces and corresponding capabilities. Application-defined extension elements enable producing applications to introduce addi
