DPP Metadata Exchange for News Implementation Guidelines

Transcription

1 DPP Metadata Exchange for News Implementation Guidelines Draft v1.0 22/05/2018 Warning This document is a DRAFT DPP Metadata Exchange for News implementation guide intended for anyone looking to develop systems which are compatible with the DPP Metadata Exchange for News framework. It is subject to change without notice. Every attempt has been made to ensure that the information contained in this document is accurate. Errors in this document should be reported to the Business Owner identified below. All other inquiries in respect of this document, including inquiries as to intellectual property requirements, should be addressed to the proposer identified below. Business Owner(s) contact information: Digital Production Partnership, 4th Floor, Fat Side, ITV, 200 Gray s Inn Road, London, WC1X 8HF, UK Version Control ID Document Title Date Comment V1.0 DPP Metadata Exchange for News 22/05/2018 First Published 0

2 DPP Metadata Exchange for News Implementation Guidelines Contents 1 Scope Normative References DPP minimum metadata requirements News Production Stages and NewsML-G Planning Planning metadata XML structure Planning structure metadata definitions Acquire & Finish Acquire & Finish metadata XML structure Adding keyframes Editing Transcoding and Ingest Delivery Delivery metadata XML structure - Simple Delivery metadata XML structure - Complex Future developments

3 1 Scope This document provides Implementation Guidance for the use of the [Draft] DPP Metadata Exchange for News framework when delivering to, or exchanging, news content. This includes the following purposes: Transfer of news planning information to in-field news acquisition systems Transfer of captured assets (clips) and metadata from in-field news acquisition systems to media asset management systems Transfer of news content and metadata to NLEs Exchange of news content and metadata between international broadcasters and news agencies Modern news production workflows involve a number of distinct phases where news stories are planned, acquired, processed, broadcast and then archived. By exchanging story-related information (its metadata) each of these stages can be enhanced. The capability to capture basic metadata existed in news production when content was captured on videotape - which came with a box and a label. But as organisations moved to digital file based capture this simple capability was lost. Today, metadata is inserted retrospectively once the digital news recording has made its way to the newsroom. This process takes a huge amount of time and resources because of the sheer number of clips and recordings typically being acquired and ingested in large newsrooms. There is often a duplication of information that already exists - much of it from as early as the planning process. Clearly this is inefficient. News broadcasters and agencies agree that a minimum metadata specification for exchanging content would increase efficiency by supporting and enabling faster discovery, better rights-informed exploitation, automation and greater re-use of captured content throughout the news production workflow. This guide sets out a framework for implementation of such a minimum metadata specification, to enable the business requirements of news production to be supported via technical capability in the systems used by those teams. A constrained set of editorial, rights, technical and structural metadata based on the larger NewsML- G2 XML schema is being used by the DPP. NewsML-G2 is an international standard owned by the IPTC (International Press Telecommunications Council). This document describes the different blocks and elements needed to build valid DPP Metadata Exchange for News XML files, which can be used to transfer or exchange news content and its associated metadata. The guide sets out how system providers and equipment manufacturers can implement this common minimum metadata set designed to be used in news production and distribution. The use of IP streaming based workflows are in scope of the DPP News Exchange initiative; however, the implementation guidelines will be released in a future version of this document. 2

4 2 Normative References The following standards contain provisions which, through reference in this text, constitute provisions for this implementation. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. IPTC NewsML-G2 version DPP minimum metadata requirements Table 1.0 below lists the human-readable business requirements as agreed by the DPP News Exchange working group in April The agreed requirements have since been updated to facilitate implementation. The requirements vary slightly according to which stage of the News production process is being supported, as some information will not be available early on; but the majority of the attributes will apply and should persist throughout the lifecycle. These business requirements have been mapped to the NewsML-G2 standard and will be detailed in later sections. FIELD NAME DEFINITION Editorial Information Story Title Description Key Words (Tags) Category Genre Version Origination Time Date Duration Modification Date and Time Language Contributor Headline: a brief and snappy introduction to the content, designed to catch the reader s attention. A free-form textual description of the content of the item. Identifiers that provide categories of people, places, events, organisations, storylines. The high level categorisation of the News story; i.e. Storm, cyclone, blizzard, etc. Indicates the journalistic or conceptual characteristic of an item. News, Drama, Weather, Entertainment, Comedy, Factual, Sport etc. The persistent, universally unique identifier increment linked back to the original identifier item. The date and the time on which the content was created. The asset duration in time units defined by duration/unit. The date and time on which the content was last modified. Factual information relating to the spoken language; e.g. English, French, Spanish etc. A party (person or organisation) which modified or enhanced the content. Preferably the name of a person. 3

5 Rights Information Source/Originator A party (person or organisation) which created the asset. Copyright Holder Restrictions The person or organisation claiming the intellectual property for the asset(s). A natural-language statement about the usage terms pertaining to the asset(s). Technical Information Identifier: Item ID Identifier: System ID Identifier: Device ID Identifier: Clip ID A persistent, universally unique identifier common for all story assets created. A persistent, unique identifier of any systems that creates or modifies a story. A persistent, unique identifier of the capture device. A unique identifier of the clips(s). File Format Audio Channels Audio Format Proxy Field/IP Stream Location Technical description of the source video captured assets. Technical description of the source audio channel of the captured assets. Technical description of the source audio codec format of the captured assets. Technical description of a lower resolution version of the source A technical description of a streamed version of the source. The GPS location from which the source assets originate. Key Frame Yes/No Technical data about key frames generated from the source captured assets provided by the capture device. Table 1.0 Business requirements captured by the DPP News Exchange working group 4

6 4 News Production Stages and NewsML-G2 News production workflows vary from organisation to organisation, and may further vary depending on the type of story being covered. However, there are some broad stages that are commonly recognised. These are as follows: 1. Planning 2. Acquisition 3. Ingest 4. Editing 5. Broadcast 6. Distribution 7. Archive In addition, the process of Exchange between news organisations may occur during any of the above stages. The different stages also have an impact on the way in which the metadata is represented within the NewsML-G2 framework. This has only three stages or structures: Planning, Acquire & Finish, and Delivery. Diagram 1.0 below shows how the structure provided by the Planning part of the schema will typically map to activities performed during the production planning stage. The Acquire & Finish structure maps to the activities related to acquiring content using a camera, ingesting it into a system such as a Media Asset Management system, or Editing (either offline or online). The Delivery structure relates to activities performed when there is a finished piece of content that is ready to be broadcast or distributed via some other means such as online. It may also be used for archiving content. Planning Structure 1. Planning Acquire & Finish Structure 2. Acquisition 3. Ingest 4. Editing Delivery Structure 5. Broadcast 6. Distribution 7. Archive Diagram 1.0 Mapping of metadata structures to production processes 5

