CAN CSA-ISO IEC 26300A-2013 Information technology - Open Document Format for Office Applications (OpenDocument) v1 0 AMENDMENT 1 Open Document Format for Office Applications (Open.pdf

《CAN CSA-ISO IEC 26300A-2013 Information technology - Open Document Format for Office Applications (OpenDocument) v1 0 AMENDMENT 1 Open Document Format for Office Applications (Open.pdf》由会员分享，可在线阅读，更多相关《CAN CSA-ISO IEC 26300A-2013 Information technology - Open Document Format for Office Applications (OpenDocument) v1 0 AMENDMENT 1 Open Document Format for Office Applications (Open.pdf（112页珍藏版）》请在麦多课文档分享上搜索。

1、Information technology Open Document Format for Office Applications (OpenDocument) v1.0 AMENDMENT1:OpenDocument Format for Office Applications (OpenDocument) v1.1Amendment 1:2013 (IDT) toNational Standard of CanadaCAN/CSA-ISO/IEC 26300-08(ISO/IEC 26300:2006, IDT)NOT FOR RESALE. / PUBLICATION NON DES

2、TINE LA REVENTE.Standards Update ServiceAmendment 1:2013 toCAN/CSA-ISO/IEC 26300-08January 2013Title:Information technology Open Documen t Format for Office Applications (OpenDocument) v1.0 AMENDMENT1:OpenDocument Format for Office Applications (OpenDocument) v1.1Pagination:106 pages (iv preliminary

3、 and 102 text)To register for e-mail notification about any updates to this publicationgo to shop.csa.caclick on CSA Update ServiceThe List ID that you will need to register for updates to this publication is 2422268.If you require assistance, please e-mail techsupportcsagroup.org or call 416-747-22

4、33.Visit CSA Groups policy on privacy at csagroup.org/legal to find out how we protect your personal information.Reference numberISO/IEC 26300:2006/Amd.1:2012(E)ISO/IEC 2012INTERNATIONAL STANDARD ISO/IEC26300First edition2006-12-01AMENDMENT 12012-03-15Information technology Open Document Format for

5、Office Applications (OpenDocument) v1.0 AMENDMENT 1: Open Document Format for Office Applications (OpenDocument) v1.1Technologies de linformation Format de document ouvert pour applications de bureau (OpenDocument) v1.0 AMENDEMENT 1: Format de document ouvert pour applications de bureau (OpenDocumen

6、t) v1.1 ISO/IEC 26300:2006/Amd.1:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permissio

7、n in writing 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 ii ISO/IEC 2012 All rights reservedAmendment 1:2013 to CA

8、N/CSA-ISO/IEC 26300-08ISO/IEC 26300:2006/Amd.1:2012(E) ISO/IEC 2012 All rights reserved iiiForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are mem

9、bers of ISO or IEC participate 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 or

10、ganizations, governmental and 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. International Standards are drafted in accordance with the rules given in the ISO/

11、IEC Directives, Part 2. The main task of the joint technical committee 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

12、 % of the national bodies casting a vote. Attention is drawn to the possibility 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. Amendment 1 to ISO/IEC 26300:2006 was prepared by J

13、oint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 34, Document description and processing languages. This Amendment should be read in conjunction with ISO/IEC 26300:2006 and the associated Technical Corrigenda 1 and 2. The current edition of ISO/IEC 26300 should be unde

14、rstood by first applying the change specified in the Technical Corrigenda, then applying the changes specified in this Amendment. Amendment 1:2013 to CAN/CSA-ISO/IEC 26300-08ISO/IEC 26300:2006/Amd.1:2012Notation conventionsThe title of each change is the complete reference to the section or sub-sect

15、ion being modified. In all cases (except for an amendment inserting two new Appendices) the title begins with the section or sub-section number, the section or sub-section name, and the page number. In most cases the location of the amendment is more precisely indicated by a paragraph number or othe

16、r indicator. Paragraph numbers are determined by counting the number of paragraphs from the beginning of the section or sub-section in question, ignoring lists, tables and examples.In the case of amendments to the normative Relax-NG schema, the lines of the schema that are amended are indicated in i

17、talics below the heading. Schema line numbers refer to the amended schema. Other guidance on the intended application of an amendment may be given in italics below the heading.A change can contain any one or more of the following kinds of edits:Addition of text: New text is displayed in blue and is

18、underlined, as demonstrated here.Deletion of text: Deleted text is displayed in red and is struck-through, as demonstrated here.An ellipsis is occasionally used to indicate deliberate omission of fragments of the original text that are unchanged by this Amendment and would unreasonably extend the te

19、xt of this Amendment. ISO/IEC 2012 All rights reserved ivAmendment 1:2013 to CAN/CSA-ISO/IEC 26300-08ISO/IEC 26300:2006/Amd.1:2012(E)Front matter, p. 1Open Document Format for OfficeApplications (OpenDocument) v1.10(Second Edition)Committee Specification1, 19 Jul 2006OASIS Standard, 1 Feb 2007Docume

20、nt identifier:OpenDocument-v1.1ed2-.odtLocation:This Version: http:/www.oasis-open.org/committees/officePrevious Version: http:/docs.oasis-open.org/office/v1.0Specification URIsThis Version:http:/docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.odthttp:/docs.oasis-open.org/office/v1.1/OS/OpenDoc

21、ument-v1.1.pdfhttp:/docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.html.zipPrevious Version:http:/www.oasis-open.org/committees/download.php/19275/OpenDocument-v1.0ed2-cs1.odthttp:/www.oasis-open.org/committees/download.php/19274/OpenDocument-v1.0ed2-cs1.pdfLatest Version:http:/docs.oasis-open

22、.org/office/v1.1/OpenDocument-v1.1.odthttp:/docs.oasis-open.org/office/v1.1/OpenDocument-v1.1.pdfhttp:/docs.oasis-open.org/office/v1.1/OpenDocument-v1.1.html.zipLatest Approved Version:http:/docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.odthttp:/docs.oasis-open.org/office/v1.1/OS/OpenDocument

23、-v1.1.pdfhttp:/docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.html.zipTechnical Committee:OASIS Open Document Format for Office Applications (OpenDocument) TCChair:Michael Brauer, Sun Microsystems, Inc.Editors:Patrick Durusau, IndividualMichael Brauer, Sun Microsystems, Inc.Lars Oppermann, Sun

24、 Microsystems, Inc.Related Work:This specification supersedes OASIS OpenDocument v1.0.Declared XML Namespaces:A list of XML namespaces declared by this specification is available in section 1.3.Abstract:This is the specification of the Open Document Format for Office Applications (OpenDocument) form

25、at, an open, XML-based file format for office applications, based on OpenOffice.org XML OOo. ISO/IEC 2012 All rights reserved 1Amendment 1:2013 to CAN/CSA-ISO/IEC 26300-08ISO/IEC 26300:2006/Amd.1:2012(E)Status:This document was last revised or approved by the membership of OASISOASIS Open Document F

26、ormat for Office Applications (OpenDocument) Technical Committee on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.Technical Committee me

27、mbers should send comments on this specification to the Technical Committees email list. Others should send comments to the Technical Committee by using the “Send A Comment“ button on the Technical Committees web page at www.oasis-open.org/committees/office.For information on whether any patents hav

28、e been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (www.oasis-open.org/committees/office/ipr.php.The non-normative errata page for this speci

29、fication is located at www.oasisopen.org/committees/office. 1.4, “Relax-NG Schema”, schema fragment, p. 32The following text amends lines 3-4 and 9-10 of the normative Relax-NG schema, as reproduced in this section. 1.5, “Document Processing and Conformance”, paragraph 7, p. 34There are no rules reg

30、arding the elements and attributes that actually have to be supported by conforming applications, except that applications should not use foreign elements and attributes for features defined inby the OpenDocument schema. See also appendix D. 2.1.1, “Document Root Element Content Models”, paragraph 1

31、, p. 37The following text corrects an editorial error in ISO/IEC 26300:2006/Cor 1, in which part of the text of the sentence inserted at the end of the paragraph is missing.The content models of the five root elements is summarized in the following table. Note that may contain all supported top-leve

32、l elements. All four subdocument root elements together contain the same information as an element that contains the same subdocument root elements.2 ISO/IEC 2012 All rights reserved1234567891011Amendment 1:2013 to CAN/CSA-ISO/IEC 26300-08ISO/IEC 26300:2006/Amd.1:2012(E) 2.1.1, table following parag

33、raph 1, p. 37The following text amends the heading of the second column of the table.meta-data 2.3.1, “Text Documents”, sub-section “Text Document Content Model”, schema fragment, p. 42The following text inserts a new line (line 179 of the amended schema) in the definition of pattern “text-content”

34、in the normative Relax-NG schema, as reproduced in this section. 2.3.1, “Text Documents”, following sub-section “Global Text Documents”, p. 42The following text inserts a new sub-section, including reproduction of a new pattern definition “office-text-attlist” inserted into the normative Relax-NG sc

35、hema (lines 201-207 of the amended schema).Use Soft Page BreaksThe text:use-soft-page-breaks attribute specifies whether the document contains soft page breaks. A soft page break is a page break that has been included by a page oriented processor at a position where the document itself does not incl

36、ude a page break (e.g. by using the fo:break-before and fo:break- after formatting properties described in section 15.5.2). Soft page breaks are specified by the elements described in sections 4.7 and 5.1.1:Soft Page breaks.The use of the elements is always optional. An application generating the fo

37、rmat may include the element if it has computed a paginated layout. A consuming application may handle the element while computing the layout, but it shall not depend on its existence. Soft page breaks are only supported within text documents.A generating application that stores soft page breaks sha

38、ll indicate this by setting the text:use-page- breaks attribute to true . A generating application that does not store soft page breaks shall indicate that by omitting this attribute, or by setting it to false . ISO/IEC 2012 All rights reserved 3170171172173174175176177178179180181182183184185186187

39、188189190Amendment 1:2013 to CAN/CSA-ISO/IEC 26300-08An application that does not support pagination and soft page-breaks, that modifies an OpenDocument file, which includes soft page-breaks, shall at least set the text:use-page-breaks attribute to false (or remove it). It should also remove the ele

40、ments from the document but is not required to do so.An application that computes a paginated layout of a document should provide a facility to turn on export of soft page breaks for the purposes of consistent page breaks and for proper conversion to digital talking book formats (such as DAISY ). Fo

41、r elements that appear within table rows, the maximum number of elements that appear within the single table cells determines the number of page breaks that appear within the table row. The elements contained in each cell determine the positions where these page breaks appear within the cell content

42、.Similarly, elements that appear within text boxes and other content displayed outside the text flow, do not start a new page, but only indicate where the text-boxs content breaks between two pages. 2.5, “Scripts”, paragraph 2, p. 50Scripts do not imply a scripting language or an object model. A scr

43、ipt can for instance operate on the Document Object Model (DOM) composed from the XML representation of a document in OpenDocument format (see DOM2), operate on the Document Object Model (DOM) of a document in OpenDocument format or on an application specific API. 3, “Meta Data Elements”, section ti

44、tle, p. 56The section title is revised as follows.3 Metad Data Elements 3.1.18, “Document Statistics”, schema fragment, pp. 6263The following text moves five lines of the definition of the pattern “office-meta-data” to a new position (lines 771-775 of the amended schema) in the normative Relax-NG sc

45、hema, as reproduced in this section.4 ISO/IEC 2012 All rights reserved201202203204205206207744745766767768769770771772773774775ISO/IEC 26300:2006/Amd.1:2012(E)Amendment 1:2013 to CAN/CSA-ISO/IEC 26300-08ISO/IEC 26300:2006/Amd.1:2012(E). 4.3.2, “List Item”, paragraph 1, p. 71List items contain the te

46、xtual content of a list. A element can contain paragraphs, headings, lists or soft page breaks. A list item cannot contain or lists. A list item cannot contain headings or tables. 4.3.2, “List Item”, pp. 71-72The following text inserts a new line in the definition of the pattern “text-list-item-cont

47、ent” (line 994 of the amended schema) in the normative Relax-NG schema, as reproduced in this section. 4.3.2, “List Item”, sub-section “Formatted number”, example, p. 72This is the first list itemThis is a continuation of the first list item.This is the second list item. It contains a sub list. ISO/

48、IEC 2012 All rights reserved 5776777778779780816817818819820821822979980981982983984985986987988989990991992993994995996997Amendment 1:2013 to CAN/CSA-ISO/IEC 26300-08This is a sub list item.This is a sub list item.This is a sub list item.This is the third list item 4.4.3, “DDE Source”, following pa

49、ragraph 1, p. 77The following text inserts a new paragraph following existing paragraph 1 and preceding the schema fragment.See section 12.6 for the use of DDE connections. 4.6.4, “Deletion”, second bulleted list, p. 80 If the change mark is inside a paragraph, insert the text content of the element as if the beginning and final tags were missing. If the change mark is inside a header, proceed as above, except adapt the end tags to matchinserted tags t