BS PD ISO IEC TR 30114-1-2016 Information technology Extensions of Office Open XML file formats Guidelines《信息技术 Office Open XML文件格式扩展 指南》.pdf

《BS PD ISO IEC TR 30114-1-2016 Information technology Extensions of Office Open XML file formats Guidelines《信息技术 Office Open XML文件格式扩展 指南》.pdf》由会员分享，可在线阅读，更多相关《BS PD ISO IEC TR 30114-1-2016 Information technology Extensions of Office Open XML file formats Guidelines《信息技术 Office Open XML文件格式扩展 指南》.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、PD ISO/IEC TR 30114-1:2016 Information technology Extensions of Office Open XML file formats Part 1: Guidelines BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06PD ISO/IEC TR 30114-1:2016 PUBLISHED DOCUMENT National foreword This Published Document is the UK implemen

2、tation of ISO/ IEC TR 30114-1:2016. The UK participation in its preparation was entrusted to Technical Committee IST/41, Document description and processing language. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport

3、to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 91228 3 ICS 35.060; 35.240.30 Compliance with a British Standard cannot confer immunity from legal

4、obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 December 2016. Amendments/corrigenda issued since publication Date Text affectedPD ISO/IEC TR 30114-1:2016 Information technology Extensions of Office Open XML file formats Part

5、1: Guidelines Technologies de linformation Extensions de formats de fichiers Office Open XML Partie 1: Lignes directrices TECHNICAL REPORT ISO/IEC TR 30114-1 First edition 2016-12-15 Reference number ISO/IEC TR 30114-1:2016(E) ISO/IEC 2016 PD ISO/IEC TR 30114-1:2016ii ISO/IEC 2016 All rights reserve

6、d COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2016, Published in Switzerland 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 i

7、ntranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightis

8、o.org www.iso.org ISO/IEC TR 30114-1:2016(E)PD ISO/IEC TR 30114-1:2016ISO/IEC TR 30114-1:2016(E)Foreword iv Introduction v 1 Scope . 1 2 Normative references 1 3 Terms and definitions . 1 4 Adding markup or other data to OOXML documents 1 4.1 General . 1 4.2 Markup Compatibility and Extensibility (M

9、CE): Ignorable elements and attributes (ISO/IEC 29500-3) . 1 4.3 MCE: Alternate Content Blocks (ISO/IEC 29500-3) 2 4.4 MCE: Application-defined extension elements (ISO/IEC 29500-3) 3 4.5 Embedding foreign Open Packaging Conventions (OPC) parts 4 Bibliography 5 ISO/IEC 2016 All rights reserved iii Co

10、ntents PagePD ISO/IEC TR 30114-1:2016ISO/IEC TR 30114-1:2016(E) 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 particip

11、ate in the development of International 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 a

12、nd non-governmental, in liaison with ISO 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. The procedures used to develop this document and those intended for its further maintenance are described in

13、the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibi

14、lity that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO l

15、ist of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformit y assessment, as

16、well as information about ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html. The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 34, Document description a

17、nd processing languages. A list of all parts in the ISO/IEC 30114 series, published under the general title Information technology Extensions of Office Open XML file formats, can be found on the ISO website.iv ISO/IEC 2016 All rights reservedPD ISO/IEC TR 30114-1:2016ISO/IEC TR 30114-1:2016(E) Intro

18、duction ISO/IEC 29500 was designed to allow the addition of markup and other data to Office Open XML (OOXML) documents, and to allow OOXML applications unaware of such markup and date to provide reasonable results. ISO/IEC TR 30114-1 provides guidance for such additions, and also specifies a collect

19、ion of such additions. ISO/IEC 2016 All rights reserved vPD ISO/IEC TR 30114-1:2016PD ISO/IEC TR 30114-1:2016Information technology Extensions of Office Open XML file formats Part 1: Guidelines 1 Scope This document gives guidelines for the use of extensibility mechanisms in ISO/IEC 29500 (Office Op

20、en XML). In particular, it makes clear which of these mechanisms supports lossless round tripping. 2 Normative references The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edit