7 Table 2.0 below maps the DPP business requirements to the different structures and shows where a value is required (Y/N), whether the requirement is Mandatory (M) or Optional (O) or some variant is appropriate. The table also suggests whether a requirement should be Editable or Automated. Editable means that the data for that requirement is inserted by users and can modify it any point. Automated means that is generated by machine - however it may be static data that doesn't change (such as ids), or it could be data that changes (such as version numbers). In practice, organisations and systems will have different capabilities and over time it is anticipated that more of these will become automated. Different and equivalent blocks of the NewsML-G2 structure are required depending on the stage (as shown below), and this will be detailed in the subsequent sections below. The NewsML-G2 schema also contains structural/operational metadata, which relates to the grouping and hierarchy of elements within the XML file. Many more blocks are needed to represent the overall structure. Some of these blocks are mandatory and inherited from NewsML-G2. In some cases, the actual mapped field is a low level child and so the parent appears as a block in the overall structure. 6

8 Table 2.0 mapping business requirements to DPP Metadata Exchange for News structures (Note that in the above table Modification Date and Time in the Planning Structure is Mandatory only if the planning data has changed) 7

9 4.1 Planning The Planning stage is where the typical News production workflow commences. It is the stage where a duty editor (or similar) will identify the day s activities and planned news stories. This is the first point at which the concept of a news story emerges - where an editor, producer or journalist will create a placeholder in a system for a particular story. This is also when planning information such as a story title, description and rights information is created for the first time. To avoid having to insert metadata retrospectively in the newsroom, this planning metadata should be pushed to a video capture device and then subsequently ingested back in the newsroom. This fulfils the business requirement for metadata to persist through the News production workflow. The action of pushing planning data to an acquisition device is a form of metadata exchange - i.e. the planning system is exchanging planning information with the acquisition/capture device. A subset of the minimum metadata from the business requirements is needed at the planning stage, some of which is dependent on how much of the actual story is known in advance. Table 3.0 below maps the required Planning stage DPP Metadata Exchange for News fields or attributes to the NewsML-G2 blocks. NewsML-G2 also uses a number of reference data sources to provide recognised codes for certain values to avoid free-text, and these are usually accessed via their urls. Examples include Audio Channels, Audio Codecs, News Provider codes, News Item Nature News Codes, and Media Topic Q codes. It also requires identification data from input and destination systems or devices, which should be automated. NewsML-G2 also has operational metadata and is included here to explain the groupings and parentchild relationships within the XML structure, but this is not intended to be human readable. There are also metadata management elements to show the history of the file itself. These are shown in a further table 4.0 below. 8

10 Table 3.0 mapping of required planning stage DPP Metadata Exchange for News fields to NewsML-G2 blocks 9

11 The operational metadata fields in NewsML-G2 at the Planning stage is as follows: Table 4.0 showing NewsML-G2 operational metadata fields used at planning stage Diagram 2.0 below shows the logical structure of the NewsML-G2 blocks required at the Planning stage. These blocks are elements within the XML schema and are explained in detail in the next section. 10

12 4.1.1 Planning metadata XML structure The overall metadata structure resides within the framework of an XML schema. This section takes each element in the block diagram below and provides the NewsML-G2 definition of that element, where appropriate its mapping to the business requirements and an explanation of its usage. The NewsML-G2 definition for each block is also provided alongside the element title. Diagram 2.0 Planning structure using NewsML-G2 blocks 11

13 4.2 Planning structure metadata definitions newsmessage - A container to exchange one or more items The newsmessage is a top level (parent) container element that stores header information along with a set of items. It s an operational metadata element that is required as part of NewsML-G2. The items themselves can be considered to be containers for different information (editorial, rights and technical). At the planning stage two items are used: - a packageitem and a planningitem. Between the two items they host all the fields needed to store planning metadata as identified in the business requirements. Additionally, the newsmessage attributes provide the namespace declarations as well as references to the schema locations. header a group of properties providing information about the exchange The header element is an operational metadata field and a child of the newsmessage. It is used to provide information about an exchange, and in this case it uses the sent element which stores the date and time of transmission of the message. sent the date-and-time of transmission of the message The sent element is an operational metadata field and a child of the header element. At the planning stage this value is the date and time of when the story is saved and published to capture devices. The actual Date and Time value is contained within an element called sent which is a child of the header element. Note that the Date and Time property must conform with NewsML-G2 format - the Z at the end of the time indicates the Date and Time format is in UTC format - otherwise + or - must be used to denote time offsets to account for global time zones. An example of this provided below. 12

14 itemset - the set of items to be exchanged itemset is a child element of newsmessage and an operational metadata field. During the planning stage the itemset contains two containers that convey the editorial and rights information that should be exchanged with capture devices. The two items are the packageitem and the planningitem. They are similar in structure however they serve two purposes. The packageitem stores the rights information and acts as a container (index) for downstream production processes. For example, when story related video clips are captured, a list with references to all the clips that form the story is stored here, like an index (within a groupset). The planningitem contains the editorial information related to a planned news story. Note - to help with understanding the concept, the illustration above does not display the child elements of the packageitem and planningitem, which would normally be present packageitem - An Item used for packaging references to other Items and web resources packageitem is a child element of itemset and is an operational metadata field. This item is a container for storing references to collections of other items and its use will be important in downstream news production processes. The Acquire & Finish structure later on introduces how clips are captured within a newsitem structure (which is another item and a container for news media assets). At the planning stage of the production process, the packageitem is also where the rights information related to the planned story is stored. Most of the attributes of the packageitem are default values, which are mostly static (the value doesn t change from story to story, unless there is a change in the standard). A key attribute of the packageitem is the guid which is a persistent universally unique identifier for the packageitem: - i.e. the unique identifier for the story - Identifier: Item ID in the DPP business requirements for metadata. Here the IPTC recommends the following notation is adopted: - guid= urn:newsml:[providerid]:[dateid]:[newsitemid] Where the ProviderId = Internet domain name owned by the organisation (see above code example). The DateId is a date stamp such as and the NewsItemId is the story title i.e. the headline. Universal Unique ID (UUID) should be added to the end of a NewsItemID, for consistency and to enable the uniqueness of the guid s when used with newsitems. The UUID should conform to RFC

