CAN CSA-ISO IEC 15938-1A-2006 Information technology - Multimedia content description interface - Part 1 Systems AMENDMENT 1 Systems extensions.pdf

1、 Reference numberISO/IEC 15938-1:2002/Amd.1:2005(E)ISO/IEC 2005INTERNATIONAL STANDARD ISO/IEC15938-1First edition2002-07-01AMENDMENT 12005-02-15Information technology Multimedia content description interface Part 1: Systems AMENDMENT 1: Systems extensions Technologies de linformation Interface de de

2、scription du contenu multimdia Partie 1: Systmes AMENDEMENT 1: Extensions des systmes Amendment 1:2006 toNational Standard of CanadaCAN/CSA-ISO/IEC 15938-1:04Amendment 1:2005 to In ternational Standard ISO/IEC 15938-1:2002 has been adopted withoutmodification (IDT) as Amendment 1:2006 to CAN/CSA-ISO

3、/IEC 15938-1:04. This Amendment was reviewedby the CSA Technical Committee on Information Technology (TCIT) under the jurisdiction of the StrategicSteering Committee on Information Technology and deemed acceptable for use in Canada.December 2006ISO/IEC 15938-1:2002/Amd.1:2005(E) PDF disclaimer This

4、PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept there

5、in the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the

6、 PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. ISO/IEC 2005 All rights re

7、served. 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 permission in writing from either ISO at the address below or ISOs member body in the country of the requ

8、ester. 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 2005 All rights reservedAmendment 1:2006 toCAN/CSA-ISO/IEC 15938-1:04ISO/IEC 15938-1:2002/Amd.1:2005(E) ISO/IEC 2005 All rights reserved iiiFo

9、reword 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 International Standards through technica

10、l 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 ISO and IEC, also take part i

11、n 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 committee is to prepare Internat

12、ional 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 the possibility that some of

13、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 15938-1:2002 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding

14、of audio, picture, multimedia and hypermedia information. Amendment 1:2006 toCAN/CSA-ISO/IEC 15938-1:04ISO/IEC 15938-1:2002/Amd.1:2005(E) iv ISO/IEC 2005 All rights reservedIntroduction This document specifies the first Amendment to the Systems (MDS) part of ISO/IEC 15938. Note: this document preser

15、ves the sectioning of ISO/IEC 15938-1 Systems. The text and figures given below are additions and/or modifications to those corresponding sections in ISO/IEC 15938-1. All figures and tables shall be renumbered due to the addition of several figures and tables. Amendment 1:2006 toCAN/CSA-ISO/IEC 1593

16、8-1:04ISO/IEC 15938-1:2002/Amd.1:2005(E) ISO/IEC 2005 All rights reserved 1Information technology Multimedia content description interface Part 1: Systems AMENDMENT 1: Systems extensions Add the following reference in Clause 2: RFC 1950, ZLIB Compressed Data Format Specification version 3.3. Add the

17、 following definition at the end of subclause 3.1.2.2.5: ReservedBitsZero: a binary syntax element whose length is indicated in the syntax table. The value of each bit of this element shall be “0”. These bits may be used in the future for ISO/IEC defined extensions. Add the following definitions to

18、subclause 3.2 (keep alphabetical order): initial schema The schema that is known by the decoder before the decoding process starts. additional schema A schema that can be updated after the start of the decoding process. schema update unit Information in an access unit, conveying a schema or a portio

19、n thereof. Schema update units provide the means to modify the current decoder schema knowledge. description fragment reference A reference to a description fragment. Note - For instance, a fragment reference can be a URI which serves to locate the fragment on the world wide web. fragment reference

20、short term for description fragment reference. fragment reference resolver An entity that is capable of resolving the fragment reference provided in the fragment update payload. fragment reference marker A specific information used to describe a deferred fragment reference, which is present within t