21、ion cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. There are no normative references in this document. 3 Terms and definitions No terms and definitions are listed in this document. ISO and IEC maintain terminological databases

22、 for use in standardization at the following addresses: IEC Electropedia: available at http:/ /www.electropedia.org/ ISO Online browsing platform: available at http:/ /www.iso.org/obp 4 Adding markup or other data to OOXML documents 4.1 General There are two main ways to add extra markup or other da

23、ta to Office Open XML (OOXML) documents: Using the extension mechanisms described in ISO/IEC 29500-3, Markup Compatibility and Extensibility (MCE) offers three primary mechanisms for extending XML files, each with its own advantages and disadvantages. Embedding foreign Open Packaging Conventions (OP

24、C) parts. 4.2 Markup Compatibility and Extensibility (MCE): Ignorable elements and attributes (ISO/IEC 29500-3) The most commonly used extension mechanism, marking elements or attributes as ignorable, allows lightweight additions to be made to existing markup. A good use of ignorable markup would be

25、 the addition of a custom metadata tag onto a paragraph in a WordprocessingML document. This could be accomplished by declaring a custom namespace, marking it as ignorable, and adding the attribute to the p element in that namespace. The relevant portions of the resulting document.xml part might res

26、emble the following: TECHNICAL REPORT ISO/IEC TR 30114-1:2016(E) ISO/IEC 2016 All rights reserved 1PD ISO/IEC TR 30114-1:2016ISO/IEC TR 30114-1:2016(E)hello Ignorable markup can be used anywhere in XML parts and requires minimal markup. It allows custom markup to be added to documents while retainin

27、g the documents conformance with the standard and allowing it to be opened by a third-party application without errors. However, ignorable elements and attributes will almost definitely be lost if files are round tripped (i.e., opened and saved again) in an application that does not understand them,

28、 as there is no requirement for applications to persist ignorable markup, and typically unknown ignorable markup is stripped during file load. 4.3 MCE: Alternate Content Blocks (ISO/IEC 29500-3) While ignorable constructs allow markup to be added to documents easily, Alternate Content Blocks (ACBs)

29、allow existing markup to be replaced, with the replacement targeted at particular consumers that understand it. A good use of ACBs would be in developing an application that preferred to use the Open Document Format (ODF) in WordprocessingML paragraph markup. When creating files, the application wou

30、ld continue to write OpenXML markup in order to be compliant to the standard, but would also provide ODF markup in an ACB. When opening files, the application would disregard the OOXML fallback markup and only read the ODF. The resulting document.xml part for a document with text stored in such a wa

31、y might appear as shown below (note that, for simplicity, all ODF namespaces are merged into one):This document is stored in two formats. This document is stored in two 2 ISO/IEC 2016 All rights reservedPD ISO/IEC TR 30114-1:2016ISO/IEC TR 30114-1:2016(E)formats. ACBs allow for the replacement of ex

32、isting markup for consumers that understand it. Much like ignorables, there is no requirement for applications to preserve ACBs on round-tripping operations, so data can be lost if third-party applications are used to open and save files. 4.4 MCE: Application-defined extension elements (ISO/IEC 2950

33、0-3) Application-defined extension elements essentially allow markup designers to put “this space left for future expansion” elements into their formats. Syntactically, these are similar to ignorable elements but, because they only appear at predefined locations, markup consumers can easily keep tra

34、ck of unknown extension elements, which makes round tripping a simpler proposition. In ISO/IEC 29500-1, SpreadsheetML is the only markup that utilizes extension elements (see extLst in ISO/IEC 29500-1). extLst elements occur at several predefined points in SpreadsheetML and allow the markup to be ex