15 The format becomes: - guid= urn:newsml:[providerid]:[dateid]:[newsitemid]:[uuid] The following are all child elements of packageitem and each will be explained in further detail. The sample xml has been split to ease reading. catalogref rightsinfo itemmeta groupset catalogref - A reference to a remote catalog. A hyperlink to a set of scheme alias declarations catalogref is a child element of packageitem and is an operational metadata field. This element contains links to published catalogues and in this case it links to catalogues that have been published by the IPTC. rightsinfo - Expression of rights to be applied to content rightsinfo is a child element of packageitem and within the child structure it contains elements that map to the DPP Metadata Exchange for News business requirements that convey rights related information. It contains child elements that use the copyrightholder element which in turn has a number of child elements that accommodates the name, and the phone number for the organisation that holds the copyright. These are nested further down and are shown in the sample structure below. copyrightholder The person or organisation claiming the intellectual property for the content This element contains a number of child elements that conveys information about the copyright holder of the planned news story. This enables users in the process to track the rights from the planning stage, through to later stages in the news production process. It makes use of the name and organisationdetails child elements to capture this detail. name a natural language name for the concept This element maps to the DPP Metadata Exchange for News Copyright Holder requirement. The value stored in this element is the actual name of the copyright holder. Typically, this will be the name of the broadcaster or agency organisation. 14

16 organisationdetails A group of properties specific to an organisation This element is a child element of copyrightholder and stores child elements of its own to capture the organisation s phone contact information. It does this via the contactinfo and phone child elements. contactinfo Information how to contact the organisation This element is a child element of organisationdetails and makes use of the phone child element to store the contact details. phone A phone number, preferred in an international format A child element of contactinfo used to store the phone number of the organisation that holds the copyright. usageterms A natural-language statement about the usage terms pertaining to the content. This is a child element of rightsinfo and maps to the DPP Metadata Exchange for News Restrictions field. It s populated if there is a requirement to capture any known restrictions at the planning stage. If there are no known restrictions, then its value should be set to None. itemmeta - A set of properties directly associated with the Item itemmeta is a child element of packageitem and an operational metadata element. Specifically, this contains metadata about the packageitem itself. The itemclass and provider are child elements of itemmeta, whose attributes are defined by IPTC QCodes from the IPTC News Item Nature NewsCodes. The codes for the various options can be viewed/linked from the below URLs. itemclass - The nature of the item, set in accordance with the structure of its content This is an operational metadata element that is a child of itemmeta. The values are derived from the below catalogue. provider The party (person or organisation) responsible for the management of the Item. This is an operational metadata element that is a child of itemmeta. The values are derived from the below catalogue. Note - DPP is not currently a news provider and is used here for illustrative purposes There are four additional child elements of itemmeta used here and these are detailed in the below: - versioncreated - The date and time in UTC format on which the current version of the Item was created versioncreated is a child element of itemmeta. This should change if there is a version increment of the packageitem. 15

17 firstcreated - The date and time on which the first version of the Item was created firstcreated is a child element of itemmeta. Once set this should remain static. generator - the name and version of the software tool used to generate the Item generator is a child element of itemmeta. This element maps to the DPP Metadata Exchange for News System ID requirements makes use of an attribute called the versioninfo, which conveys the version number of the software in use (i.e. the newsroom planning system) and the value of this element conveys the unique identifier of the system that generates the planning data. profile - the name of the structural template (aka profile) used for the generation of the Item profile is a child element of itemmeta and an operational metadata field. This element is used to help distinguish between DPP implementation of the NewsML-G2 standard and other third party implementations. Furthermore, it also helps identify the stage of the news production process. At the planning stage DPP_metadata_news_planning is used. groupset - A hierarchical set of groups groupset is a child element of packageitem and an operational metadata element. A groupset element is like an index that references other items and is required to support the next stages in the production process. It allows other items such as newsitems to be grouped. At the planning stage it is used to reference and index the planningitem. The groupset makes use of the group and itemref child element, which is where the link to the respective item is stored. It uses the root attribute to identify the name of the root group and to determine what the parent group is. The root attribute should be the same value as the id value of the first group i.e. the System ID of the planning system. group - A mixed set of group references and references to items or Web resources group is a child element of the groupset and is an operational metadata element. The id attribute helps identify the group within the groupset. It also makes use of the role attribute to identify where within the groupset structure this group sits (i.e planning). At planning there should only be a single group though in other stages of the production process, such as when content has been acquired, there could be multiple groups. The value of the id attribute should be the system id number of the newsroom planning system. This enables the group to be linked to the system that generated it. The value of the id attribute is prefixed with the word System_ followed by the id of the newsroom planning system. This is because the id value of the attribute starts with a letter or underscore and cannot start with an integer value, which can become an issue if the newsroom planning system id begins with a number. itemref - A reference to a target item or Web resource itemref is a child element of group and an operational metadata element. The residref attribute is used as a reference link to another item that s part of the itemset, such as the planningitem. In this case the guid of the planningitem item is used as the pointer. Diagram 4.0 below shows how guids in a planningitem are referenced to a group within a packageitem. The group can be considered as an index of related items. 16

18 Diagram 4.0 showing how groups reference different items (planningitem shown here) The full packageitem can be seen below: - 17

19 planningitem - An Item containing information about the planning and delivery of news coverage planningitem is a child element of itemset and an operational metadata element. It acts as the container for all child elements that store the relevant editorial information that applies to the planning structure. Other than the guid which has to be different and unique, the rest of the attribute values are the same as for a packageitem. To ensure that consistently unique guids can be generated the following format is to be adopted: - guid= urn:newsml:[providerid]:[dateid]:[newsitemid]:[uuid] The following are all child elements of planningitem and each will be explained in further detail. The sample xml below has been split to ease reading. catalogref itemmeta contentmeta newscoverageset catalogref - A reference to a remote catalog. A hyperlink to a set of scheme alias declarations catalogref is the first child element and is used in the same way as described earlier in the packageitem. itemmeta - A set of properties directly associated with the Item itemmeta is a child element of planningitem. Specifically, this contains metadata about the planningitem itself. The itemclass and provider are child elements of itemmeta, whose attributes are defined by IPTC QCodes from the IPTC News Item Nature NewsCodes. The codes for the various options can be viewed/linked from the below URLs. itemclass: - provider: - versioncreated - The date and time in UTC format on which the current version of the Item was created versioncreated is a child element of itemmeta. This should change if there is a version increment of the planningitem. From the DPP Metadata Exchange for News business requirements this element represents the Modification Date and Time requirement. The value needs to change when the planningitem is changed. firstcreated - The date and time on which the first version of the Item was created firstcreated is a child element of itemmeta. Once set automatically this should remain static. 18

