CEN/TR 17862:2022

SLOVENSKI STANDARD
01-oktober-2022
Smernice za izvajanje paketa za varstvo filmov (CPP) v EN 17650
Guideline for the implementation of the Cinema Preservation Package (CPP) in EN
Leitlinien für die Umsetzung des Cinema Preservation Package (CPP) in EN 17650
Lignes directrices relatives à la mise en œuvre du paquetage de conservation cinéma
(CPP) dans l’EN 17650
Ta slovenski standard je istoveten z: CEN/TR 17862:2022
ICS:
35.240.30 Uporabniške rešitve IT v IT applications in information,
informatiki, dokumentiranju in documentation and
založništvu publishing
37.060.99 Drugi standardi v zvezi s Other standards related to
kinematografijo cinematography
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

CEN/TR 17862
TECHNICAL REPORT
RAPPORT TECHNIQUE
August 2022
TECHNISCHER REPORT
ICS 35.240.30; 37.060.99
English Version
Guideline for the implementation of the Cinema
Preservation Package (CPP) in EN 17650
Lignes directrices relatives à la mise en œuvre du Leitlinien für die Umsetzung des Cinema Preservation
paquetage de conservation cinéma (CPP) dans Package (CPP) in EN 17650
l'EN 17650
This Technical Report was approved by CEN on 17 July 2022. It has been drawn up by the Technical Committee CEN/TC 457.

CEN members are the national 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, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATIO N

