SMPTE ST 2001-1-2015 XML Representation of SMPTE Registered Data (Reg-XML) - Mapping Rules.pdf

1、 Access to Content for (SMPTE ST 2001-1:2015) (Click here to view the publication) This Page is not part of the original publication: This page has been created by IHS as a convenience to the user in order to provide access to the content as authorized by the Copyright holder of this document. Click

2、 the link(s) below to access the content and use normal procedures for downloading or opening the files. SMPTE_Additional Data Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer or that a certain course of action is preferred but not necessarily r

3、equired; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. The keywords “may“ and “need not“ indicate courses of action permissible within the limits of the document. The keyword “reserved” indicates a provision that is not defined at this tim

4、e, shall not be used, and may be defined in the future. The keyword “forbidden” indicates “reserved” and in addition indicates that the provision will never be defined in the future. A conformant implementation according to this document is one that includes all mandatory provisions (“shall“) and, i

5、f implemented, all recommended provisions (“should“) as described. A conformant implementation need not implement optional provisions (“may“) and need not implement them as described. Unless otherwise specified, the order of precedence of the types of normative information in this document shall be

6、as follows: Normative prose shall be the authoritative definition; Tables shall be next; followed by formal languages; then figures; and then any other language forms. SMPTE ST 2001-1:2015 Page 6 of 52 pages 3 Normative References Note: All references in this document to other SMPTE documents use th

7、e current numbering style (e.g. SMPTE ST 298:2009) although, during a transitional phase, the document as published (printed or PDF) may bear an older designation (such as SMPTE 298-2009). Documents with the same root number (e.g. 298) and publication year (e.g. 2009) are functionally identical. The

8、 following standards contain provisions that, through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this recommended practice are encouraged to i

9、nvestigate the possibility of applying the most recent edition of the standards indicated below. SMPTE ST 298:2009, Universal Labels for Unique Identification of Digital Data SMPTE ST 330:2011, Unique Material Identifier (UMID) SMPTE ST 335:2012, Metadata Element Dictionary Structure SMPTE ST 395:20

10、14, Metadata Groups Register SMPTE ST 400:2012, SMPTE Labels Structure SMPTE ST 2003:2012, Types Dictionary Structure SMPTE ST 2029:2009, Uniform Resource Names for SMPTE Resources Extensible Markup Language (XML) 1.0 (Third Edition), W3C Recommendation, 4 February 2004, http:/www.w3.org/TR/2004/REC

11、xml-20040204/ Namespaces in XML 1.0 (Third Edition), W3C Recommendation, 8 December 2009, http:/www.w3.org/TR/REC-xml-names/ XML Schema Part 1: Structures Second Edition, W3C Recommendation, 28 October 2004, http:/www.w3.org/TR/2004/REC-xmlschema-1-20041028/ XML Schema Part 2: Datatypes Second Edit

12、ion, W3C Recommendation, 28 October 2004, http:/www.w3.org/TR/2004/REC-xmlschema-2-20041028/ XML Linking Language (XLink) Version 1.1, W3C Recommendation, 6 May 2010, http:/www.w3.org/TR/xlink11/ XML Path Language (XPath) Version 1.0, W3C Recommendation, 16 November 1999, http:/www.w3.org/TR/xpath/

13、IETF RFC 1738 Uniform Resource Locators (URL), December 1994 IETF RFC 2141 URN Syntax, May 1997 IETF RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax, August 1998 IETF RFC 3061 A URN Namespace of Object Identifiers, February 2001 IETF RFC 4122 A Universally Unique Identifier (UUID) URN Na

14、mespace, July 2005 SMPTE ST 2001-1:2015 Page 7 of 52 pages 4 Definition of Acronyms, Terms and Notation 4.1 Acronyms and Terms AUID A 16-byte UID that shall contain a UL or a UUID. If the value is a UUID, it shall be stored such that the top and bottom 8 bytes of the UUID are swapped. For UUIDs, thi

15、s makes the most significant bit of the first byte a 1 and thus creates a UID value that is always distinct from a UL. Namespace XML Namespace URI Uniform Resource Identifier URL Uniform Resource Locator URN Uniform Resource Name UUID Universally Unique IDentifier XML eXtensible Markup Language XSDL

16、 XML Schema Definition Language the W3C XML schema language used to define a class of XML documents XSD XML Schema Definition an XML document containing a schema expressed in XSDL XLink XML Linking Language - allows elements to be inserted into XML documents in order to create and describe links bet

17、ween resources XPath XML Path Language - a language for addressing parts of an XML document 4.2 Notation A property X owned by class Y is shown using the notation Y:X, e.g. Preface:FileLastModified refers to the FileLastModified property in the Preface class. The mapping rules use the notation xxx t

18、o indicate that the value xxx must be filled in when applying the mapping rule, e.g. the name of the type must be filled in the XSD definition . The mapping rules use the notation ? for things that are only required when certain conditions are met, e.g. reg:uid=”id”? means that the reg:uid attribute

19、 is only required when the conditions given in the notes are met. The mapping rules use the Namespace prefix reg to refer to the baseline namespace, cx for an example company X namespace representing user/vendor extensions and this for adhoc extensions not explicitly assigned to a namespace. Applica

20、tions are not required to use these Namespace prefixes. 5 Prologue Reg-XML has two distinct components: the specification of data models that correspond to definitions in the SMPTE metadata registers (SMPTE ST 395, SMPTE ST 335, SMPTE ST 2003 and SMPTE ST 400) and the normative source of those defin

21、itions; the representation of data defined by the data models using XML. SMPTE ST 2001-1:2015 Page 8 of 52 pages The XML representation consists of an XML document, called a Reg-XML document, and zero or more files or resources containing stream data. The stream data files are referenced from within

22、 the Reg-XML document. The Reg-XML document and the referenced stream data are together called a Reg-XML file group. A fragment of a Reg-XML document, called a Reg-XML fragment, may be included in another context. A Reg-XML file group is intended for use directly as a data interchange format between

23、 systems, or it may be converted to or from some other data representation for the purpose of data interchange between systems. For example, a Reg-XML file group may be converted to or from an AAF or MXF file. SMPTE ST 2001 is a multipart standard, with this part defining the rules for specifying a

24、Reg-XML data model and its use. SMPTE 2001-1 is independent of any particular Reg-XML data model. The structure of this document is as follows: Section 6 provides an informative description of a Reg-XML data model and defines the use of a Reg- XML data model. The Reg-XML data model is used as input

25、for both the data and model mapping rules and is normatively specified by the meta dictionary XML schema in Annex A. Section 7 defines the association between a Reg-XML document and Reg-XML data models that contain baseline and extension definitions for the data the document contains. This associati

26、on is achieved through the use of XML Namespaces. Section 8 defines the data mapping rules for representing data as a Reg-XML file group. The data mapping rules are described independently from any XML schema language. Section 9 defines the informative model mapping rules for generating W3C XML Sche

27、mas (XSDs) from a Reg-XML data model for validation. 6 Reg-XML Data Models (Informative) 6.1 Definition of a Reg-XML Data Model A Reg-XML data model is a collection of class, property and type definitions. A Reg-XML data model is described using one or more Schemes, with a Meta Dictionary used to de

28、fine each Scheme. The XML schema in Annex A provides the normative specification of a Reg-XML data model, with additional annotations provided in this section. Class, property and type definitions share the following attributes: Identification: an AUID that uniquely identifies the definitions. Symbol: a string that uniquely identifies the definition in the context of a Scheme. Description: describes the definition. Name: a descriptive name for the definition.