20 From the DPP Metadata Exchange for News business requirements this element represents the Origination Time Date requirement. contentmeta - Content metadata for a Planning Item contentmeta is a child element of planningitem. The editorial metadata for the planned story is captured within this container. From the DPP Metadata Exchange for News business requirements, Source / Originator, Contributor, Story Title, Description, Key words (Tags), Category and Language are all represented by child elements within this structure. creator - A party (person or organisation) which create the resource creator is a child element of contentmeta. The creator element uses the name child element - the name value is the name of the news organisation that has created the planned item such as BBC, ITV, ITN etc. It maps to the Source / originator requirements of the DPP Metadata Exchange for News requirements. contributor - A party (person or organisation) which modified or enhanced the content, preferably the name of a person contributor is a child element of contentmeta. The contributor element uses a combination of role attribute and child element called name. The name element stores the actual value, however the role attribute defined by a Qcode specifies the type of contributor. A number of roles have been defined by the IPTC, such as Correspondent, Camera Operator, Interviewee. These are referenced by the following newscodes library - name a natural language name for the concept This element maps to the DPP Metadata Exchange for News Contributor requirements. The name value is the name of a contributor that will feature or appear in the news recordings. If more than one contributor is scheduled to appear (e.g. an interviewee and a correspondent) then additional name elements can be used to store their details. headline - A brief and snappy introduction to the content, designed to catch the reader s attention The headline is a child element of contentmeta. It maps to the DPP Metadata Exchange for News requirements identified as Story Title. Its value is used to store the title of a story. 19

21 description - A free-form textual description of the content of the item The description is a child element of contentmeta. The element maps to the DPP DPP Metadata Exchange for News identified as Description. Its value is used to store a detailed description of the story. keyword - Free-text term to be used for indexing or finding the content of text-based search engines keyword is a child element of contentmeta. The value of the element is the keyword term to be used. It maps to the Key words (tags) DPP Metadata Exchange for News requirement. If there s more than one keyword, then additional elements should be used for each keyword term. subject - An important topic of the content; what the content is about subject is a child element of contentmeta. The value of this element meets the DPP Metadata Exchange for News requirement to classify the news story as belonging to a certain Category of news. Within NewsML-G2 this is represented by Media Topic QCodes. For ease of use, the associated value of the QCode is stored through a child name element. name a natural language name for the concept This element is child of subject. It s used to store the Category of news in human-readable format. language - A language used by the news content language is a child element of contentmeta. The value of this element meets the DPP Metadata Exchange for News requirement to capture the main Language of the news story. NewsML-G2 specifies that the tag attribute is used whose values are derived from BCP 47 - the IETF convention for abbreviating languages. See newscoverageset - A set of data about planned and delivered news coverage newscoverageset is a child element of planningitem. This container is used to store the assignment of a story to a video acquisition device and also the genre of a story as such it is an operational metadata element. It uses the child element called newscoverage to do this. newscoverage - Information about the planned and delivered news coverage of the news provider newscoverage is a child element of newscoverageset. This element contains a child element called planning that stores the assignment of camera device IDs and genre of the story. It s an operational metadata element. 20

22 planning - Details about the planned news coverage by a specific kind of G2 item planning is a child element of newscoverage. This element makes use of two child elements, assignedto and genre. This is an operational metadata element. assignedto - The party which is assigned to cover the event and produce the planned G2 item assignedto is a child element of planning. It makes use of the name child element, whose value is used to store the device ID of the camera that the planning information is being issued to. This element also maps to the Identifier: Device ID DPP Metadata Exchange for News requirement. An additional assignedto element is required for each additional device that the story has been assigned to. NOTE: If a story has been assigned to two or more devices and discretion is required between them (e.g. they could be freelancer), it can become necessary to publish the metadata to the devices with only one resource specified in the assignedto element. Each device would receive metadata with only a single entry in the assignedto element that is unique to it. genre A nature, intellectual or journalistic form of the content genre is a child element of planning. The value of this element meets the DPP Metadata Exchange for News requirement to classify the news story as belonging to a certain Genre of news. Within NewsML-G2 this is represented by Product Genre QCodes. The sample above shows how the story has been assigned to two devices. 21

23 The full planningitem is shown below: Acquire & Finish Typically, the Acquire & Finish stage will follow the Planning stage in a news production workflow. It begins when a story is planned in the planning system and then assigned to correspondents and camera crews for coverage. The planning metadata from the planning system is sent to one or more camera acquisition devices. At acquisition the camera device(s) receives the planning information via an appropriate transport mechanism - such as or other file transfer mechanism. It may be received directly by the device or via an intermediary connected app. As the camera device is recording clips it is augmenting the planning information with technical metadata associated with that recording. The camera may not be aware of other devices that the story has been assigned to as the metadata is local to the camera. The metadata will be consolidated later on during editing to include clips from other cameras or sources. There are a number of different scenarios to consider from a news gathering perspective and depending on the scale of the news story. A story may be covered independently by a broadcaster using their own resources and perhaps also choosing to exchange clips with other organisations. The Acquire & Finish metadata structure accommodates for scenarios where a number of organisations 22

24 may get together to share resources. A camera operator may record on behalf of a host but then the recording is shared among the other organisations. Furthermore, the Acquire & Finish metadata structure can be used for downstream production processes such as ingest and editing. In a typical scenario where the material is being sent back to the production office straight after capture (i.e. no local edits are made), media files may be transferred electronically, transcoded to a house format and then ingested into a Media Asset Management (MAM) system. Once in the MAM it may be edited (online edit), scheduled for broadcast, processed further (e.g. for Online) and subsequently archived. The metadata is simply updated as it passes from system to system. The metadata structure is flexible enough to accommodate both online and offline edits. Typically, offline edits are made in the field by a correspondent or a journalist who then files the content back to the production office. Online edits are typically made in the production office by accessing the MAM via an appropriate editing platform. In these kinds of scenarios the Acquire & Finish XML structure remains the same, but the data values change. From a business requirements perspective, all of the minimum metadata set is needed at the Acquire & Finish stage. Table 5.0 below maps the required Acquire & Finish stage DPP Metadata Exchange for News fields or attributes to the NewsML-G2 blocks. 23

25 Table 5.0 DPP Metadata for News requirements mapped to Acquire & Finish NewsML-G2 blocks 24

26 Operational metadata is included in the NewsML-G2 Acquire & Finish schema to explain the groupings and parent-child relationships within the XML structure, but this is not intended to be human readable. There are also metadata management elements to show the history of the file itself. These are shown in a further table 6.0 below and the rows highlighted in green are introduced in the Acquire & Finish structure. Table 6.0 showing additions to the operational metadata in the Acquire & Finish stage Diagram 5.0 below shows the NewsML-G2 blocks required at the Acquire & Finish stage. These blocks are elements within the XML schema and are explained below. 25

27 4.3.1 Acquire & Finish metadata XML structure Diagram 5.0 Acquire & Finish NewsML-G2 blocks This builds on the structure that was created in the planning stage with updates to elements in the packageitem, planningitem and introduction of a new item called the newsitem. The section below explains where changes to values are expected in existing elements and the introduction of a new element (an item) called the newsitem. newsmessage - A container to exchange one or more items In the header element of the newsmessage the sent element is updated to reflect the time and date at which the newsmessage is sent onwards via file transfer (or last saved for manual transfer) to the next stage in the process. 26