EUROPÄISCHES KOMITEE FÜR NORMUN G

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TR 17862:2022 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Abbreviations . 5
5 Syntax convention used in this document . 6
6 Usage of XML schemas in CPP . 9
Annex A (informative) Structure of the Cinema Preservation Package . 10
Annex B (informative) Naming Conventions in Cinema Preservation Packages . 25
Annex C (informative) Technical metadata in subpackages . 28
Annex D (informative) Descriptive Metadata of CPP . 79
Annex E (informative) Usage of playlists in CPP . 93
Annex F (informative) Checker Reports in CPP . 96
Annex G (informative) Usage of CPP in archive context . 98
Annex H (informative) FAQ (Frequenly Asked Questions) . 100
Bibliography . 102
European foreword
This document (CEN/TR 17862:2022) has been prepared by Technical Committee CEN/TC 457 “Digital
preservation of 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 shall not be held responsible for identifying any or all such patent rights.
This document has been prepared based on the Rolling Plan for ICT standardization 2015-2018.
This document serves as implementation guide to the European Standard EN 17650: A framework for
digital preservation of cinematographic works — The Cinema Preservation Package.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
Introduction
This document is part of a series of standards and technical recommendations for the digital preservation
of cinematographic work. It gives European film archives and producers a guideline how to store and
manage film content in the digital age.
Versions of digital cinematographic work using different encoding formats can be preserved in a layered
structure where the lowest level is describing the physical file. The files can carry data representing
images, sound, movies, subtitles, metadata or ancillary information like QC reports or film posters.
To structure these files in a consistent and interoperable way, the Cinema Preservation Package (CPP) is
specified and adds additional metadata like file lists, links or hash values. The Cinema Preservation
Package uses different XML files to store these additional metadata. The XML files are based on existing
schemas with extensions, in particular METS, EBUCore and PREMIS. The XML files also contain hash
values to ensure data integrity and version control. The syntax for this description and the methods for
the hash value generation are specified in EN 17650. Various types of content coding are described as
reference for concrete implementations.
The Cinema Preservation Package is well suited to serve as a Submission Information Package (SIP) in an
OAIS compliant preservation system [2] and/or as a self-contained exchange format between media
archives. The CPP does not necessarily contain a complete cinematographic work, it can also be used for
exchange of parts of a work (see Annex G).
1 Scope
This document describes the implementation of the Cinema Preservation Package (CPP) to facilitate the
digital preservation of cinematographic works. The related standard EN 17650 specifies methods to
describe the relationship of components of the cinematographic work and delivers syntax to describe the
package content. EN 17650 specifies the structure of the package and the constraints that are necessary
to enable compliance and interoperability. This document gives additional information how to implement
EN 17650 and gives additional explanations to the structure.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 17650, A framework for digital preservation of cinematographic works — The Cinema Preservation
Package
3 Terms and definitions
For the purposes of this document, the terms and definitions given in EN 17650 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• ISO Online browsing platform: available at http://www.iso.org/obp
• IEC Electropedia: available at http://www.electropedia.org/
3.1
ancillary data
small additional data supporting other data in the same hierarchy, preferably annotations
3.2
element
simple or essential part of which anything exists
3.3
file
collection of information stored on a digital storage medium
3.4
persistent identifier
unique identifier that ensures permanent access for a digital object by providing access to it
independently of its physical location or current ownership
3.5
preservation
act of maintaining information in a correct and independently understandable form over a long time
4 Abbreviations
ACES Academy Color Encoding System
ASCII American Standard Code for Information Interchange
BMFF Base Media File format
CPP Cinema Preservation Package
DCP Digital Cinema Package
DPX Digital Picture Exchange
IMF Interoperable Master Format
JPEG Joint Photographic Experts Group
LoC Library of Congress, see https://www.loc.gov/
MPEG Moving Pictures Experts Group
OAIS Open Archive Information System
PCM Pulse code modulation
PDF Portable Document Format
PNG Portable Network Graphics
SIP Submission Information Package
TIFF Tagged Image File Format
UUID Universal Unique Identifier
XML Extensible Markup Language
5 Syntax convention used in this document
5.1 General
For the file and folder name descriptions the following conventions are used.
5.2 Expressions used to denote file or folder names
5.2.1 Composition of name with parts
A name may be composed of one or several parts.
5.2.2 Literal parts
A literal part appearing between quotes appears as is.
EXAMPLE “LiteralPart” designates a part which is exactly “LiteralPart”.
5.2.3 Optional part
A part appearing between brackets appears zero or one time.
EXAMPLE [“OptionalPart”]”Radical” designates a name which is either “OptionalPartRadical” or “Radical”.
5.2.4 Alternative parts
Exactly one of the items in parentheses, separated by a vertical line ‘|’, appears in the result.
EXAMPLE (“Prefix1”|“Prefix2”|“Prefix3”)“Radical” designates a name which is either “Prefix1Radical”,
“Prefix2Radical” or “Prefix3Radical”.
5.2.5 Explicitly defined part
is a placeholder text and is replaced as specified by the prose.
EXAMPLE “Name_” designates a name which could be “Name_0123456789”, supposing
“0123456789” is defined as a valid custom identifier.
5.3 Expressions used to denote file or folder multiplicity
5.3.1 General
Some files or folders may appear several times in the parent folder. The final modifier therefore indicates
the allowed multiplicity.
5.3.2 One occurrence or more
A file or folder name with a trailing ‘+’ appears one or more times in the parent folder.
EXAMPLE “File_”+ designates a set of multiple files such as “File_0000”, or “File_0000” and
“File_0001” and “File_0002”, etc., assuming the prose describes such a 4-digit numbering.
5.3.3 Zero occurrence or more
A file or folder name with a trailing ‘*’ appears zero or more times in the parent folder.
EXAMPLE “File_”* designates a set of multiple files such as no file, “File_0000”, or “File_0000” and
“File_0001” and “File_0002”, etc., assuming the prose describes such a 4-digit numbering.
5.3.4 Optional file or folder
A file or folder name with a trailing ‘?’ appears zero or one time in the parent folder.
EXAMPLE “OptionalFile”? designates no file, or exactly one file with name “OptionalFile”.
5.4 Typographic conventions
5.4.1 Monospaced fonts
In the document, monospaced fonts are used for literal expression of textual content of a file, for instance
as example quotation.
EXAMPLE example text
5.4.2 Italic
In the document, italic text is expected to be substituted as specified in the prose.
EXAMPLE relative path to file is the path from the root folder to the Descriptive Metadata file including the
filename.
5.5 Conventions used to denote XML content
5.5.1 General consideration
Constraints on XML files are specified either as an XML Schema to apply, or as listed constraints for each
element of a list of specific XML Nodes.
5.5.2 Hierarchy
To denote the hierarchical position of a node the XPath syntax is used.
EXAMPLE “/rootElement/subElement/subSubElement” denotes an element with name “”
which is a child of a “” element, which itself is a child of the “” root element.
NOTE When an element in the path occurs more than one time, the XPath will be completed with discriminary
attributes if necessary. If the description applies to multiple elements, no discriminatory attribute will be added.
5.5.3 Namespace
XML elements may use a prefix to denote a namespace. The prefix indicated in the prose is only used for
convenience, and does not denote a namespace. The prefix in the file may be different and this is suitable
as long as the relation with the namespace is correctly indicated as a namespace attribute from a parent
element.
EXAMPLE “/mainNs:rootElement/mainNs:subElement” the “” and the “” belong
to the namespace denoted by “mainNs” in the prose.
5.5.4 Subelements
The following are used:
— @attributeName: denotes the name of an attribute of the element;
— #children: denotes the child elements;
— #text: denotes the child text of the element.
EXAMPLE


example 2

“/mainNs:rootElement/#children” denotes “subElement1” or “subElement2”
“/mainNs:rootElement/@att
...