35、tended in a manner that permits round tripping. A good use of SpreadsheetML s extension elements would be a spreadsheet application whose developers wished to add the ability for cells to be denoted as model inputs or outputs. Such an application could use these tags at runtime and, if users were to

36、 round trip the files in other applications, the markup would be preserved. The CT_Cell type in SpreadsheetML contains an extLst element, so this will be an acceptable extension point. It contains an unbounded collection of ext elements, and the developer can add an ext with the developers extension

37、s markup. The resulting sheetData for a given spreadsheet might look something like the following:1234 Specifies the interest rate to be passed into amortisation model. Because consuming spreadsheet applications understand that this data is attached at a cell level, this metadata remains with the ce

38、ll when it is moved around the sheet via cut/paste or through row/column insertion or deletions above it. Note that some implementations can parse through application-defined- extension elements and modify constructs within them Microsoft Excel, for example, will look for any sqref elements in the n

39、amespace http:/ / It assumes that they will contain spreadsheet row/column references and adjusts them appropriately if that referenced cell area is moved around at runtime. Application-defined extension elements are only usable in locations pre-defined by a markup language, but allow for data prese

40、rvation in round-tripping scenarios. ISO/IEC 2016 All rights reserved 3PD ISO/IEC TR 30114-1:2016ISO/IEC TR 30114-1:2016(E) 4.5 Embedding foreign Open Packaging Conventions (OPC) parts Markup consumers are able (but not required) to preserve OPC parts with unrecognized relationship types during save

41、 operations. Such foreign parts are best suited to data (either binary or XML) that the creator desires to be preserved during round-tripping operations. One good use of a foreign part would be for an embedded video file attached to a WordprocessingML document. This involves three steps: Firstly, th

42、e file is added to the OPC package: Secondly, a relationship item is added to the /_rels/.rels part. Relationships in this part are known as “package relationships,” since the source is the package as a whole.Thirdly, an element is added to the /Content_Types.xml stream, unless an appropriate elemen

43、t is already present.The content will likely be preserved on round tripping through non-understanding applications, and because there is no requirement to serialize it into XML, this extension mechanism is well-suited to binary data such as video or images. A second good use of a foreign part would

44、be to embed richer metadata than supported in the Core Properties part of an OPC package (ISO/IEC 29500-2) or the Custom Properties part of an OOXML document (ISO/IEC 29500-1). For example, an ONIX for Books record could be embedded in the package for a WordProcessingML document using the same appro

45、ach as outlined above. Although the ONIX record would be in XML, applications would not be required to parse or understand the record. For an ONIX record in a part with name example_ONIX.xml, an appropriate location would be in a folder called “meta”. An appropriate package relationship would be:If

46、not already present in the /Content_Types.xml stream, the following addition would be appropriate:4 ISO/IEC 2016 All rights reservedPD ISO/IEC TR 30114-1:2016ISO/IEC TR 30114-1:2016(E) Bibliography 1 Document Interoperability Initiative (DII) Workshop on MCE - Redmond, WA. September 18, 2009 https:/

47、 / 2 Excel (.xlsx) Extensions to the Office Open XML SpreadsheetML File Format https:/ /msdn. 3 ISO/IEC 26300, Information technology Open Document Format for Office Applications (OpenDocument) v1.0 4 ISO/IEC 29500-1, Information technology Document description and processing languages Office Open

48、XML File Formats, Part 1: Fundamentals and Markup Language Reference 5 ISO/IEC 29500-2, Information technology Document description and processing languages Office Open XML File Formats Part 2: Open Packaging Conventions 6 ISO/IEC 29500-3, Information technology Document description and processing languages Office Open XML File Formats Part 3: Markup Compatibility and Extensibility 7 Word Extensions to the Office Open XML. (.docx) File Format https:/ /msdn.microsoft. com/en-us/library/dd773189.aspx 8 Office Drawing Extensions to Office Open XML Structure https:/ /msdn.microsoft. com/en-us/