28 packageitem - An Item used for packaging references to other Items and web resources In the packageitem the version attribute is incremented to reflect that this is an updated package. Note that the version can only be a positive integer and should only be incremented at key exchange points. Within the itemmeta structure of the packageitem the value of the versioncreated element will need to be updated to reflect the date and time stamp of when this particular version is created. The version of the packageitem may change for example during edits if additional newsitems are created which results in the groupset being updated. profile - the name of the structural template (aka profile) used for the generation of the Item profile is a child element of itemmeta. This element is used to help distinguish between DPP implementation of the NewsML-G2 standard and other third party implementations. Furthermore, it also helps identify the stage of the news production process. It s also an operational metadata element. At the Acquire & Finish stage DPP_metadata_news_af is used (af = acquire & finish). This field should be set automatically by the system. groupset - A hierarchical set of groups At the Acquire & Finish (af) stage the groupset (which is a child element of packageitem) is updated. The groupset is an operational metadata element and acts much like an index. It contains reference links to the guids of different items (planningitem and newsitems) contained in the itemset. newsitems are introduced to the package at the af stage (the video clip related metadata structure). The difference is that at the planning stage the groupset is used to reference and index only the planningitem and at the af stage, newsitems are a new addition into the group. The group element containing the details for the planningitem remains unchanged, as does the attributes of the groupset. The number of groups within the structure will vary depending on the part of the production process. For example, at content capture by a camera, the output xml file will only contain a total of two groups. The first group referencing the planningitem and the second group referencing one or more newsitem as shown below in diagram 6.0. Furthermore, the quantity of itemref within a group will match the number of newsitem that have been generated. (One newsitem per video file). 27

29 Diagram 6.0 multi-group packageitem referencing a number of other items In later stages in the production process, additional groups could be required. If we take a simple edit as an example, a different group is required for each clip that has originated from another source. So in an edit where material has been captured from two different cameras, a total of three groups will be required. The first being the planningitem, the second group referencing the first capture device and the third group referencing the material acquired from another (second) capture device. This is typical of an offline edit scenario. 28

30 Diagram 7.0 clips from each source device is assigned its own group If at the end of editing, the file is rendered into a single video file, then this will result in a single newsitem being required to reflect the rendered file. It will in essence become content that is in the delivery stage which is covered later. The example XML below shows the structure of the groupset at the output of a camera: - The groupset shown in the sample above contains two groups that are child elements. One which contains a reference to the planningitem and the other which contains a reference to a newsitem. The 29

31 reference is via the urn in the itemref. The group id of the second group is in the format Device_Device_ID where the Device_ID is the unique identifier of the camera acquisition device. The id begins with the word Device because as per the NewsML-G2 standard, the id attribute cannot start with an integer. The role attribute is group:af to indicate that it is part of the Acquire & Finish structure. itemref - A reference to a target item or Web resource The itemref elements in this group are links to newsitems. The total number of itemref in a group will equal the total number of individual video files recorded. If a series of video files are rendered into a single file, then that will result in a single newsitem - and thereby a single itemref should be present in the group (this is the case when a sequence of clips recorded on a camera are exported as a single file). planningitem - An Item containing information about the planning and delivery of news coverage The planningitem remains mostly unchanged except for the addition of a new child element called delivery in the newscoverage element (detailed below). The version is incremented and versioncreated is updated. delivery - A set of references to G2 items which have been delivered under this news coverage definition. delivery is a child element of newscoverage. It is used to indicate that a planneditem has been delivered and by using a reference it links the planneditem to the associated newsitem. It makes use of a child element called delivereditemref. delivereditemref - a reference to a G2 item which has been delivered under this news coverage definition The attribute residref is used here whose value is a urn link to the newsitem guid. Note that each newsitem requires a corresponding reference (i.e. each recorded file requires a corresponding entry). newsitem - An Item containing news-related information The major difference in the structure of the XML in the Acquire & Finish (af) stage occurs with the introduction of the newsitem. This is a new container structure required to capture the metadata of news video assets. The structure requires one newsitem per recorded video file. The number of newsitems in the itemset are impacted by the configuration of the camera during acquisition. When recording a sequence of video clips some cameras will render it as separate files and others will render it as a continuous video file. In the former scenario - a newsitem is required per video clip recorded (i.e. file). If there is a sequence of 50 video files, then 50 newsitems will be required. 30

32 On the other hand, if the sequence is rendered as a single video file then only one newsitem is required. This is similar to a finished piece of content that is ready to be exchanged with a third party. The underlying video asset could be a single video file such as an mp4. The broad structure of the newsitem is similar to the other items such as packageitem and planningitem. It makes use of some of the same attributes that were used for the planningitem and packageitem - guid, version, standardversion, conformance and xml:lang. To create a persistent unique guid - the urn is appended with a UUID. It also makes use of the catalogref and itemmeta elements in much the same way. However, in the itemmeta it should be noted that the versioncreated should be the date time stamp when the video clip was created. There is an additional new element inserted in the itemmeta called deliverableof. role the role of the Item in the editorial workflow role is a child element of itemmeta and an operational metadata element. It uses a child element called name and offers the ability to capture the status of the item in the news production process. For instance an editor may want to flag this item up as Work-in progress. name a natural language name for the concept name is a child element of role and an operational metadata element. It s used to capture editorial status of the item. It s a free form field so can be populated with statuses as appropriate e.g. status can be added manually or from a pre-existing list. deliverableof - a reference to the Planning Item under which this item has been published deliverableof is a child element of itemmeta. It uses an attribute called residref the value of which is the guid that references the associated planningitem. contentmeta - a set of properties about the content contentmeta is a child element of newsitem. This container structure stores the GPS co-ordinates of recorded clips and the unique identifier of the capture device (device ID). It does this via a number of child elements - located and infosource. located - the location from which the content originates located is a child element of contentmeta. It contains child elements that store the GPS coordinates of the actual location of the recorded material. It uses the geoareadetails element to store the GPS value. 31