21、he current description tree. It consists of a fragment reference, the name and type of the top most element of the referenced fragment. fragment reference format An encoding format of fragment references. Amendment 1:2006 toCAN/CSA-ISO/IEC 15938-1:04ISO/IEC 15938-1:2002/Amd.1:2005(E) 2 ISO/IEC 2005

22、All rights reserveddeferred fragment reference A fragment reference that can be resolved at any time by the application using the terminal. non-deferred fragment reference A fragment reference that shall be resolved by the terminal at the composition time of the access unit containing the fragment r

23、eference. optimised decoder A decoder associated to a type and dedicated to certain encoding methods better suited than the generic ones. type codec Synonym to optimised decoder. fixed optimised decoder An optimised decoder used to decode either a complex type or a simple type. Fixed optimised decod

24、ers are set up at decoder initialisation phase and their mapping to types cant be modified during binary description stream lifetime. advanced optimised decoder An optimised decoder used to decode a simple type. Advanced optimised decoders parameters and their mappings to types can be modified durin

25、g binary description stream lifetime. advanced optimised decoder instance An advanced optimised decoder initialised and ready to be used for the decoding of some data types. Note - There can be several instances of the same advanced optimised decoder with different or identical parameters. advanced

26、optimised decoder type The type, identified by a URI, of an advanced optimised decoder. advanced optimised decoder instances table A table of all the advanced optimised decoders available at a certain instant in time. contextual optimised decoder An optimised decoder which behavior is dependent on t

27、he current context of the decoding. Note - For instance, the ZLib optimised decoder (see Clause 9) is a contextual optimised decoder. Note - Upon certain events, the context must be reset. Upon a certain command or events they are flushed to release their contents. Only contextual optimised decoders

28、 are flushable. advanced optimised decoder parameters The parameters of an advanced optimised decoder. contextual optimised decoder reset An operation that resets the optimised decoder to put it in a defined initial state. All contextual information is discarded. skippable subtree A subtree of an XM

29、L document that the decoder is permitted not to decode. optimised decoder mapping An association between a type and a set of optimised decoders. Renumber all definitions in subclause 3.2. Amendment 1:2006 toCAN/CSA-ISO/IEC 15938-1:04ISO/IEC 15938-1:2002/Amd.1:2005(E) ISO/IEC 2005 All rights reserved

30、 3Add the following abbreviations to the table in subclause 4.1: MSB Most Significant Bit SU Schema Update SUU Schema Update Unit Add the following mnemonic to subclause 4.3: Name Definition vlurmsbf5 Variable length code unsigned rational number, most significant bit first. The first n bits (Ext) w

31、hich are 1 except of the nth bit which is 0, indicate that the rational number R in the interval 0R by Amendment 1:2006 toCAN/CSA-ISO/IEC 15938-1:04ISO/IEC 15938-1:2002/Amd.1:2005(E) 10 ISO/IEC 2005 All rights reservedIn subclause 6.5.2, replace the add command definition by: addNode Adds the node c

32、onveyed within the FUPayload to the context node or the parent node of the context node according to the value of the position attribute of the FUContext. If the position is set to the value “lastChild”, the node conveyed within the FUPayload shall be added to the context node as the last child of t

33、he context node, or if the position attribute is set to the value “prevSibling”, the node conveyed within the FUPayload shall be added to the parent node of the context node as the previous sibling of the context node. In subclause 6.6.1, rename the “FUContextType” in the DDL definition to “Fragment

34、UpdateContextTypeBase”. In subclause 6.6.1, add the following DDL definition: In subclause 6.6.2, add the following semantics: position This attribute shall be only present when the FUCommand takes the value “addNode”, and indicates the position of the node added by the “addNode” command against the

35、 context node specified by the navigation path. This attribute can have the following values: “lastChild” : the last child of the context node. “prevSibling” : the previous sibling of the context node. In subclause 6.7.1, replace the following text: Amendment 1:2006 toCAN/CSA-ISO/IEC 15938-1:04ISO/I

