1、Information technology Multimedia framework (MPEG-21) Part 18: Digital Item Streaming AMENDMENT 1: Simple fragmentation ruleAmendment 1:2009 (IDT) toNational Standard of CanadaCAN/CSA-ISO/IEC 21000-18-08(ISO/IEC 21000-18:2007, IDT)NOT FOR RESALE.PUBLICATION NON DESTINE LA REVENTE.CSA Standards Updat
2、e ServiceAmendment 1:2009 toCAN/CSA-ISO/IEC 21000-18-08October 2009Title: Information technology Multimedia framework (MPEG-21) Part 18: Digital Item Streaming AMENDMENT 1: Simple fragmentation rulePagination: 24 pages (iii preliminary and 21 text)To register for e-mail notification about any update
3、s to this publicationgo to www.ShopCSA.caclick on E-mail Services under MY ACCOUNTclick on CSA Standards Update ServiceThe List ID that you will need to register for updates to this publication is 2419156.If you require assistance, please e-mail techsupportcsa.ca or call 416-747-2233.Visit CSAs poli
4、cy on privacy at www.csagroup.org/legal to find out how we protect your personal information.Reference numberISO/IEC 21000-18:2007/Amd.1:2008(E)ISO/IEC 2008INTERNATIONAL STANDARD ISO/IEC21000-18First edition2007-06-15AMENDMENT 12008-06-01Information technology Multimedia framework (MPEG-21) Part 18:
5、 Digital Item Streaming AMENDMENT 1: Simple fragmentation rule Technologies de linformation Cadre multimdia (MPEG-21) Partie 18: Transmission dlment numrique AMENDEMENT 1: Rgle de fragmentation simple ISO/IEC 21000-18:2007/Amd.1:2008(E) PDF disclaimer This PDF file may contain embedded typefaces. In
6、 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 therein the responsibility of not infringing Ado
7、bes 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 PDF-creation parameters were optimized for
8、 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. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2008 All rights reserved. Unless
9、 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 requester. ISO cop
10、yright 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 2008 All rights reservedAmendment 1:2009 toCAN/CSA-ISO/IEC 21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) ISO/IEC 2008 All rights reserved iiiForeword ISO (
11、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 technical committees
12、 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 in the work.
13、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 International Standa
14、rds. 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 the elements
15、 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 21000-18:2007 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audio, p
16、icture, multimedia and hypermedia information. Amendment 1:2009 toCAN/CSA-ISO/IEC 21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) ISO/IEC 2008 All rights reserved 1Information technology Multimedia framework (MPEG-21) Part 18: Digital Item Streaming AMENDMENT 1: Simple fragmentation rule In Clause 2
17、add the following normative reference following the reference to ISO/IEC 15938-5: ISO/IEC 16262:2002, Information technology ECMAScript language specfication In 7.3.5 add the following paragraph: BBL also allows for user-defined XPath functions to be defined by the BBL author using ECMAScript with D
18、IS extensions. See also 7.3.24 and 9. Amendment 1:2009 toCAN/CSA-ISO/IEC 21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) 2 ISO/IEC 2008 All rights reservedIn 7.3.17 replace Table 17 Register Type with the following: Table 17 RegisterType Diagram Children bbl:Handler bbl:Encoder bbl:Multiplexer bbl:Bs
19、d Name Type Use Description xmlSource xs:string optional binarySource xs:string optional Attributes bSrcNamespace xs:string optional See SourceElementType (7.3.8) Source Insert a new Subclause 7.3.24 as follows and renumber subsequent subclauses appropriately: 7.3.24 Function element A Function elem
20、ent is of type FunctionType and registers a user-defined XPath function. A user-defined XPath function is defined using the ECMAScript language (ISO/IEC 16262) with the DIS extensions as per clause 9. The function definition shall be contained as text content of a Function element. Amendment 1:2009
21、toCAN/CSA-ISO/IEC 21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) ISO/IEC 2008 All rights reserved 3Table AMD1. 1 FunctionType Diagram Used by bbl:Register Name Type Use Description bbl:name xs:Qname required The name of the function being defined. Attributes bbl:args xs:nonNegativeInteger optional T
22、he number of arguments that the function accepts. Source In 7.3.36 replace the Fragmentation element specification with the following: Diagram Children bbl:FragmentAt bbl:Size bbl:Duration bbl:Count bbl:Constraint Name Type Use Description Attributes attributes xs:NCName optional Specifies whether r
23、eassembly attributes should be added to the fragments. Possible values are none, id, and context. A value of none indicates that no reassembly attributes should be attached to the fragments. This is the default value. A value of id indicates that bbl:fragmentRef and bbl:fragmentID attributes are to
24、be attached to fragmentation nodes in the parent and child fragments respectively. The ID value assigned to each fragment is that of the id attribute of the fragmentAt element, if present, or an arbitrary ID which is unique in the BBL description, assigned by the processor. If the fragmentAt element
25、 matches multiple nodes, the ID assigned shall be the concatenation of the value of the fragmentAt id attribute and a unique integer. A value of context indicates that the bbl:context attribute, with a value as specified in 3 is added to the child fragment. Source Amendment 1:2009 toCAN/CSA-ISO/IEC
26、21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) 4 ISO/IEC 2008 All rights reservedInsert a new Subclause 7.3.37 as follows and renumber subsequent subclauses appropriately: 7.3.37 FragmentAt element A FragmentAt element is of type FragmentAtType and declares that content should be fragmented so that
27、a new fragment is to be created for any node matched. The specific node(s) matched shall be present in both parent and child fragments, and may have fragmentRef and fragmentID attributes respectively. Included descendants shall be be present in the child fragment. Included content shall be traversed
28、 in hierarchical order beginning at the root of the content and descendant content of a fragmentation node will be included in subsequent fragments. For an example of the use of this element see C.8. Table AMD1. 2 FragmentAtType Diagram Used by bbl:Fragmentation Name Type Use Description match xs:st
29、ring required A W3C XPATH expression which is evaluated against the nodes returned by the parent include element and resolves to the node(s) at which new fragment(s) are to be created. deliveryTime xs:string optional The delivery time of the fragment(s) declared by FragmentAt. repeat xs:string optio
30、nal The repetition period of the fragment(s) declared by FragmentAt. Attributes id xs:ID optional If the attributes attribute is present on the parent Fragmentation element (see 7.3.36) and its value is id, then if the id attribute is present on a FragmentAt element its value shall be the ID value a
31、ssigned to the bbl:fragementRef and bbl:fragmentID attributes attached to fragmentation nodes in the parent and child fragments. Source Amendment 1:2009 toCAN/CSA-ISO/IEC 21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) ISO/IEC 2008 All rights reserved 5In 7.4 add the following rows to the Table 46: b
32、bl:fragmentRef This attribute may be attached to a fragmentation node in a parent fragment whose descendant content will be in a subsequent fragment. The value of this attribute shall match the value of a corresponding bbl:fragmentID attribute attached to the fragmentation node in the child fragment
33、. bbl:fragmentID This attribubte may be attached to a fragmentation node in a child fragment whose parent has been included in a previous fragment. The value of this attribute shall match the value of a corresponding bbl:fragmentRef attribute attached to the fragmentation node in the parent fragment
34、. Add Clause 9 as follows: 9 Extensions to ECMAScript 9.1 Overview This clause defines a set of ECMAScript (ISO/IEC 16262) objects and their properties that extend ECMAScript for use in DIS. ECMAScript is used in DIS for user-defined XPath functions (see also 7.3.24). 9.2 DOM API For processing of X
35、ML in ECMAScript based functions in DIS, the W3C DOM API shall be used. For this purpose the ECMAScript bindings for the DOM Level 3 Core (see W3C DOM) are normatively included in ECMAScript for DIS. The DOM API has additional restrictions in DIS in regards to calling functions that modify nodes. If
36、 a node belongs to the BBL document, then it shall not be modifiable unless otherwise stated elsewhere in this document. If a node belongs to a source document, then it shall not be modifiable unless otherwise stated elsewhere in this document. NOTE Nodes that are part of a Packet remain modifiable.
37、 9.3 Global properties The following properties are globally available in the ECMAScript for DIS environment. Table AMD1. 3 Global properties Property name Description bblInfo This global property is a BBLInfo object (see 9.4.1) that contains functions to access BBL provided information. Amendment 1
38、:2009 toCAN/CSA-ISO/IEC 21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) 6 ISO/IEC 2008 All rights reserved9.4 Objects 9.4.1 BBLInfo A BBLInfo object provides the ECMAScript function with access to information provided by the BBL processor. A BBLInfo object has the properties listed in the table below
39、. Table AMD1. 4 BBLInfo object properties Value properties: timeScheme This is a read-only string value that is the in-scope time scheme. Object properties: None. Function properties: addr( node ) This function accepts a DOM Element object argument representing an element from the in-scope XML Sourc
40、e Document and returns a string value which is an XPath expression providing an absolute and unambiguous location of the node within the XML Source Document. This function generates a DISError if the node argument is not a DOM Element object belonging to the in-scope XML Source Document. deliveryTim
41、e( id ) This function accepts a string value argument that is the id of a Packet or PacketStream element in the BBL document and returns a number value which is the delivery time of the Packet (if the id identifies a Packet) or first Packet in the Packet Stream (if the id identifies a PacketStream).
42、 This function generates a DISError if the id argument does not identify either a Packet or PacketStream element in the BBL document duration( id ) This function accepts a string value argument that is the id of a Packet or PacketStream element in the BBL document and returns a number value which is
43、 the duration of the Packet (if the id identifies a Packet) or of the most recently transmitted Packet in the Packet Stream (if the id identifies a PacketStream). This function generates a DISError if the id argument does not identify either a Packet or PacketStream element in the BBL document final
44、DeliveryTime( id ) This function accepts a string value argument that is the id of a Packet or PacketStream element in the BBL document and returns a number value which is the delivery time of the Packet (if the id identifies a Packet) or last Packet in the Packet Stream (if the id identifies a Pack
45、etStream). NOTE For a Packet this function returns the same value as a call to deliveryTime( id ). This function generates a DISError if the id argument does not identify either a Packet or PacketStream element in the BBL document 9.4.2 DISError This object inherits from the ECMAScript Error object
46、and is thrown as an exception when a runtime error specific to DIS occurs. It has no additional properties to the ones inherited from the Error object. Amendment 1:2009 toCAN/CSA-ISO/IEC 21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) ISO/IEC 2008 All rights reserved 79.4.3 XPath types The table belo
47、w defines the ECMAScript for DIS bindings for XPath types. Table AMD1. 5 ECMAScript for DIS bindings for XPath types XPath type ECMAScript object node-set NodeLista boolean Booleanb number Numberbstring StringbaAs defined by the ECMAScript bindings for the W3C DOM API (see also 0). bNative ECMAScrip
48、t object. 9.4.4 BBL variable types The table below defines the ECMAScript for DIS bindings for BBL variable types as defined in Table 13 Allowed variable types. Table AMD1. 6 ECMAScript for DIS bindings for BBL variable types BBL variable type ECMAScript object xs:integer Numberxs:int Numberxs:long
49、Numberxs:short Number xs:decimal Numberxs:float Numberxs:double Numberxs:boolean Boolean xs:byte Number xs:QName Stringxs:dateTime Date xs:base64Binary String xs:hexBinary Stringxs:unsignedInt Numberxs:unsignedShort Number xs:unsignedByte Numberxs:time String xs:date Date xs:anySimpleType String Amendment 1:2009 toCAN/CSA-ISO/IEC 21000-18-08ISO/IEC 21000-18:2007/Amd.1:2008(E) 8 ISO/IEC 2008 All rights reservedIn Annex A replace the schema text with the following: Amendment 1:2009 toCAN/