33 geoareadetails - A group of properties specific to a geopolitical area geoareadetails is a child element of located. It makes use of the position child element to store the GPS coordinates. position - the coordinates of the location position is a child element of geoareadetails. This is the actual element that stores the GPS value. It uses the attributes latitude and longitude whose value is in the decimal degree format - eg. latitude=" " longitude=" " infosource - a party (person or organisation) which originated, distributed, aggregated or supplied the content or provided some information used to create or enhance the content infosource is a child element of contentmeta. It has two attributes which are used, the first of which is the role as defined in It also has a name child element whose value is used to store the actual unique identifier of the capture device. The role is set to isrol:origcont - The second attribute is called type and has the value "cpnat:object". name - a natural language name for the concept name is a child element of infosource. The value of this element is the unique identifier of the capture device. The maps to the Unique identifier - device ID from the business requirements. contentset - a set of alternate renditions of the Item content contentset is a child element of newsitem. This element stores the technical details of the video asset. It does this via a child element called remotecontent. remotecontent - a rendition of the content using a reference/link to a resource representing the content data at a remote location remotecontent is a child element of contentset. It makes use of a number of attributes which map to the DPP Metadata Exchange for News business requirements. The attribute id - is the unique identifier of the clip - i.e. clip ID. However, the actual id has been prefixed with the word clip. This is because in NewsML-G2 id attributes must start with a letter or underscore. Some camera systems will generate unique identifiers that start with integers values. The residref is another attribute that stores the clip ID but this time it stores the value without a prefix. This attribute can be used if a clean version of the actual clip ID is required. href attribute stores a link to the video asset - i.e. the video file. 32

34 contenttype - the IANA mime type of the target resource. durationunit - defines the time unit of the duration attribute. This is defined by the IPTC at the following link: - duration - the actual duration in seconds of the video asset. audiocodec the applicable codec used to encode the audio such as MP3 or LPCM This is expressed as a Qcode. audiochannels - defines the audio channels format of the video. It makes use of EBU definitions which can be found at the following link: - Another application of remotecontent is to store an alternate rendition of the same content. It is conceivable that a camera may be configured to generate a high resolution copy and a proxy at the same time. To capture both renditions a second remotecontent element can be used that references the alternate rendition Adding keyframes The newsitem structure seen so far is the basic structure to accommodate multiple video assets. In field operations may require for a user such as a camera operator to define key frames. The business requirement is to indicate whether a key frame is present or alternatively to identify the markers at which the key frame resides on the recording. This is achieved by the introduction of a new child element called partmeta into the newsitem. partmeta - A set of properties describing a specific part of the content of the Item partmeta is a child element of newsitem and is used here to identify key frames within a video clip. It makes use of three child elements to link to the asset representing the key frame - i.e. the image file, the first is icon which is the href link to the asset and then its uses the child element timedelim to point to the location in the video asset where that keyframe occurs. Finally, it uses the role element to describe that this is referencing a key frame. It also utilises an attribute called contentrefs which is a list of identifiers that describe the content represented by this element. Here it is used as a pointer to the video asset - the clip, using the clip s unique identifier (the value stored in - see previous section on remotecontent). 33

35 icon - An iconic visual identification of the content icon is a child element of partmeta and is used to store the link to the asset representing the keyframe. It makes use of two attributes href which stores the link to the image file and then contenttype which stores the IANA mime type of the asset. timedelim - a delimiter for a piece of streaming media content expressed in various time formats timedelim is a child element of partmeta and is used to mark and identify the time at which the key frame occurs. It makes of three attributes which are start, end, and timeunit. The start time is the point at which the marker is set - and is a time unit from the beginning of the clip. The end attribute does not contain a value as this is used to identify a key frame. The timeunit attribute makes use of an IPTC defined value timeunit:normalplaytime. role is a child element of partmeta and makes use of a child element called name to describe the purpose of this part i.e. to describe that it is being used in the context of a keyframe. 34

36 A complete example of a single newsitem is shown below, in practice there will be multiple newsitem: Editing This section will address the treatment of metadata during editing. Editing can take place offline or online. In both of these scenarios the treatment of metadata is broadly the same. First, the media assets need to be loaded up into the non-linear editing (NLE) system. The NLE should be able to load up/or import the media asset along with the corresponding DPP Metadata Exchange for News files. The structure at this stage will be based on the metadata that has been delivered to the system, that could include the Acquire & Finish structure or the Delivery structure (see later section). In the edit timeline there may be one or more clips and for each clip there will be a corresponding newsitem. If one or more clips are trimmed, then the corresponding duration value in the associated newsitem needs to be updated. It should be noted that the timeline could be rendered out into a single file, in 35

37 which case only one newsitem with the total duration of all of the clips is stored as the value in the output file. The Delivery structure is likely to apply to the output metadata file if the timeline is rendered. The structure does accommodate for sequences of clips and so the clip related metadata is still retained. Edit systems may also offer the ability to update the metadata from within the system. For example, if the story has evolved and the description needs to be updated then the description element must be capable of being amended. For any similar amendments, the impact is such that the version number and versioncreated of the respective item needs to be updated Transcoding and Ingest This section will address the treatment of metadata during transcode and ingest into Media Asset Management (MAM) systems. In a typical newsroom scenario prior to ingest into the organisation s MAM the content is transcoded to one or more formats. Depending on the configuration of the workflow, if the original format is discarded then only details within in the remotecontent element need be updated. If the original format is retained, then the transcoded version is a new rendition in which case a new remotecontent element is required. Transcoders may also have deep integrations with MAMs, in which case the metadata exchange between the two systems is not necessarily via the transfer of files but rather the exchange of data via web service calls. The transcoders will therefore need to be able to read the metadata file and pass the data values to the MAM. If the MAM is directly ingesting content, then the MAM is to be able to read the metadata file and store the data values and the file accordingly. If the MAM is used to export the media asset, then it is to be capable of generating the appropriate metadata file according to the stage it s in - either Acquire & Finish or Delivery. 4.4 Delivery The structure for Delivery is more streamlined than previous stages, as the news story would have evolved into a finished product ready for delivery for transmission or distribution. It would have gone through the production process (as covered in the Acquire & Finish stages), with all the different clips edited and rendered into a single video file. Only a single newsitem is required since there is now a single video file (though it can have multiple renditions). In practice there will be instances where there could be more than one newsitem - for instance some operators may also use additional newsitem to convey text or image based content, in addition to the video file. However, for the purposes of exchanging a video asset with DPP Metadata Exchange for News only a single newsitem is required. The planningitem is no longer present as planning information is not needed when it s going to be exchanged or stored in archive. Previously some of the editorial information was stored in the planningitem. This information is now stored in the packageitem. From a business requirements perspective, all of the minimum metadata set is needed at the Delivery stage. Table 7.0 below maps the required Delivery stage DPP Metadata Exchange for News fields or attributes to the NewsML-G2 blocks. 36

38 Table showing required DPP Metadata for News fields mapped to NewsML-G2 at the Delivery stage 37

