1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationGuidelines for implementors of EN 15744 and EN 15907PD CEN/TS 16371:2012National forewordThis Published Document is the UK implementation of CEN/TS 16371:2012. The UK participati
2、on in its preparation was entrusted by Technical CommitteeIDT/2, Information and documentation, to Subcommittee IDT/2/18, Identifiers and metadata.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the ne
3、cessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2012Published by BSI Standards Limited 2012 ISBN 978 0 580 76932 0 ICS 35.240.30; 37.060.99Compliance with a British Standard cannot confer immunity from legal obligations.This Publ
4、ished Document was published under the authority of the Standards Policy and Strategy Committee on 31 March 2012.Amendments issued since publicationAmd. No. Date Text affectedPUBLISHED DOCUMENTPD CEN/TS 16371:2012TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16371 Fe
5、bruary 2012 ICS 35.240.30; 37.060.99 English Version Guidelines for implementors of EN 15744 and EN 15907 Richtlinien fr Implementierer von EN 15744 und EN 15907This Technical Specification (CEN/TS) was approved by CEN on 14 February 2012 for provisional application. The period of validity of this C
6、EN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard. CEN members are required to announce the existence of this CEN/TS in the same way as fo
7、r an EN and to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached. CEN members are the na
8、tional standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switz
9、erland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2012 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. R
10、ef. No. CEN/TS 16371:2012: EPD CEN/TS 16371:2012CEN/TS 16371:2012 (E) 2 Contents PageForeword 31 Scope 42 Normative references 43 Terms and definitions .44 Options for implementing the CEN metadata standards for cinematographic works .54.1 General 54.2 Data exchange options for EN 15744.54.2.1 Gener
11、al 54.2.2 EN 15744 mapped to DCMES 54.2.3 EN 15744 native54.3 EN 15907 Data exchange using XML .54.3.1 General 54.3.2 Wrapper element 54.3.3 Description units54.3.4 Expressing Relationships .64.3.5 Adding Type Vocabularies 74.3.6 Adding elements from foreign namespaces .84.3.7 Representing metadata
12、statements outside the scope of EN 15907 9Annex A (informative) List of EN 15907 elements and attributes that may be redefined in an application-specific schema layer 10Bibliography . 12PD CEN/TS 16371:2012CEN/TS 16371:2012 (E) 3 Foreword This document (CEN/TS 16371:2012) has been prepared by Techni
13、cal Committee CEN/TC 372 “Project Committee - Cinematographic Works”, the secretariat of which is held by DIN. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or
14、 all such patent rights. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Gre
15、ece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. PD CEN/TS 16371:2012CEN/TS 16371:2012 (E) 4 1 Scope This Technical Specification outlines techno
16、logical approaches towards implementing EN 15907 and (partially) EN 15744 for the purpose of exchanging metadata about cinematographic works. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. Fo
17、r dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 15744, Film identification Minimum set of metadata for cinematographic works EN 15907:2010, Film identification Enhancing interoperability
18、of metadata Element sets and structures ISO 15836:2009, Information and documentation The Dublin Core metadata element set ISO/IEC 19757-2:2008, Information technology Document Schema Definition Language (DSDL) Part 2: Regular-grammar-based validation RELAX NG ISO/IEC 19757-4:2006, Information techn
19、ology Document Schema Definition Languages (DSDL) Part 4: Namespace-based Validation Dispatching Language (NVDL) 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 19757-2:2008 and the following apply. 3.1 encoding scheme a set of definitions for th
20、e structured representation of complex data objects 3.2 foreign element element with a name whose namespace URI is not the namespace URI for the parent schema 3.3 instance XML document that is being validated with respect to an XML schema 3.4 schema XML-encoded set of declarative rules against which
21、 one or more instances can be validated 3.5 URI compact string of characters that uses the syntax defined in IETF RFC 2396 to identify an abstract or physical resource 3.6 valid with respect to a schema member of the set of XML documents described by the schema 3.7 validator software module that det
22、ermines whether a schema is correct and whether an instance is valid with respect to a schema PD CEN/TS 16371:2012CEN/TS 16371:2012 (E) 5 4 Options for implementing the CEN metadata standards for cinematographic works 4.1 General Neither EN 15744 nor EN 15907 mandate a particular representation for
23、conformant metadata. Interoperability is assumed if metadata is communicated in a format that (1) preserves the meaning as defined in the standards, and (2) can be produced and/or consumed by all parties taking part in an exchange of metadata. Both standards specify element names and associated defi
24、nitions, while EN 15907 additionally specifies relationships between elements. 4.2 Data exchange options for EN 15744 4.2.1 General EN 15744 specifies fifteen metadata elements similar in intent to many core“ specifications such as the Dublin Core Metadata Element Set (DCMES, ISO 15836:2003, revised
25、 2009). For data exchange purposes, EN 15744-conformant metadata can be prepared in one of the following ways. 4.2.2 EN 15744 mapped to DCMES In cases where a party in a metadata exchange is unable to provide or consume EN 15744-conformant metadata, or such metadata is to be merged with DCMES-based
26、metadata, the element contents may be transformed to a DCMES-conformant representation using the Dublin Core mapping statements contained in EN 15744. A representation transformed according to the DCMES may be encoded in any syntax endorsed by the Dublin Core Metadata Initiative. 4.2.3 EN 15744 nati
27、ve Metadata using the EN 15744 element specifications may be encoded in any syntax endorsed by the Dublin Core Metadata Initiative. Where appropriate, this metadata may be combined with elements from other standards and specifications, provided that any element not defined in EN 15744 is labelled wi
28、th a namespace reference indicating its origin. 4.3 EN 15907 Data exchange using XML 4.3.1 General The following clauses specify requirements for an XML-based exchange of metadata instances conformant with EN 15907. Further definitions based on different encoding schemes may be made available in the
29、 future. 4.3.2 Wrapper element A wrapper element is required whenever more than a single instance of a Cinematographic Work element is to be exchanged as a contiguous data stream. Depending on the exchange scenario, such an element may or may not be defined by the exchange specification. Where this
30、is not the case, sequences of Cinematographic Work elements shall be enclosed in an ExchangeSet element. 4.3.3 Description units Cinematographic Work Since EN 15907 defines this unit of description as the reference point for any Variant and/or Manifestation, it shall be used as the top-level element
31、 in an XML-based representation of a conformant metadata. This requirement entails that a work-level identity shall be supplied even in cases where no work-level information PD CEN/TS 16371:2012CEN/TS 16371:2012 (E) 6 about a Manifestation is available. It is the task of the metadata supplier to pro
32、vide elementary work-level identification, independent of whether this information is transitory, preliminary, or persistent. Variant Defined as optional in EN 15907, this unit of description may or may not be included depending on one of the following conventions: a) All work-level descriptions hav
33、e a default instance of Variant. In this case, any instance of Manifestation, even if not more than one is known, shall occur as a child element of a Variant. b) A Variant is used to distinguish two or more sets of (one or more) Manifestations, and omitted if all Manifestations are considered to bel
34、ong to a single set. In the latter case, each instance of Manifestation will occur as a direct sub-element of the Cinematographic Work, while in the former case each Manifestation will occur as a direct child element of a Variant instance. c) A Variant is used to distinguish a particular set of Mani
35、festations from those that are not considered to belong to any Variant. In this case, instances of Manifestation can occur both as sub-elements of Cinematographic Work and of one or more instances of Variant. d) The Variant is never used. In this case, each instance of Manifestation shall occur as a
36、 child element of the Cinematographic Work instance. It is recommended that a contiguous XML-encoded data stream containing EN 15907-compliant metadata restricts the use (or non-use) of the Variant to a single convention from the above list. It is further recommended that parties engaging in an XML-
37、based exchange of EN 15907-compliant metadata agree on one of the above conventions so as to minimise the risk of misalignment when processing this metadata. Manifestation Although not explicitly stated in EN 15907, this unit of description shall be considered mandatory if compatibility with EN 1574
38、4 is required. A Cinematographic Work without a known manifestation, or one that has never been realised, shall be associated with a Manifestation of an appropriate type (e.g. unknown“ or production aborted“). Item Any item-level description shall be represented as a dependent element (i.e. a sub-el
39、ement in XML) with respect to a Manifestation. Where an item is the only source for metadata, the EN 15907 data model assumes that properties such as extent and format are those of the manifestation, i.e. common to all possibly existing exemplars. An item may be composed of sections representing a u
40、nique combination of cinematographic works. Such item-level compilations are not in the immediate scope of EN 15907. They may be expressed by associating a single instance of Item with two or more manifestations of different works by use of a suitable specialisation of the HasOtherRelationship. 4.3.
41、4 Expressing Relationships Except for some one-to-many relationships, which can be expressed through XML element nesting, any relationship expression requires the use of identifiers. An XML encoding of EN 15907-conformant metadata shall not use the ID/IDREF or KEY/KEYREF types, since these require r
42、eferences to be resolvable within the scope of accessible XML document instances. Moreover, these features are specific to XML whereas EN 15907 may also be used with other encodings. Each many-to-many relationship defined in EN 15907 can be understood as a predicate (in the linguistic sense) with a
43、subject represented by the element instance at hand, and an object represented by an identifier or, in some cases, an instance of some other element. Identifiers in the object position shall have global PD CEN/TS 16371:2012CEN/TS 16371:2012 (E) 7 scope, wherever possible. Element instances in the ob
44、ject position shall be represented as XML child elements of the relationship element. Semantic enrichment The basic many-to-many relationship types defined in EN 15907 are semantically weak and typically require specialisation by means of type vocabularies. EN 15907 provides for type attributes or s
45、ub-elements that may or shall take on values from (preferably controlled) vocabularies. An XML-based representation of specialised relationship types shall meet the following requirements: a) Multiplicity of types. An object of a relationship shall be allowed to appear in more than one role without
46、the necessity of repeating subject and object for each role. b) Language attribute. A type name shall be allowed to have a language attribute. Neither of these requirements can be met by using the XML attribute syntax. An XML encoding of EN 15907 relationship types shall therefore use the XML elemen
47、t syntax wherever any of the above requirements apply. 4.3.5 Adding Type Vocabularies All metadata values apart from those that are free text or scalar values shall be taken from controlled vocabularies wherever an appropriate source for such vocabulary is available. Parties planning to exchange EN
48、15907-conformant metadata in an XML encoding are advised to add their choice of vocabularies to the XML schema definition in the following way: Figure 1 References between XML schema components A type vocabulary may be added by redefining an element type declaration from the base definitions within
49、an application-specific schema layer. As an example, let the data type for the usage attribute specified in 6.9.2 of EN 15907:2010 be defined as follows: This definition allows any sequence of characters to be accepted as a legal value for the usage attribute. Restricting the set of allowed values can be achieved by adding a replacement for the base definition to the application-specific schema layer: (.) PD CEN/TS 16371:2012CEN/TS 16371:2012 (E) 8 where ns1 shall be