36、EC 15938-1:2002/Amd.1:2005(E) ISO/IEC 2005 All rights reserved 11by In subclause 6.7.2, add the following semantics: FragmentReference Defines that the current fragment update payload carries a fragment reference instead of a complete fragment. This element shall not be present if fragment payload a

37、ctually contains a fragment. The element name and type of the top most element of the fragment being referenced shall be carried before the fragment reference itself. Add the following subclause (subclause 6.8): 6.8 Textual Fragment Reference 6.8.1 Syntax 6.8.2 Semantics The FragmentReferenceType is

38、 an abstract complex type which serves as a base type for specific implementation of a fragment reference. The URIFragmentReferenceType is a concrete complexType which defines fragment references as a URI. Amendment 1:2006 toCAN/CSA-ISO/IEC 15938-1:04ISO/IEC 15938-1:2002/Amd.1:2005(E) 12 ISO/IEC 200

39、5 All rights reservedName Definition isDeferred Defines the deferred nature of the fragment reference: If the isDeferred attribute has a value of true, the fragment reference is deferred and shall be resolved as defined in subclause 5.8.2. If the isDeferred attribute has value of false, the fragment

40、 reference is non-deferred and shall be resolved as defined in subclause 5.8.1. href Defines the URI of a fragment refererence of type URIFragmentReferenceType. 6.8.3 Examples In the following, example of the instances of the FUPayload datatype using the fragment reference is shown: In subclause 7.1

41、, add the following text and figure at the end of the subclause: Identifying schema components in the BiM framework As described in Clause 5, BiM relies upon schema knowledge. In this specification, schema components (elements, types and attributes) are identified by both a schema identifier and a c

42、omponent identifier. The decoder manages both a unique initial schema and several additional schemas. From the decoder point of view, both initial schemas and additional schemas are indentified through a unique table in which each entry identifies a specific schema: the first NumberOfSchemas entries

43、 identify schemas that are part of the initial schema. The following ones identify additional schemas (starting at the NumberOfSchemas entry and ending at the NumberOfSchemas + NumberOfAdditionalSchemas - 1). Initial schema012345678NumberOfSchemas = 5NumberOfAdditionalSchemas = 4Additional schemas F

44、igure AMD1-2 - Addressing the initial schema and the additional schemas Amendment 1:2006 toCAN/CSA-ISO/IEC 15938-1:04ISO/IEC 15938-1:2002/Amd.1:2005(E) ISO/IEC 2005 All rights reserved 13The schema component codes (type codes, element codes or attribute codes) are accessible through all these schema

45、s. However codes are constructed differently depending on which schema they are defined. The initial schema aggregates all schema components possibly coming from different namespaces in a single code space. On the contrary, additional schemas contains only schema components which are defined in thei

46、r namespace. In subclause 7.2.1, replace the following text: An optimised type codec specifies an encoding for a data type not using the generic mechanism specified in Clause 8 but optimised with full knowledge of the properties of that data type. Some optimised type codecs are specified in Part 3 o

47、f this specification. by An optimised type codec specifies an encoding for a data type not using the generic mechanism specified in Clause 8 but optimised with full knowledge of the properties of that data type. There are two kinds of optimised type codec (or optimised decoders). A fixed optimised d

48、ecoder associates a specific encoding scheme to a type of the schema (complex as well as simple) and this association is fixed for the entire stream. An advanced optimised decoder associates a specific encoding scheme to any simple type and this association can be changed during the transmission of

49、the bitstream. Moreover, several advanced optimised decoders can be associated to a single type and can accept parameters. Some fixed optimised type codecs are specified in Part 3 of the specification. Some advanced optimised decoders are defined in Clause 9. In subclause 7.2.1, add the following text at the end of the subclause: Several other coding modes are initialised in the DecoderInit related to the features used by the binary description stream: the insertion of elements, the transmission of schema i