39 Operational metadata for the Delivery structure shown in the table 8.0 below: Table showing operational metadata required at the Delivery stage The section below sets out the NewsML-G2 blocks required at the Delivery stage. This is a simpler structure compared to what has been used before. It no longer contains any planning information (as it is no longer required). At its core, all that is required is a packageitem and a newsitem as shown in Diagram 8.0 below. Two scenarios and the respective structures are detailed below for implementation. In practice there could be other variations to this. A simple version of the structure can be used for rendered video news package that have the same rights and restrictions for all clips. A complex structure is required when the package consists of one or more clips that have bespoke rights and restriction that are different from the main package shown in Diagram 9.0. For example, a complex Delivery structure is required if a news story has global usage rights except for one clip that was supplied by a third party who has specified that the clip can only be used in a specific region only Delivery metadata XML structure - Simple In the simple version, the rendered video news package has the same rights and restrictions for all clips. A single uniform right exists across the whole package. 38

40 Diagram Delivery Structure Simple - with single rights and restrictions 39

41 The elements in use are as follows: - newsmessage - A container to exchange one or more items In the header element of the newsmessage the sent element should be updated to reflect the time and date at which the newsmessage is sent onwards via file transfer (or last saved for manual transfer) to the next stage in the process. Note that itemset is still required - see previous sections for details. packageitem - An Item used for packaging references to other Items and web resources In the packageitem the version attribute is incremented to reflect that this is an updated package. Note that the version can only be a positive integer and should only be incremented at key exchange points. rightsinfo - Expression of rights to be applied to content rightsinfo is a child element of packageitem. This element contains child elements that convey rights related information. This uses the copyrightholder element which in turn has a number of child elements that accommodates the name, and the phone number for the organisation that holds the copyright. These are nested further down in the tree structure. Any known restrictions are indicated by making use of the usageterms element. However, if there are no restrictions then the value of the usageterms is set to none. Note that in the simple structure the rights applied here represent the whole package. If the package includes clips that have bespoke rights and restrictions, then those rights are reflected by using the complex structure. 40

42 itemmeta - A set of properties directly associated with the Item itemmeta is a child element of packageitem. Specifically, this contains metadata about the packageitem itself. The itemclass and provider are child elements of itemmeta, whose attributes are defined by IPTC QCodes from the IPTC News Item Nature NewsCodes. The codes for the various options can be viewed/linked from the below URLs. itemclass: - provider: - Note - DPP is not currently a news provider and is used here for illustrative purposes There are four additional child elements of itemmeta used here and these are detailed in the below: - versioncreated - The date and time in UTC format on which the current version of the Item was created versioncreated is a child element of itemmeta. This should change if there was a version increment of the packageitem. From the DPP Metadata Exchange for News business requirements this element represents the Modification Date and Time requirement. The value needs to change when the packageitem is changed. Note that during the previous two stages planning, acquire and finish the element from the planningitem was used. In the delivery structure the planningitem is no longer present so the packageitem is used instead. firstcreated - The date and time on which the first version of the Item was created firstcreated is a child element of itemmeta. This maps to the Origination Time Date DPP Metadata Exchange for News requirements. Once set this should remain static. generator - the name and version of the software tool used to generate the Item generator is a child element of itemmeta. This element makes use of an attribute called the versioninfo, which conveys the version number of the software in use (i.e. the media asset management system) and the value conveys the unique identifier of the system that generates the packageitem data. profile - the name of the structural template (aka profile) used for the generation of the Item profile is a child element of itemmeta. This element is used to help distinguish between DPP implementation of the NewsML-G2 standard and other third party implementations. Furthermore, it also helps identify the stage of the news production process. At the delivery stage DPP_metadata_news_delivery is used. contentmeta a set of properties about the content contentmeta is a child element of packageitem. The editorial metadata that was originally derived from the planned story is captured within this container. From the DPP Metadata Exchange for News business requirements, Origination Time Date, Source / Originator, Contributor, Story Title, 41

43 Description, Key words (Tags), Category and Language are all represented by child elements within this structure. contentcreated - The date (and optionally the time) on which the content was created contentcreated is a child element of contentmeta. This element is used to store the date and time value when a planning item is created. It should be set when a planning item is first saved in the planning system. This element represents the DPP Origination Time Date requirement. It should be noted that this element does not need to be represented in the UTC offset format. From a NewsML-G2 standard perspective the time is optional, in the context of this application, when used, both the date and time must be present. creator - A party (person or organisation) which create the resource Creator is a child element of contentmeta. The creator element uses the name child element - the name value is the name of the news organisation that has created the planned item such as BBC, ITV, ITN etc. It maps to the Source / originator requirements of the DPP. contributor - A party (person or organisation) which modified or enhanced the content, preferably the name of a person contributor is a child element of contentmeta. The contributor element uses the role attribute and name child element - The name value is the name of a contributor that will feature in the news recordings. The role attribute is defined by a Qcode and specifies the type of contributor. A number of contributor roles have been defined by the IPTC, such as Correspondent, Camera Operator, Interviewee. These are referenced by the following newscodes library - If more than one contributor is involved, then additional name elements can be used to store their details. headline - A brief and snappy introduction to the content, designed to catch the reader s attention The headline is a child element of contentmeta. It maps to the DPP Metadata Exchange for News business requirements identified as Story Title. Its value is used to store the title of a story. description - A free-form textual description of the content of the item The description is a child element of contentmeta. The element maps to the DPP business requirements identified as Description. Its value is used to store a detailed description of the story. keyword - Free-text term to be used for indexing or finding the content of text-based search engines keyword is a child element of contentmeta. The value of the element is the keyword term to be used. If there is more than one keyword then additional elements should be used for each term. 42

44 subject - An important topic of the content; what the content is about subject is a child element of contentmeta. The value of this element meets the business requirement to classify the news story as belonging to a certain Category of news. Within NewsML-G2 this is represented by Media Topic QCodes. For ease of use the associated value of the QCode is stored through a child name element. language - A language used by the news content language is a child element of contentmeta. The value of this element meets the business requirement to capture the main language of the news story. NewsML-G2 specifies that the tag attribute must be used whose values are derived from BCP 47 - the IETF convention for abbreviating languages. See genre - The party which is assigned to cover the event and produce the planned G2 item genre is a child element of planning. The value of this element meets the business requirement to classify the news story as belonging to a certain Genre of news. Within NewsML-G2 this is represented by Product Genre QCodes. groupset - A hierarchical set of groups At the Delivery stage the groupset (which is a child element of packageitem) is updated. It provides links to newsitems (the video clip related metadata structure) and thereby allows the newsitem to be part of the package. The groupset makes use of the group and itemref child element, which is where the link to the respective item is stored. It uses the root attribute to identify the name of the root group and to determine what the parent group is. The root attribute is already present and is the system ID of the MAM or equivalent system that has generated this packageitem (i.e. equal to the ID value of the first group). As a minimum, at the delivery stage a single corresponding group should exist in the groupset. An example of this is provided below: - 43

45 The groupset above has one group - which contains a reference to the newsitem. The reference is via the URN in the itemref. The role attribute is group:delivery. In the delivery stage a series of video files are rendered into a single file which results in a single newsitem - and thereby a single itemref should be present in the group. newsitem - An Item containing news-related information The newsitem has been used before in the Acquire & Finish stages. This is the container structure required to capture the metadata of news video assets. The structure requires one newsitem per recorded video file. At the delivery stage a single newsitem is created. The broad structure of the newsitem is similar to the other items such as packageitem and planningitem. It makes use of some of the same attributes that were used for the packageitem - guid, version, standardversion, conformance and xml:lang. Depending on the scenario the version of the newsitem may be reset to 1 if for example this is the first version that has been produced for exchanging with a third party. catalogref - A reference to a remote catalog. A hyperlink to a set of scheme alias declarations catalogref is a child element of newsitem. This element contains links to published catalogues and in this case it links to catalogues that have been published by the IPTC and the EBU. As this newsitem also contains information about the video asset it references an additional library that describes the different audio formats. <catalogref href=" /> <catalogref href=" itemmeta - A set of properties directly associated with the Item itemmeta is a child element of newsitem. Specifically, this contains metadata about the newsitem itself. The itemclass and provider are child elements of itemmeta, whose attributes are defined by IPTC QCodes from the IPTC News Item Nature NewsCodes. The codes for the various options can be viewed/linked from the below URLs. itemclass: - provider:

46 Note - DPP is not currently a news provider and is used here for illustrative purposes There are four additional child elements of itemmeta used here and these are detailed in the below: - versioncreated - The date and time in UTC format on which the current version of the Item was created versioncreated is a child element of itemmeta. This should change if there was a version increment of the newsitem. firstcreated - The date and time on which the first version of the Item was created firstcreated is a child element of itemmeta. Once set this should remain static. deliverableof - a reference to the Planning Item under which this item has been published deliverableof is a child element of itemmeta. It uses an attribute called residref the value of which is the guid that references the associated planningitem. At the Delivery stage the value is set depending on the scenario and therefore it is optional. There may be scenarios such as for internal archiving that the reference to the planningitem may be retained but also it is unlikely that this reference is needed when creating a distribution. role - The role of the Item in the editorial workflow role is a child element of itemmeta. This makes use of a child element called name that describes the state of the newsitem. name - A natural language name for the concept name is a child element of role. This contains a description of the state of the newsitem. This is a free form field to capture an editorial description of the state of the newsitem. For example, in a Delivery package the role value could be set to complete to indicate that it s the final edited version. link - A link from the current Item to a target Item or Web resource link is a child element of itemmeta. In the simple Delivery structure where the video has the same set of rights for the whole duration, the link is used to store the path to the packageitem. Although the newsitem is in the same overall itemset - items cannot inherit properties. So a link is used as a substitute. It makes use of two attributes: - residref - The provider s identifier of the target resource reluri - The identifier of the relationship between the current Item and the target resource - expressed by a URI 45

47 located - the location from which the content originates located is a child element of contentmeta. It contains child elements that store the GPS coordinates of the actual location of the recorded material. It uses the geoareadetails element to GPS value. In practice for the Delivery stage it is likely that this will not be populated over privacy and data protection concerns. geoareadetails - A group of properties specific to a geopolitical area geoareadetails is a child element of located. It makes use of the position child element to store the GPS coordinates. position - the coordinates of the location position is a child element of geoareadetails. This is the actual element that stores the GPS value. It uses the attributes latitude and longitude whose value is in the decimal degree format - eg. latitude=" " longitude=" " There may be a number of cases where the GPS co-ordinates are not appropriate to be shared so often this information may be missing. infosource - a party (person or organisation) which originated, distributed, aggregated or supplied the content or provided some information used to create or enhance the content infosource is a child element of contentmeta. It has two attributes which are used, the first of which is the role as defined in It also has a name child element whose value is used to store the actual unique identifier of the capture device. The role is set to isrol:origcont - The second attribute is called type and has the value "cpnat:object". name - a natural language name for the concept name is a child element of infosource. The value of this element is the unique identifier of the capture device. The maps to the Unique identifier - device ID from the business requirements. contentset - a set of alternate renditions of the Item content contentset is a child element of newsitem. This element stores the technical details of the video asset. It does this via a child element called remotecontent. remotecontent - a rendition of the content using a reference/link to a resource representing the content data at a remote location remotecontent is a child element of contentset. It makes use of a number of attributes which map to the business requirements. The attribute id - is the unique identifier of the clip - i.e. clip ID. However, 46

48 the actual id has been prefixed with the word clip. This is because in NewsML-G2 id attributes must start with a letter or underscore. Some systems will generate unique identifiers that start with integers values which is why it has been appended with a prefix. The residref is another attribute that stores the clip ID but this time it stores the value without a prefix. This attribute can be used if a clean version of the actual clip ID is required. href attribute stores a link to the video asset - i.e. the video file. contenttype - the IANA mime type of the target resource. durationunit - defines the time unit of the duration attribute. This is defined by the IPTC at the following link: - duration - the actual duration in seconds of the video asset audiocodec the applicable codec used to encode the audio such as MP3 or LPCM This is expressed as a Qcode. audiochannels - defines the audio channels format of the video. It makes use of EBU definitions which can be found at the following link:

49 A complete example of a sample can be found below: - Continues below 48

50 Continues below 49

51 50

52 4.4.2 Delivery metadata XML structure - Complex A complex Delivery structure is required when the package consists of one or more clips that have bespoke rights that are different from the main package. This section details the changes that required to the Delivery structure in this more complex scenario. Everything else can be assumed to be the same as the simple Delivery structure. Diagram Delivery Structure - Complex with multiple rights and restrictions 51

53 Within the newsitem structure a rightsinfo element is required per clip that has unique rights. rightsinfo - Expression of rights to be applied to content rightsinfo is a child element of newsitem. This element contains child elements that convey rights related information. This uses the copyrightholder element which in turn has a number of child elements that accommodates the name, and the phone number for the organisation that holds the copyright. These are nested further down in the tree structure. usageterms element is used to capture any known restrictions at the clip level. However, there is a difference from previous use of rightsinfo. In this structure the attribute idrefs is used to identify the partmeta that contains specific sequence of clip that contains the unique rights. If another clip within the video has a different set of rights then another rightsinfo element is required to describe that - and then its links to the part where this occurs in the video using the value of the idrefs attribute. Diagram 10.0 below shows an illustration of a timeline that consists of four different clips. Within the newsitem the four clips are reflected within the partmeta which defines the identifier e.g. Part1_ID and then referenced by the rightsinfo attribute idrefs. Diagram 10.0 showing an illustration of a timeline with different clips 52