Introduction
This document is for all those interested in promoting efficient exchange and re-use of multi-media news content within their own organisations and with information partners, using open standards and technologies.
Whilst a good deal of the content of this document is aimed at technical architects and software writers, business influencers and decision-makers are encouraged to read the Executive Summary, which gives a broadly non-technical justification for the use of IPTC Standards, and how they may be applied to solve the real-world issues of all organisations that create or consume news.
Purpose and Audience
The Guidelines are intended to provide implementers of the NewsML-G2 Standards with a thorough knowledge of the XML data structures used to manage and describe content, and an appreciation of the issues involved in implementing the standards in their organisation, whether they are a content provider, content customer, or software vendor.
Terms of Use
Copyright © 2023 IPTC, the International Press Telecommunications Council. All Rights Reserved.
The Guidelines are published under the Creative Commons Attribution 4.0 license - see the full license agreement at http://creativecommons.org/licenses/by/4.0/. By obtaining, using and/or copying this document, you (the licensee) agree that you have read, understood, and will comply with the terms and conditions of the license.
This document uses materials that are either in the public domain or are made available by permission of their respective copyright holders. Permission of the copyright holder must be obtained prior to the use of protected material. All materials of this IPTC standard covered by copyright shall be licensable at no charge.
If you do not agree to the Terms of Use you must cease all use of the NewsML-G2 specifications and materials now. If you have any questions about the terms, please contact the Managing Director of the International Press Telecommunication Council. (Contact Details below)
While every care has been taken in creating this document, it is not warranted to be error-free, and is subject to change without notice. Check for the latest version and applicable NewsML-G2 Standards and Documentation by visiting www.newsml-g2.org/doc. The versions of the NewsML-G2 Standards covered by this document are listed in About the NewsML-G2 Standards.
Acknowledgements
IPTC member delegates past and present who have contributed to this documentation project:
BABY, Vincent |
Thomson Reuters* |
BEYNET, Yannick |
Agence France-Presse |
CARD, Tony |
BBC Monitoring* |
COMPTON, Dave |
Refinitiv, an LSEG business |
CRAIG-BENNETT, Honor |
Press Association* |
EVAIN, Jean-Pierre |
European Broadcasting Union* |
EVANS, John |
Transtel Communications Ltd |
GEBHARD, Andreas |
Getty Images* |
GORTAN, Philipp |
APA (Austrian News Agency)* |
GULIJA, Darko |
HINA (Croatia News Agency)* |
HARMAN, Paul |
Press Association (-2014), Bloomberg (2015-) |
HOLLAND, Kelvin |
Point House Media Ltd. |
HUSO, Trond |
NTB (Norwegian News Agency)* |
KELLY, Paul |
XML Team (-2016), Independent (2016-) |
LE MEUR, Laurent |
Agence France-Presse* |
LINDGREN, Johan |
TT Nyhetsbyrån (Swedish News Agency) |
LORENZEN, Jayson |
Business Wire |
MOUGIN, Philippe |
Agence France-Presse |
MYLES, Stuart |
Associated Press* |
QUINN, Brendan |
IPTC |
RATHJE, Kalle |
Deutsche Presse Agentur* |
SCHMIDT-NIA, Robert |
Deutsche Presse Agentur* |
SERGENT, Benoît |
European Broadcasting Union* |
STEIDL, Michael |
IPTC* |
WHESTON, Siobhán |
BBC Monitoring* |
WOLF, Misha |
Thomson Reuters* |
* Delegate is no longer with the member company in 2022.
About the Guidelines
This is the 15th edition of the NewsML-G2 Implementation Guidelines, covering NewsML-G2 v2.31.
Guidelines author: Kelvin Holland, Point House Media Ltd.
Conventions used by this document
Code examples are shown as follows:
<element attribute="attribute_value">Data</element>In NewsML-G2, all XML elements that consist of two (or more) concatenated words are in lowerCamel case. For example:
<catalog>
<catalogRef>Where a word is normally capitalized, it remains so. Thus:
<inlineXML>Attribute names are always all lowercase For example
standardversion="2.31"In these Guidelines, an "Item" with capitalised "I" indicates a NewsML-G2 Item (for example News Item, Planning Item, and so on).
| Admonitions indicate especially important notes or warnings to implementers |
All scheme QCodes used in examples in this document that start with ex- are example schemes used for illustrative purposes. All other schemes relate to IPTC defined vocabularies, known as NewsCodes. These are defined in the official IPTC catalog at https://iptc.org/std/catalog/ . The values of each IPTC scheme can be viewed at http://cv.iptc.org/newscodes/ .
Note on Spelling (English)
The IPTC convention for documents in English is to use UK English spelling, In general, U.S. English is used for property names and values used in IPTC XML Standards (for example, canceled, color, catalog).
A common sense approach dictates that there may be exceptions to this convention.
Terminology: MUST and SHOULD
There are few mandatory features in NewsML-G2. This document uses the terms MUST (NOT), SHOULD (NOT) and MAY as defined in RFC 2119. A MUST instruction in this document refers to mandatory actions; SHOULD refers to recommended actions or best practice to be used unless there is a very good reason not to do so; MAY refers to optional actions.
Note on Time and Date-Time properties
The XML Specification for time-based properties is based on ISO 8601 and permits the omission of time zone/time offset information. However, these values MUST be present in NewsML-G2 timestamps that express a date AND time, such Item Metadata timestamps, because the exchange of news information may cross time zones, and timing information must be unambiguous. The following examples comply:
<versionCreated>2022-11-06T12:12:12+01:00</versionCreated> (1)
<versionCreated>2022-11-06T12:12:12-01:00</versionCreated> (2)
<versionCreated>2022-11-06T12:12:12Z</versionCreated> (3)| 1 | +ve offset |
| 2 | -ve offest |
| 3 | indicates UTC |
The following example does NOT comply:
<versionCreated>2022-11-06T12:12:12</versionCreated> <!-- invalid: no timezone offset -->Administrative content metadata properties such as <contentCreated> and descriptive date-time properties such as <founded> and <dissolved> use a Truncated DateTime data type permitting parts of the data-time to be truncated from the right, for example:
<founded>2022-11-06</founded> <!-- valid TruncatedDateTime -->complies, but this does not:
<founded>2022-11-06T12:00:00</founded> <!-- not a valid TruncatedDateTime: no timezone offset -->IPTC NewsCodes vocabularies in NewsML-G2 examples
The NewsML-G2 examples used in this document and in the accompanying
files illustrate the use of QCodes and Controlled Vocabularies. Although
the examples include IPTC NewsCodes and Scheme Aliases as defined in a
Catalog, some other QCodes are for example only and not controlled by
the IPTC. In each of the Listings in the document, it will be made clear
which are NOT values from the IPTC NewsCodes vocabularies. All example
vocabularies use scheme aliases starting with the characters ex-.
Use of IPTC web resources
The IPTC makes NewsML-G2 resources, including XML Schema files, IPTC Catalog and controlled vocabularies, available on its public web servers on an "as is" basis; 24/7 availability of these resources is not guaranteed.
Implementers who wish to reference IPTC-hosted resources in their NewsML-G2 documents should consider the following:
-
Introducing dependencies on an external resource into the processing of news will break the process if that resource is temporarily unavailable
-
Processing performance will be throttled by the response from the IPTC server if it is overwhelmed with requests.
-
The IPTC may reject requests that appear to be an abuse of its service.
The following IPTC resources referenced in NewsML-G2 documents must be retrieved and cached by the implementer according to the following guidance:
-
The NewsML-G2 XML Schema files and the IPTC Catalog (catalog.IPTC-G2-Standards_nn.xml) can be cached indefinitely as the content of any version will never change.
-
Controlled Vocabularies (IPTC NewsCodes) referenced as Scheme URIs in the IPTC Catalog may be retrieved and cached daily; their contents are subject to change as IPTC Schemes are updated and this happens not more frequently than daily.
The IPTC also recommends that NewsML-G2 consuming systems should gracefully handle the case where an IPTC-hosted resource is temporarily unavailable.
For further information, please see the NewsML-G2 Specification section on processing remote catalogs. See also the NewsML-G2 Basics chapter and the section on Processing Catalogs and CVs within these guidelines.
1. How-To Index
The Implementation Guide is written using worked examples and use cases in order to give implementers an insight into the practical application of NewsML-G2 features. It may be helpful to have the NewsML-G2 Specification at hand; this will contain further detailed information about features discussed. This document can be downloaded by visiting www.newsml-g2.org/spec.
After reading the introductory chapters on NewsML-G2 Basics, handling text, pictures and graphics, video and packages, implementers may wish to go straight to the How To topics for answers to specific questions.
1.3. Manage all kinds of content
1.7. Receiver view
We have created a Quick Start guide to Receiving NewsML-G2. The content is not included in the full Guidelines document, but as a separate document which can be accessed at https://iptc.atlassian.net/wiki/spaces/NEWSMLG2/pages/622034945/Receiving+NewsML-G2-+NewsML-G2+Quick+Start+Guide or in PDF form at https://www.iptc.org/std/NewsML-G2/2.25/documentation/QuickStart-Receiving_NewsML-G2_1.0.1.pdf . It is intended that this standalone document can be used by NewsML-G2 Providers as a template to create customer guides to their own implementations of NewsML-G2.
2. What’s New in NewsML-G2 2.31
Verson 2.31 contains the following change from 2.30. (A full change history of NewsML-G2 is documented in Changes to NewsML-G2 and related Standards).
2.1. The <hasInstrument> property extended to cover more than organisations
Not all financial instruments are attached to organisations: for example exchange-traded funds, currencies, commodities. Previously, the only way to declare a hasInstrument was to create an organisationDetails entity. In this change, <hasInstrument> is added to the EntityDetailsGroup of elements and DEPRECATED from OrganisationDetails. Example:
<concept>
<conceptId qcode="ex-P:18040196349" />
<type qcode="ex-cptType:97"/>
<name>Invesco Capital Appreciation Fund;R6</name>
<hasInstrument symbol="OPTFX.O" type="ex-symType:RIC" symbolsrc="ex-symSrc:RFT"/>
<hasInstrument symbol="US00141G7328" symbolsrc="ex-symSrc:ISO" type="ex-symType:ISIN"/>
</concept>3. Executive Summary
3.1. Why News Exchange standards matter
Information is valuable. Many major financial decisions rely on split-second delivery of news about companies and markets; successful businesses have been built on the ability to target individuals and groups with information which is relevant to their needs. News organisations and information providers have also invested heavily in the people and the technology needed to gather and disseminate news to their customers.
Without standards for news exchange, most of the value of this information would be lost in a confusion of customised feeds and competing formats. The huge volumes of content now being exchanged not only demand a common format, or mark-up, for the content itself but also a common framework for information about the content - the so-called metadata.
3.2. The purpose of NewsML-G2
NewsML-G2 is an open standard for the exchange of all kinds of news information. This can be content, such as text, pictures, audio and video, or information about Events and News Planning. A sister standard, SportsML-G2 conveys rich sports information. The content can be in any format or encoding. It is conveyed with semantically-precise metadata that matches the needs of a professional news workflow and the way that content is consumed both in a B2B and B2C context.
The standard is not concerned with the presentation or mark-up of the content that it conveys; this is the role of standards such as HTML5 and NITF (News Industry Text Format, an IPTC XML standard) that are used to mark up the payload of a NewsML-G2 Item. Microformats such as hNews are complementary; the IPTC has its own semantic mark-up standard rNews, which is compatible with NewsML-G2.
NewsML-G2 models the way that professional news organisation work, but goes beyond this by standardising the handling of the metadata that ultimately enables all types of content to be linked, searched, and understood by end users. NewsML-G2 metadata properties are designed to be mapped to RDF, the language of the Semantic Web, enabling the development of new applications and opportunities for news organisations in evolving digital markets.
3.3. Business Drivers
Many of the business challenges faced by media organisations are related to the development of the World Wide Web, which has not only increased the availability of news content, but is constantly creating new ways to consume it. These challenges are not a once-in-a-lifetime event, but a continuing fact of life.
Businesses need to:
-
Control, and if possible reduce, the cost of developing and maintaining services.
-
Quickly develop new media-rich products and services that can exploit emerging trends and new business models.
-
Give customers access to added-value assets, including archives and metadata repositories.
-
Allow innovation by third-party vendors and partners.
-
Enhance IT investment by enabling the sharing of complex content across separate systems.
3.4. Business Requirements
In response to these business challenges, an information exchange standard needs to:
-
Fit an MMM strategy (Multi-media, Multi-channel, Multi-platform)
-
Handle texts, pictures, graphics, animated, audio or video news
-
Be a lightweight container for news, simple to implement and extend, yet offer powerful features for advanced applications.
-
Be useful at all stages of the lifecycle of news, from initial event planning, through content gathering, syndication, to archiving.
3.5. Design and Benefits
The NewsML-G2 standards are based on common framework – the News Architecture – that is independent of any technical implementation. It may be implemented using object-oriented software, such as Java, or in a database.
The IPTC has implemented the NAR specification in XML Schema to create NewsML-G2 and SportsML-G2, because of the need to facilitate news exchange using W3C standards. XML provides continuity with existing standards, and also has an existing large community of experts.
The standard enables all parties involved in news – providers, receivers and software vendors – to send and receive information quickly, accurately, and appropriately.
-
A common framework maximises the value of investments and provides a path into the future, with maximum inter-operability between different information partners.
-
Machine-readable metadata enables automation of standard processes, cutting costs, speeding delivery, and increasing quality.
-
Innovative solutions are possible because NewsML-G2 complements the work of companies working on search and navigation technologies to realise the vision of the Semantic Web.
4. About the IPTC
IPTC members are technologists and thought leaders from the world’s main news agencies and leading media players. They are expert in the field of news production and dissemination. IPTC Standards today play an essential role in efficient news exchange between the world’s news and media organisations.
The text transmission standards IPTC7901 and its cousin ANPA1312 have been a key enabler of news exchange for news agencies and their newspaper and broadcaster customers, as has the IIM standard for pictures. All media organisations have benefited from these standards; they have been essential to the adoption of digital production technologies. NewsML was first launched in 2000, and the G2 version of NewsML in 2006.
5. How News Happens
5.1. Introduction
NewsML-G2 represents a content and processing model for news that aligns with the way that professional news organisations work. It is therefore important that implementers have at least a high-level understanding of how the news business works, in order to appreciate the rationale behind its features.
An event becomes news when someone decides to create a record of it, and place that record in the public domain. Professional news production is not a haphazard or random process, but a highly organised activity, shaped by a number of influences:
-
The publishing of news originally centred on printing, an industrial process which imposes time and logistical constraints. Print remains an important channel for news dissemination.
-
The selection of what is, and what is not, news to any given audience is vital to the success of any publishing venture, whether in print, broadcasting, web or other media.
-
For legal and ethical reasons, professional news organisations ensure that standards are maintained in the selection and production of news, and that content is reviewed before being authorised for release to the public
These constraints and considerations lead to the news production process being divided into five generic domains:
-
Planning and Assignment
-
Information Gathering
-
Verification
-
Dissemination
-
Archiving
5.2. Assignment
News organisations need to plan their operations, based on prior knowledge of newsworthy events that are expected to occur in any given time frame (daily, weekly, monthly and so on). The resulting schedule of events is called a variety of names, according to custom, such as schedule, budget, day book or diary.
Unexpected events (breaking news) will cause this schedule to change at short notice.
According to the schedule, people and resources will be assigned to “cover” the news events, and those who are dependent on the timely gathering of the news, such as co-workers and customers, will be kept informed of expected coverage, deadlines and any updates,
Large organisations may have several schedules for different categories of news, for example General News, Sport, Finance, Features etc.
Increasingly, text and pictures are being augmented by dynamic content: video, audio, animated graphics, and the availability of this material needs to be signalled in the schedule to interested parties in a way that is amenable to software processing.
These business processes are addressed by Events in NewsML-G2 and Editorial Planning – the Planning Item.
5.3. Information Gathering
Most people recognise the model – beloved of Hollywood – of reporters, photographers, film/video and sound personnel rushing to the scene of a news event and generating content based on material they are able to obtain as the event unfolds.
In fact, news is gathered by an endless variety of means, such as press releases, reports from news agencies and freelance journalists, tip-offs from the public, statements on web sites, blogs etc. Generally, information gathered in this way is incomplete and needs to be augmented by additional material. Sometimes this material is gathered and prepared by contributors, working with the original creator.
This information gathering process ultimately results in journalists submitting event coverage: written copy, photographs, video footage and so on, to the Verification Stage of an editorial workflow.
5.4. Verification
The process of verifying the authenticity of news often starts before the content is generated, as part of the selection and assignment process. However, the detail of the content needs to be checked before the content can be released.
Responsible news organisations take steps to ensure that the facts of any news coverage are correct, and that they are presented in a fair, balanced and impartial way. It is also surprisingly easy to break the law by the inappropriate release of content. Lawyers or legally-trained staff routinely work with editors to ensure that content does not transgress the civil or criminal law, and that it is not gratuitously offensive to individuals or groups.
Clear and consistent writing, spelling and grammar are considered important and an organisation’s rules will often be written down in a Style Guide which journalists are required to use when writing and editing.
Only when content meets all of the required standards will it be authorised for release. Completing these essential tasks under time pressure is one of the major operational challenges faced by news organisations.
5.5. Dissemination
Although seen conceptually as a physical “publication” process, the dissemination of information and news assets in digital form is pre-eminent today.
When news is received electronically, the recipient needs to be able to process the information quickly and reliably. When one considers that each day, a large news organisation may receive, from multiple sources, thousands of images, and hundreds of thousands of words of text, plus video, audio and graphics, the scale of the processing required becomes apparent.
The management of news requires organisations to know whether any given piece of content is useable, and in what context. Media organisations often receive content under embargo. This is information that has been released to professional journalists in advance so that they may complete any work needed to make it ready for dissemination to the public. Only when the embargo time has passed may the content be published. These informal protocols work because it is in the interests of all parties to co-operate. If they break an embargo, journalists know that their job may become more difficult because the provider will withhold information in future.
When content is transmitted electronically, it cannot be physically deleted by the provider. There must therefore be a means for providers to inform their customers that a piece of content must be deleted, (“cancelled” or “killed”) and it is vital that any examples of the content are deleted from all systems, including archives, often for copyright or serious legal reasons.
The right to use a piece of content is an important aspect of news. Picture and video rights can be particularly complex. Although formal rights languages that are machine-readable, such as RightsML, (www.rightsml.org) are available, many organisations continue to indicate rights using a natural-language statement.
This management and administrative information must also be accompanied by descriptive information – metadata – that enables the receiver to direct the content to the appropriate workflow and users, retrieve related content, and if necessary re-purpose it for a variety of media channels.
Descriptive metadata will include some type of classification of the news so that its relevance to a sphere of interest(s) can be determined. Ad-hoc tags or keywords are useful, but their value is increased if they form part of a formal classification scheme, or taxonomy.
The use of taxonomies enables searches to yield consistent predictable results across a wide range of content and further enables accurate processing of content by software.
5.6. Archiving
A comprehensive digital archive of news, people and organisations plays an increasingly active role in the news process because of the features offered by electronic media such as the World Wide Web.
Today it is desirable to publish news which contains links to related news and information assets, allowing the consumer to view any aspect of a news story, including details of the people and organisations involved, and the concepts at issue.
The archiving process completes the news production cycle and accurate, comprehensive metadata is the key to unlocking the value of this information asset. The value of content is in direct proportion to the quality and quantity of its metadata; one can imagine that content with no metadata could be almost valueless.
6. NewsML-G2 Basics
6.1. Introduction
The basic structure of a NewsML-G2 Item document is common to all applications. The available types of Item are:
-
News Item: for all kinds of news content.
-
Package Item: for structured collections of news content.
-
Concept Item: for expressing knowledge about entities, abstract concepts, and events.
-
Knowledge Item: for collections of concepts, often grouped for a specific purpose such as Controlled Vocabularies.
-
Planning Item: for exchanging information about news coverage and fulfilment.
-
Catalog Item: for managing references to Controlled Vocabularies.
6.2. Item structure
The building blocks of a NewsML-G2 Item are shown in the diagram below:
All have a root element that is specific to the type of Item that contains identification, version and some basic information to initiate the NewsML-G2 processor.
The Catalog information is required to resolve QCodes, a fundamental feature of NewsML-G2 that enables partners to guarantee that codes used within an Item are globally unique.
The Rights Information block allow publishers to assert fine-grained information about copyright and usage terms as human-readable statements, or by inclusion of a machine-readable rights expression language such as RightsML.
The Item Metadata wrapper contains metadata about the Item as a whole, and this is followed by metadata about whole of the content <contentMeta>, and optionally by the <partMeta> wrapper, which enables publishers to express metadata about specific parts of the content.
Optional "helper" structures are available for specialised processing needs.
Each type of NewsML-G2 Item has a specific wrapper element for content, shown in the diagram below that also shows the basic top level elements common to all NewsML-G2 Items. The colours of the wrapper elements in the diagram are repeated in the code example in order to highlight the relevant sections of the News Item:
This example uses a News Item with text content to illustrate the basic principles in action. The following chapters walk through other basic implementations specific to Text, Pictures, Video and Packages.
<?xml version="1.0" encoding="UTF-8"?>
<newsItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:acmenews.com:20161018:US-FINANCE-FED"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-GB">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://www.example.com/newsml-g2/catalog.enews_2.xml" />
<rightsInfo>
<copyrightHolder uri="http://www.example.com/about.html#copyright" >
<name>Example Enews LLP</name>
</copyrightHolder>
<copyrightNotice>
Copyright 2021-22 Example Enews LLP, all rights reserved
</copyrightNotice>
<usageTerms>
Not for use outside the United States
</usageTerms>
</rightsInfo>
<itemMeta>
<itemClass qcode="ninat:text" />
<provider qcode="nprov:REUTERS" />
<versionCreated>2022-10-19T16:25:32-05:00</versionCreated>
<firstCreated>2016-10-18T13:12:21-05:00</firstCreated>
<embargoed>2022-10-21T12:00:00Z</embargoed>
<pubStatus qcode="stat:usable" />
<service qcode="ex-svc:uknews">
<name>UK News Service</name>
</service>
<edNote>
Note to editors: STRICTLY EMBARGOED. Not for public release until 12noon
on Friday, October 21, 2022.
</edNote>
<signal qcode="sig:update" />
<link rel="irel:seeAlso"
href="http://www.example.com/video/20081222-PNN-1517-407624/index.html"/>
</itemMeta>
<contentMeta>
<contentCreated>2016-10-18T11:12:00-05:00</contentCreated>
<contentModified>2022-10-19T16:22:45-05:00</contentModified>
<located type="loctyp:City" qcode="ex-geo:345678">
<name>Berlin</name>
<broader type="loctyp:Sublocation" qcode="ex-prov:2365">
<name>Berlin</name>
</broader>
<broader type="loctyp:Country" qcode="iso3166-1a2:DE">
<name>Germany</name>
</broader>
</located>
<creator uri="http://www.example.com/staff/mjameson" >
<name>Meredith Jameson</name>
</creator>
<infoSource uri="http://www.example.com" />
<subject type="cpnat:abstract" qcode="medtop:04000000">
<name xml:lang="en-GB">economy, business and finance</name>
</subject>
<subject type="cpnat:abstract" qcode="medtop:20000523">
<name xml:lang="en-GB">labour market</name>
<name xml:lang="de">Arbeitsmarkt</name>
<broader qcode="medtop:04000000" />
</subject>
<genre qcode="genre:Interview">
<name xml:lang="en-GB">Interview</name>
</genre>
<slugline>US-Finance-Fed</slugline>
<headline> Fed to halt QE to avert "bubble"</headline>
</contentMeta>
<contentSet>
<inlineXML contenttype="application/nitf+xml"> <!-- A VALID MIME TYPE -->
<!-- Inline XML must contain well-formed XML such as NITF or XHTML -->
</inlineXML>
</contentSet>
</newsItem>6.3. Root element <newsItem>
Each NewsML-G2 Item Type uses a specific root element name as shown in the diagram above. In the example News Item the root element is <newsItem> (note camel case spelling).
6.3.1. Root element attributes
Item Identifier
All NewsML-G2 Items must have a @guid, an identifier that should be globally unique for all time and independent of location. The IPTC has registered a URN namespace for the purpose of creating GUIDs for NewsML-G2 Items using a specification based on RFC3085. The syntax for a @guid using this scheme is:
guid="urn:newsml:[ProviderId]:[DateId]:[NewsItemId]"Use an internet domain name owned by your organisation as a ProviderId, for example:
<newsItem guid= "urn:newsml:acmenews.com:20161018:US-FINANCE-FED"| Do not try to "reverse engineer" the DateId part of a GUID to create a time-stamp. This may have unintended consequences and result in errors. Use the appropriate NewsML-G2 timestamp property instead. |
Version
A simple indicator of the version of the Item:
version="15"Version numbers need not be consecutive, but must START at 1, and a new version must be a higher number than the previous version. If version is missing, the value is assumed to be 1. See Implied Values of NewsML-G2 Properties
Standard Version
A string denoting the major and minor version of the Standard being used:
standardversion="2.31"Conformance
The Conformance of all versions of NewsML-G2 since 2.24 is "power" and MUST be declared:
conformance="power"Language
Setting the default language of XML elements with text content in NewsML-G2 is UK English:
xml:lang="en-GB"IPTC namespace
Sets the default namespace for elements:
xmlns="http://iptc.org/std/nar/2006-10-01/"Putting this together, the required root element attributes are:
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:acmenews.com:20161018:US-FINANCE-FED"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-GB">6.3.2. Validating code
When developing a NewsML-G2 processing application, implementers will need to validate the generated NewsML-G2 code against the appropriate schema. To validate code against the latest version of NewsML-G2 covered by these Guidelines (2.31) add the following code to the <newsItem> element:
<newsItem
//...
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
http://www.iptc.org/std/NewsML-G2/2.27/specification/NewsML-G2_2.31-spec-All-Power.xsd"| The IPTC does NOT permit validation of production documents against the XML Schema files hosted by the IPTC. |
6.3.3. Catalog wrapper <catalogRef>
Codes, short mnemonics used to express the value of properties such as Category, are a long-established feature of news exchange. QCodes are the NewsML-G2 mechanism that enables partners in news exchange to guarantee that codes are globally unique. Without going into details of the mechanism here, the News Item <catalog> enables a NewsML-G2 processor to resolve QCodes, and guarantee that uniqueness, by mapping the code to a globally-unique URI. It is recommended that this URI locates a web resource.
One of the few mandatory NewsML-G2 elements, <itemClass>, uses QCodes issued by the IPTC to identify the business intention of the Item. For a News Item, the scheme is News Item Nature, with a recommended Scheme Alias of "ninat". Values from the scheme include (not limited to) "ninat:text" and "ninat:picture". The catalog reference is:
<catalog>
<scheme alias="ninat" uri="http://cv.iptc.org/newscodes/ninature/" />
</catalog>Other types of NewsML-G2 Item use specific schemes for the <itemClass> property.
All Scheme Aliases used in the example listing indicate IPTC NewsCodes
vocabularies, except for the following
alias values (note that they are prefixed "ex-" to aid readability):
ex-cptype, ex-geo, ex-prov and ex-svc.
As the CVs used by a provider are usually quite consistent across the NewsML-G2 Items they publish, the IPTC recommends that the <catalog> references are aggregated into a stand-alone file which is made available as a web resource referenced by <catalogRef>. This is how the IPTC publishes its Catalogs:
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml"
/>The use of stand-alone web resources is preferable because all of the QCode mappings are shared across many NewsML-G2 Items; a local <catalog> can only be used by the single Item.
It’s likely that provider-specific catalogs will be needed to resolve QCodes used in the Item, for example:
<catalogRef
href="http://www.example.com/newsml-g2/catalog.enews_2.xml" />Adding the Catalog information to the example results in the following:
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:acmenews.com:20161018:US-FINANCE-FED"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-GB">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml"
/>
<catalogRef
href="http://www.example.com/newsml-g2/catalog.enews_2.xml"
/>See also Use of URIs in place of QCodes
6.3.4. Rights information wrapper <rightsInfo>
The optional <rightsInfo> wrapper holds copyright information and usage terms, such as the following example:
<rightsInfo>
<copyrightHolder uri="http://www.example.com/about.html#copyright">
<name>Example Enews LLP</name>
</copyrightHolder>
<copyrightNotice>
Copyright 2022-23 Example Enews LLP, all rights reserved
</copyrightNotice>
<usageTerms>Not for use outside the United States</usageTerms>
</rightsInfo>6.4. Item Metadata <itemMeta>
6.4.1. Mandatory Properties
The mandatory <itemMeta> section has four mandatory elements, present in the following order:
Item Class
As previously mentioned, the <itemClass> property describes the type of content conveyed by the Item. It is mandatory to use one of the IPTC News Item Nature NewsCodes (recommended Scheme Alias: "ninat") for the Item Class of News Items and Package Items, expressed as a QCode:
<itemClass qcode="ninat:text" />Other possible values from this scheme include (not limited to) "ninat:picture", "ninat:video" and "ninat:audio".
Provider
Can be represented by a QCode, or a URI. If the value of this property is NOT taken from a controlled vocabulary, the @qcode or @uri will be omitted and the child <name> element used to give a human-readable value for the property. The IPTC recommends using a QCode with the Provider NewsCodes, a controlled vocabulary of providers registered with the IPTC with recommended Scheme Alias of "nprov":
<provider qcode="nprov:REUTERS" />Version Created
This contains the date, time and time zone (or UTC) that this version
of the NewsML-G2 Item was created. The value must be expressed as XML
Schema datetime:
YYYY-MM-DDThh:mm:ss±hh:mm
<versionCreated>2022-10-21T16:25:32-05:00</versionCreated>The -05:00 denotes U.S. Eastern Standard Time offset from UTC
Publication Status
Every NewsML-G2 Item must have a publication status. The value defaults to "usable", which permits the <pubStatus> property to be omitted, however it is recommended that a value is explicitly included:
<pubStatus qcode="stat:usable" />Publication status is highly likely to be used by most news agencies, because the ability to explicitly signal the status of news is essential. The use of the IPTC Publishing Status NewsCodes is mandatory. Its recommended alias is "stat". Other values permitted by the scheme are:
-
stat:canceled (note U.S. spelling) means that the content of the newsItem must not be used, ever.
-
stat:withheld means the content must not be used until further notice.
When an Item is cancelled, it must never be used, but an Item that has been withheld may subsequently have its status updated to "usable".
6.4.2. Use of URIs in place of QCodes
The original NewsML-G2 developers wanted to use URIs as the preferred way to identify concepts, as this would enable the resulting concept identifiers to be globally unique and optionally to be a reference to a web resource. The constraints on network bandwidth (compared to today) led the developers to propose QCodes to represent URIs, because:
-
they are lightweight and economise file sizes,
-
although they are designed to reference web resources, the delivery of data in response to requesting QCodes that are resolved to full URIs is optional; the codes may be used "as is" without de-referencing to the full URI.
Later, some providers asked for flexibility to use full URIs in property values, so from NewsML-G2 v2.11 this feature was added enabling @uri to be used in place of, or in parallel with, @qcode. (If a @qcode and @uri are both present, they MUST refer to the same semantic concept, and the resolved @qcode SHOULD be the same as the @uri). The <pubStatus> assertion:
<pubStatus qcode="stat:usable" />could be expressed using a URI as:
<pubStatus uri="http://cv.iptc.org/newscodes/pubstatusg2/usable" />Further, in NewsML-G2 v2.18 onwards, other properties with QCode Type values had "URI siblings" added, for example properties with @role may now have a value expressed as @roleuri. In NewsML-G2 v2.20, properties with a mandatory @qcode were changed so that @uri may be used instead.
| The elements <catalog> and <catalogRef> are now OPTIONAL so that implementers who wish to use URI identifiers exclusively do not have to reference schemes that are unused. |
6.4.3. Optional Properties
The following optional properties are frequently used by NewsML-G2 providers.
First Created
The <firstCreated> element indicates when the first version of the Item (not the content) was created.
<firstCreated>2016-10-18T13:12:21-05:00</firstCreated>Embargoed
Business-to-business news organisations often use an embargo to release information in advance, on the strict understanding that it may not be released into the public domain until after the embargo time has expired, or until some other form of permission has been given.
Embargoed is NOT the same as the Publishing Status; embargoed content should have a publishing status of "usable".
<embargoed>2022-10-23T12:00:00Z</embargoed>It is not required to give any further information about the embargo conditions, but some providers may provide a natural language <edNote>, see below.
Service
The <service> element allows the provider to declare which of its services delivered this package, using a Controlled Vocabulary:
<service qcode="ex-svc:uknews">
<name>UK News Service</name>
</service>Editorial Note
The <edNote> element contains a note that is intended to be read by internal staff at the receiving organisation, but not published to the end-user; in this example it conveys some optional information about the release condition imposed by the <embargoed> element:
<edNote>
Note to editors: STRICTLY EMBARGOED. Not for public release until 12noon
on Sunday, October 23, 2022.
</edNote>Signal
Additional processing instructions can be given using <signal> and its @qcode. This example uses the IPTC Signal NewsCodes (recommended Scheme Alias "sig") that advises the end-user that this Item updates a previous versions of the Item:
<signal qcode="sig:update" />The other value in the Signal scheme is "correction". There is further NewsML-G2 functionality for expressing fine-grained information about the reason and impact of updates and also for applying signals to different parts of an Item’s content.
Link
The <link> element has two basic purposes:
-
To assert relationships to other Items, such as a previous version of an Item
-
To create a navigable link from an Item to some supporting or additional resource.
This example provides a "see also" link to a resource on the Web that end-users can view to get further information about the event. @rel is used to denote the reason that the link is provided. In this example, the QCode uses the recommended IPTC Item Relation NewsCodes with a recommended Scheme Alias of "irel" and the code value is "seeAlso":
<link rel="irel:seeAlso" href="http://www.example.com/video/20081222-PNN-1517-407624/index.html"/>Completed Item Metadata
<itemMeta>
<itemClass qcode="ninat:text" />
<provider qcode="nprov:REUTERS" />
<versionCreated>2022-10-21T16:25:32-05:00</versionCreated>
<firstCreated>2016-10-18T13:12:21-05:00</firstCreated>
<embargoed>2022-10-23T12:00:00Z</embargoed>
<pubStatus qcode="stat:usable" />
<service qcode="ex-svc:uknews">
<name>UK News Service</name>
</service>
<edNote>
Note to editors: STRICTLY EMBARGOED. Not for public release until 12noon
on Sunday, October 23, 2022.
</edNote>
<signal qcode="sig:update" />
<link rel="irel:seeAlso" href="http://www.example.com/video/20081222-PNN-1517-407624/index.html"/>
</itemMeta>6.5. Content Metadata <contentMeta>
Conceptually, there are two kinds of content metadata: Administrative and Descriptive.
6.5.1. Administrative Metadata
This is information about the content that cannot necessarily be deduced by examining it, for example: when it was created and/or modified. Administrative properties that are widely used by implementers of NewsML-G2 for editorial content are:
-
Timestamps (Created, Modified)
-
Story location (Located)
-
Creator
-
Information Source
Timestamps
The <contentCreated> timestamp corresponds to a "Created on" field of the story. It is expressed in NewsML-G2 as Truncated DateTime data type, meaning that the date-time elements may optionally be stripped, starting from the right. If required, the <contentModified> property may also be used to contain the "Last Edit" timestamp. This must be later than the Created timestamp.
<contentCreated>2016-10-21T15:21:06-05:00</contentCreated>
<contentModified>2022-10-21T16:22:45-05:00</contentModified>Located
The place that the content was created uses the <located> element. Note that this is not necessarily the place of the event or subject. For example, for a UK story written in the London office, <located> would be "London"; a picture of Mount Fuji taken from downtown Tokyo would have a <located> value of "Tokyo".
The semantics of <located> are similar to the natural-language location carried in the dateline that often prefaces news (such as "BERLIN, October 24") but can be conveyed more precisely, and in terms that may be more readily processed by software, using a @qcode or @uri:
<located type="loctyp:City" qcode="ex-geo:345678">
<name>Berlin</name>
</located>The optional @type uses a controlled vocabulary to indicate the nature of the location being expressed; in the example this indicates that <located> refers to a city.
Broader, Narrower
Both Located and Subject (below) contain child elements that express a specific relationship between entities or concepts. For example, the content originated in the city of Berlin and the <located> element shows that the city of Berlin has a "broader" relationship – that is a child-to-parent relationship – to Berlin the state, and to Germany the country:
<located type="loctyp:City" qcode="ex-geo:345678">
<name>Berlin</name>
<broader type="ex-cptype:statprov" qcode="ex-prov:2365">
<name>Berlin</name>
</broader>
<broader type="ex-cptype:country" qcode="iso3166-1a2:DE">
<name>Germany</name>
</broader>
</located>Creator
The writer, photographer or other party (person or organisation) who created the content is expressed using the <creator> element:
<creator uri="http://www.example.com/staff/mjameson">
<name>Meredith Jameson</name>
</creator>Information Source
The <infoSource> element, together with its optional @role, enables finely-grained identification of the various parties who provided information used to create and develop an item of news. If absent, the default value of @role is the originator of the information used to create or enhance the content.
<infoSource uri="http://www.example.com/pressreleases/201610/newproducts.html"/>6.5.2. Descriptive Metadata
These properties set the context of news content in relation to other news by describing and classifying it. Information that has historically been carried within the content itself, such as the headline and by-line (for text) or embedded metadata (for pictures) may also be specified as metadata. The practical benefit is that the end user no longer needs to scan or retrieve the actual content in order to process it. None of the Descriptive Metadata elements are mandatory, but the following feature frequently in NewsML-G2 implementations.
Subject
The subject matter of content uses the <subject> element. When the value of the Subject is taken from a Controlled Vocabulary, this is identified using either a @qcode or @uri:
<subject type="cpnat:abstract" qcode="medtop:20000523" />
<subject uri="http://cv.iptc.org/newscodes/mediatopic/20000523" />For concepts not taken from a CV, the identifier is omitted and the name of the concept is given in the child <name> element, for example:
<subject>
<name>Labour Market</name>
</subject>The optional @type uses the IPTC "nature of the concept" NewsCodes (recommended scheme alias "cpnat") to indicate the type of concept being expressed, for example, an abstract concept, that is a concept that does not represent a real-world entity, but something like an idea, or news category.
<subject type="cpnat:abstract" qcode="medtop:04000000">
<name xml:lang="en-GB">economy, business and finance</name>
</subject>The above example uses a concept from the IPTC Media Topic NewsCodes. Also note the use of the W3C XML attribute xml:lang that expresses the language used for the element’s value. It is also possible to add relationships to related concepts, as shown above in <located>. For example:
<subject type="cpnat:abstract" qcode="medtop:04000000">
<name xml:lang="en-GB">economy, business and finance</name>
</subject>
<subject type="cpnat:abstract" qcode="medtop:20000523">
<name xml:lang="en-GB">labour market</name>
<name xml:lang="de">Arbeitsmarkt</name>
<broader qcode="medtop:04000000" /> relationship property
</subject>The IPTC highly recommends that providers use the Media Topic NewsCodes unless there is an over-riding requirement to use proprietary codes. This promotes inter-operability and standardisation in news exchange. It is also recommended that if a <name> is used in conjunction with a QCode, then the value of the <name> agrees with the value in the Scheme for the language specified in xml:lang. IPTC NewsCodes are provided in UK English (en-GB) and translations in French and German have been provided by IPTC members.
The "medtop" code prefix is the recommended Scheme Alias for the Codes, which is resolved via the IPTC Catalog (see Catalog wrapper <catalogRef>, above) to the Scheme URI http://cv.iptc.org/newscodes/mediatopic/ This is guaranteed to be globally unique because it is part of the Internet Domain controlled by the IPTC. Appending the code "04000000" to the Scheme URI forms the Concept URI http://cv.iptc.org/newscodes/mediatopic/04000000 that cannot be confused with a concept with the same code 04000000 from another source.
When using @type to indicate the nature of the concept, the possible values from the IPTC Concept Nature NewsCodes are:
-
Abstract: a concept that does not represent a real-world entity
-
Event
-
geoArea: a geo-political area
-
Object: A real-world object, such as a painting; an aircraft
-
Organisation
-
Person
-
Point of Interest
Genre
The <genre> element indicates the style of the content, in this example "interview" as a property that is distinct from <subject> that is used to indicate the subject matter of content. In the example, an IPTC Genre NewsCodes value of "Interview" is used:
<genre qcode="genre:interview">
<name xml:lang="en-GB">Interview</name>
</genre>Slugline
Some news services implemented in NewsML-G2 retain the <slugline> property as a human-readable index for legacy reasons; therefore receivers may sometimes see this property. However, it has never been a completely reliable identifier, and it is recommended that more purposeful identifiers that are also machine-readable are implemented in its place.
<slugline>US-Finance-Fed</slugline>Headline
Even if the Headline is carried inline in text content, it is useful also to place it explicitly in metadata so that it can more easily be identified and extracted by the end-user:
<headline> Fed to halt QE to avert "bubble"</headline>Completed Content Metadata
<contentMeta>
<contentCreated>2016-10-21T15:21:06-05:00</contentCreated>
<contentModified>2022-10-21T16:22:45-05:00</contentModified>
<located type="loctyp:City" qcode="ex-geo:345678">
<name>Berlin</name>
<broader type="loctyp:Sublocation" qcode="ex-prov:2365">
<name>Berlin</name>
</broader>
<broader type="loctyp:Country" qcode="iso3166-1a2:DE">
<name>Germany</name>
</broader>
</located>
<creator uri="http://www.example.com/staff/mjameson">
<name>Meredith Jameson</name>
</creator>
<infoSource uri="http://www.example.com" />
<subject type="cpnat:abstract" qcode="medtop:04000000">
<name xml:lang="en-GB">economy, business and finance</name>
</subject>
<subject type="cpnat:abstract" qcode="medtop:20000523">
<name xml:lang="en-GB">labour market</name>
<name xml:lang="de">Arbeitsmarkt</name>
<broader qcode="medtop:04000000" />
</subject>
<genre qcode="genre:interview">
<name xml:lang="en-GB">Interview</name>
</genre>
<slugline>US-Finance-Fed</slugline>
<headline> Fed to halt QE to avert "bubble"</headline>
</contentMeta>6.6. Content <contentSet>
The content of a NewsML-G2 document varies according to its Item type: the example below shows a News Item with a <contentSet> wrapper containing a trivial text payload. Following this code example are skeletal examples showing the other options for conveying content in NewsML-G2 News Items and Package Items:
6.6.1. News Content options for News Items and Package Items
The News Item <contentSet> contains a single logical piece of content, but allows alternative renditions of the SAME content to be carried in a single NewsML-G2 Item:
<contentSet>
<inlineXML contenttype="application/nitf+xml"><!-- A VALID MEDIA TYPE -->
<!-- Inline XML must contain well-formed XML such as NITF or XHTML -->
</inlineXML>
</contentSet>or
<contentSet>
<inlineData>
<!-- Inline Data contains plain text -->
</inlineData>
</contentSet>or
<contentSet>
<!-- Remote Content contains a reference to a binary asset such as -->
<!—-a PDF or image file -->
<remoteContent rendition="rnd:one" />
<remoteContent rendition="rnd:two" />
<remoteContent rendition="rnd:three" />
</contentSet>Package Item content is wrapped by the <groupSet> element, which can contain one or more <group> children. Each Group contains references to Items that make up the News Package, using the <itemRef> element. A Group can also reference other Groups via the <groupRef> element.
<groupSet ... >
<group ...>
<itemRef ... >
<!-- Properties extracted from the packaged Item -->
</itemRef>
<groupRef />
</group>
<group ... >
//...
</group>
</groupSet>6.7. Summary and Next Steps
This chapter has covered the basic structure that is common to all NewsML-G2 Items, and also outlined properties that are commonly used for news content. The following chapters show how to build upon this foundation:
The Text chapter takes an example news story and shows how the information on an editor’s screen would be implemented in NewsML-G2.
Pictures and Graphics takes an example image and its embedded metadata and converts this to a NewsML-G2 properties with several image renditions carried in a single NewsML-G2 Item. The guide also shows how to express the various technical characteristics of images using NewsML-G2 properties.
The Video chapter is split into two sections: the first covers a simple case of a standalone video file with various technical renditions expressed in NewsML-G2; the second uses a more comprehensive structure that separates the metadata for multiple segments of a video, using the <partMeta> wrapper.
The Packages chapter shows how NewsML-G2 Items and other kinds of content can be assembled into Packages of managed objects with an explicit structure.
6.8. Implied Values of NewsML-G2 Properties
There are some default values set by the specification which allow an element or attribute to be omitted and the default assumed. The list below shows NewsML-G2 elements and attributes which may be absent from an Item but for which an implied value or status exists.
6.8.1. All NewsML-G2 items
-
@version of the root element = "1"
-
<embargoed> = no embargo
-
<pubStatus> = "usable"
-
<catalog> and <catalogRef> = one is required; many of either, or a mix of both may be used
-
@scope of <hash> = "content". Hash value is a message digest included in the Item for security purposes. A hash scope of "content" indicates that the hash value was derived by hashing some/all of the content only.
-
@why (attribute of many elements) = "direct". The attribute value indicates that the value is directly related to the content.
-
@how (attribute of many elements) = "person". The attribute indicates how the value was extracted from the content: by a person. (See Why and How metadata has been added: @why and @how for essential guidance on the use of @why and @how.)
-
@custom (attribute of many elements) = "false". The attribute indicates that the property was added specifically for a customer or group of customers
-
@dir (many elements) = "ltr". The directionality of the script of the language of the property is left to right.
6.8.2. News Items only
-
@timeunit (when @duration is used) = "seconds"
-
@dimensionunit (when @width/@height is used) = (for example) pixels for a still picture. See the Pictures and Graphics chapter for details.
7. Text
7.1. Introduction
One of the most fundamental needs of a news organisation is to handle text. This chapter covers the basics of a simple NewsML-G2 News Item containing text content.
| We recommend reading the chapter on NewsML-G2 Basics before this guide to implementing Text. |
7.2. Example
Below is an example story and supporting information as might be displayed on the journalist’s editing screen at a fictional news provider, Acme News and Media (ANM):
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This screen contains nearly all of the information needed to create the NewsML-G2 document below:
(All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-geoloc and ex-is.)
<?xml version="1.0" encoding="UTF-8" ?>
<newsItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:acmenews.com:20161121:US-FINANCE-FED"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-US">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef
href="http://catalog.acmenews.com/news/ANM_G2_CODES_2.xml" />
<rightsInfo>
<copyrightHolder uri="http://www.acmenews.com/about.html#copyright">
<name>Acme News and Media LLC</name>
</copyrightHolder>
<copyrightNotice>Copyright 2022-23 Acme News and Media LLC</copyrightNotice>
</rightsInfo>
<itemMeta>
<itemClass qcode="ninat:text" />
<provider uri="http://www.acmenews.com/about/" />
<versionCreated>2022-11-21T16:25:32-05:00</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<contentCreated>2016-11-21T15:21:06-05:00</contentCreated>
<contentModified>2022-11-21T16:22:45-05:00</contentModified>
<located qcode="ex-geoloc:NYC">
<name>New York, NY</name>
</located>
<creator uri="http://www.acmenews.com/staff/mjameson">
<name>Meredith Jameson</name>
</creator>
<infoSource qcode="ex-is:AP">
<name>Associated Press</name>
</infoSource>
<language tag="en-US" />
<subject qcode="medtop:04000000">
<name>economy, business and finance</name>
</subject>
<subject qcode="medtop:20000350">
<name>central bank</name>
</subject>
<subject qcode="medtop:20000379">
<name>money and monetary policy</name>
</subject>
<slugline>US-Finance-Fed</slugline>
<headline> Fed to halt QE to avert "bubble"</headline>
</contentMeta>
<contentSet>
<inlineXML contenttype="application/nitf+xml">
<nitf xmlns="http://iptc.org/std/NITF/2006-10-18/">
<body>
<body.head>
<hedline>
<hl1>Fed to halt QE to avert "bubble"</hl1>
</hedline>
<byline>By Meredith Jameson, <byttl>Staff Reporter</byttl></byline>
</body.head>
<body.content>
<p>(New York, NY - October 21) Et, sent luptat luptat, commy
Nim zzriureet vendreetue modo
dolenis ex euisis nosto et lan ullandit lum doloreet vulla
feugiam coreet, cons eleniam il ute facin veril et aliquis ad
minis et lor sum del iriure dit la feugiamcommy nostrud min ulla
autpat velisl duisismodip ero dipit nit utpatum sandrer cipisim
nit lortis augiat nulla faccum at am, quam velenis nulput la
auguerostrud magna commolore eliquatie exerate facilis
modiamconsed dion henisse quipit at. Ut la feu facilla feu
faccumsan ecte modoloreet ad ex el utat.
</p>
<p>Ugiating ea feugait utat, venim velent nim quis nulluptat num
Volorem inci enim dolobor eetuer sendre ercin utpatio dolorpercing
Et accum nullan voluptat wisis alit dolessim zzrilla commy nonulpu
tpatinis exer sequatueros adit verit am nonse exerili quismodion
esto cons dolutpat, si.
</p>
</body.content>
</body>
</nitf>
</inlineXML>
</contentSet>
</newsItem>7.3. Document structure
The building blocks of the text document shown above are the <newsItem> root element, with additional wrapping elements for metadata about the News Item (itemMeta), metadata about the content (contentMeta) and the content itself (contentSet). The top level (root) element <newsItem> attributes are:
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:acmenews.com:20161121:US-FINANCE-FED"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-US">This is followed by references to the Catalogs used to resolve QCodes in the Item, and Rights information:
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml"
/>
<catalogRef
href="http://catalog.acmenews.com/news/ANM_G2_CODES_2.xml" />
<rightsInfo>
<copyrightHolder uri="http://www.acmenews.com/about.html#copyright">
<name>Acme News and Media LLC</name>
</copyrightHolder>
<copyrightNotice>Copyright 2021-22 Acme News and Media LLC</copyrightNotice>
</rightsInfo>7.3.1. Item Metadata <itemMeta>
Note the three mandatory child elements of the mandatory<itemMeta>:
-
Item Class
-
Provider
-
Version Created
A publication status is also mandatory, but the <pubStatus> element may be omitted, in which case the publication status is "usable". However, it is recommended that the publication status is explicitly given, as in this example. As Acme News & Media is fictional, the Provider property does not use one of the IPTC Provider NewsCodes, and is expressed by a URI:
<itemMeta>
<itemClass qcode="ninat:text" />
<provider uri="http://www.acmenews.com/about.html" />
<versionCreated>2022-11-21T16:25:32-05:00</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>7.3.2. Content Metadata <contentMeta>
Administrative Metadata
The administrative properties of the example text story are:
<contentCreated>2016-11-21T15:21:06-05:00</contentCreated>
<contentModified>2022-11-21T16:22:45-05:00</contentModified>The place that the content was created uses the <located> element:
<located qcode="ex-geoloc:NYC">
<name>New York, NY</name>
</located>(Note that this is where the story was written, not the place where the subject of the story took place. That would be expressed using <subject>, part of Descriptive Metadata.)
The author of the article is expressed using the <creator> element:
<creator uri="http://www.acmenews.com/staff/mjameson">
<name>Meredith Jameson</name>
</creator>The Information Source for the article is also given. When used without a @role, <infoSource> is used to denote the person or party that provided the original information on which the content is based. This is the relationship to be expressed here:
<infoSource qcode="ex-is:AP">
<name>Associated Press</name>
</infoSource>The default language for the content is given as U.S. English:
<language tag="en-US" />Descriptive Metadata
In the example, the Subject properties use QCodes from the Controlled Vocabulary of Media Topics NewsCodes that are owned and maintained by the IPTC and expressed as QCodes. Thus:
<subject qcode="medtop:04000000">
<name>economy, business and finance</name>
</subject>
<subject qcode="medtop:20000350">
<name>central bank</name>
</subject>
<subject qcode="medtop:20000379">
<name>money and monetary policy</name>
</subject>The <slugline> property contains the value of the "Slugline" field of the story:
<slugline>US-Finance-Fed</slugline>In a similar fashion, the <headline> property will contain the value of the "Headline" field:
<headline>Fed to halt QE to avert "bubble"</headline>Complete Content Metadata
<contentMeta>
<contentCreated>2016-11-21T15:21:06-05:00</contentCreated>
<contentModified>2022-11-21T16:22:45-05:00</contentModified>
<located qcode="ex-geoloc:NYC">
<name>New York, NY</name>
</located>
<creator uri="http://www.acmenews.com/staff/mjameson">
<name>Meredith Jameson</name>
</creator>
<infoSource qcode="ex-is:AP">
<name>Associated Press</name>
</infoSource>
<language tag="en-US" />
<subject qcode="medtop:04000000">
<name>economy, business and finance</name>
</subject>
<subject qcode="medtop:20000350">
<name>central bank</name>
</subject>
<subject qcode="medtop:20000379">
<name>money and monetary policy</name>
</subject>
<slugline>US-Finance-Fed</slugline>
<headline>Fed to halt QE to avert "bubble"</headline>
</contentMeta>7.4. Text content choices
7.4.1. Inline XML
The content of the NewsML-G2 document is enclosed by the <contentSet> wrapper. In the example, IPTC’s news text mark-up language NITF (News Industry Text Format) is used to format the text content. As an XML standard, it is contained in an <inlineXML> child element of <contentSet>, and uses @contenttype to denote the XML-based standard, using the IANA Media Type.
XHTML is also a popular text mark-up choices among NewsML-G2 providers; the contents of <inlineXML> may be any XML language that can express generic or specialised news information, including SportsML-G2. Other languages such as XBRL (Extended Business Reporting Language) may also be used. The content inside <inlineXML> must be valid XML, in other words, it could stand alone as a valid XML document in its own namespace.
<contentSet>
<inlineXML contenttype="application/nitf+xml">
<nitf xmlns="http://iptc.org/std/NITF/2006-10-18/">
<!--STORY CONTENT HERE -->
</nitf>
</inlineXML>
</contentSet>7.4.2. Inline data
The <inlineData> child element of <contentSet> holds data encoded as a string in the same encoding as the full XML document, for example utf-8. Data not covered by this encoding, such as binary data, must use a special encoding resulting in a text string. In the case of binary data (images, graphics, video, audio etc) we recommend that the encoding attribute is used to express the encoding used, and the media type of the data expressed by the contenttype attribute, for example “image/jpeg”, “video/quicktime”. We suggest that base64 encoding is used as it can be easily decoded on the receiver side. The encoding is expressed using a QCode or IRI, and it is recommended to use the IPTC Encoding NewsCodes (Scheme URI http://cv.iptc.org/newscodes/encoding/ and recommended Scheme Alias "encd")
Any characters that are not within the definition of xs:string, such as syntax characters used in HTML, must be escaped or placed within CDATA. and we recommend that the contenttype attribute is used (for example “text/plain”, “text/markdown”, “text/html”), but NOT the encoding attribute. See below for examples.
When encoding binary assets, we recommend that only relatively small objects are conveyed using <inlineData>; normally the <remoteContent> wrapper should be used to convey binary assets.
| Name | Definition |
|---|---|
Simplest example |
|
Markdown |
|
Embedded GIF |
|
HTML5 embedded widget |
|
8. Pictures and Graphics
8.1. Introduction
Image content, including pictures and graphics, can be conveyed in a standard NewsML-G2 document. Picture providers and consumers need a rich vocabulary for descriptive and technical metadata, and for administrative metadata such as rights and usage terms. There is also a long-established use of embedded metadata, such as the IPTC/IIM Fields in JPEG and TIFF files. This chapter addresses some aspects of embedded metadata, but for a full description of the mapping embedded metadata and IIM fields to NewsML-G2, please see the chapter Mapping Embedded Photo Metadata to NewsML-G2.
The example in this chapter is a simple but complete document that shows how to implement in NewsML-G2 the frequently-used needs of a professional picture workflow:
-
Right and usage instructions
-
Descriptive and administrative properties such as Location and Categorisation
-
Separate technical renditions of a picture
|
We recommend reading the chapter on NewsML-G2 Basics before this guide to implementing Pictures and Graphics. |
The picture and the metadata used in the example are courtesy of Getty Images. Note that the sample code is NOT intended to be a guide to receiving NewsML-G2 from Getty Images.
8.2. About the example
A library picture is provided to customers in three sizes: a large image intended for high resolution and/or large size display, a medium-sized image intended for web use, and a small image for use as a thumbnail or icon. These are three alternative renditions of the same picture and can be contained in a single NewsML-G2 document.
(All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-gycon, ex-gyibt, ex-gyiid, ex-gyimeid, ex-gyrel and ex-gyrol.)
<newsItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="tag:gettyimages.com,2010:GYI0062134533"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-US">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://cv.gettyimages.com/nml2catalog4customers-1.xml" />
<rightsInfo>
<copyrightHolder uri="http://www.gettyimages.com">
<name>Getty Images North America</name>
</copyrightHolder>
<copyrightNotice
href="http://www.gettyimages.com/Corporate/LicenseInfo.aspx">
Copyright 2010 Getty Images. --
http://www.gettyimages.com/Corporate/LicenseInfo.aspx
</copyrightNotice>
<usageTerms>Contact your local office for all commercial or
promotional uses. Full editorial rights UK, US, Ireland, Canada (not
Quebec). Restricted editorial rights for daily newspapers elsewhere,
please call.</usageTerms>
</rightsInfo>
<itemMeta>
<itemClass qcode="ninat:picture"/>
<provider qcode="nprov:GYI" >
<name>Getty Images Inc.</name>
</provider>
<versionCreated>2022-10-12T06:42:04Z </versionCreated>
<firstCreated>2010-10-20T20:58:00Z</firstCreated>
</itemMeta>
<contentMeta>
<contentCreated>2010-10-20T19:45:58-04:00</contentCreated>
<creator role="ex-gyrol:photographer">
<name>Spencer Platt</name>
<related rel="ex-gyrel:isA" qcode="ex-gyibt:staff" />
</creator>
<contributor role="cpprole:descrWriter">
<name>sp/lrc</name>
</contributor>
<creditline>Getty Images</creditline>
<subject type="cpnat:event" qcode="ex-gyimeid:104530187" />
<subject type="cpnat:abstract" qcode="medtop:20000523">
<name xml:lang="en-GB">labour market</name>
<name xml:lang="de">Arbeitsmarkt</name>
</subject>
<subject type="cpnat:abstract" qcode="medtop:20000533">
<name xml:lang="en-GB">unemployment</name>
<name xml:lang="de">Arbeitslosigkeit</name>
</subject>
<subject type="cpnat:geoArea">
<name>Las Vegas Boulevard</name>
</subject>
<subject type="cpnat:geoArea" qcode="ex-gycon:89109">
<name>Las Vegas</name>
<broader qcode="iso3166-1a2:US-NV">
<name>Nevada</name>
</broader>
<broader qcode="iso3166-1a3:USA">
<name>United States</name>
</broader>
</subject>
<keyword>business</keyword>
<keyword>economic</keyword>
<keyword>economy</keyword>
<keyword>finance</keyword>
<keyword>poor</keyword>
<keyword>poverty</keyword>
<keyword>gamble</keyword>
<headline>Variety Of Recessionary Forces Leave Las Vegas
Economy Scarred</headline>
<description role="drol:caption">A general view of part of downtown,
including Las Vegas Boulevard, on October 20, 2010 in Las Vegas,
Nevada. Nevada once had among the lowest unemployment rates in the
United States at 3.8 percent but has since fallen on difficult times.
Las Vegas, the gaming capital of America, has been especially hard
hit with unemployment currently at 14.7 percent and the highest
foreclosure rate in the nation. Among the sparkling hotels and
casinos downtown are dozens of dormant construction projects and
hotels offering rock bottom rates. As the rest of the country slowly
begins to see some economic progress, Las Vegas is still in the midst
of the economic downturn. (Photo by Spencer Platt/Getty Images)
</description>
</contentMeta>
<contentSet>
<remoteContent rendition="rnd:highRes"
href="./GYI0062134533.jpg" version="1"
size="346071" contenttype="image/jpeg" width="1500"
height="1001" colourspace="colsp:AdobeRGB" orientation="1"
layoutorientation="loutorient:horizontal">
<altId type="ex-gyiid:masterID">105864332</altId>
</remoteContent>
<remoteContent rendition="rnd:web"
href="file:///./ GYI0062134533-web.jpg" version="1"
size="28972" contenttype="image/jpeg" width="480"
height="320" colourspace="colsp:AdobeRGB" orientation="1"
layoutorientation="loutorient:horizontal"/>
<remoteContent rendition="rnd:thumb"
href="file:///./GYI0062134533-thumb.gif" version="1"
size="6381" contenttype="image/gif" width="80"
height="53" colourspace="colsp:AdobeRGB" orientation="1"
layoutorientation="loutorient:horizontal"/>
</contentSet>
</newsItem>8.3. Document structure
The building blocks of the NewsML-G2 document are the <newsItem> root element, with additional wrapping elements for metadata about the News Item (itemMeta), metadata about the content (contentMeta) and the content itself (contentSet).
The root <newsItem> attributes are:
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="tag:gettyimages.com.2010:GYI0062134533"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-US">Note that this example uses a Tag URI (see TAG URI home page for details)
This is followed by references to the Catalogs used to resolve QCodes in the Item, and Rights information:
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml"
/>
<catalogRef
href="http://cv.gettyimages.com/nml2catalog4customers-1.xml" />
<rightsInfo>
<copyrightHolder uri="http://www.gettyimages.com">
<name>Getty Images North America</name>
</copyrightHolder>
<copyrightNotice
href="http://www.gettyimages.com/Corporate/LicenseInfo.aspx">
Copyright 2010 Getty Images. -- http://www.gettyimages.com/Corporate/LicenseInfo.aspx
</copyrightNotice>
<usageTerms>Contact your local office for all commercial or promotional uses. Full editorial rights UK, US, Ireland, Canada (not Quebec). Restricted editorial rights for daily newspapers elsewhere, please call.</usageTerms>
</rightsInfo>8.4. Item Metadata <itemMeta>
<itemMeta>
<itemClass qcode="ninat:picture">
<provider qcode="nprov:GYI">
<name>Getty Images Inc.</name>
</provider>
<versionCreated>2022-11-12T06:42:04Z</versionCreated>
<firstCreated>2010-10-20T20:58:00Z</firstCreated>
</itemMeta>The <itemClass> property uses a QCode from the IPTC News Item Nature NewsCodes to denote that the Item conveys a picture.
The Z suffix denotes UTC. Note the <firstCreated> property refers to the creation of the Item, NOT the content.
8.5. Embedded metadata
For many years IPTC metadata fields have been embedded in JPEG and TIFF image files. From 1995 on, the IPTC Information Interchange Model (IIM) defined the semantics of the fields and the technical format for saving them in image files. In 2003, Adobe introduced a new format for saving metadata, namely XMP (Extended Metadata Platform), and many IPTC IIM fields were specified as the "IPTC Core" metadata schema. This defined identical semantics but opened the formats for saving to IIM and XMP in parallel. Later the "IPTC Extension" metadata schema was added; the defined fields are stored by XMP only. Thus, many people work with IPTC photo metadata, regardless how they are saved in the files; this is handled by the software they use.
The transfer of IPTC Photo Metadata fields to NewsML-G2 properties has a focus on the equivalence of the semantics of fields. The retrieval of the embedded values from the files is a secondary issue and documents like the Guidelines for Handling Image Metadata, produced by the Metadata Working Group (http://www.metadataworkinggroup.org/specs/) help in this area.
This chapter provides the basics of this mapping, for more details see Mapping Embedded Photo Metadata to NewsML-G2. You can also learn more from the IPTC web by visiting https://www.iptc.org/standards/ and following the link to Photo Metadata.
The screen shot on the following page shows the panel for the IPTC Core fields as displayed by Adobe’s Photoshop CS File Info screen; note the IPTC Extension tab that displays the additional IPTC Extension metadata.
There are advantages, in a professional workflow, to carrying metadata independently of the binary asset:
-
There is no need to retrieve and open the file to read essential information about the picture
-
An editor may not have access to the original picture to modify its metadata
-
A library picture used to illustrate a news event may have inappropriate embedded metadata.
A situation may arise where the metadata expressed in the NewsML-G2 Item and the embedded metadata in the photo are different. Some providers choose to strip all embedded metadata from objects, to avoid potential confusion. If not, a provider should specify any processing rules in its terms of use.
The IPTC recommends that descriptive metadata properties that exist in the NewsML-G2 Item (in Content Metadata) ALWAYS take precedence over the equivalent embedded metadata (if it exists). These properties include genre, subject, headline, description and creditline.
8.6. Content Metadata <contentMeta>
This example shows how embedded metadata from the example picture are translated into NewsML-G2, and includes the equivalent IPTC Core metadata schema property highlighted thus:
8.6.1. Administrative metadata
Timestamp
The <contentCreated> element is used to give the creation date of the picture:
<contentCreated>2010-10-20T19:45:58-04:00</contentCreated>Note that this value refers to the creation of the original content; for a scanned picture this is always the date (and optionally the time) of the original photograph. The property type is Truncated Date Time, so that when the precise date-time is unknown, for example for an historic photograph, the value can be truncated (from the right) to a simple date or just a year.
Creator
The example uses a <creator> element without an identifier, but includes an optional @role that contains a QCode qualifying the creator as a photographer:
<creator role="ex-gyrol:photographer">
<name>Spencer Platt</name>
<related rel="ex-gyrel:isA" qcode="ex-gyibt:staff" />
</creator>The <related> child element of <creator> further qualifies the photographer as a member of staff (as distinct from, say, a freelance photographer)
Contributor
A <contributor> identifies people or organisations who did not originate the content, but have added value to it. In this case, the @role value (from the IPTC Content Production Party Role scheme) is a hint that the contributor added descriptive metadata:
<contributor role="cpprole:descrWriter">
<name>sp/lrc</name>
</contributor>8.6.2. Descriptive metadata
Subject
As described in the chapter on NewsML-G2 Basics, the subject matter of content is expressed using the <subject> element. The optional @type uses the IPTC Concept Nature NewsCodes (recommended scheme alias "cpnat") to indicate the type of concept being expressed. The following example uses a value of "cpnat:event" to indicate that the concept is an Event, and the QCode identifies the Event in the scheme with an alias "ex-gyimeid":
<subject type="cpnat:event" qcode="ex-gyimeid:104530187" />The provider can use this Event ID to "tag" each of the pictures that relate to this topic, enabling receivers to group them via the Event ID.
The picture of Las Vegas Boulevard illustrates a story about unemployment. This example uses codes and associated <name> child elements from the IPTC Media Topic NewsCodes:
<subject type="cpnat:abstract" qcode="medtop:20000523">
<name xml:lang="en-GB">labour market</name>
<name xml:lang="de">Arbeitsmarkt</name>
</subject>
<subject type="cpnat:abstract" qcode="medtop:20000533">
<name xml:lang="en-GB">unemployment</name>
<name xml:lang="de">Arbeitslosigkeit</name>
</subject>City, State/Province, Country
The <located> element in the <contentMeta> block describes the place where the picture was created. This may be the same location as the event portrayed in the picture, but this cannot be assumed. The location of the event is logically part of the subject matter – the City, State/Province, Country fields in the IPTC Photo Metadata are defined as "the location shown" – so should use the <subject> element. To summarise:
-
Use <located> to describe where the camera was located when taking the picture.
-
Use <subject> to describe the location shown in the picture. It is recommended that @type is used to indicate the property identifies a geographical area.
The location shown in the example picture is Las Vegas Boulevard. Child elements of <subject> may be used to add further details, including:
-
<name> gives the place name in plain text, and
-
<broader> expresses the concept of Las Vegas Boulevard as part of the broader entity of Las Vegas which in turn is part of broader entities of Nevada state and of the United States.
It is recommended that the nature of the concept is indicated by @type using a value from the IPTC Concept Nature NewsCodes, in this case that the concept identifies a geographical area:
The completed <subject> structure for the geographical information is:
<subject type="cpnat:geoArea">
<name>Las Vegas Boulevard</name>
</subject>
<subject type="cpnat:geoArea" qcode="ex-gycon:89109">
<name>Las Vegas</name>
<broader qcode="iso3166-1a2:US-NV">
<name>Nevada</name>
</broader>
<broader qcode="iso3166-1a3:USA">
<name>United States</name>
</broader>
</subject>Keywords
QCodes and relationship properties are powerful tools, but keywords are still widely used by picture archives. The NewsML-G2 <keyword> property is mapped from the "Keywords" field in XMP. The semantics of "keyword" can vary from provider to provider, but should not present problems in the news industry, which is familiar enough with their use:
<keyword>business</keyword>
<keyword>economic</keyword>
<keyword>economy</keyword>
<keyword>finance</keyword>
<keyword>poor</keyword>
<keyword>poverty</keyword>
<keyword>gamble</keyword>Headline, Description
These two IPTC/IIM fields map directly to elements of the same name in NewsML-G2. Both <headline> and <description> also have an optional @role. The IPTC maintains a set of NewsCodes for Description Role (recommended scheme alias "drol"). In this case, as the description is of a photograph, the role will be "caption". Description is a Block type element, meaning it may contain line breaks.
Both elements have optional attributes which may be used to support international use: @xml:lang, @dir (text direction):
<headline>Variety Of Recessionary Forces Leave Las Vegas
Economy Scarred</headline>
<description role="drol:caption">A general view of part of downtown,
including Las Vegas Boulevard, on October 20, 2010 in Las Vegas,
Nevada. Nevada once had among the lowest unemployment rates in the
United States at 3.8 percent but has since fallen on difficult times.
Las Vegas, the gaming capital of America, has been especially hard
hit with unemployment currently at 14.7 percent and the highest
foreclosure rate in the nation. Among the sparkling hotels and
casinos downtown are dozens of dormant construction projects and
hotels offering rock bottom rates. As the rest of the country slowly
begins to see some economic progress, Las Vegas is still in the midst
of the economic downturn. (Photo by Spencer Platt/Getty Images)
</description>8.6.3. Completed <contentMeta>
<contentMeta>
<contentCreated>2010-10-20T19:45:58-04:00</contentCreated>
<creator role="ex-gyrol:photographer">
<name>Spencer Platt</name>
<related rel="ex-gyrel:isA" qcode="ex-gyibt:staff" />
</creator>
<contributor role="cpprole:descrWriter">
<name>sp/lrc</name>
</contributor>
<creditline>Getty Images</creditline>
<subject type="cpnat:event" qcode="ex-gyimeid:104530187" />
<subject type="cpnat:abstract" qcode="medtop:20000523">
<name xml:lang="en-GB">labour market</name>
<name xml:lang="de">Arbeitsmarkt</name>
</subject>
<subject type="cpnat:abstract" qcode="medtop:20000533">
<name xml:lang="en-GB">unemployment</name>
<name xml:lang="de">Arbeitslosigkeit</name>
</subject>
<subject type="cpnat:geoArea">
<name>Las Vegas Boulevard</name>
</subject>
<subject type="cpnat:geoArea" qcode="ex-gycon:89109">
<name>Las Vegas</name>
<broader qcode="iso3166-1a2:US-NV">
<name>Nevada</name>
</broader>
<broader qcode="iso3166-1a3:USA">
<name>United States</name>
</broader>
</subject>
<keyword>business</keyword>
<keyword>economic</keyword>
<keyword>economy</keyword>
<keyword>finance</keyword>
<keyword>poor</keyword>
<keyword>poverty</keyword>
<keyword>gamble</keyword>
<headline>Variety Of Recessionary Forces Leave Las Vegas Economy Scarred</headline>
<description role="drol:caption">A general view of part of downtown,
including Las Vegas Boulevard, on October 20, 2010 in Las Vegas,
Nevada. Nevada once had among the lowest unemployment rates in the
United States at 3.8 percent but has since fallen on difficult times.
Las Vegas, the gaming capital of America, has been especially hard
hit with unemployment currently at 14.7 percent and the highest
foreclosure rate in the nation. Among the sparkling hotels and
casinos downtown are dozens of dormant construction projects and
hotels offering rock bottom rates. As the rest of the country slowly
begins to see some economic progress, Las Vegas is still in the midst
of the economic downturn. (Photo by Spencer Platt/Getty Images)
</description>
</contentMeta>8.7. Picture data
Binary content is conveyed within the NewsML-G2 <contentSet> wrapper by one or more <remoteContent> elements, enabling multiple alternate renditions of a picture within the same Item.
8.7.1. Remote Content
The <remoteContent> element references objects that exist independently of the current NewsML-G2 Item. In the example there is an instance of <remote Content> for each of the three separate binary renditions of the picture.
Each remote content instance contains attributes that conceptually can be split into three groups:
-
Target resource attributes enable the receiver to accurately identify the remote resource, it’s content type and size;
-
Content attributes enable the processor to distinguish the different business purposes of the content using @rendition;
-
Content Characteristics contain technical metadata such as dimensions, colour values and resolution.
Frequently used attributes from these groups are described below, but note that the NewsML-G2 XML structure that delimits the groups may not be visible in all XML editors. For details of these attribute groups, see the NewsML-G2 Specification, which can be downloaded from www.newsml-g2.org/spec.
8.7.2. Target Resource Attributes
This group of attributes express administrative metadata, such as identification and versioning, for the referenced content, which could be a file on a mounted file system, a Web resource, or an object within a CMS. NewsML-G2 flexibly supports alternative methods of identifying and locating the externally-stored content. For this example, the picture renditions are located in the same folder as the NewsML-G2 document.
The two attributes of <remoteContent> available to identify and locate the content are Hyperlink (@href) and Resource Identifier Reference (@residref). Either one MUST be used to identify and locate the target resource. They MAY optionally be used together, Their intended use is:
-
@href locates any resource, using an IRI.
-
@residref identifies a managed resource, using an identifier that may be globally unique.
Hyperlink (@href)
An IRI, for example:
<remoteContent href="
http://example.com/2008-12-20/pictures/foo.jpg"Or (amongst other possibilities):
<remoteContent href="file:///./GYI0062134533-web.jpg"Resource Identifier Reference (@residref)
An XML Schema string, such as:
<remoteContent residref="tag:example.com,2008:PIX:FOO20081220098658"The provider may use residrefformat or residrefformaturi to specify the format of the @residref. The recommended CV to be used is https://cv.iptc.org/newscodes/valueformat/ with a recommended scheme alias of "valfmt":
<remoteContent residref="tag:example.com,2008:PIX:FOO20081220098658"
residrefformat="valfmt:uri"8.7.3. News Content Attributes
This group of attributes of <remoteContent> enables a processor or human-reader to distinguish between different components; in this case the alternative resolutions of the picture. The principal attribute of this group is @rendition, described below.
Rendition
The rendition attribute MUST use a QCode, either proprietary or using the IPTC NewsCodes for rendition, which has a Scheme URI of http://cv.iptc.org/newscodes/rendition/ and recommended Scheme Alias of "rnd" and contains (amongst others) the values that we need: highRes, web, thumbnail. Thus using the appropriate NewsCode, the high resolution rendition of the picture may be identified as:
<remoteContent rendition="rnd:highRes"To avoid processing ambiguity, each specific rendition value should be used only once per News Item, except when the same rendition is available from multiple remote locations. In this case, the same value of rendition may be given to several Remote Content elements.
8.7.4. News Content Characteristics
This group of attributes describes the physical properties of the referenced object specific its media type. Text, for example, may use @wordcount). Audio and video are provided with attributes appropriate to streamed media, such as @audiobitrate, @videoframerate. The appropriate attributes for pictures are described below.
Picture Width and Picture Height
The dimension attributes @width and @height are optionally qualified by @dimensionunit, which specifies the units being used. This is a @qcode value and it is recommended that the value is taken from the IPTC Dimension Unit NewsCodes, whose URI is http://cv.iptc.org/newscodes/dimensionunit/ (recommended Scheme Alias is "dimensionunit")
If @dimensionunit is absent, the default units for each content type are:
| Content Type | Height Unit (default) | Width Unit (default) |
|---|---|---|
Picture |
pixels |
pixels |
Graphic: Still / Animated |
points |
points |
Video (Analog) |
lines |
pixels |
Video (Digital) |
pixels |
pixels |
As the dimensions of the example picture are expressed in pixels, @dimensionunit is not needed:
width="1500"
height="1001"Picture Orientation
This indicates that the image requires an orientation change before it can be properly viewed, using values of 1 to 8 (inclusive), where 1 (the default) is "upright": that is the visual top of the picture is at the top, and the visual left side of the picture in on the left.
The application of these orientation values is described in detail in the News Content Characteristics section of the NewsML-G2 Specification. (This can be downloaded by visiting https://iptc.org/standards/ and following the link to NewsML-G2.)
The picture used in our example has an orientation value of 1:
width="1500"
height="1001"
orientation="1"Layout Orientation
It is possible to calculate the best way to use a picture in a page layout using the combined technical characteristics of Height, Width and Orientation, but many implementers are reluctant to rely on technical characteristics to make editorial judgements (determining whether a video is SD or HD is another example). The @layoutorientation is a way to express editorial advice on the best way to use a picture in a layout. The value for the example picture is:
layoutorientation="loutorient:horizontal"Values in the Layout Orientation Scheme are:
| Code | Definition |
|---|---|
horizontal |
The human interpretation of the top of the image is aligned to the long side. |
vertical |
The human interpretation of the top of the image is aligned to the short side. |
Square |
Both sides of the image are about identical, there is no short and long side. |
unaligned |
There is no human interpretation of the top of the image. |
Picture Colour Space
The colour space of the target resource, and MUST use a QCode. The recommended scheme is the IPTC Colour Space NewsCodes (recommended scheme alias "colsp") Note the UK English spelling of colour.
colourspace="colsp:AdobeRGB"Colour Depth
The optional @colourdepth indicates using a non-negative integer the number of bits used to define the colour of each pixel in a still image, graphic or video.
colourdepth="24"Content Hints
| It is not mandatory for the metadata to be extracted from the target resource, but it MUST agree with any existing metadata within the target resource. |
In this case, the provider has added an <altId> – an alternative identifier – for the resource.
Alternative identifiers may be needed by customer systems. The <altId> element may optionally be refined using a QCode to describe the context – in this case a "master ID" that is proprietary to the provider. This makes clear the purpose of the alternative identifier. Also note that Alternative Identifiers are useful only to another application; and not intended to be used by THIS NewsML-G2 processor. The provider MUST tell receivers how to interpret alternative identifiers, otherwise they are meaningless.
<altId type="ex-gyiid:masterID">105864332</altId>Note that in this example only the high resolution rendition has an <altId>.
Signal
The signal property instructs the NewsML-G2 processor to process an Item or its content in a specific way. As a child element of itemMeta, the scope of <signal> is the whole of the document and/or its contents. If alternative renditions of content have specific processing needs, use <signal> as a child element of <remoteContent> to specify the processing instructions.
8.7.5. Completed <remoteContent> wrapper
The <remoteContent> wrapping element in full for the "High Res" picture in the example:
<remoteContent rendition="rnd:highRes"
href="./GYI0062134533.jpg" version="1"
size="346071" contenttype="image/jpeg" width="1500"
height="1001" colourspace="colsp:AdobeRGB" orientation="1"
layoutorientation="loutorient:horizontal">
<altId type="ex-gyiid:masterID">105864332</altId>
</remoteContent>9. Video
9.1. Introduction
Now that streamed media is part of everyone’s day-to-day experience on the Web, organisations with little or no tradition of "broadcast media" production need to be able to process audio and video.
NewsML-G2 allows all media organisations, whether traditional broadcasters or not, to access and exchange audio and video in a professional workflow, by providing features and Extension Points that enable proprietary formats to be "mapped" to Newsml-G2 to achieve freedom of exchange amongst a wider circle of information partners.
This chapter is split into two parts:
-
Part I deals with a video that is available in multiple different renditions and the example focuses on expressing the technical characteristics of each rendition of the content.
-
Part II shows an example of video content has been assembled from multiple sources, each with distinct metadata.
|
We recommend reading the chapter on NewsML-G2 Basics before this guide to implementing video. |
9.2. Part I – Multiple Renditions of a Single Video
The following example is based on a sample NewsML-G2 video item from Agence France Presse (but is not a guide to processing AFP’s NewsML-G2 news services).
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for ex-afpdescRole.
<?xml version="1.0" encoding="utf-8"?>
<newsItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.30-spec-All-Power.xsd"
guid="urn:newsml:afp.com:20140131:CNG.3424d3807bc.391@video_1359566"
version="14"
standard="NewsML-G2"
standardversion="2.30"
conformance="power"
xml:lang="en-US">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://cv.afp.com/std/catalog/catalog.AFP-IPTC-G2_3.xml" />
<itemMeta>
<itemClass qcode="ninat:video" />
<provider qcode="nprov:AFP" />
<versionCreated>2022-10-31T11:37:23+01:00</versionCreated>
<firstCreated>2014-01-30T13:29:38+00:00</firstCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<icon contenttype="image/jpeg" height="62"
href="http://spar-iris-p-sco-http-int-vip.afp.com/components/9601ac3"
rendition="rnd:thumbnail" width="110" />
<creditline>AFP</creditline>
<description role="ex-afpdescRole:synthe">- Amir Hussein Abdullahian, Iranian
foreign ministry's undersecretary for Arab and African affairs -
Panos Moumtzis (man), UNHCR regional coordinator for Syrian refugees
</description>
<description role="ex-afpdescRole:script">SHOTLIST: KUWAIT. JANUARY 30,
2014. SOURCE: AFPTV -VAR inside the conference room -VAR of Ban
Ki-moon -MS of King Abdullah II of Jordan -MS of Michel Sleiman,
president of Lebanon -MS of Tunisian president Moncef Marzouki
SOUNDBITE 1 - Amir Hussein Abdullahian (man), Iranian foreign
ministry's undersecretary for Arab and African affairs (Farsi, 10
sec): "Those who send arms to Syria are behind the daily killings
there." SOUNDBITE 2 - Amir Hussein Abdullahian (man), Iranian foreign
ministry's undersecretary for Arab and African affairs (Farsi, 9
sec): "We regret that some countries, such as the United States, have
created a very high level of extremism in Syria." SOUNDBITE 3 - Panos
Moumtzis (man), UNHCR regional coordinator for Syrian refugees
(Arabic, 12 sec): "The United Nations is providing humanitarian
assistance to more than four million people inside Syria, two million
of them displaced." SOUNDBITE 4 - Panos Moumtzis (man), UNHCR
regional coordinator for Syrian refugees (Arabic, 17 sec): "The
funding will first go to UN relief organizations, who are working
inside Syria and in neighbouring countries. Funding will also go to
the more than 55 NGOs in Syria with whom we cooperate and coordinate
to deliver aid."
</description>
<language tag="en" />
</contentMeta>
<contentSet>
<remoteContent contenttype="video/mpeg-2"
href="http://components.afp.com/ab652af034e.mpg"
rendition="ex-vidrnd:dvd"
size="54593540"
width="720"
height="576"
duration="69"
durationunit="timeunit:seconds"
videocodec="vcdc:c015"
videoframerate="25"
videodefinition="videodef:sd"
colourindicator="colin:colour"
videoaspectratio="4:3"
videoscaling="sov:letterboxed" />
<remoteContent contenttype="video/mp4-1920x1080"
href="http://components.afp.com/3e353716caa.1920x1080.mp4"
rendition="ex-vidrnd:HD1080"
size="87591736"
width="1920" height="1080"
duration="69"
durationunit="timeunit:seconds"
videocodec="vcdc:c041"
videoframerate="25"
videodefinition="videodef:hd"
colourindicator="colin:colour"
videoaspectratio="16:9"
videoscaling="sov:unscaled" />
<remoteContent contenttype="video/mp4-1280x720"
href="http://components.afp.com/5ba0d14a64f.1280x720.mp4"
rendition="ex-vidrnd:HD720"
size="71010540"
width="1280" height="720"
duration="69"
durationunit="timeunit:seconds"
videocodec="vcdc:c041"
videoframerate="25"
videodefinition="videodef:hd"
colourindicator="colin:colour"
videoaspectratio="16:9"
videoscaling="sov:unscaled" />
</contentSet>
</newsItem>9.2.1. Document structure
The building blocks of the NewsML-G2 Item are the <newsItem> root element, with additional wrapping elements for metadata about the News Item (itemMeta), metadata about the content (contentMeta) and the content itself (contentSet).
The root <newsItem> attributes are:
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:afp.com:20160131:CNG.3424d3807bc.391@video_1359566"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-US">This is followed by Catalog references:
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml"
/>
<catalogRef
href="http://cv.afp.com/std/catalog/catalog.AFP-IPTC-G2_3.xml" />9.2.2. Item Metadata <itemMeta>
The <itemClass> property uses a QCode from the IPTC News Item Nature NewsCodes to denote that the Item conveys a picture. Note that <provider> uses the recommended IPTC Provider NewsCodes, a controlled vocabulary of providers registered with the IPTC, recommended scheme alias "nprov":
<itemMeta>
<itemClass qcode="ninat:video" />
<provider qcode="nprov:AFP" />
<versionCreated>2022-01-31T11:37:23+01:00 </versionCreated>
<firstCreated>2016-01-30T13:29:38+00:00</firstCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>9.2.3. Content Metadata <contentMeta>
The <icon> element tells receivers how to retrieve an image to use as an iconic image for the content, for example a still image extracted from the video. It’s possible to have multiple icons to suit different applications, each qualified by @rendition.
Two <description> elements are qualified by @role: first a summary, second a more detailed shotlist:
<contentMeta>
<icon contenttype="image/jpeg" height="62"
href="http://spar-iris-p-sco-http-int-vip.afp.com/components/9601ac3"
rendition="rnd:thumbnail" width="110" />
<creditline>AFP</creditline>
<description role="ex-afpdescRole:synthe">- Amir Hussein Abdullahian,
foreign ministry's undersecretary for Arab and African affairs -
Panos Moumtzis (man), UNHCR regional coordinator for Syrian refugees
</description>
<description role="ex-afpdescRole:script">SHOTLIST: KUWAIT. JANUARY 30,
\2016. SOURCE: AFPTV -VAR inside the conference room -VAR of Ban
Ki-moon -MS of King Abdullah II of Jordan -MS of Michel Sleiman,
president of Lebanon -MS of Tunisian president Moncef Marzouki
SOUNDBITE 1 - Amir Hussein Abdullahian (man), Iranian foreign
ministry's undersecretary for Arab and African affairs (Farsi, 10
sec): "Those who send arms to Syria are behind the daily killings
there." SOUNDBITE 2 - Amir Hussein Abdullahian (man), Iranian foreign
ministry's undersecretary for Arab and African affairs (Farsi, 9
sec): "We regret that some countries, such as the United States, have
created a very high level of extremism in Syria." SOUNDBITE 3 - Panos
Moumtzis (man), UNHCR regional coordinator for Syrian refugees
(Arabic, 12 sec): "The United Nations is providing humanitarian
assistance to more than four million people inside Syria, two million
of them displaced." SOUNDBITE 4 - Panos Moumtzis (man), UNHCR
regional coordinator for Syrian refugees (Arabic, 17 sec): "The
funding will first go to UN relief organizations, who are working
inside Syria and in neighbouring countries."
</description>
<language tag="en" />
</contentMeta>9.2.4. Video Content
Video is conveyed within the NewsML-G2 <contentSet> using the <remoteContent> element; where there are multiple alternate renditions of SAME content, <remoteContent> can be repeated for each rendition within the same Item.
The <remoteContent> element references binary objects that exist independently of the current NewsML-G2 document. In this example there is an instance of <remote Content> for each of three renditions of the video.
Each remote content instance contains attributes that can conceptually be split into three groups:
-
Target resource attributes enable the receiver to accurately identify the remote resource, its content type and size;
-
Content attributes enable the processor to distinguish the different business purposes of the content using @rendition;
-
Content Characteristics contain technical metadata such as dimensions, duration and format.
Frequently used attributes from these groups are described below, but note that the NewsML-G2 XML structure that delimits the groups may not be visible in all XML editors. For a detailed description of these attribute groups, see the NewsML-G2 Specification (This can be downloaded by visiting www.newsml-g2.org/spec and following the link to NewsML-G2.)
9.2.5. Target Resource Attributes
This group of attributes express administrative metadata, such as identification and versioning, for the referenced content, which could be a file on a mounted file system, a Web resource, or an object within a content management system. NewsML-G2 flexibly supports alternative methods of identifying and locating the externally-stored content.
The two attributes of <remoteContent> that identify and optionally locate the content are Hyperlink (@href) and Resource Identifier Reference (@residref). Either one MUST be used to identify the target resource. They MAY optionally be used together.
Although @href and @resideref are superficially similar, their intended use is:
-
@href locates any resource, using an IRI.
-
@residref identifies a managed resource, using an identifier that may be globally unique.
Hyperlink (@href)
An IRI, for example:
<remoteContent href="http://components.afp.com/ab652af034e5f7acc131f8f122b274a5ef8ee37e.mpg"Resource Identifier Reference (@residref)
An XML Schema string e.g.
<remoteContent residref="tag:example.com,2008:PIX:FOO20081220098658"The provider may use residrefformat or residrefformaturi to specify the format of the @residref. The recommended CV to be used is https://cv.iptc.org/newscodes/valueformat/ with a recommended scheme alias of "valfmt":
<remoteContent residref="tag:example.com,2008:PIX:FOO20081220098658"
residrefformat="valfmt:uri"Version
An XML Schema positive integer denoting the version of the target resource. In the absence of this attribute, recipients should assume that the target is the latest available version
version="15"Format
A refinement of a Content Type using a value from a controlled vocabulary:
format="frmt:MPEG"9.2.6. News Content Attributes
This group of attributes of <remoteContent> enables a processor or human operator to distinguish between different components; in this case the alternative resolutions of the video.
Rendition
The rendition attribute MUST use a QCode. Providers may have their own schemes, or use the IPTC NewsCodes for rendition, which has a Scheme URI of http://cv.iptc.org/newscodes/rendition/ and recommended Scheme Alias of "rnd". This example uses a fictional provider-specific scheme with a Scheme Alias of "ex-vidrnd":
<remoteContent rendition="ex-vidrnd:dvd"To avoid processing ambiguity, each specific rendition value should be used only once per News Item, except when the same rendition is available from multiple remote locations. In this case, the same value of rendition may be given to several Remote Content elements.
9.2.7. News Content Characteristics
This third a group of attributes of <remoteContent> is provided to enable further efficiencies in processing and describes physical characteristics of the referenced object specific its media type. Text, for example, may use @wordcount; Audio and video are provided with attributes appropriate to streamed media, such as @audiobitrate, @videoframerate. The appropriate attributes for video are described below.
Duration (@duration and @durationunit)
Indicates the duration of the content in seconds by default, but can be expressed by some other measure of temporal reference (e.g. frames) when using the optional @durationunit. From NewsML-G2 2.14, the data-type of @duration is a string; earlier versions use non-negative integer. The reason for the change is that video duration is often expressed using non-integer values.
For example, expressing duration as an SMPTE time code requires the following NewsML-G2:
duration="00:06:32:12" durationunit="timeunit:timeCode"The recommended CV for @durationunit is the IPTC Time Unit NewsCodes whose URI is http://cv.iptc.org/newscodes/timeunit/. The recommended alias for the scheme is "timeunit".
Video Codec (@videocodec)
A QCode value indicating the encoding of the video – for example one of the encodings used in this example is MPEG-2 Video Simple Profile. This is indicated by the IPTC Video Codec NewsCodes with a recommended Scheme Alias "vcdc", and the corresponding code is "c015".
videocodec="vcdc:c015"Video Frame Rate (@videoframerate)
A decimal value indicating the rate, in frames per second [fps] at which the video should be played out to achieve the correct visual effect. Common values (in fps) are 25, 50, 60 and 29.97 (drop-frame rate):
videoframerate="25"Video Scaling (@videoscaling)
The @videoscaling attribute describes how the aspect ratio of a video has been changed from the original in order to accommodate a different display dimension:
videoscaling="sov:letterboxed"The value of the property is a QCode; the recommended CV is the IPTC Video Scaling NewsCodes (Scheme URI: http://cv.iptc.org/newscodes/videoscaling/) The recommended Scheme Alias is "sov".
Video Definition (@videodefinition)
Editors may need to know whether video content is HD or SD, as this may not be obvious from the technical specification ("HD", for example, is an umbrella term covering many different sets of technical characteristics). The @videodefinition attribute carries this information:
videodefinition="videodef:sd"The value of the property can be either "hd" or "sd", as defined by the Video Definition NewsCodes CV. The Scheme URI is http://cv.iptc.org/newscodes/videodefinition/ and the recommended scheme alias is "videodef".
Colour Indicator <colourindicator>
Indicates whether the still or moving image is coloured or black and white (note the UK spelling of colour). The recommended vocabulary is the IPTC Colour Indicator NewsCodes (Scheme URI: http://cv.iptc.org/newscodes/colourindicator/) with a recommended Scheme Alias of "colin". The value of the property is "bw" or "colour":
colourindicator="colin:colour"The completed Remote Content wrapper will be:
<remoteContent contenttype="video/mpeg-2"
href="http://components.afp.com/ab652af034e5f7acc131f8f122b274a5ef8ee37e.mpg"
rendition="ex-vidrnd:dvd"
size="54593540"
width="720" height="576"
duration="69"
durationunit="timeunit:seconds"
videocodec="vcdc:c015"
videoframerate="25"
videodefinition="videodef:sd"
colourindicator="colin:colour"
videoaspectratio="4:3"
videoscaling="sov:letterboxed" />9.2.8. Audio metadata
There are specific properties for describing the technical characteristics of audio, for example:
Audio Bit Rate (@audiobitrate)
A positive integer indicating kilobits per second (Kbps)
audiobitrate="32"Audio Sample Rate (@audiosamplerate)
A positive integer indicating the sample rate in Hertz (Hz)
audiosamplerate="44100"For a detailed description of all of the News Content Characteristics for Video and Audio content, see section News Content Characteristics in the NewsML-G2 Specification Document.
9.3. Part 2 – Multi-part video
|
We recommend reading the chapter on NewsML-G2 Basics and the
preceding Part 1 of this guide to video before reading Part 2. |
Audio and video, including animation, have a temporal dimension: the nature of the content is expected to change over its duration: in this example a single piece of video has been created from a number of shots – shorter segments of content from different creators - that were combined during an editing process.
Note that this complies with the basic NewsML-G2 rule that "one piece of content = one newsItem". Although the video may be composed of material from many sources, it remains a single piece of journalistic content created by the video editor. This is analogous to a text story that is compiled by a single reporter or editor from several different reports.
NewsML-G2 supports this by enabling the expression of metadata about separate identifiable parts of content using <partMeta> in addition to metadata structures that apply to the whole content.
The example video is about a retrospective exhibition in Berlin of works by the German humourist and animator Vicco von Bülow. It consists of a number of shots, so provides a shotlist summarising the visual content of each shot, and a dopesheet, giving an editorial summary of the video’s content.
The document structure and the NewsML-G2 properties included in the example have been previously described, except for the <partMeta> wrapper, which is described in detail below. A full code listing for the example is included at the end.
The example is based on a sample NewsML-G2 video item from the European Broadcasting Union (EBU). The News Item references a multi-part broadcast video and contains separate metadata for each segment of the content, including a keyframe, and additionally describes the technical characteristics of the video.
| Please note that it may resemble but does NOT represent the EBU’s NewsML-G2 implementation. |
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following: ex-addressType, ex-codeorigin, ex-codesource, ex-cptype, ex-descrole, ex-geo, ex-langusecode, ex-prov, ex-providercode, ex-rolecode, ex-servicecode and ex-vidrnd.
<?xml version="1.0" encoding="ISO-8859-1"?>
<newsItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
standardversion="2.31"
guid="tag:example.com,2008:407624"
version="15"
standard="NewsML-G2"
conformance="power"
xml:lang="en">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef
href="http://www.example.com/metadata/newsml-g2/catalog.NewsML-G2.xml" />
<rightsInfo>
<usageTerms>
Access only for Eurovision Members and EVN / EVS Sub-Licensees.
<br />
Coverage cannot be used by a national competitor of the contributing
broadcaster.
</usageTerms>
</rightsInfo>
<itemMeta>
<itemClass qcode="ninat:video" />
<provider qcode="ex-providercode:EBU">
<name>European Broadcasting Union - EVN</name>
<organisationDetails>
<contactInfo>
<web>http://www.eurovision.net</web>
<phone>+41 22 717 2869</phone>
<email>features@eurovision.net</email>
<address role="ex-AddressType:Office">
<line>Eurovision Sports News Exchanges</line>
<line>L Ancienne Route 17 A</line>
<line>CH-1218</line>
<locality>
<name>Grand-Saconnex</name>
</locality>
<country qcode="iso3166-1a2:ch">
<name xml:lang="en">Switzerland</name>
</country>
</address>
</contactInfo>
</organisationDetails>
</provider>
<versionCreated>2022-10-19T10:54:04Z</versionCreated>
<firstCreated>2008-11-06T10:22:28Z</firstCreated>
<pubStatus qcode="stat:usable" />
<service qcode="ex-servicecode:EUROVISION">
<name>Eurovision services</name>
</service>
<edNote>Originally broadcast in Germany</edNote>
<link rel="irel:associatedWith"
href="http://www.example.com/video/407624/index.html"/>
</itemMeta>
<contentMeta>
<contentCreated>2008-11-05T19:04:00-08:00</contentCreated>
<located type="loctyp:City" qcode="ex-city:345678">
<name>Berlin</name>
<broader type="loctyp:Sublocation" qcode="ex-state:2365">
<name>Berlin</name>
</broader>
<broader type="loctyp:Country" qcode="iso3166-1a2:DE">
<name>Germany</name>
</broader>
</located>
<creator qcode="ex-codesource:DEZDF">
<name>Zweites Deutsches Fernsehen</name>
<organisationDetails>
<location>
<name>MAINZ</name>
</location>
</organisationDetails>
</creator>
<contributor qcode="ex-codeorigin:DEZDF" role="ex-rolecode:TechnicalOrigin">
<name>Zweites Deutsches Fernsehen</name>
</contributor>
<creator qcode="ex-codesource:GBRTV">
<name>Reuters Television Ltd</name>
</creator>
<language tag="en" role="lrol:voiceOver" >
<name>English</name>
</language>
<genre qcode="genre:Biography">
<name xml:lang="en-GB">Biography</name>
<name xml:lang="fr">biographie</name>
</genre>
<subject type="cpnat:abstract" qcode="medtop:01000000">
<name xml:lang="en-GB">arts, culture, entertainment and media</name>
<name xml:lang="fr">Arts, culture, divertissement et médias</name>
<narrower type="cpnat:abstract" qcode="medtop:20000003">
<name xml:lang="en-GB">Animation</name>
<name xml:lang="fr">Dessin animé</name>
</narrower>
</subject>
<headline>Loriot retrospective</headline>
<description role="ivqu:dopesheet">
Yesterday evening (November 5) an exhibition opened in Berlin in
honour of German humorist Vicco von Bülow, better known under the
pseudonym "Loriot", to commemorate his 85th birthday. He was born
November 12, 1923 in Brandenburg an der Havel and comes from an old
German aristocratic family. He is most well-known for his cartoons,
television sketches alongside late German actress Evelyn Hammann and
a couple of movies. Under the name "Loriot" in 1971 he created a
cartoon dog named "Wum", which he voice acted himself. In 1976 the
first episode of the TV series "Loriot" was produced.
<br />
</description>
<description role="ex-descrole:shotlist">
Berlin, 05/11/2008
<br />
- vs. Vicco von Bülow entering exhibition
<br />
- vs. Loriot and media
<br />
- sot Vicco von Bülow
<br />
"Since 85 years I didn't succeed in pursuing a job that could be
called a profession."
<br />
- vs exhibition
<br />
- sot Irm Herrmann, actress
<br />
"Loriot is timeless. You always can watch him and I can always
laugh."
<br />
- actor Ulrich Matthes in exhibition
<br />
sot Ulrich Matthes, actor
<br />
" I would say: one of the great German classics. Goethe, Kleist,
Schiller, Thomas Mann, Loriot. That's the way I would say it."
<br />
</description>
</contentMeta>
<partMeta partid="Part1_ID" seq="1">
<icon href=" http://www.example.com/video/Keyframes/407624.jpeg"/>
<timeDelim renditionref="ex-vidrnd:avi25" start="0" end="446" timeunit="timeunit:editUnit"/>
<language tag="en" role="ex-langusecode:VoiceOver" />
<description>Vicco von Bülow entering exhibition</description>
</partMeta>
<partMeta partid="Part2_ID" seq="2">
<icon href="http://www.example.com/video/Keyframes/407624-447.jpeg"/>
<timeDelim renditionref="ex-vidrnd:avi25" start="446" end="831" timeunit="timeunit:editUnit"/>
<language tag="en" role="ex-langusecode:VoiceOver" />
<description>Loriot and media</description>
</partMeta>
<partMeta partid="Part3_ID" seq="3">
<icon href="http://www.example.com/video/Keyframes/407624-832.jpeg"/>
<timeDelim renditionref="ex-vidrnd:avi25" start="831" end="1081" timeunit="timeunit:editUnit"/>
<language tag="en" role="ex-langusecode:Interlocution" />
<description>Vicco von Bülow interview</description>
</partMeta>
<partMeta partid="Part4_ID" seq="4">
<icon href="http://www.example.com/video/Keyframes/407624-1082.jpeg"/>
<timeDelim renditionref="ex-vidrnd:avi25" start="1081" end="1313" timeunit="timeunit:editUnit"/>
<language tag="en" role="ex-langusecode:NaturalSound" />
<description>Exhibition panorama </description>
</partMeta>
<partMeta partid="Part5_ID" seq="5">
<icon href="http://www.example.com/video/Keyframes/407624-1314.jpeg"/>
<timeDelim renditionref="ex-vidrnd:avi25" start="1313" end="1616" timeunit="timeunit:editUnit"/>
<language tag="en" role="ex-langusecode:Interlocution" />
<description>Irm Herrmann, actress, interview</description>
</partMeta>
<partMeta partid="Part6_ID" seq="6">
<icon href="http://www.example.com/video/Keyframes/407624-1617.jpeg"/>
<timeDelim renditionref="ex-vidrnd:avi25" start="1616" end="2109" timeunit="timeunit:editUnit"/>
<language tag="en" role="ex-langusecode:VoiceOver" />
<description>Ulrich Matthes, actor, in exhibition</description>
</partMeta>
<partMeta partid="Part7_ID" seq="7">
<icon href="http://www.example.com/video/Keyframes/407624-2110.jpeg"/>
<timeDelim renditionref="ex-vidrnd:avi25" start="2109" end="2732" timeunit="timeunit:editUnit"/>
<language tag="en" role="ex-langusecode:Interlocution" />
<description>Ulrich Matthes, actor, interview</description>
</partMeta>
<partMeta partid="Part8_ID" seq="9">
<icon href="http://www.example.com/video/Keyframes/407624-2733.jpeg"/>
<timeDelim renditionref="ex-vidrnd:avi25" start="2732" end="2775" timeunit="timeunit:editUnit"/>
<language tag="en" role="ex-langusecode:VoiceOver" />
<description>"I would say: one of the great German classics. Goethe, Kleist,
Schiller, Thomas Mann, Loriot. That's the way I would say it."</description>
</partMeta>
<contentSet>
<remoteContent href="http://www.example.com/video/407624.avi"
rendition="ex-vidrnd:avi25"
format="frmt:MPEG"
duration="111" durationunit="timeunit:seconds"
videocodec="vcdc:c155"
videoframerate="25"
videoaspectratio="16:9" />
</contentSet>
</newsItem>9.3.1. Part Metadata
NewsML-G2 Items can have many <partMeta> wrappers, each expressing properties for an identifiably separate part of the content; in this example each of the shots, or segments, which make up the video. The properties for each segment include:
-
an ID for the segment, and a sequence number
-
a keyframe, or icon that may help to visually identify the content of the segment
-
the start and end positions of the segment within the content
It is also possible to assert any Administrative or Descriptive Metadata for each <partMeta> element, if required.
The id and sequence number for the shot are expressed as attributes of <partMeta> and the <partMeta> element is repeated for each video segment. Below is a complete example of a single segment:
<partMeta partid="Part1_ID" seq="1">
<icon href=" http://www.example.com/video/Keyframes/407624.jpeg"/>
<timeDelim start="0" end="446" timeunit="timeunit:editUnit"/>
<language tag="en" role="lrol:voiceOver" />
<description>Vicco von Bülow entering exhibition</description>
</partMeta>These elements of video <partMeta> are discussed below.
Add keyframe using <icon>
A keyframe for the video segment is expressed as the child element <icon> with @href pointing to the keyframe image as a resource on the Web:
<icon href="http://www.example.com/video/Keyframes/407624.jpeg"/>Timing metadata
The <timeDelim> property indicates the start and end positions of this segment within the video, and the units being used to express these values, as shown for example:
<timeDelim start="0" end="446" timeunit="timeunit:editUnit"/>This @timeunit uses a QCode to indicate that @start and @end are expressed in Edit Units, the smallest editable units of the content; in the case of video this is frames. Edit Unit is the assumed default value of @timeunit if this attribute is not present. It is one of the values of the IPTC Time Unit NewsCodes (recommended Scheme Alias "timeunit"), which is used in this example.
The values in the scheme are:
-
editUnit: the time delimiter is expressed in smallest editable unit of the content: frames (video) or samples (audio) and requires the frame rate or sampling rate to be known. This must be defined by the referenced rendition of the content.
-
timeCode: the format of the timestamp is hh:mm:ss:ff (ff for frames).
-
timeCodeDropFrame: the format of the timestamp is hh:mm:ss:ff (ff for frames).
-
normalPlayTime: the format of the timestamp is hh:mm:ss.sss (milliseconds).
-
seconds.
-
milliseconds.
| In the example @start and @end are expressed as integers, but their datatype is XML String, because start and end can be expressed as integers, time values, or SMPTE time codes. |
The value of @start expresses the non-inclusive start of the segment of the timeline; the value of @end expresses the inclusive end of the segment of the timeline. For example, a 30 second segment at 25 frames per second may be expressed using Edit Unit as:
<timeDelim start="0" end="750" timeunit="timeunit:editUnit"/>A following 30 second segment would start at "750" and end at "1500".
The same segment would be expressed using milliseconds as:
<timeDelim start="0" end="30000" timeunit="timeunit:milliseconds"/>and the following 30 second segment would start at "30000" and end at "60000"
|
When processing a time delimiter expressed as frames, use the the following example as a guide: <timeDelim start="3" end="4" timeunit="timeunit:editUnit"/>Q: Does it mean that two frames are included, or just one frame, and which one(s) exactly? A: one frame, the fourth. |
When specifying the start and end points of a segment of video, be aware that these are unlikely to be frame-accurate for the same segment rendered in different technical formats; if frame-rates are different, the viewer is likely to see a different result for each rendition.
It is therefore highly recommended when expressing time delimiters using frames or timecodes that @renditionref is used to specify separate time delimiters corresponding to alternative renditions of the same shot, as follows:
<partMeta....>
<!-- 10 seconds in frames at 25 fps = 250 frames -->
<timeDelim renditionref="_vidrnd:avi25" start="0" end="250" +
timeunit="timeunit:editUnit"/>
<!-- 10 seconds in frames at 30 fps = 300 frames -->
<timeDelim renditionref="ex-vidrnd:avi30" start="0" end="300" +
timeunit="timeunit:editUnit"/>
</partMeta>Each @renditionref identifies a corresponding @rendition in <remoteContent>:
<contentSet>
<remoteContent contenttype="..."
href="..."
rendition="ex-vidrnd:avi25"
... />
<remoteContent contenttype="..."
href="..."
rendition="ex-vidrnd:avi30"
... />
</contentSet>Description and Language
The example also indicates the language being used in the shot, and the context in which it is used. In this case, @role uses a QCode from a proprietary EBU scheme to indicate that the soundtrack of the shot is a voiceover in English.
<language tag="en" role="ex-langusecode:VoiceOver" />Implementers may also use the IPTC Language Role NewsCodes (recommended Scheme Alias "lrol") for this purpose.
Using <description>, we can also indicate what the viewer can expect to see in this segment:
<description>Vicco von Bülow entering exhibition</description>9.3.2. Video Content
The <contentSet wrapper contains a single rendition of the video inside the <remoteContent> element. Note that the video frame rate is included, as this is required to calculate points in the timeline when using time delimiters based on Edit Unit:
<contentSet>
<remoteContent href="http://www.example.com/video/407624.avi"
format="frmt:MPEG"
duration="111" durationunit="timeunit:seconds"
videocodec="vcdc:c155"
videoframerate="25"
videoaspectratio="16:9" />
</contentSet>9.4. Further Resources
The IPTC Video Metadata Hub Recommendation (VMHub) was launched in October 2016 as a comprehensive solution to the exchange of video metadata between multiple existing standards. Visit the IPTC website www.iptc.org and follow the links to Video Metadata Hub.
10. Packages
| We recommend reading the chapter on NewsML-G2 Basics before this guide to implementing News Packages. |
10.1. Introduction
The ability to package together items of news content is important to news organisations and customers. Using packages, different facets of the coverage of a news story can be viewed in a named relationship, such as "Main Article", "Sidebar", Background". Another frequent application of packages is to aggregate content for news products, for example "Top Ten" news packages such as that illustrated below.
| A description of how to create this type of package with ordered components can be found further on in this document. |
Packages can range from simple collections on a common theme, to rich hierarchical structures.
NewsML-G2 is flexible in allowing a provider to package content that has already been published, or a package may be sent together with all of its content resources in a single News Message. See the Guidelines section on News Messages.
10.2. Packages and Links: the difference
The NewsML-G2 <link> property is a useful way to indicate optional supplementary resources that may be retrieved by the end-user when processing or consuming a NewsML-G2 Item. Links should not be used as a lightweight method of packaging news; a NewsML-G2 processor would not be able to distinguish between News Items with some optional resources, and News Items that are intended to be pseudo-packages using links. It is also a basic NewsML-G2 rule that a News Item only conveys one piece of content.
By contrast, Packages:
-
Express structure, allowing news to be packaged as a list, or as a named hierarchy of content resources.
-
Have a mode property that enables the expression of a relationship between the components of a package group.
10.3. Package Structure
A simple Package has a structure as shown in the example below. The top level for content of a Package Item is one and only one <groupSet> element, followed by at least one <group> structure containing one or more <ItemRef> references to content. The <group> structure may also be repeated, but this example has only one. The diagram below shows a skeleton of the XML elements in a simple package and a visualisation of the relationship that this structure creates:
The following NewsML-G2 document illustrates the package structure above.
(All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-staffjobs, ex-mystaff, ex-svc and ex-group.)
<?xml version="1.0" encoding="UTF-8"?>
<packageItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
guid="tag:example.com,2008:UK-NEWS-TOPTEN:UK20081220098658" version="15">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef
href="http:/www.example.com/customer/cv/catalog4customers-1.xml" />
<itemMeta>
<itemClass qcode="ninat:composite" />
<provider qcode="nprov:AcmeNews" />
<versionCreated>2022-11-17T12:30:00Z</versionCreated>
<firstCreated>2008-12-20T12:25:35Z</firstCreated>
<pubStatus qcode="stat:usable" />
<profile versioninfo="1.0.0.2">simple_text_with_picture.xsl</profile>
<service qcode="ex-svc:uktop">
<name>Top UK News stories hourly</name>
</service>
<title>UK-TOPNEWS</title>
<edNote>Updates the previous version</edNote>
<signal qcode="sig:update" />
</itemMeta>
<contentMeta>
<contributor jobtitle="ex-staffjobs:cpe" qcode="ex-mystaff:MDancer">
<name>Maurice Dancer</name>
<name>Chief Packaging Editor</name>
<definition validto="2022--11-17T17:30:00Z">
Duty Packaging Editor
</definition>
<note validto="2022--11-17T17:30:00Z">
Available on +44 207 345 4567 until 17:30 GMT today
</note>
</contributor>
<headline xml:lang="en">UK</headline>
</contentMeta>
<groupSet root="G1">
<group id="G1" role="ex-group:main">
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial-item-A"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="2345">
<itemClass qcode="ninat:text" />
<provider qcode="ex-nprov:AcmeNews"/>
<pubStatus qcode="stat:usable"/>
<title>Obama annonce son équipe</title>
<description role="drol:summary">Le rachat il y a deux ans de la
propriété par Alan Gerry, magnat local de la télévision câblée, a
permis l'investissement des 100 millions de dollars qui étaient
nécessaires pour le musée et ses annexes, et vise à favoriser le
développement touristique d'une région frappée par le chômage.
</description>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-B"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="300039">
<itemClass qcode="ninat:picture" />
<provider qcode="ex-nprov:AcmeNews"/>
<pubStatus qcode="stat:usable"/>
<title>Barack Obama arrive à Washington</title>
<description role="drol:caption">Si nous avons aujourd'hui un
afro-américain et une femme dans la course à la présidence.
</description>
</itemRef>
</group>
</groupSet>
</packageItem>10.4. Document structure
The building blocks of the Package Item are the <packageItem> root element, with additional wrapping elements for metadata about the Package (itemMeta), metadata about the content (contentMeta) and the package content (groupSet). The top level (root) element <packageItem> attributes are:
<packageItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="tag:example.com,2008:UK-NEWS-TOPTEN:UK20081220098658"
version="15">
standard="NewsML-G2"
standardversion="2.31"
conformance="power"This is followed by Catalog information:
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef
href="http:/www.example.com/customer/cv/catalog4customers-1.xml" />10.5. Item Metadata
The <itemMeta> wrapper contains properties that are aids to processing the package contents.
10.5.1. Profile
The <profile> element allows a provider to name a pre-arranged template or transformation stylesheet that can be used to process the package, for example "text and picture" could be the name of a template; "textpicture.xsl" would be an xsl stylesheet. The @versioninfo of a <profile> enables the template or stylesheet to be versioned:
<profile versioninfo="1.0.0.2">simple_text_with_picture.xsl</profile>10.5.2. Item Metadata in full
<itemMeta>
<itemClass qcode="ninat:composite" />
<provider qcode="nprov:AcmeNews" />
<versionCreated>2022-11-07T12:30:00Z</versionCreated>
<firstCreated>2008-12-20T12:25:35Z</firstCreated>
<pubStatus qcode="stat:usable" />
<profile versioninfo="1.0.0.2">simple_text_with_picture.xsl</profile>
<service qcode="ex-svc:uktop">
<name>Top UK News stories hourly</name>
</service>
<title>UK-TOPNEWS</title>
<edNote>Updates the previous version</edNote>
<signal qcode="sig:update" />
</itemMeta>10.6. Content Metadata
The <contentMeta> wrapper in this example contains extended metadata about the person who compiled the package, including hours of duty and contact telephone number.
<contentMeta>
<contributor jobtitle="ex-staffjobs:cpe" qcode="ex-mystaff:MDancer">
<name>Maurice Dancer</name>
<name>Chief Packaging Editor</name>
<definition validto="2022-11-17T17:30:00Z">Duty Packaging Editor</definition>
<note validto="2022-11-17T17:30:00Z">Available on +44 207 345 4567 until 17:30 GMT today</note>
</contributor>
<headline xml:lang="en">UK</headline>
</contentMeta>10.7. Group Set
The <groupSet> has a mandatory root attribute that references the primary child <group> element. The primary <group> element must identify itself using an @id that matches the @root of <groupSet>.
<groupSet root="G1">10.7.1. Group
Although the id attribute is optional, in practice one must be provided to match the mandatory root attribute of the <groupSet>, even if there is only one <group>. If there is more than one <group> element, one and only one can be identified as the root group.
Group elements must also contain a role attribute to declare its role within the package structure. The role is a QCode, but a Scheme of Roles may typically contain values representing "main", "sidebar" or other editorial terms that express how the content is intended to be used in the package.
<group id="G1" role="ex-group:main">10.7.2. Item Reference
The <itemRef> element identifies an Item or a Web resource using @href and/or @residref. The IPTC recommends that Package Items should reference NewsML-G2 Items if they are available (typically News Items) rather than other types of resource, such as "raw" news objects. Referring to other kinds of Web-accessible resource is allowed and is a legitimate use-case, however it has some disadvantages. Resources referred to in this way cannot be managed or versioned: if one of the resources is changed, the entire package may need to be re-compiled and sent, whereas a reference to a managed object such as a <newsItem> may refer to the latest (or a specific) version.
The example versions the referenced Items using @version, and gives processing or usage hints using @contenttype and @size. The @contenttype uses the registered IANA Media Type for a NewsML-G2 News Item:
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial-item-A"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="2345">The Item Reference includes properties from the referenced Item that have been extracted as an aid to processing:
<itemClass qcode="ninat:text" />
<provider qcode="nprov:AcmeNews"/>
<pubStatus qcode="stat:usable"/>
<title>Obama annonce son équipe</title>
<description role="drol:summary">Le rachat il y a deux ans de la
propriété par Alan Gerry, magnat local de la télévision câblée, a
permis l'investissement des 100 millions de dollars qui étaient
nécessaires pour le musée et ses annexes, et vise à favoriser le
développement touristique d'une région frappée par le chômage.
</description>
</itemRef>10.8. Hierarchical Package Structure
Hierarchies of Groups and Item References can be created by adding multiple Groups to Packages and using <groupRef>, to reference other Groups by @idref, as illustrated by the following diagram:
The code listing below shows how such a hierarchical package would be fully expressed in XML in a NewsML-G2 Group Set:
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for ex-group.
<groupSet root="G1">
<group id="G1" role="ex-group:main">
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-A"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="2345">
<itemClass qcode="ninat:text" />
<title>Obama annonce son équipe</title>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-B"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="300039">
<itemClass qcode="ninat:picture" />
<title>Barack Obama arrive à Washington</title>
</itemRef>
<groupRef idref="G2" />
</group>
<group id="G2" role="ex-group:sidebar">
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-C"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="1503">
<itemClass qcode="ninat:text" />
<title>Clinton reprend son rôle de chef de la santé</title>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-D"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="350280">
<itemClass qcode="ninat:picture" />
<title>Hillary Clinton à une rassemblement à New York</title>
</itemRef>
</group>
</groupSet>In the example, the "root" group is identified as the group with id="G1". This group has a role of "main" and consists of a text story and a picture of Barack Obama. The group with id="G2" has the role of "sidebar" and contains a text and picture of Hillary Clinton. It is referenced by a <groupRef> in Group G1.
10.9. List Type Package Structure
The @mode indicates the relationship between components of a group using one of three values from the IPTC Package Group Mode NewsCodes (recommended Scheme Alias "pgrmod"):
-
pgrmod:bag – an unordered collection of components, for example different components of a web news page with no special order, as in the example below. This is the default @mode.
-
pgrmod:seq – denotes a sequential package group set in descending order, for example a "Top Ten" list: each sub-group would provide references to a text article and a related picture.
-
pgrmod:alt – an unordered collection. Each sub-group is an alternative to its peer groups in the set, for example coverage of a news event supplied in different languages.
The diagram above shows a package containing two Items in the root group, and a group reference to a "group of groups" with package mode set to "alt" indicating that the child groups contain alternative content. The example uses groups of associated video suitable for different Android device screen sizes as indicated by the @role of each group.
The code overview shows the root group referencing the two Items and the <groupRef> element referencing the group with @id "G2". Group G2 has its package mode set to "alt" and its components are references to alternate groups G3, G4 and G5, which reference videos at the required rendition for each screen type.
The right-hand image in the diagram is a visual representation of the relationship expressed through this package structure.
Note the <group> that has its Mode set to "alt" – not the "main" group but the second group with @id "G2". The components of this group are alternatives: each references a group containing the video content. The code example below shows how this relationship is fully expressed in NewsML-G2:
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for ex-group.
<groupSet root="G1">
<group id="G1" role="ex-group:main">
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-A"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="2345">
<itemClass qcode="ninat:text" />
<title>Obama annonce son équipe</title>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-B"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="1503">
<itemClass qcode="ninat:text" />
<title>Clinton reprend son rôle de chef de la santé</title>
</itemRef>
<groupRef idref="G2" />
</group>
<group id="G2" role="ex-group:video" mode="pgrmod:alt">
<groupRef idref="G3" />
<groupRef idref="G4" />
<groupRef idref="G5" />
</group>
<group id="G3" role="ex-group:mdpi">
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-C"
contenttype="video/mp4" width="480" height="320">
<itemClass qcode="ninat:video" />
<title>Barack Obama arrive à Washington</title>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-D"
contenttype="video/mp4" width="480" height="320">
<itemClass qcode="ninat:video" />
<title>Hillary Clinton à une rassemblement à New York</title>
</itemRef>
</group>
<group id="G4" role="ex-group:hdpi">
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-E"
contenttype="video/mp4" width="720" height="480">
<itemClass qcode="ninat:video" />
<title>Barack Obama arrive à Washington</title>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-F"
contenttype="video/mp4" width="720" height="480">
<itemClass qcode="ninat:video" />
<title>Hillary Clinton à une rassemblement à New York</title>
</itemRef>
</group>
<group id="G5" role="ex-group:xhdpi">
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-G"
contenttype="video/mp4" width="960" height="640">
<itemClass qcode="ninat:video" />
<title>Barack Obama arrive à Washington</title>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-H"
contenttype="video/mp4" width="960" height="640">
<itemClass qcode="ninat:video" />
<title>Hillary Clinton à une rassemblement à New York</title>
</itemRef>
</group>
</groupSet>10.10. A Sequential "Top Ten" Package
The screenshot at the start of this Chapter shows a "Top Ten" list of news items in order of importance. The package mode of "seq" indicates that the components are in descending order and a code skeleton and visual representation of the package structure is shown in the diagram below:
Note how the <group> sets the Mode for its components, in this case the component group references of the "main" group are sequentially ordered. The relationship is fully-expressed in XML in NewsML-G2 as shown below:
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for ex-group.
<groupSet root="G1">
<group id="G1" role="ex-group:main" mode="pgrmod:seq">
<groupRef idref="G2" />
<groupRef idref="G3" />
<groupRef idref="G4" />
<groupRef idref="G5" />
<groupRef idref="G6" />
<groupRef idref="G7" />
<groupRef idref="G8" />
<groupRef idref="G9" />
<groupRef idref="G10" />
<groupRef idref="G11" />
</group>
<group id="G2" role="ex-group:top" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial-item-A"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="3452">
<itemClass qcode="ninat:text" />
<provider qcode="ex-nprov:AcmeNews"/>
<pubStatus qcode="stat:usable"/>
<title>Bank cuts interest rates to record low</title>
<description role="drol:summary">London (Reuters) - The Bank of England cut
interest rates by half a percentage point on Thursday to a record low of
1.5 percent and economists expect it to cut again in February as it
battles to prevent Britain from falling into a deep slump.
</description>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-B"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="230003">
<itemClass qcode="ninat:picture" />
<provider qcode="ex-nprov:AcmeNews "/>
<pubStatus qcode="stat:usable"/>
<title>BoE Rate Decision</title>
</itemRef>
</group>
<group id="G3" role="ex-group:two" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial-item-C"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="2345">
<itemClass qcode="ninat:text" />
<provider qcode="ex-nprov:AcmeNews"/>
<pubStatus qcode="stat:usable"/>
<title>Government denies it will print more cash</title>
<description role="drol:summary">London (Reuters) – Chancellor
Alistair Darling dismissed reports on Thursday that the government was about
to boost the money supply to ease the impact of recession.
</description>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-D"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="24065">
<itemClass qcode="ninat:picture" />
<provider qcode="ex-nprov:AcmeNews "/>
<pubStatus qcode="stat:usable"/>
<title>Sterling notes and coin</title>
</itemRef>
</group>
<group id="G4" role="ex-group:three" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial-item-E"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="2345">
<itemClass qcode="ninat:text" />
<provider qcode="ex-nprov:AcmeNews"/>
<pubStatus qcode="stat:usable"/>
<title>Rugby's Mike Tindall banned for drink-driving</title>
<description role="drol:summary">London (Reuters) - England rugby player Mike
Tindall was banned from driving for three years and fined £500 on Thursday
for his second drink-drive offence.
</description>
</itemRef>
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-F"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="25346">
<itemClass qcode="ninat:picture" />
<provider qcode="ex-nprov:AcmeNews "/>
<pubStatus qcode="stat:usable"/>
<title>Mike Tindall in rugby action for England</title>
</itemRef>
</group>
<group id="G5" role="ex-group:four" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-G"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="3654">
<itemClass qcode="ninat:text" />
<title>Crunch forces employees to work unpaid overtime</title>
</itemRef>
</group>
<group id="G6" role="ex-group:five" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-H"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="5123">
<itemClass qcode="ninat:text" />
<title>Government warns of tax fraudsters</title>
</itemRef>
</group>
<group id="G7" role="ex-group:six" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-I"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="4323">
<itemClass qcode="ninat:text" />
<title>Nissan to cut 1,200 jobs at Sunderland plant</title>
</itemRef>
</group>
<group id="G8" role="ex-group:seven" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-J"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="3122">
<itemClass qcode="ninat:text" />
<title>Sainsbury sales tops forecast</title>
</itemRef>
</group>
<group id="G9" role="ex-group:eight" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-K"
contenttype="video/mp4-480x320"
size="322443">
<itemClass qcode="ninat:video" />
<title>Cause of wind turbine damage unknown</title>
</itemRef>
</group>
<group id="G10" role="ex-group:nine" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-L"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="4123">
<itemClass qcode="ninat:text" />
<title>Muslims warn Gaza crisis could provoke extremism</title>
</itemRef>
</group>
<group id="G11" role="ex-group:ten" >
<itemRef residref="urn:newsml:iptc.org:20081007:tutorial—item-M"
contenttype="application/vnd.iptc.g2.newsitem+xml"
size="8192">
<itemClass qcode="ninat:text" />
<title>Banks hiring young Britons to prepare for upturn</title>
</itemRef>
</group>
</groupSet>10.11. Package Processing Considerations
10.11.1. Other NewsML-G2 Items
In the above examples, the referenced resources in the package have been News Items, but <itemRef> may also refer to other Items, such as Package Items. The following example of <itemRef> shows how a Package Item can be used as part of a Package Item. This type of "Super Package" could be used to send a "Top Ten" package (a themed list of news) where each referenced item is also a package consisting of references to the text, picture and video coverage of each news story.
The advantage of using this "package of packages" approach is that it promotes more efficient re-use of content. Once created, any of the "sub-packages" can be easily referenced by more than one "super-package": a package about a given story could be used by both "Top News This Hour" and by "Today’s Top News". If the individual News Items that make up a sub-package were to be referenced directly, these references have to be assembled each time the story is used, either by software or a journalist, which would be less efficient.
As these sub-packages are managed objects, we use @residref to identify and locate the referenced items. Each referenced item may be a Package Item, shown by the Item Class of "composite" and the Content Type of "application/vnd.iptc.g2.packageitem+xml". Each <itemRef> would then resemble the following:
<itemRef residref="tag:afp.com,2008:TX-PAR:20080529:JYC99"
contenttype="application/vnd.iptc.g2.packageitem+xml"
size="28047">
<itemClass qcode="ninat:composite" />
<provider qcode="nprov:AFP"/>
<pubStatus qcode="stat:usable"/>
<title>Tiger Woods cherche son retour</title>
<description role="drol:summary"> Tiger Woods lorem ipsum dolor sit amet,
consectetur adipiscing elit. Etiam feugiat. Pellentesque ut enim eget
eros volutpat consectetur. Quisque sollicitudin, tortor ut dapibus
porttitor, augue velit vulputate eros, in tempus orci nunc vitae nunc.
Nam et lacus ut leo convallis posuere. Nullam risus.
</description>
</itemRef>10.11.2. Facilitating the Exchange of Packages
There needs to be some consideration of how such a "Super Package" should be processed by the receiver. The power and flexibility inherent in NewsML-G2 Packages could lead to confusion and processing complexity unless provider and receiver agree on a method for specifying the structure of packages and signalling this to the receiving application. Processing hints such as the <profile> property (described above) intended to help resolve this issue.
In the example below, we maintain flexibility and inter-operability with potential partner organisations by defining any number of standard package "templates" – termed Profiles – for the Package, among other processing hints. Partners would agree in advance on the Profiles and rules for processing them. All that the provider then needs to do is place the pre-arranged Profile name, or the name of a transformation script, in the <profile> property.
Package profiles could be represented as diagrams like those shown below:
In this example, the Profile Name is intended to be a signal to the processor that references to each member of the Top Ten list are placed in their own group, and that we create our Top Ten list in the "root" group of the Package Item as an ordered list of <groupRef> elements. (as in the "Top Ten" list profile shown in the above diagram)
The properties in <itemMeta> that can be used to provide information on processing are:
<generator>, a versioned string denoting the name of the process or service that created the package:
<generator versioninfo="3.0">MyNews Top Ten Packager</generator><profile>, as discussed, sets the template or transformation stylesheet of the package
<profile versioninfo="1.0.0.2">ranked_idref_list</profile><signal> is a flexible type property (may have a @qcode, @uri, or @literal value) that instructs the receiver to perform any required actions upon receiving the Item. An <edNote> may contain natural-language instructions, if necessary, and a <link> property denotes the previous version of the package.
<signal qcode="sig:update" />
<edNote>Updates the previous package</edNote>
<link
rel="irel:previousVersion"
residref="tag:example.com,2008:UK-NEWS-TOPTEN:UK20081220098658"
version="1"
/>11. Concepts and Concept Items
11.1. Introduction
Concepts in NewsML-G2 are a method of describing real-world entities, such as people, events and organisations, and also to describe thoughts or ideas: abstract notions such as subject classifications, facial expressions. Using concepts, we can classify news, and the entities and ideas found in news, to make the content more accessible and relevant to people’s particular information needs.
Content originators who make up the IPTC membership constantly strive to increase the value proposition of their products. The need to extract and properly express the meaning of news using concepts is a major reason for moving to NewsML-G2.
Clear and unambiguously-defined concepts enable receivers of information to categorize and otherwise handle news more effectively, routing content and archiving it accurately and quickly using automated processes.
NewsML-G2 Concepts are powerful because they bring meaning to news content in a way that can be understood by humans and processed by machines. The concept model aligns with work being done at the W3C and elsewhere to realize the Semantic Web.
Concepts are conveyed individually in Concept Items, or (more commonly) are collected as groups of Concepts in Knowledge Items. These can be collections with a common purpose, such as Controlled Vocabularies.
This Chapter gives details of the Concept element that is common to both types of Item, and also describes the Concept Item. The Chapter Knowledge Items, succeeding this one, describes Knowledge Items in detail.
Concepts are also used to convey event information, which is described in detail in Events in NewsML-G2.
11.2. What is a Concept?
A NewsML-G2 Concept is anything about which we can be express knowledge in some formal way, and which may also have a named relationship with other concepts:
-
"Mario Draghi" is a concept about which, or whom, we can express knowledge, for example, date of birth (September 3, 1947), job title (President of the European Central Bank).
-
"The European Central Bank" is a concept. It has an address, a telephone number, and other inherent characteristics of an organisation.
-
We can express a named relationship: "Mario Draghi" is a member of "The European Central Bank" NewsML-G2 concept expressions thus conform with an RDF triple of subject, predicate and object
Concepts are either global in scope, when they are identified by a URI using a @uri, optionally taking the format of a QCode attribute @qcode, or their scope is local to the containing document when identified by a string value using @literal (where permitted) The use of @literal identifier is a special case that matches the identifier of an <assert> in the NewsML-G2 document that contains a localised concept structure. See 20.2 The Assert Wrapper for more details. This Chapter describes Concepts identified by QCodes and URIs.
11.3. Creating Concepts – the <concept> element
The <concept> element contains the properties that express the concept in detail and identify it so that it can be used and re-used:
11.3.1. Concept ID <conceptId>
A concept MUST contain a <conceptId> which takes the form of a QCode (@qcode) attribute. Optionally the full URI may be added using a @uri. If the URI resolved from the @qcode is not the same as the @uri value, then the URI resolved from the @qcode takes precedence. Optionally, this can be refined using date-time for @created and @retired.
<concept>
<conceptId created="2009-01-01T12:00:00Z" qcode="ex-foo:bar" />
...
</concept>When a concept is created the @created attribute SHOULD be defined for the <conceptId>; there is no @created attribute at the <concept> level, as its creation is coincident with the mandatory <conceptId>.
Any change to a <concept>, including to its descendant properties, should be reflected in the @modified attribute of the property being updated, and in the @modified attribute of the <concept>.
Even though <conceptId> supports the @modified attribute, the <conceptId> should NOT be modified; if there is the need for a <conceptId> to be updated, the existing concept should be retired, and a new <conceptId> created.
When a concept is retired by use of the @retired attribute of <conceptId>, the authority behind the concept is indicating that it is no longer actively using this concept (for example it may have been merged with another concept), but resources that were created before the change must continue to be able to resolve the concept.
11.3.2. Concept Name <name>
A concept MUST contain at least one <name>, a natural language name for the concept, with optional attributes of @xml:lang and @dir (text direction):
<concept>
<conceptId qcode="ex-foo:bar" />
<name>Mario Draghi</name>
</concept>Concepts are designed to be useable in multiple languages:
<concept>
<conceptId created="2000-10-30T12:00:00+00:00" qcode="medtop:01000000" />
<type qcode="cpnat:abstract" />
<name xml:lang="en-GB">arts, culture and entertainment</name>
<name xml:lang="de">Kultur, Kunst, Unterhaltung</name>
<name xml:lang="fr">Arts, culture, et spectacles</name>
<name xml:lang="es">arte, cultura y espectáculos</name>
<name xml:lang="ja-JP">文化</name>
<name xml:lang="it">Arte, cultura, intrattenimento</name>
</concept>11.3.3. Concept Type
The optional <type> element expresses the "nature of the Concept", for example, using the recommended IPTC Concept Nature NewsCodes to identify this concept is of type "abstract". We can also use <related> to extend this notion into further characteristics of the concept (see Relationships between Concepts, below).
<type> demonstrates the use of the subject, predicate, object triple of RDF to express a named relationship with another concept; <type> can only express one kind of relationship – "is a(n)". It is used to express the most obvious, or primary, inherent characteristic of a concept, as in:
arts, culture and entertainment (Subject) is a(n) (Predicate)
abstract concept (Object):
<type qcode="cpnat:abstract" />The current types agreed by the IPTC and contained in the "concept nature" CV at http://cv.iptc.org/newscodes/cpnature/ are:
-
abstract concept (cpnat:abstract),
-
person (cpnat:person),
-
organisation (cpnat:organisation),
-
geopolitical area (cpnat:geoArea),
-
point of interest (cpnat:poi),
-
object (cpnat:object)
-
event (cpnat:event).
11.3.4. Concept Definition
The optional <definition> element allows more extensive natural language information with some mark-up, if required. Block type elements may use an optional @role QCode to differentiate repeating Definition statements such as "summary" and "long":
<definition xml:lang="en-GB" role="ex-definitionrole:short">
Matters pertaining to the advancement and refinement of the human mind,
of interests, skills, tastes and emotions
</definition>Note that although much of this information could be, and may be, duplicated in machine-readable XML, it is still useful to carry some core information in human-readable form.
11.4. Conveying Concepts: the Concept Item structure
A Concept Item conveys knowledge about a single concept, whether a real-world entity such as a person, or an abstract concept such as a subject. It shares the basic structure of all NewsML-G2 Items and therefore uses the same methods for identification and versioning.
Item Metadata is mandatory and contains the mandatory properties for Item Class, Provider and Version Created (note that Publication Status is optional but the Item’s publication status must be assumed to be the default "usable" if the property is absent).
Content Metadata is optional and is not included in this example:
Note the <itemClass> property for a Concept Item must use the IPTC Concept Item Nature NewsCodes with a recommended Scheme Alias of "cinat" and denotes this Item conveys a NewsML-G2 Concept.
11.4.1. Completed Concept Item
This example is a Concept Item that describes one of the IPTC Media Topic NewsCodes:
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies.
<?xml version="1.0" encoding="UTF-8"?>
<conceptItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20080229:ncdci-subjectcode"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<rightsInfo>
<copyrightHolder>
<name>IPTC International Press Telecommunications Council, 20 Garrick Street, London WC2E 9BT, UK</name>
</copyrightHolder>
<copyrightNotice>Copyright 2022-23, IPTC, www.iptc.org, All
Rights Reserved</copyrightNotice>
</rightsInfo>
<itemMeta>
<itemClass qcode="cinat:concept" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-11-07T12:35:21+01:00</versionCreated>
<firstCreated>2008-02-29T12:00:00+00:00</firstCreated>
<pubStatus qcode="stat:usable" />
<title xml:lang="en">Concept Item delivering a concept requested from the IPTC Media Topic NewsCodes</title>
</itemMeta>
<concept>
<conceptId created="2000-10-30T12:00:00+00:00" qcode="medtop:01000000" />
<type qcode="cpnat:abstract" />
<name xml:lang="en-GB">arts, culture and entertainment</name>
<name xml:lang="de">Kultur, Kunst, Unterhaltung</name>
<name xml:lang="fr">Arts, culture, et spectacles</name>
<name xml:lang="es">arte, cultura y espectáculos</name>
<name xml:lang="ja-JP">文化</name>
<name xml:lang="it">Arte, cultura, intrattenimento</name>
<definition xml:lang="en-GB">Matters pertaining to the advancement and refinement
of the human mind, of interests, skills, tastes and emotions</definition>
<definition xml:lang="de">Sachverhalte, die die Veränderung und Weiterentwicklung
des menschlichen Geistes, der Interessen, des Geschmacks, der Fähigkeiten und
der Gefühle betreffen.</definition>
<definition xml:lang="fr">Tout ce qui est relatif à la création d'œuvres, au
développement des facultés intellectuelles, et à leur représentation
publique</definition>
<definition xml:lang="es">Asuntos pertinentes al avance y refinamiento de la mente
humana, intereses, habilidades, gustos y emociones.</definition>
<definition xml:lang="ja-JP">
人間の精神や興味、技能、嗜好、感情の進歩や洗練に関係する事柄</definition>
<definition xml:lang="it">Creazione e rappresentazione dell'opera d'arte, gli
Interessi intellettuali, il gusto e le emozioni umane</definition>
<note xml:lang="en-GB">
This is a top-level concept from the IPTC Media Topic NewsCodes
</note>
</concept>
</conceptItem>11.5. Concepts for real-world entities
For each of the types of named entities agreed by the IPTC: person, organisation, geographical area, point of interest, object and event, there is a specific group of additional properties. The following example is a Concept Item for a person.
11.5.1. Document Structure
The document structure is as previously described, with a root <conceptItem> element and <itemMeta>. The <contentMeta> element is optional and may only contain Administrative metadata properties, such as <contentModified> (not included in the example)
<?xml version="1.0" encoding="UTF-8"?>
<conceptItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:iptc.org:20080229:ncdci-person"
version="1010181123618"
standard="NewsML-G2"
standardversion="2.31"
conformance="power">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml"
/>
<rightsInfo>
<copyrightHolder>
<name>IPTC - International Press Telecommunications Council, 20 Garrick Street, London WC2E 9BT, UK</name>
</copyrightHolder>
<copyrightNotice>Copyright 2008, IPTC, www.iptc.org, All
Rights Reserved</copyrightNotice>
</rightsInfo>
<itemMeta>
<itemClass qcode="cinat:concept" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-11-07T12:38:18Z</versionCreated>
<firstCreated>2008-12-29T11:00:00Z</firstCreated>
<pubStatus qcode="stat:usable" />
<title xml:lang="en">Concept Item describing Mario Draghi</title>
</itemMeta>11.5.2. Top-level concept details
The <concept> wrapper starts with the properties common to all types of concepts:
<concept>
<conceptId created="2009-01-10T12:00:00Z" qcode="ex-people:329465"/>
<type qcode="cpnat:person" />
<name xml:lang="en-GB">Mario Draghi</name>
<definition xml:lang="en-GB" role="ex-definitionrole:biog">
Mario Draghi, born 3 September 1947,
is an Italian banker and economist who succeeded Jean-Claude Trichet as the
President of the European Central Bank on 1 November 2011. He was previously
the governor of the Bank of Italy from January 2006 until October 2011.
In 2014 Forbes nominated Draghi 9th most powerful person in the world.<br />
</definition>
<note xml:lang="en-GB">
Not Mario D’roggia, international powerboat racer
</note>
<related rel="ex-relation:occupation" qcode="ex-jobtypes:puboff" />
<sameAs type="cpnat:person" qcode="ex-pers:567223">
<name>DRAGHI, Mario</name>
</sameAs>
....
</concept>Note the inclusion of Concept Relationship properties: the <related> element indicates that the person who is the subject of the concept "has occupation of" the related concept expressed in by the @qcode "ex-jobtypes:puboff". The <sameAs> element indicates that this concept is the same as AFP’s (note: fictitious) concept expressed by the @qcode "ex-pers:567223".
11.5.3. Person details
The <personDetails> element is a container for additional properties that are specifically designed to convey information about people:
Born <born> and Died <died>
The date of birth and date of death of the person, for example:
<born>1947-09-03</born>The data type is "TruncatedDateTime", which means that the value is a date, with an optional time part. The date value may be truncated from the right to a minimum of YYYY. If used, the time must be present in full, with time zone, and ONLY in the presence of the full date.
<born>1947</born>Affiliation <affiliation>
An affiliation of the person to an organisation.
<affiliation type="ex-orgnat:employer" qcode="ex-org:ECB">
<name>European Central Bank</name>
</affiliation>Note that the @type refers to the type of organisation – not the type of relationship with the person. In the example we use scheme "orgnat" to describe the Nature of the Organisation as a Bank.
Contact Info <contactInfo>
Contact information associated with the person. The <contactInfo> element wraps a structure with the properties outlined below. A "person" concept may have many instances of <contactInfo>, each with @role indicating their purpose, or example work or home. These are controlled values, so a provider may create their own CV of address types if required. The IPTC NewsCodes for the roles of parts of <contactInfo> is http://cv.iptc.org/newscodes/contactinfopartrole/ with a recommended scheme alias of "ciprol" (used in the example below)
Each of the child elements of <contactInfo> may be repeated as often as needed to express different @roles, for example different "office" and "mobile" phone numbers.
| Property Name | Element | Type | Notes |
|---|---|---|---|
Email Address |
<email> |
Electronic Address |
An “Electronic Address” type allows the expression of @role (QCode) to qualify the information, for example: <email role=“addressrole:office”> info@ecb.eu </email> |
Instant Message Address |
<im> |
Electronic Address |
<im role=“imsrvc:reuters”> jc.trichet.ecb.eu@reuters.net </im> |
Phone Number |
<phone> |
Electronic Address |
|
Fax Number |
<fax> |
Electronic Address |
|
Web site |
<web> |
IRI |
<web role=“webrole:corporate”> www.ecb.eu </web> |
Postal Address |
<address> |
Address |
The Address may have a @role to denote the type of address is contains (e.g. work, home) and may be repeated as required to express each address @role. |
Other information |
<note> |
Block |
Any other contact-related information, such as “annual vacation during August” |
For example:
<contactInfo>
<email role="ciprol:office">info@ecb.eu</email>
<im role="ctech:rm">president.ecb.eu@reuters.net</im>
<phone role="ciprol:office">+49 69 13 44 0</phone>
<phone role="ciprol:mobile">+49 69 13 44 60 00</phone>
<web>www.ecb.eu</web>
<address role="ciprol:office">
<!-- see below -->
</address>
</contactInfo>Postal address <address>
The Address Type property may have a @role to indicate its purpose, The following table shows the available child properties. Apart from <line>, which is repeatable, each element may be used once for each <address>
| Property Name | Element | Type | Notes/Example |
|---|---|---|---|
Address Line |
<line> |
Internationalized string |
As many as are needed |
Locality |
<locality> |
Flexible Property |
May be a URI, QCode or Literal value, or no value with a <name> child element |
Area |
<area> |
Flexible Property |
|
Country |
<country> |
Flexible Property |
|
Postal Code |
<postalCode> |
||
World Region |
<worldRegion> |
Flexible Property |
For example:
<address role="ciprol:office">
<line>Postfach 16 03 19</line>
<locality>
<name>Frankfurt am Main</name>
</locality>
<country qcode="iso3166-1a2:DE">
<name xml:lang="en">Germany</name>
</country>
<postalCode>D-60066</postalCode>
<worldRegion qcode="ex-maxmindcc:EU">Europe</worldRegion>
</address>11.5.4. Putting it together
The complete concept listing for this example:
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-definitionrole, ex-imsrvc ex-jobtypes, ex-maxmindcc, ex-orgnat, ex-org, ex-pers and ex-relation.
<?xml version="1.0" encoding="UTF-8"?>
<conceptItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20080229:ncdci-person"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<rightsInfo>
<copyrightHolder>
<name>IPTC - International Press Telecommunications Council, 20 Garrick Street, London WC2E 9BT, UK</name>
</copyrightHolder>
<copyrightNotice>Copyright 2022-23, IPTC, www.iptc.org, All
Rights Reserved</copyrightNotice>
</rightsInfo>
<itemMeta>
<itemClass qcode="cinat:concept" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-11-07T12:38:18Z</versionCreated>
<firstCreated>2008-12-29T11:00:00Z</firstCreated>
<pubStatus qcode="stat:usable" />
<title xml:lang="en">Concept Item describing Mario Draghi</title>
</itemMeta>
<concept>
<conceptId created="2009-01-10T12:00:00Z" qcode="ex-people:329465" />
<type qcode="cpnat:person" />
<name xml:lang="en-GB">Mario Draghi</name>
<definition xml:lang="en-GB" role="ex-definitionrole:biog">
Mario Draghi, born 3 September 1947,
is an Italian banker and economist who succeeded Jean-Claude Trichet as the
President of the European Central Bank on 1 November 2011. He was previously
the governor of the Bank of Italy from January 2006 until October 2011. In 2013
Forbes nominated Draghi 9th most powerful person in the world.<br />
</definition>
<note xml:lang="en-GB" role="ex-nrol:disambiguation">
Not Mario D’roggia, international powerboat racer
</note>
<related rel="ex-relation:occupation" qcode="ex-jobtypes:puboff" />
<sameAs type="cpnat:person" qcode="ex-pers:567223">
<name>DRAGHI, Mario</name>
</sameAs>
<personDetails>
<born>1947-09-03</born>
<affiliation type="ex-orgnat:employer" qcode="ex-org:ECB">
<name>European Central Bank</name>
</affiliation>
<contactInfo>
<email role="ciprol:office">info@ecb.eu</email>
<im role="ex-imsrvc:reuters">president.ecb.eu@reuters.net</im>
<phone role="ciprol:office">+49 69 13 44 0</phone>
<phone role="ciprol:mobile">+49 69 13 44 60 00</phone>
<web>www.ecb.eu</web>
<address role="ciprol:office">
<line>Kaiserstrasse 29</line>
<locality>
<name>Frankfurt am Main</name>
</locality>
<country qcode="iso3166-1a2:DE">
<name xml:lang="en">Germany</name>
</country>
<postalCode>D-60311</postalCode>
</address>
</contactInfo>
</personDetails>
</concept>
</conceptItem>11.6. More real-world entities
11.6.1. Organisation Details <organisationDetails>
A concept of type "organisation" may hold the following additional properties:
Founded <founded> and Dissolved <dissolved>
The date of foundation / dissolution of the organisation, equivalent to born/died for a person, for example
<founded>1998-06-01</founded>Or
<founded>1998</founded>See note on Truncated Date Time Property Type
Location <location>
A place where the organisation is located, expressed as Flexible Property, NOT an address, repeated as many times as needed. For example:
<location type="loctyp:City" qcode="ex-poi:75001">
<name>Paris</name>
</location>Contact Information <contactInfo>
Contact information associated with the organisation, uses the same structure as described in Contact Information.
11.6.2. Geopolitical Area Details <geoAreaDetails>
A "geoArea" concept may have the following additional properties:
Position <position>
This expresses the coordinates of the concept using the following attributes:
| Attribute Name | Attribute | Type | Notes/Example |
|---|---|---|---|
Latitude |
@latitude |
XML Decimal |
The latitude in decimal degrees |
Positive value = north of the Equator |
|||
Negative value = south of the Equator |
|||
Longitude |
@longitude |
XML Decimal |
The longitude in decimal degrees |
Positive value = east of the Greenwich Meridian |
|||
Negative value = west of the Greenwich Meridian |
|||
Altitude |
@altitude |
XML Integer |
The absolute altitude in metres with reference to mean sea level |
GPS Datum |
@gpsdatum |
XML String |
The GPS datum associated with the position measurement, default is WGS84 |
11.6.3. Point of Interest <poiDetails>
A Point of Interest (POI) is a place "on the map" of interest to people, which is not necessarily a geographical feature, for example concert venue, cinema, sports stadium. As such is has different properties to a purely-geographical point. POI may have the additional properties listed below.
Address
The location of the point of interest expressed as a postal address. The <address> element is a wrapper for child elements described in Postal Address In this context, the address is expressly the location of the POI, whereas the <address> wrapper when used as a child of <contactInfo> (see Contact Information) expresses the address of the entity who should be contacted about the POI, which could be an office some distance away.
Position <position>
The coordinates of the location as described in Position
Opening Hours <openHours>
The opening hours of the POI are expressed as a Label type, which is an internationalized string – a natural language expression – extended to include @role if required. Example:
<openHours>9.30am to 5.30pm, closed for lunch from 1pm to
2pm</openHours>Capacity <capacity>
The capacity of the POI is expressed as a Label:
<capacity>10,000 seats</capacity>Contact Information <contactInfo>
Contact information for the POI uses the <contactInfo> structure as described in Contact Information. It expresses who should be contacted regarding the POI. This could be an organisation located miles away from the location of the POI.
Access details <access>
Methods of accessing the POI, including directions. This is a Block type of element, allowing some mark-up and may be repeated as often as needed:
<access role="ex-traveltype:public">
The Jubilee Line is recommended as the quickest route to ExCeL London. At Canning
Town change to the DLR (upstairs on platform 3) for the quick two-stop journey
to Custom House for ExCeL Station.
</access>
<access role="ex-traveltype:road">
When driving to ExCeL London follow signs for Royal Docks, City Airport and ExCeL
There is easy access to the M25, M11, A406 and A13.
</access>Detailed Information <details>
Detailed information about the location of the POI expressed as a Block type:
<details>Room M345, 3rd Floor</details>11.6.4. Object Details <objectDetails>
Objects that may be expressed as a concept include works of art, books, inventions and industrial artefacts. The IPTC provides three properties for Objects as part of NewsML-G2, but as with any of the types of concept discussed, providers are able to extend the standard. Note these are properties of the object described by the Concept, NOT properties of <itemMeta> which apply to the Concept Item conveying the Concept. The standard additional properties of an Object concept are:
Creation Date <created>
The date and, optionally, the time and time zone when the object was created. Non-repeatable.
<created>1994-06-14</created>11.7. Relationships between Concepts
This is a group of four properties, <broader> <narrower> <related> and <sameAs> that enable the creation of particular types of relationship to another concept. For example, our subject was born in Rome. We could create a concept for Rome as follows, with a <broader> property that denotes that the city as part the region of Lazio:
<concept>
<conceptId qcode="ex-urban:roma" />
<type qcode="cpnat:geoArea" />
<definition role="ex-definitionrole:short">
Rome (Italian: Roma) is a city and special commune
(named "Roma Capitale") in Italy. Rome is the capital of Italy and also
homonymous province and of the region of Lazio.<br />
</definition>
<broader type="cpnat:geoArea" qcode="ex-locale:lazio">
<name xml:lang="en">Lazio (region)</name>
</broader>
</concept><narrower> expresses the reverse relationship. A concept for Rhône could have a <narrower> property linking it to Lyon, and a <broader> link to the concept of its parent region, or to the concept of the country, France.
<sameAs> allows the provider to inform the recipient that this concept has an equivalent concept in some other taxonomy. For example, we may know that AFP’s knowledge base of people has an entry for Mario Draghi that can be referenced using the appropriate alias.
<sameAs type="cpnat:person" qcode="ex-AFPpers:567223">
<name>DRAGHI, Mario</name>
</sameAs>The sameAs property also assists inter-operability because it can be used to enable recipients to choose the CV, or standard, they employ.
For example, the document may have a concept for Germany identified by the provider’s QCode "ex-country:de". Some recipients may have standardized on using ISO-3166 Country Codes to classify nationality. The provider can assist recipients to make a direct reference to their preferred scheme using "sameAs":
<sameAs qcode="iso3166-1a2:DE" />
<sameAs qcode="iso3166-1a3:DEU" />
<sameAs qcode="ex-iso3166n:276" /><related> allows the expression of a relationship with another concept that cannot be expressed using <broader>, <narrower>, or <sameAs>. For example, the "European Central Bank" may be "related to" "Mario Draghi" – thus the ECB concept may include:
<related rel="ex-relation:hasPresident" type="cpnat:person" qcode="ex-people:329465">
<name>Mario Draghi</name>
</related>The nature of the relationship is expressed using @rel; the example above indicates that the European Central Bank "has a President" Mario Draghi. This relationship must be part of a CV of relationships, which might include "has a CEO", "has a Finance Director". The IPTC recommends that the <related> property should always contain a @rel.
The property may be extended by adding @rank, a numeric ranking of the current concept amongst other concepts related to the target concept.
For example, if the European Central Bank is the second most important concept related to Mario Draghi, amongst other concepts related to him, we can express this as follows:
<related rank="2" rel="ex-relation:hasPresident" type="cpnat:person" qcode="ex-people:329465">
<name>Mario Draghi</name>
</related>11.7.1. Expressing quantitative values using <related>
The <related> property also allows the expression of quantitative values, for example a share price or a sport score, in addition to the concept relationships described above.
The three attributes of <related> that enable this feature are @value, @valueunit and @valuedatatype. Implementers can type the @value by applying an XML Schema datatype, and optionally to declare the units of the value (e.g. the currency) using @valueunit and @valuedatatype.
For example, to express scores in a sports game where the named team won by 4 goals to 2 and gained 3 points:
<concept xmlns:xs="http://www.w3.org/2001/XMLSchema">
<conceptId qcode="ex-ukprem:WBA" />
<name>West Bromwich Albion</name>
...
<related rel="ex-crel:scoreFor" value="4"
valueunit="ex-valunits:goals"
valuedatatype="xs:nonNegativeInteger" />
<related rel="ex-crel:scoreAgainst" value="2"
valueunit="ex-valunits:goals"
valuedatatype="xs:nonNegativeInteger" />
<related rel="ex-crel:pointsAdded" value="3"
valueunit="ex-valunits:points"
valuedatatype="xs:nonNegativeInteger" />
...
</concept>A further example expresses a recommendation from an analyst in the financial markets where the EUR changes from 39 to 44 (expressed as a value), and the rank changes from Hold to Buy (expressed as a value or QCode):
<concept xmlns:xs="http://www.w3.org/2001/XMLSchema">
...
<related rel="ex-crel:price_new" value="44"
valueunit="iso4217a:EUR"
valuedatatype="xs:decimal" />
<related rel="ex-crel:price_old" value="39"
valueunit="iso4217a:EUR"
valuedatatype="xs:decimal" />
<related rel="ex-crel:rank_old" value="Hold"
valueunit="ex-valunits:trRanks"
valuedatatype="xs:string" />
<related rel="ex-crel:rank_new" value="Buy"
valueunit="ex-valunits:trRanks"
valuedatatype="xs:string" />
<related rel="ex-crel:rank_new" qcode="ex-trRanks:Buy" />
...
</concept>When using <related>: ONLY ONE out of @qcode, @uri, @literal, OR @value MUST be used. (i.e. these properties are mutually exclusive).
The @value has a datatype XML Schema String. If using @value, a @valuedatatype MUST also be used and its datatype must be one of the data types defined by the W3C XML Schema specification. The inclusion of @valueunit is optional, for example if @rel="ex-crel:noOfSiblings" and @value="2" the type of units is obvious.
11.8. Supplementary information about a Concept
Links can be used to enhance the information carried by a NewsML-G2 Concept. For example, a Concept may represent a person in the news; it may also contain some key facts about the person and relationships to other concepts (e.g. membership of an organisation). Links to other resources can also be used to add articles, pictures and other objects to the Concept.
However, the use of <link> as a child of <itemMeta> in a Concept Item would create a problem if a number of Concept Items containing Links were to be aggregated into a Knowledge Item: only the content of the <concept> wrapper would be carried across into the Knowledge Item and the Concept Item Metadata and any Links, would be lost.
To resolve this issue, a <remoteInfo> property may be added to <concept>, with a datatype of Link1Type, matching that of <link>. This enables implementers to provide links to supplementary information inside the <concept> wrapper, and thus into a Knowledge Item:
<concept>
<conceptId created="2009-01-10T12:00:00Z" qcode="ex-people:329465"/>
<type qcode="cpnat:person" />
<name xml:lang="en-GB">Mario Draghi</name>
<definition xml:lang="en-GB" role="ex-definitionrole:biog">
Mario Draghi, born 3 September
1947, is an Italian banker and economist who succeeded Jean-Claude Trichet
as President of the European Central Bank on 1 November 2011.<br />
</definition>
<related rel="ex-relation:occupation" qcode="ex-jobtypes:puboff" />
<remoteInfo "link" start
rel="irel:seeAlso"
contenttype="image/jpeg">
residref="tag:acmenews.com,2008:TX-PAR:20090529:JYC90" // Item ref
<title>ECB official portrait picture of Mario Draghi</title>
</remoteInfo> "link" end
<personDetails>
<born>1942-12-20</born>
....
<contactInfo role="ex-contactrole:official">
....
</contactInfo>
</personDetails>
</concept>Using the rules given in [Hints and Extension Points] when adding properties of the target NewsML-G2 Item, the parent property must be included if it is not from either <contentMeta> or <itemMeta>. For example, a <description> element extracted from <contentMeta> (no parent needed):
<remoteInfo
rel="irel:seeAlso"
contenttype="video/mpeg">
residref="tag:acmenews.com,2008:TX-PAR:20090529:JYC90"
<description>
ECB official video of Mario Draghi working with senior colleagues at the Bank
</description>Contrast with a <description> from <partMeta>, which must be included as the parent element:
<remoteInfo>
<partMeta partid="part1" seq="1"
<description>The first part shows...</description>
</partMeta>
<partMeta partid="part2" seq="2"
<description>The second part shows...</description>
</partMeta>
</remoteInfo>11.8.1. Faceted Concepts
The elements <mainConcept> and <facetConcept> are members of the Flex1ConceptPropType which is currently used by <genre> and <subject>.
This enables faceted concepts to be expressed as a combination of a main concept (which requires a facet) and another concept which provides the facet to the main concept, for example:
<subject>
<mainConcept qcode=”medtop:20001057”>
<name xml:lang="en">alpine skiing</name>
</mainConcept>
<facetConcept qcode=”aspfacetvalue:women”>
<name xml:l-ng="en">women</name>
</facetConcept>
<facetConcept qcode=”aspfacetvalue:slalom-alpineskiing”>
<name xml:lang="en">alpine skiing slalom</name>
</facetConcept>
</subject>Faceted concepts were added to the IPTC Media Topics taxonomy in 2017, hence the requirement to support this in NewsML-G2.
Standard taxonomies of sports facets and values are provided by the IPTC to support interoperability. These are a Sport Facet CV and a Sport Facet Value CV.
11.9. Concepts in Practice
The more common method of exchanging Concepts is as part of a Controlled Vocabulary (otherwise known as Taxonomy, Thesaurus, Dictionary, for example), which are conveyed in NewsML-G2 as a set of concepts in a Knowledge Item. This is discussed in Knowledge Items.
The use of Concepts to convey Event information is discussed in Events in NewsML-G2.
12. Knowledge Items
12.1. Introduction
When news happens, the event rarely takes place in isolation. There will be a series of relationships between the news event and the people, places and organisations that are directly or indirectly involved. Many of these entities will be well-known, and readers of the news may expect to be able to navigate to further information about these entities, or to find other events in which they are involved. This expectation is heavily fostered by people’s familiarity with the Web: they expect to be able to click on the name of, say, a company and see more information about it.
There will also be references to abstract notions such as subject classifications that enable the news event to be searched and sorted according to user preferences.
To fully exploit the value of their services, news organisations need to be able to exchange this supporting information in an industry-standard way that can be processed using standard technology.
As described in the previous chapter Concepts and Concept Items, NewsML-G2 has powerful features for encapsulating this detailed information about entities and notions, but the Concept Item can convey only a single concept, while the Knowledge Item is able to convey many of them, even a full taxonomy.
For example, a profile of, say, Vladimir Putin can be conveyed in a Concept. By including this Concept in a set of similar Concepts profiling world leaders, we can create and exchange a Knowledge Base of political personalities that can be updated and referred to over time.
The level of detail of information that a provider may make available in a Knowledge Item will depend on its business model and relationship with the receiving customer(s). Providers may make variable levels of information available according to subscription since it is clear that the content of their Knowledge Bases is likely to be valuable.
There are also opportunities for third-party providers of specialist information to partner with providers and customers to create value-added knowledge services using a NewsML-G2 infrastructure.
IPTC NewsCodes are controlled vocabularies maintained as Knowledge Items and are available on the IPTC web site at http://www.iptc.org/newscodes/. Choose View NewsCodes and follow instructions for downloading any of the CVs.
12.2. Example: a Knowledge Item for <accessStatus>
One of the available properties for describing a news event is <accessStatus> to provide information about the physical accessibility of the place where an event is due to occur.
The property takes a QCode value:
<conceptId qcode="ex-access:restricted" />As there is no IPTC NewsCodes scheme currently defined for Access Status, any provider wishing to include this information would need to create a Controlled Vocabulary.
This example shows a Knowledge Item which defines a Controlled Vocabulary of Access Status terms. This CV would be available as a Knowledge Item, with names and definitions in English, French and German, as shown below:
| Value | Names | Definitions |
|---|---|---|
easy |
Easy Facile d’accès Der Zugang ist einfach |
Unrestricted access for vehicles and equipment. Loading bays and/or lifts for unimpeded access to all levels Un accès sans restriction pour les véhicules et l’équipement. Les quais de chargement et / ou des ascenseurs pour l’accès sans entrave à tous les niveaux Ungehinderten Zugang für Fahrzeuge und Ausrüstung. Laderampen und / oder Aufzüge für den uneingeschränkten Zugang zu allen Ebenen |
restricted |
Access is Restricted Accès Restreint Der Zugang ist eingeschränkt |
Access for vehicles and equipment possible but restricted. There may be obstacles, height or width restrictions that will impede large or heavy items. Advise checking with the organizers. L’accès des véhicules et de matériel possible, mais limitée. Il y mai être des obstacles, la hauteur ou la largeur des restrictions qui empêchent les grandes ou d’objets lourds. Conseiller à la vérification avec les organisateurs. Zugang für Fahrzeuge und Ausrüstung möglich, aber eingeschränkt. Möglicherweise gibt es Hindernisse, Höhe und Breite, die Beschränkungen behindern große oder schwere Gegenstände. Beraten Sie mit dem Veranstalter in Verbindung |
difficult |
Access is difficult L’accès est difficile Der Zugang ist schwierig |
Access includes stairways with no lift or ramp available. It will not be possible to install bulky or heavy equipment that cannot be safely carried by one person Comprend l’accès aux escaliers ou la rampe sans ascenseur disponible. Il ne sera pas possible d’installer des équipements lourds ou volumineux qui ne peuvent pas être transportés en sécurité par une seule personne Access enthält Treppen ohne Fahrstuhl oder Rampe zur Verfügung. Es wird nicht möglich sein, installieren sperrige oder schwere Geräte, die sich nicht sicher befördert werden von einer Person |
12.3. Structure and Properties
Knowledge Items share a common structure with News Items, Package Items and Concept Items.
| This Chapter assumes that the reader is familiar with the chapter on Concepts and Concept Items. |
12.3.1. The <knowledgeItem> element
The top level element of a Knowledge Item is <knowledgeItem>, which contains id, versioning and catalog information.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<knowledgeItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:iptc.org:20090202:ncdki-accesscode"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />12.3.2. Item Metadata
The <itemMeta> block contains management metadata for the Knowledge Item document. Below is a minimum set of properties.
The Item Class property should use the IPTC "Nature of Concept Item" NewsCodes (scheme alias "cinat"). The appropriate value in the case of sending a CV or taxonomy is "scheme", denoting that this is a full scheme of concepts contained in this Knowledge Item.
<itemMeta>
<itemClass qcode="cinat:scheme" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-11-08T00:00:00Z</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>12.3.3. Content Metadata
The optional <contentMeta> block contains Administrative Metadata and Descriptive Metadata shared by the concepts conveyed by the <conceptSet>.
Administrative Metadata
This example timestamps the content:
<contentMeta>
<contentModified>2009-01-28T13:00:00Z</contentModified>
...More details about informing receivers about changes to Knowledge Item content are contained in Handling Updates to Knowledge Items using @modified
Descriptive Metadata
The descriptive metadata properties <subject> and <description> may be used by Knowledge items, in any order. They are optional and repeatable. This example uses the <description> element:
<description xml:lang="en">
Classification of the ease of gaining physical access to the location of
a news event for the purpose of deploying personnel, vehicles and equipment.
</description>
<description xml:lang="fr">
Classification de la facilité d'obtenir un accès physique à l'emplacement d'un événement pour
le déploiement de personnel, de véhicules et d'équipements.
</description>
<description xml:lang="de">
Klassifikation der physischen Zugriff auf den Standort eines News Termine für Die Zwecke der
Bereitstellung von Personal, Fahrzeugen und Ausrüstungen.
</description>12.3.4. Concept Set
A single <conceptSet> element wraps zero or more <concept> components. The order of the Concepts is not important. Properties of <concept> are optional and described in Concepts and Concept Items.
Each member of the CV requires its own <concept> wrapper with a Concept ID and Name within the Concept Set:
<conceptSet>
<concept>
<conceptId qcode="ex-access:easy" />
<name xml:lang="en">Easy access</name>
...
</concept>
<concept>
<conceptId qcode="ex-access:difficult" />
<name xml:lang="en">Access is difficult</name>
...
</concept>
<concept>
<conceptId qcode="ex-access:restricted" />
<name xml:lang="en">Access is Restricted</name>
...
</concept>
</conceptSet>Each Concept also has a <definition> in three languages that gives further details in natural language, for example the English definition:
<definition xml:lang="en">
Access for vehicles and equipment possible but restricted. There may be
obstacles, height or width restrictions that will impede large or heavy
items. Advise checking with the organisers.
</definition>This completes the first Concept in the <conceptSet>. The two other concepts in the CV are added in a similar fashion.
12.3.5. Scheme Metadata
In NewsML-G2 v 2.17, the <schemeMeta> element was added to enable a Knowledge Item to support similar properties to the <scheme> in a Catalog. It should be noted that <schemeMeta> is used to express metadata about the scheme being conveyed, and should ONLY be used where the Knowledge Item contains all the concepts from a single scheme, as denoted by:
<itemClass qcode="cinat:scheme"/>The <schemeMeta> element is used after <conceptSet> and contains the same attributes and child properties of <scheme> in a catalog, with the exception of @alias, but has the following additional properties:
The optional child elements <related>, which enables implementers to express the top-level concept(s) of a scheme, a requirement of SKOS, and <concepttype> listing the concept types that are used within the Knowledge Item. Please note the IPTC recommends that if <concepttype> is used, ALL concept types in the scheme are listed.
The attributes @authority, to indicate the party that controls the scheme, and @preferredalias, which indicates the scheme authority’s recommended scheme alias to be used with QCodes.
As with <scheme>, the <schemeMeta> element has the optional attributes schemecreated, schememodified and schemeretired to record the date and optionally the time of changes to the scheme.
If a scheme is marked as retired using schemeretired, then ALL concepts in that scheme (identified by the schemeMeta @uri) must also be retired.
|
<schemeMeta uri="http://cv.example.org/newscodes/ex-access/"
authority="http://www.example.org" preferredalias="ex-access"
schemecreated="2010-10-01T12:00:00.000Z"
schememodified="2015-09-22T12:00:00.000Z">
<definition xml:lang="en-GB">Classification of the ease of gaining physical access
to the location of a news event for the purpose of deploying personnel,
vehicles and equipment.</definition>
<name xml:lang="en-GB">Ease of Access/name>
<related qcode="ex-access:easy" rel="skos:hasTopConcept"/>
<related qcode="ex-access:difficult" rel="skos:hasTopConcept"/>
<related qcode="ex-access:restricted" rel="skos:hasTopConcept"/>
<schemeMeta/>All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for ex-access.
<?xml version="1.0" encoding="UTF-8"?>
<knowledgeItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20090202:ncdki-accesscode" version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power" >
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<itemMeta>
<itemClass qcode="cinat:scheme" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-11-08T00:00:00Z</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<contentCreated>2009-01-28T12:00:00Z</contentCreated>
<contentModified>2009-01-28T13:00:00Z</contentModified>
<description xml:lang="en">
Classification of the ease of gaining physical access to the location of a news
event for the purpose of deploying personnel, vehicles and equipment.
</description>
<description xml:lang="fr">
Classification de la facilité d'obtenir un accès physique à l'emplacement d'un
événement pour le déploiement de personnel, de véhicules et d'équipements.
</description>
<description xml:lang="de">
Klassifikation der physischen Zugriff auf den Standort eines News Termine für
Die Zwecke der Bereitstellung von Personal, Fahrzeugen und Ausrüstungen.
</description>
</contentMeta>
<conceptSet>
<concept>
<conceptId qcode="ex-access:easy" />
<name xml:lang="en">Easy access</name>
<name xml:lang="fr">Facile d'accès</name>
<name xml:lang="de">Der Zugang ist einfach</name>
<definition xml:lang="en">
Unrestricted access for vehicles and equipment. Loading bays
and/or lifts for unimpeded access to all levels
</definition>
<definition xml:lang="fr">
Un accès sans restriction pour les véhicules et l'équipement. Les quais de
chargement et / ou des ascenseurs pour l'accès sans entrave à tous les
niveaux
</definition>
<definition xml:lang="de">
Ungehinderten Zugang für Fahrzeuge und Ausrüstung. Laderampen und / oder
Aufzüge für den uneingeschränkten Zugang zu allen Ebenen
</definition>
</concept>
<concept>
<conceptId qcode="ex-access:difficult" />
<name xml:lang="en">Access is difficult</name>
<name xml:lang="fr">L'accès est difficile</name>
<name xml:lang="de">Der Zugang ist schwierig</name>
<definition xml:lang="en">
Access includes stairways with no lift or ramp available. It will not be
possible to install bulky or heavy equipment that cannot be safely carried
by one person
</definition>
<definition xml:lang="fr">
Comprend l'accès aux escaliers ou la rampe sans ascenseur disponible. Il ne
sera pas possible d'installer des équipements lourds ou volumineux qui ne
peuvent pas être transportés en sécurité par une seule personne
</definition>
<definition xml:lang="de">
Access enthält Treppen ohne Fahrstuhl oder Rampe zur Verfügung. Es wird nicht
möglich sein, installieren sperrige oder schwere Geräte, die sich nicht
sicher befördert werden von einer Person
</definition>
</concept>
<concept>
<conceptId qcode="ex-access:restricted" />
<name xml:lang="en">Access is Restricted</name>
<name xml:lang="fr">Accès Restreint</name>
<name xml:lang="de">Der Zugang ist eingeschränkt</name>
<definition xml:lang="en">
Access for vehicles and equipment possible but restricted. There may be
obstacles, height or width restrictions that will impede large or heavy
items. Advise checking with the organisers.
</definition>
<definition xml:lang="fr">
L'accès des véhicules et de matériel possible, mais limitée. Il y mai être
des obstacles, la hauteur ou la largeur des restrictions qui empêchent les
grandes ou d'objets lourds. Conseiller à la vérification avec les
organisateurs.
</definition>
<definition xml:lang="de">
Zugang für Fahrzeuge und Ausrüstung möglich, aber eingeschränkt.
Möglicherweise gibt es Hindernisse, Höhe und Breite, die Beschränkungen
behindern große oder schwere Gegenstände. Beraten Sie mit dem Veranstalter in
Verbindung
</definition>
</concept>
</conceptSet>
<schemeMeta uri="http://cv.example.org/newscodes/ex-access/"
authority="http://www.example.org" preferredalias="ex-access"
schemecreated="2010-10-01T12:00:00.000Z"
schememodified="2015-09-22T12:00:00.000Z">
<definition xml:lang="en-GB">Classification of the ease of gaining physical access
to the location of a news event for the purpose of deploying personnel,
vehicles and equipment.</definition>
<name xml:lang="en-GB">Ease of Access</name>
<related qcode="ex-access:easy" rel="skos:hasTopConcept"/>
<related qcode="ex-access:difficult" rel="skos:hasTopConcept"/>
<related qcode="ex-access:restricted" rel="skos:hasTopConcept"/>
</schemeMeta>
</knowledgeItem>12.4. Knowledge Workflow
The diagram below shows a possible information flow for news information that exploits the possibilities of NewsML-G2 Concepts and Knowledge Items to add value to news:
Increasingly, news organisations are using entity extraction engines to find "things" mentioned in news objects. The results of these automated processes may be checked and refined by journalists. The goal is to classify news as richly as possible and to identify people, organisations, places and other entities before sending it to customers, in order to increase its value and usefulness.
This entity extraction process will throw up exceptions – unrecognised and potentially new concepts – that may need to be added to the Knowledge Base. Some news organisations have dedicated documentation departments to research new concepts and maintain the Knowledge Base.
When new concepts are submitted to the Knowledge Base, they are added to the appropriate taxonomy and may be made available to customers (depending on the business model adopted) either partially or fully as Knowledge Items.
12.5. Using NewsML-G2 Knowledge Items with SKOS
The Simple Knowledge Organisation System is a W3C standard for using RDF-based means to share information about knowledge organization systems (see www.w3.org/2004/02/skos/).
The IPTC Media Topic NewsCodes are a working example of how a NewsML-G2 Knowledge Item may have features added that can align a NewsML-G2 Scheme to SKOS using the <related> child element of <concept> and <schemeMeta>.
For example, the Media Topic for the sport of biathlon, part of the Media Topics scheme (http://cv.iptc.org/newscodes/mediatopic/):
<concept id="medtop20000852" modified="2010-12-14T21:53:19+00:00">
<conceptId qcode="medtop:20000852" created="2009-10-22T02:00:00+00:00"/>
<type qcode="cpnat:abstract"/>
<name xml:lang="en-GB">biathlon</name>
<definition xml:lang="en-GB">A combination of cross country skiing and target
shooting on a 12.5 K course in a pursuit format. </definition>
<broader qcode="medtop:20000822"/>
<related qcode="medtop:20000822" rel="skos:broader"/>
<related qcode="subj:15009000" rel="skos:exactMatch"/>
<related uri="http://cv.iptc.org/newscodes/mediatopic/" rel="skos:inScheme"/>
</concept>This uses the NewsML-G2 <broader> property to express that the
‘’biathlon’’ topic (medtop:20000852) is a child of the "competition
discipline" topic (medtop:20000822), and this is complemented by the
using a <related> to indicate the same relationship by the SKOS term
"skos:broader". The second <related> element indicates that the legacy
IPTC Subject Code NewsCodes 15009000 is the exact match (G2 = <sameAs>)
for this Media Topic.
The CV also contains a Scheme Metadata element as follows:
<schemeMeta uri="http://cv.iptc.org/newscodes/mediatopic/"
authority="http://www.iptc.org" preferredalias="medtop">
<definition xml:lang="en-GB">Indicates a subject of an item.</definition>
<name xml:lang="en-GB">Media Topic</name>
<note xml:lang="en-GB">The Media Topic NewsCodes is IPTC's new (as of December
2010) 1100-term taxonomy with a focus on text. The development started with the
Subject Codes and extended the tree to 5 levels and reused the same 17 top
level terms. The terms below the top level have been revised and rearranged.
Each Media Topic provides a mapping back to one of the Subject Codes.
</note>
<related qcode="medtop:01000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:02000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:03000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:04000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:05000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:06000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:07000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:08000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:09000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:10000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:11000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:12000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:13000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:14000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:15000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:16000000" rel="skos:hasTopConcept"/>
<related qcode="medtop:17000000" rel="skos:hasTopConcept"/>
</schemeMeta>This satisfies the SKOS requirement to indicate the top-level concepts of any scheme.
The current structure of NewsML-G2 Knowledge Items delivered by IPTC is documented at http://dev.iptc.org/NewsCodes-G2-Knowledge-Items-by-IPTC
13. Controlled Vocabularies and QCodes
13.1. Introduction
One of the fundamental ideas underpinning NewsML-G2 is the use of Controlled Vocabularies (CVs) or taxonomies to enable two basic operations:
-
To restrict the allowed values of certain properties in order to maintain the consistency and inter-operability of machine-readable information – supplying data to populate menus, for example.
-
To provide a concise method of unambiguously identifying any abstract notion (e.g. subject classification) or real-world entity (person, organisation, place etc.) present in, or associated with, an item. This enables links to be made to external resources that can provide the consumer with further information or processing options.
A Controlled Vocabulary (CV) is a set of concepts usually controlled by an authority which is responsible for its maintenance, i.e. adding and removing vocabulary entries. In NewsML-G2, CVs are also known as Schemes. The person or organisation responsible for maintaining a Scheme is the Scheme Authority.
Examples of CVs include the set of country codes maintained by the International Standards Organisation, and the NewsCodes maintained by the IPTC. An application of a CV could be a drop-down list of countries in an application interface.
Many CVs are dedicated to a specific metadata property, for example there are CVs for <subject> and for <genre>. Other CVs are dedicated to a specific attribute that refines a property such as the CV for the @role of <description>.
In news distributions that use NewsML-G2, it is recommended that Controlled Vocabularies are exchanged as Knowledge Items, with members of the CV contained in individual <concept> structures.
Members of a Scheme are each identified by a concept identifier expressed as a QCode (note capitalisation), which is resolved via the Catalog information in the NewsML-G2 Item to form a URI that is globally unique.
13.2. Business Case
Controlled Vocabularies are needed in information exchange because they establish a common ground for understanding content that is language-independent. Schemes and QCodes enable CVs to be exchanged and referenced using Web technology, and provides a lightweight, flexible and reliable model for sharing concepts and information about concepts
For example, the IPTC Media Topics Scheme is a language-independent taxonomy for classifying the subject matter of news. A consumer receiving news classified using this scheme can discover the meaning of this classification, using a publicly-accessible URL.
Examples abound of non-IPTC CVs in everyday use: IANA Media Types, ISO Country Codes or ISO Currency Codes to name but three.
News providers use CVs to add value to their content:
-
News can be accurately processed by software if it adheres to known (i.e. controlled) parameters expressed as a CV, for example the publishing status of a news item
-
by establishing CVs of people, places and organisations, the identity of entities in the news can be unambiguously affirmed;
-
CVs can be extended to store further information about entities in the news, for example biographies of people, contact details for organisations.
13.3. How QCodes work
A QCode is a string with three parts, all of which MUST be present:
-
Schema Alias: the prefix, for example "stat"
-
Scheme-Code Separator: a separator, which MUST be a colon ":" (ASCII 58dec = 003Ahex)
-
Code Value: the suffix, for example "usable"
This produces a complete QCode of "stat:usable" represented in XML as
qcode="stat:usable"13.3.1. Scheme Alias to Scheme URI
The key to resolving scheme aliases is the Catalog information, a child of the root element of every NewsML-G2 Item. A scheme alias may be resolved directly using the <catalog> element:
<catalog>
<scheme alias="stat" uri="http://cv.iptc.org/newscodes/pubstatusg2/" />
</catalog>Using the information in <catalog>, a processor now has a Scheme URI that can be used as the next step in resolving the QCode.
Catalogs
The <catalog> element may contain many <scheme> components. Catalog information can be stored in one of two ways:
-
directly in a NewsML-G2 Item using the <catalog> element, or
-
remotely in a file containing the catalog information, referenced by the @href of a <catalogRef> element.
There is likely to be more than one <catalogRef> in an Item:
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef
href="http://www.xmlteam.com/specification/xts-SportsCodesCatalog_1.xml"/>These remote catalogs are hosted by specific authorities, in this case by the IPTC, and by the information provider XML Team. Each remote catalog file will contain a <catalog> element and a series of <scheme> components that map the scheme aliases used in the item to their scheme URIs. For a more detailed description of managing Catalogs, see Creating and Managing Catalogs.
13.3.2. Concept URI
Appending the QCode Code Value to the Scheme URI produces the Concept URI.
The IPTC recommends that Scheme/Concept URIs can be resolved to a Web resource that contains information in both machine-readable and human-readable form (This is also a recommendation for the Semantic Web), i.e. they are URLs. The concept resolution mechanism used by the IPTC is http-based, and the NewsML-G2 Specification describes how an http-URL should be resolved.
Entering the above Concept URI in a web browser results in the following page being displayed:
A question often asked by implementers is: "What happens if I receive files from two providers who inadvertently have a clash of scheme aliases?"
The scenarios they envisage are either:
-
Provider A and Provider B use the same scheme alias to represent different schemes. For example the alias "pers" is used by both providers to represent their own proprietary CVs of people, or
-
Provider A and Provider B use a different scheme alias to represent the same scheme. For example, A uses "subj" to represent the IPTC Subject NewsCodes, and B uses "tema" to represent the same CV.
The answer is "everything works fine!"; QCode to Concept URI mappings must be unique only within the scope of each document in which they appear.
A processor should correctly process two files with different aliases to the same Concept URI:
<!-- First Document – scheme alias "subj" -->
<catalog>
<scheme alias="subj" uri="http://cv.iptc.org/newscodes/subjectcode/" />
...
</catalog>
<subject type="cpnat:abstract" qcode="subj:1500000" />
<!-- Second Document – scheme alias "ex-tema" -->
<catalog>
<scheme alias="ex-tema" uri="http://cv.iptc.org/newscodes/subjectcode/" />
...
</catalog>
<subject type="cpnat:abstract" qcode="ex-tema:1500000" />This is because the concept resolution process is local to each document. The processor can unambiguously resolve the QCode to a Concept URI via the <catalog> in each case.
The following example does NOT work because the same alias is mapped to two different URIs within the same document and the processor is unable to resolve the QCode to a single Concept URI:
<catalog>
<scheme alias="ex-subject" uri="http://cv.iptc.org/newscodes/subjectcode/" />
...
<scheme alias="ex-subject" uri="http://cv.example.com/subjectcodes/codelist/" />
</catalog>
...
<subject type="cpnat:abstract" qcode="ex-subject:1500000" />
...But the following is CORRECT because it is possible to have different aliases within the same document pointing to the same URI and the processor can resolve both QCodes:
<catalog>
<scheme alias="ex-subject" uri="http://cv.iptc.org/newscodes/subjectcode/" />
...
<scheme alias="subj" uri="http://cv.iptc.org/newscodes/subjectcode/" />
</catalog>
...
<subject type="cpnat:abstract" qcode="ex-subject:1500000" />
...
<subject type="cpnat:abstract" qcode="subj:1500000" />In this document, there are many references to IPTC NewsCodes and their scheme aliases. From the above, it will be obvious that these specific alias values are not mandatory, although the IPTC recommends the consistent use of scheme alias values by implementers.
13.4. QCodes and Taxonomies
Taxonomies, also known as thesauri, knowledge bases and so on, are repositories of information about notions or ideas, and about real-world "things" such as people, companies and places.
For example, a processor might encounter the following XML in a NewsML-G2 document:
<subject type="cpnat:person" qcode="ex-pol:rus12345">The subject property shown here has two QCodes, one for @type, and the other as @qcode. The "cpnat" alias is for a controlled vocabulary of allowed categories of concept, which includes values of "person", "organisation", "poi" (point of interest). Using @type in this way enables further processing such as "find all of the people identified in the document".
The second QCode encountered in the subject is "ex-pol:rus12345". Resolving this (fictional) scheme alias and suffix might result in the following concept URI:
Fetching the information at the above resource, may return the following information:
| PUTIN, Vladimir – Prime Minister of the Russian Federation | Name (FAMILY, Given) |
|---|---|
PUTIN, Vladimir Vladimirovitch |
Name (known as) |
Vladimir Vladimirovitch Putin |
Summary |
Former Soviet intelligence officer who has served terms as Russian president and prime minister. |
Background |
Born 7 October 1952 |
Place of birth |
Leningrad (St Petersburg) |
Other |
The IPTC recommends that providers should make schemes containing concepts such as the above available to recipients as Knowledge Items. It should include at least a name; the amount of further knowledge about the concepts could be different for different customer classes and depend on contracts.
13.5. Managing Controlled Vocabularies as NewsML-G2 Schemes
13.5.1. Knowledge Items
In a workflow where partners are exchanging news information using NewsML-G2, Knowledge Items are the most compliant method of distributing a new CV: first by creating a Scheme (see Creating a New Scheme) and next creating a Knowledge Item from a set of existing Concept Items (see Creating a new Knowledge Item for distributing as a CV) for distribution to customers and partners.
Knowledge Items do not necessarily contain all of the information that a provider possesses about any given set of concepts. This, after all, may be commercially valuable information that the provider makes available on a per-subscriber basis. For example, a lower fee might entitle the subscriber to basic information about a concept, say a person, while a higher fee might give access to full biographical details and pictures.
It is not mandatory that information about CVs be stored or distributed in the technical format of a Knowledge Item. It is sufficient, for the correct processing of a NewsML-G2 Item, only that a Scheme Alias/Code Value pair (defining the Concept URI) is unambiguous. The IPTC makes the following recommendations about CVs:
-
Knowledge Items SHOULD be used to distribute CVs. Other means such as paper, fax or email are permissible but at the price of less efficient automated processing.
-
Concept URIs SHOULD resolve to a Web resource; this is a requirement for the Semantic Web.
-
In the case where a Scheme Authority does not make the concepts of a CV available as a Web resource, the Scheme URI SHOULD resolve to a Web resource, such as a human-readable Web page giving information about the purpose of the CV, and where details of the Scheme can be obtained.
13.5.2. Creating a new Scheme
A NewsML-G2 controlled vocabulary is a set of concepts. To create a CV as a NewsML-G2 Scheme:
-
Assign a Scheme URI which must be an http URL for the Semantic Web (example:
http://cv.example.org/schemeA/) and a Scheme Alias (example: abc)
Add this Scheme Alias and URI to the catalog:
<catalog>
<scheme alias="abc" uri="http://cv.example.org/schemeA/" />
</catalog>If using a remote catalog, change the catalog URI to reflect a new version of the catalog (so that recipients know that they should add this to their cache of catalogs) and ensure that all NewsML-G2 Items using the new Scheme refer to the new version of the remote catalog.
-
Create Concepts as required. You must use the Scheme Alias of the new scheme with the identifier of this new concept. For example:
<concept> +
<conceptId created="2009-09-22" qcode="ex-abc:concept-x" +
...The above Concept Identifier resolves to the Concept URI
http://cv.example.org/schemeA/concept-x
13.5.3. Creating a new Knowledge Item for distributing as a CV
The Chapter on Knowledge Items shows an example Controlled Vocabulary expressed in XML. A Knowledge Item contains concepts from one or more Schemes. The steps to begin creating a KI are:
-
Identify the set of Concept Items that contain the concepts that will be part of the Knowledge Item, which may be only from this new CV or also from other CVs.
-
Create the metadata properties for the Knowledge Item that express the rules used to create it, for example, a <title> and <description> such as "Concepts extracted from Schemes A and B based on criteria X and Y".
-
For each Concept: Copy all or part of the selected concept details (the <concept> wrapper and associated properties) into the Knowledge Item.
13.5.4. Managing Schemes
Changes to Schemes
Scheme URIs MUST persist over time, and any changes to a Scheme which involve the creation or deprecation of concepts MUST be backwardly compatible with existing concepts. (For example, the code of a retired Concept MUST NOT be reused for a new and different concept.)
Scheme Authorities can indicate that a member of a CV should no longer be applied as a new value. This must be expressed by adding a @retired attribute to the <conceptId> of the Concept that is no longer to be used.
Both @created and @retired attributes are of datatype Date with optional Time and Time Zone (DateOptTime) and their use is optional. The @retired date can be a date in the future when a Scheme Authority knows that the Concept ID should no longer be used for new NewsML-G2 Items.
Example of a retired concept:
<conceptId created="2006-09-01" retired="2009-12-31"
qcode="ex-foo:bar" />-
Concepts MUST NOT be deleted from a Scheme; this could cause processing errors for NewsML-G2 Items that pre-date the changes. Use of @retired ensures that Items that pre-date a CV change will continue to correctly resolve "legacy" concept identifiers.
-
For the same reason, Concept IDs MUST NOT be re-cycled, i.e. the same identifier MUST NOT be used for a different concept.
-
Schemes themselves MUST NOT be deleted, as archived content is likely to use the concepts contained in a retired CV.
See also <scheme> properties below in this chapter.
Recommendations for non-complying Schemes
Some Scheme Authorities may fail to comply with the NewsML-G2 Specification, and this could be beyond the control of the end-user or the provider. Guidelines for handling various scenarios are:
-
The authority of the vocabulary governs the scheme URI and the code – but does not comply with the NewsML-G2 Specification
Reusing a Concept URI which was assigned to one concept with another concept is a breach of the NewsML-G2 specifications. If there are requirements that drive the authority to do so, the authority should give a clear and warning notification about that fact to all receivers at the time of the publication of the reused Concept URI. -
The authority of the vocabulary governs only the code but not the scheme URI
This may be the case for Controlled Vocabularies of codes only and if a news provider assigns a scheme URI of its own domain to enable the CV to be used with NewsML-G2. A good example are the scheme URIs defined by the IPTC for the ISO vocabularies for country names or currencies – see http://cvx.iptc.org
The party who assigned the scheme URI has the responsibility of making users of this scheme URI together with the vocabulary aware of any reuse cases – and should post a generic warning about the potential threat of reused codes.
In addition the party who assigned the scheme URI may consider changing the scheme URI in the case of the reuse of a code. This would avoid having the same Concept URI for different concepts but would require careful management of the vocabularies as actually a completely new Controlled Vocabulary is created by the use of the new scheme URI. -
Another code is assigned to the same concept or a very likely similar concept
This use case does not violate the NewsML-G2 specifications. But care should be taken for establishing relationships between Concept URIs:-
If a new code is assigned to the same concept a sameAs or a SKOS exactMatch relationship of this new URI should be established pointing to all other existing URIs identifying this concept.
-
If a slightly modified concept is created and gets a new Concept URI it may be considered to establish a closeMatch relationship from SKOS
-
13.6. Creating and Managing Catalogs
As previously described, Catalogs are essential to the resolution of NewsML-G2 Controlled Vocabularies and constituent QCodes.
13.6.1. The <catalog> element
Each QCode Scheme Alias that is used in a NewsML-G2 Item must have a reference in the Item’s <catalog> to the Controlled Vocabulary in which it is included. A <catalog> contains the Scheme Alias and the Scheme URI:
<catalog>
<scheme alias="timeunit" uri="http://cv.iptc.org/newscodes/timeunit/" />
</catalog>13.6.2. Remote Catalogs
As the CVs used by a provider are usually quite consistent across the NewsML-G2 Items they publish, the IPTC recommends that the <catalog> references are aggregated into a stand-alone file which is made available as a web resource: known as a Remote Catalog. This file is referenced by a <catalogRef> in the Item:
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />Note: the <catalog> element in such a stand-alone file needs an XML namespace definition:
<catalog xmlns="http://iptc.org/std/nar/2006-10-01/">The use of stand-alone web resources is preferable because all of the QCode mappings are shared across many NewsML-G2 Items; the local <catalog> can only be used by the single Item.
13.6.3. Managing Catalog files
Simple management of Remote Catalogs over time is relatively straightforward: whenever a new scheme is added or the alias or the uri of any of the existing schemes are changed, a new Catalog must be published with a new URL. This URL may reflect a version number of the catalog. This is the method that the IPTC uses to maintain the NewsCodes, simply by increasing the file suffix digit as required:
href="..Standards_35.xml" -> href="..Standards_36.xml"Note that ALL versions of a Remote Catalog must continue to be available as a web resource, otherwise existing NewsML-G2 Items and QCodes that reference it will not be able to resolve related Scheme Aliases to Scheme URIs.
Receiving applications MUST use the catalog information contained in the NewsML-G2 document being processed. If a provider updates a catalog, this is likely to be because new schemes have been added. Using a catalog other than that indicated in the document could cause errors or unintended results.
Additional <catalog> features
To improve the management features of Catalogs, new (optional) properties were added to the <catalog> in NewsML-G2 v2.15:
-
@url defines the location of the Catalog as a remote resource. (This must be the same as the URL used with the href attribute of a catalogRef in NewsML-G2 Items that use this Catalog.)
-
@authority uses a URI to define the company or organisation controlling this Catalog.
-
@guid is a globally unique identifier, expressed as a URI, for this kind of Catalog as managed by a provider. (This must be the @guid of the Catalog Item, see below, that manages this Catalog) If present, the version attribute should also be used.
-
@version is the version of the @guid as a non-negative integer; a version attribute must always be accompanied by a guid attribute.
<scheme> properties
Further information about schemes is expressed using the <scheme> child elements <name>, <definition>, and <note>. In NewsML-G2 v2.15 @roleuri was added to these child elements to allow the role of the element to be defined using a full URI instead of a QCode used by the existing @role attribute).
@roleuri simplifies processing by avoiding the situation where a QCode used in a Catalog relies on an alias defined in some other Catalog, making resolution difficult or impossible.
Changes to a scheme may be expressed using the <scheme> attributes schemecreated, schememodified and schemeretired as follows:
| Property | Cardinality | Type | Definition |
|---|---|---|---|
schemecreated |
0..1 |
DateOptTimeType |
The date (and, optionally, the time) when the scheme was created. This must not be later than the creation timestamp of any concepts in the scheme. |
schememodified |
0..1 |
DateOptTimeType |
The date (and, optionally, the time) when the scheme was last modified. The initial value is the date (and, optionally, the time) of creation of the scheme. |
schemeretired |
0..1 |
DateOptTimeType |
The date (and, optionally, the time) after which the scheme should not be used anymore. If a scheme is marked as retired, then all Concept Identifiers in that scheme (identified by the scheme @uri) must also be retired. |
See also Changes to Schemes in this chapter.
In NewsML-G2 v 2.17, the <schemeMeta> element was added to the Knowledge Item, enabling the metadata previously expressed in the <scheme> elements of a Catalog to be added directly to a Knowledge Item that conveys all the concepts in a Scheme (aka Controlled Vocabulary). See Scheme Metadata
13.6.4. Catalog Item
For providers who wish to use the same basic means for managing a Catalog as are available for news content, the Catalog Item is introduced to NewsML-G2 in version 2.15. The Catalog Item inherits the additions and changes to <catalog> and <scheme> described above. The example below shows how a Scheme Authority (in this example, the IPTC) might distribute its catalog to subscribers.
The Catalog Item shares the generic identification and processing instruction attributes associated with all NewsML-G2 items, for example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<catalogItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:iptc.org:20160517:catalog"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-GB">The child properties of Catalog Item are restricted to a basic set of essentials required for Catalog management:
| Definition | Name | Cardinality | Child properties |
|---|---|---|---|
Catalog |
catalogRef catalog |
1..n |
As per all NewsML-G2 Items |
Hop History |
hopHistory |
0..1 |
As per all NewsML-G2 Items |
Rights Information |
rightsInfo |
0..n |
As per all NewsML-G2 Items |
Item Metadata |
itemMeta |
1 |
As per all NewsML-G2 Items |
Content Metadata |
contentMeta |
0..1 |
- contentCreated (0..1) - contentModified (0..1) - creator (0..1) - contributor (0..1) - altId (0..1) |
Catalog Container |
catalogContainer |
1 |
catalog (1) |
The catalogRef, rights information and itemMeta elements follow normal practice. Note that the Item Class is set to "catinat:catalog"; this uses the IPTC Catalog Item Nature NewsCodes, recommended Scheme Alias "catinat":
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<rightsInfo>
<copyrightHolder uri="http://www.iptc.org">
<name>IPTC</name>
</copyrightHolder>
</rightsInfo>
<itemMeta>
<itemClass qcode="catinat:catalog" />
<provider qcode="nprov:IPTC">
<name>International Press Telecommunications Council </name>
</provider>
<versionCreated>2022-05-17T12:00:00Z</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>The Catalog information conveyed by the Item is wrapped in the <catalogContainer> element, which must contain one and only one <catalog>. The Catalog contains one or more <scheme> elements, as previously described:
<catalogContainer>
<catalog xmlns="http://iptc.org/std/nar/2006-10-01/"
additionalInfo="http://www.iptc.org/goto?G2cataloginfo">
<scheme alias="app" uri="http://cv.iptc.org/newscodes/application/">
<definition xml:lang="en-GB">Indicates how the metadata
value was applied.</definition>
<name xml:lang="en-GB">Application of Metadata Values</name>
</scheme>
</catalog>
</catalogContainer>All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies.
<?xml version="1.0" encoding="UTF-8" ?>
<catalogItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20130517:catalog"
version="35"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-GB">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<rightsInfo>
<copyrightHolder uri="http://www.iptc.org">
<name>IPTC</name>
</copyrightHolder>
</rightsInfo>
<itemMeta>
<itemClass qcode="catinat:catalog" />
<provider qcode="nprov:IPTC">
<name>International Press Telecommunications Council</name>
</provider>
<versionCreated>2022-10-17T12:00:00Z</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<catalogContainer>
<catalog xmlns="http://iptc.org/std/nar/2006-10-01/"
additionalInfo="http://www.iptc.org/goto?G2cataloginfo">
<scheme alias="app" uri="http://cv.iptc.org/newscodes/application/">
<definition xml:lang="en-GB">Indicates how the metadata
value was applied.</definition>
<name xml:lang="en-GB">Application of Metadata Values</name>
</scheme>
</catalog>
</catalogContainer>
</catalogItem>13.7. Processing Catalogs and CVs
In practice, from a receiver’s point of view, it makes no sense to look up the contents of CVs over the network every time a document is processed, since this would consume considerable computing and network resources and probably degrade performance. Also, as discussed, some providers might not make a scheme or its contents available at all.
The NewsML-G2 Specification requires that remote Catalogs – the file(s) that map Scheme Aliases to Scheme URIs – are retrieved by processors. However, the IPTC makes NewsML-G2 resources, including the IPTC Catalog, available on its public web servers on an "as is" basis; 24/7 availability of these resources is not guaranteed. Therefore all versions of the IPTC Catalog must be cached at the receiver’s site. They may be cached indefinitely because the contents of a catalog referenced by a catalog URI must remain unchanged over time. Whenever Schemes are created or deleted, an updated catalog must be provided under a new URI. This ensures that Items that pre-date the catalog changes can continue to be processed using the previous catalog.
Controlled Vocabularies (IPTC NewsCodes) referenced as Scheme URIs in the IPTC Catalog may be retrieved and cached daily; their contents are subject to change as IPTC Schemes are updated and this happens not more frequently than daily.
See also the NewsML-G2 Specification section on processing remote catalogs and in this document Use of IPTC web resources.
13.7.1. Resolving Scheme Aliases
Some NewsML-G2 properties are important for the correct processing of an Item, for example the Item Class property tells a receiving application the type of content being conveyed by a NewsML-G2 Item: a processor may expect to apply some rule according to the value present in the <itemClass>, for example to route all pictures to the Picture Desk.
Other CVs may be important for correctly processing an Item, for example the presence of specific subject codes could cause an Item’s content to be routed to certain staff or departments in a workflow.
The schemes used by <itemClass> property are mandatory, and the IPTC recommends that implementers use the scheme aliases appropriate to the Item Type, for example "ninat" for News item Nature or "cinat" for Concept Item Nature. Note that the use of these specific alias values is NOT mandatory; they could already being used by a provider as aliases for other CVs.
This illustrates the flexibility of the NewsML-G2 model: consistency of scheme aliases between different providers – or even by the same provider – cannot be guaranteed, and in NewsML-G2 they do not have to be guaranteed. For this reason it would be unwise for NewsML-G2 processor implementers to assume that a given scheme alias can be "hard coded" into their applications.
However, this flexibility does not mean that these "needed for processing" CVs must be accessed every time an Item is processed. This could be an unnecessary overhead and performance burden.
Processing rules such as those described above would be based on acting in response to expected values. In the case of the News Item Nature Scheme, these values include "text, "picture", "audio" etc. The problem is not in obtaining the contents of the CV in real time, but in verifying that it is the correct CV.
For example:
-
A receiver knows that providers use the IPTC Media Topic NewsCodes for classifying news content by subject matter, and that the scheme URI for these NewsCodes is
http://cv.iptc.org/newscodes/mediatopic/ -
The business requires that incoming content is routed to the appropriate department, according to the Media Topic NewsCodes found in the Items,
-
A routing table is set up in the processor with a configurable rule "all items with a Media Topic NewsCode
04000000to be routed to the Business News department".
How does the processor "know" that a <subject> property with a QCode
containing 04000000 is an IPTC Media Topic NewsCode? The processor
should not rely on the scheme alias "medtop"; it could be an alias to
another CV, or the provider may use another alias:
<subject type="cpnat:abstract" qcode="ex-sc:04000000" />By following the IPTC advice to retrieve all catalog information used by Items, and cache the information indefinitely, CVs can be processed without reference to external resources.
In the example, the catalog used by the Item resolves the scheme alias "ex-sc" contained in the QCode. The Item contains the line pointing to the catalog file:
<catalogRef href="http://www.example.org/std/catalog/catalog.example_10.xml" />The processor should have retrieved and cached the contents of the file at this URL, and would have in memory the mapping of this alias to the Scheme URI:
<scheme alias="ex-sc" uri="http://cv.iptc.org/newscodes/mediatopic/" />…this verifies that the QCode value is from the Media Topic NewsCodes
scheme. A rule "all items with a Media Topic NewsCode of 04000000 to
be routed to the Business News department" is satisfied and the
NewsML-G2 Item processed appropriately.
13.7.2. Resolving Concept URIs
The IPTC recommends that Schemes SHOULD resolve to a Web resource, and that Scheme Authorities who disseminate news using NewsML-G2 should make their Schemes available as Knowledge Items.
Access Models
Making a CV available as a Web resource does not mean it must be accessible on the public Web; only that Web technology should be used to access it. The resource may be on the public Web, on a VPN, or internal network.
Providers may also wish to use Schemes to add value to content, using a subscription model. In this case, the contents of a Scheme may not be available to non-subscribers, but they could continue to resolve the QCodes to a unique and persistent Concept URI.
Concept Resolution: Provider View
In following the IPTC recommendation that CVs should be accessible as a Web resource, providers may be concerned about the implications for providing sufficient access capacity and reliability guarantees. If receivers were to interrogate CVs each time they processed a NewsML-G2 document that could act like a Denial of Service attack.
The IPTC makes no recommendations about this issue other than to advise the use of industry-standard methods of mitigating these risks. Organisations hosting CVs could also define an acceptable use policy that places limits on the load that individual subscribers can place on the service.
Concept Resolution: Receiver View
As the IPTC recommends that CVs should be available as Web resources, it follows that the Scheme Authority may host its Schemes as Knowledge Items on a Web server. However, a Scheme Authority does not guarantee the availability and capacity of connections to its hosted Knowledge Items.
In addition, from the receiver’s point of view, it could be unwise for business-critical news applications to rely on a third-party system beyond the receiver’s control.
Processors are therefore recommended to retrieve and cache the contents of third-party Knowledge Items. Providers should advise their customers on the recommended frequency for refreshing the third-party cached Knowledge Items.
Handling updates to Knowledge Items using @modified
The receiver can get information about which concepts have been modified (when cached concepts are synchronized with those in the latest received Knowledge Item) using the modified attribute of <concept>
Use Case and Example
1. A news site is using a CV maintained by a third-party Scheme Authority, for example a CV maintained by the IPTC.
2. The site retrieves a Knowledge Item about the concepts in the CV from the third-party Scheme Authority’s web server and stores them within its internal cache.
3. Sometime later the site wants to check the validity of the cache. It again downloads or receives a Knowledge Item from the third-party Scheme Authority, containing the relevant concepts which may have been updated in the meantime.
4. The site’s NewsML-G2 processor checks the @modified timestamp (date-time) of each concept conveyed within the Knowledge Item against the modification timestamp of the corresponding cached concept. Any concepts within the Knowledge Item with a modification timestamp later than the corresponding cached concept’s modification timestamp are processed as updates to the cache. (Note: this assumes that the Scheme Authority always flags Concepts conveyed within a Knowledge Item with a modification timestamp, see below.)
Updates Processing Notes
In the above use case, it was assumed that the Scheme Authority always flags Concepts with a modification timestamp. In cases where modification timestamps are missing from some or all or the concepts, either in the KI or in the cache, a receiver can be less certain about whether or not a concept has been modified. The following matrix outlines the IPTC recommendations for processing updates for each individual concept in the KI:
| Concept in local cache | Concept received in KI | Processor should: |
|---|---|---|
No modification timestamp |
No modification timestamp |
Update cache from KI |
No modification timestamp |
Has modification timestamp |
Update cache from KI, now the concept in the cache has a modification timestamp! |
Has modification timestamp |
No modification timestamp |
Update cache from KI, now the concept in the cache has lost its modification timestamp! |
Has modification timestamp |
Has modification timestamp |
Compare timestamps and update the concept in the cache IF the timestamp from the KI is later. |
The code snippet below shows how the Scheme Authority would inform receivers that the concepts in a Knowledge Item have been updated using the @modified attribute value informing receivers of the timestamp (date-time) of the change.
<?xml version="1.0" encoding="UTF-8"?>
<knowledgeItem ...>
...
<itemMeta>
...
</itemMeta>
<contentMeta>
...
</contentMeta>
<conceptSet>
<concept modified="2010-01-28T13:00:00Z">
<conceptId qcode="ex-access:easy" />
...
</concept>
<concept modified="2010-01-28T13:00:00Z">
<conceptId qcode="ex-access:difficult" />
...
</concept>
<concept modified="2009-11-23T13:00:00Z">
<conceptId qcode="ex-access:restricted" />
...
</concept>
</conceptSet>
</knowledgeItem>Notifying receivers of changes to Knowledge Items
This issue is not necessarily specific to NewsML-G2 news exchange: Most news providers have CVs that pre-date NewsML-G2, for example those CVs typically used with IPTC 7901. Channels and conventions for advising customers of changes to CVs will already exist. Generally, providers notify customers in advance about changes to CVs, especially if it is likely that a CV is used for content processing.
The IPTC hosts and maintains a large number of CVs and provides an RSS feed that notifies of changes to the IPTC Schemes. Details at www.iptc.org.
13.8. Private versions and extensions of CVs
News providers are encouraged to use pre-existing or well-known CVs, such as those maintained by the IPTC, where possible to promote interoperability and standardisation of the exchange of news. Sometimes a provider will use a CV that is maintained by some other Scheme Authority (e.g. the IPTC), but may need to add its own information. The following are typical potential business cases:
-
Case 1: A national news agency wishes to use all of the codes in a CV that is maintained by the IPTC, without alteration, except to provide local language versions of names and definitions.
-
Case 2: An organisation receives news objects from information partners and uses a CV that defines the stages in a shared workflow. The CV is maintained by a third-party organisation (the Scheme Authority), but the receiver needs to add further workflow stages for its own internal purposes.
13.8.1. Use <sameAsScheme> to provide a local language version of a well-known CV
Some useful and well-known CVs do not have the values of properties such as name and definition in the local language of a news provider. For example, although some IPTC NewsCodes contain concept information in several languages, the IPTC does not have the resources to provide concept details in every language being used by news providers.
Yet some NewsCodes schemes are recommended or mandatory. How can a provider use a local language version of these NewsCodes AND conform to the NewsML-G2 Specification?
Using the <sameAsScheme> property, a news provider can create its own CV, containing all of the NewsCodes it wishes to use with local language names and definitions, while making it clear to receivers that these codes identify the same concepts as the original IPTC Scheme.
For example, the IPTC Item Relation NewsCodes irel:seeAlso resolves
via the Catalog to a Concept URI http://cv.iptc.org/newscodes/itemrelation/seeAlso which hosts the
following information about the seeAlso concept:
<concept>
<conceptId created="2008-01-29T00:00:00+00:00" qcode="irel:seeAlso" />
<type qcode="cpnat:abstract" />
<name xml:lang="en-GB">See also</name>
<definition xml:lang="en-GB">
To fully understand the content of this item see also the content
of the related item.
</definition>
...
</concept>A provider wishes to provide this same information in the Czech language. As a first step, it creates a new Controlled Vocabulary containing the required concepts from the original scheme with translated name and definition, for example:
<concept>
<conceptId created="2010-01-29T00:00:00+00:00" qcode="irel:seeAlso" />
<type qcode="cpnat:abstract" />
<name xml:lang="cs">Viz také</name>
<definition xml:lang="cs">
Chcete-li plně pochopit obsah této položky viz též obsah
související položky.
</definition>
...
</concept>The provider then creates a Catalog file, or a new version of an existing Catalog file, containing a Scheme Alias and Scheme URI for the new CV, thus:
<catalog>
<scheme alias="irel" uri="http://cv.example.org/codes/itemrelation/">
<sameAsScheme>http://cv.iptc.org/newscodes/itemrelation/</sameAsScheme>
</scheme>
</catalog>This asserts that the ALL of the codes in the private scheme identified by the Scheme URI are semantically the "same as" the corresponding codes in the original scheme indicated by the <sameAsScheme> child element of <scheme>.
| In this example the provider MUST give the new CV a Scheme Alias – here it is "irel" – that is different to the recommended Scheme Alias "irel" of the IPTC Scheme. This is because some IPTC schemes are mandatory, so a reference to the IPTC catalog would always be present in the Item. When there is no reference to an original scheme, there is no need to use a different Scheme Alias for the private scheme. |
Finally, the provider adds a reference to the new Catalog file to NewsML-G2 Items that it publishes.
By using the <sameAsScheme> element to the Catalog, the provider is able apply a Same As relationship at the level of a set of Concepts. So for example, this code:
<link
rel="irel:seeAlso"
contenttype="image/jpeg"
residref="tag:acmenews.com,2008:TX-PAR:20090529:JYC90"
/>can be efficiently resolved: a processor does not have to search for a Same As relationship at the individual concept level but can map this relationship directly from the @rel value’s scheme (alias "irel") to the scheme identified by the <sameAsScheme> property.
Rules for <sameAsScheme>
The semantics of <sameAsScheme> are:
"all of the concepts in the scheme identified by the private scheme/@uri have a ‘same as’ relationship to concepts with the same code in the original scheme identified by the URI in the <sameAsScheme> element."
So in the example:
<scheme alias="irel" uri="http://cv.example.org/codes/itemrelation/">
<sameAsScheme>http://cv.iptc.org/newscodes/itemrelation/</sameAsScheme>
</scheme>In practice, this means:
-
The Scheme identified by scheme/@uri (the provider’s private scheme) must NOT use a code that does not exist in ALL of the original Schemes identified by the <sameAsScheme> elements. In other words, a provider cannot add new concepts to its private Scheme that have the effect of extending the set of concepts of the original Scheme(s).
-
Some codes and concepts of the original Scheme MAY not exist in the provider’s private Scheme. This could happen if for example the original Scheme has new terms added which the provider has not yet included in the private Scheme.
-
Each concept identified by a code in the provider’s private Scheme MUST be semantically equivalent to its corresponding concept in the original Scheme(s), and MUST be identified by the same code as in the original Scheme(s).
The <sameAsScheme> property was introduced to solve some issues that news providers had encountered, such as adding translations of free-text properties (for example name, definition, note), which are not available within the original scheme, or adding additional information, e.g. usage notes.
13.8.2. Adding further concepts to a well-known CV
A news provider needs to add concepts to a workflow role CV which is shared with information partners, but is maintained by some other organisation (the Scheme Authority).
The news provider would have two courses of action:
-
Ask the Scheme Authority to add the new concepts to the CV. For example, IPTC members are entitled to request the addition and/or retirement of terms in IPTC Schemes with the agreement of other members.
-
Create a new scheme that complements the original scheme, but uses properties such as <broader> and <sameAs> to link the concepts in the new scheme to concepts in the original scheme. A concept is the Same As another concept if their semantics are the same, but it MAY contain more details, such as a translation in another language. A concept with a Broader relationship to another concept is a new concept with semantics narrower than those of the broader concept.
Example using a new scheme
Using the shared workflow role example, the original scheme contains three concepts for defined roles in a workflow:
<conceptSet>
<concept>
<conceptId qcode="ex-wflow:draft" />
...
</concept>
<concept>
<conceptId qcode="ex-wflow:review" />
...
</concept>
<concept>
<conceptId qcode="ex-wflow:release" />
...
</concept>
</conceptSet>Properties that use this scheme are resolved through the <catalog> in the Item in which they appear, e.g. the Item contains the following property in <itemMeta>:
<role qcode="ex-wflow:release"and the catalog statement:
<catalog>
<scheme alias="ex-wflow" uri="http://cv.example.org/schemes/wfroles/" />
</catalog>The receiver needs to add an intermediate role in the workflow, representing a "final review" stage. Thus the private scheme in Case 2 is extending the original scheme. Unlike Case 1, where the codes in the private scheme were identical to codes contained in the original scheme, In Case 2, the concepts in the private scheme use a <sameAs> property at the level of each code in the new private scheme.
<conceptSet>
<concept>
<conceptId qcode="ex-iwf:draft" />
<sameAs qcode="ex-wflow:draft" />
...
</concept>
<concept>
<conceptId qcode="ex-iwf:review" />
<sameAs qcode="ex-wflow:review" />
...
</concept>
<concept>
<conceptId qcode="ex-iwf:finalreview" />
...
</concept>
<concept>
<conceptId qcode="ex-iwf:release" />
<sameAs qcode="ex-wflow:release" />
...
</concept>
</conceptSet>G2 Items that use this scheme must use a <catalog> statement to enable the processor to resolve both the private "ex-iwf" scheme alias and the original "ex-wflow" scheme alias:
<catalog>
<scheme alias="ex-iwf" uri="http://support.myorg.com/cv/workflow/" />
<scheme alias="ex-wflow" uri="http://cv.example.org/schemes/wfroles/" />
</catalogA Knowledge Item containing <sameAs>, <broader>, or <narrower> properties like the above must also contain a <catalog> allowing the QCodes to be resolved, in this case:
<catalog>
<scheme alias="ex-wflow" uri="http://cv.example.org/schemes/wfroles/" />
</catalog>13.9. Best Practice in QCode exchange
NewsML-G2 specifies that concepts must be identified by a full URI conforming to RFC 3986. The IPTC also recommends that a URI identifying a scheme and concept should resolve to a resource providing information about the scheme or the concept and which is either human or machine readable. In other words, a Concept URI should be a URL.
The unreserved characters that are permitted in a URL are:
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
a b c d e f g h i j k l m n o p q r s t u v w x y z
0 1 2 3 4 5 6 7 8 9 - _ . ~
the reserved characters are:
! * ' ( ) ; : @ & = + $ , / ? % # [ ]
In order to promote unambiguous processing of QCodes, the IPTC defines that it is the responsibility of providers to encode Concept URIs as they are intended to be valid for a system which resolves them and not to rely on end-users applying per-cent encoding rules for URI processing. Therefore:
-
Providers should decide whether or not to per-cent encode reserved characters used in QCodes distributed to customers in NewsML-G2 documents.
-
Receivers should not perform per-cent encoding/decoding, when resolving QCodes according to the rules outlined below.
The reason for the recommendation is illustrated by the following example of a provider distributing a document containing:
<subject qcode="fc:3#FTSE" />The catalog entry for a parent Scheme is (say):
<scheme alias="fc" uri="http://cv.example.org/schemes/fc/" />The receiver could transform this QCode literally to this URI:
Or the receiver could percent-encode the # (%23), yielding:
The resources identified by these two URIs are both valid by RFC 3986 but they are different!
Following the IPTC definition, the provider must include the per-cent encoding into the QCode of the first example if this is required by the system resolving the URIs:
<subject qcode="fc:3%23FTSE" />13.9.1. Non-ASCII characters
The encoding described above assumes that the character(s) to be per-cent encoded are from the US-ASCII character set (consisting of 94 printable characters plus the space).
If a code contains non-ASCII characters, for example accented characters, the Unicode encoding UTF-8 must be used, in line with normal practice.
For example, the UTF-8 encoding of the å character is a two-byte value
of C3hex A5hex which would be percent-coded as %C3%A5.
13.9.2. White Space in Codes
Codes in controlled vocabularies which have been created with no regards to the NewsML-G2 specifications may contain spaces. As the NewsML-G2 Specification does not allow white space characters in Codes, this section recommends a workaround.
Whitespace characters in Codes - in practice, only spaces (20hex) -
are replaced by a sequence of one or more unreserved characters that is
reused for this purpose according to the practices of the provider; it
is recommended that such a sequence is not part of the any of the codes
used by the provider.
For example, if a code contains a space, the space character might be
replaced by ~~. Receivers would be informed to translate this string
back to a space character in order to match the QCode against a list of
codes that contain spaces.
13.10. Syntactic Processing of QCodes
This section provides a summary of the processing model. Please also see the NewsML-G2 Specification for a full technical description. (This can be downloaded by visiting www.newsml-g2.org/spec.)
13.10.2. Processing Received Codes
To resolve a QCode received in an Item to a Concept URI, use the following steps:
-
Apply any XML decoding to the string (this should be performed by your XML processor)
-
Retrieve the QCode value from the document
example:fôô:bår -
Identify the first colon starting from the left; the string on left of the colon is the scheme alias, the string on the right of the colon is the code. If there is no colon, the QCode is invalid. In the example, therefore:
Scheme Alias =fôô
Code Value =bår -
Check whether the alias is defined in a catalog. If not, the QCode is invalid.
example:<scheme alias="fôô" uri="http://cv.example.org/cv/somecodes/" /> -
Append the Code Value to the Scheme URI to make the full Concept URI:
example:http://cv.example.org/cv/somecodes/bår -
It is highly recommended to use only full Concept URIs to compare identifiers of concepts.
13.11. A generic way to express concept identifiers as URIs
When NewsML-G2 was originally designed, communication capacity constraints drove implementers to find a compact way to express the typically long globally unique identifier (URI) of a concept; this led to the creation of the compact QCode notation. In NewsML-G2 version 2.11, @uri was introduced for properties having a concept identifier value type. This was restricted to properties that used @qcode or @literal to hold the identifier, but additionally allowed providers to express the full URI if required. Example:
<subject uri="http://example.com/people?id=12345&group=223" />The same flexibility was made available to properties with QCode or QCodeList attribute types in version 2.18. New URI sibling attributes (IRIType) were added to these properties by appending "uri" to the QCode name. For example @rendition gets a @renditionuri sibling, such that:
<remoteContent rendition="rnd:highRes"
... />may now be alternatively expressed as:
<remoteContent renditionuri="http://cv.iptc.org/newscodes/rendition/highRes"
... />Implementers are advised NOT use both QCode and URI type attributes for the same property; however, if a @qcode and @uri are both present, they MUST refer to the same semantic concept, and the resolved @qcode SHOULD be the same as the @uri. The following extract shows how the <contentSet> of the code listing from the Pictures and Graphics chapter would use the URI sibling properties:
<contentSet>
<remoteContent renditionuri="http://cv.iptc.org/newscodes/rendition/highRes"
href="./GYI0062134533.jpg"
version="1"
size="346071"
contenttype="image/jpeg"
width="1500"
height="1001"
colourspaceuri="http://cv.iptc.org/newscodes/colorspace/AdobeRGB"
orientation="1"
layoutorientationuri="http://cv.iptc.org/newscodes/layoutorientation/horizontal">
<altId type="ex-gyiid:masterID">105864332</altId>
...
</contentSet>This code is listed in full in the file LISTING 3A Photo in NewsML-G2 (URI sibling attributes).xml, which is part of the set of code examples in the Guidelines download package.
For a full list of QCode type attributes and their URI siblings see the table List of QCode attributes and their URI siblings below
13.11.1. Change to cardinality of QCode Type attributes
After the introduction of @uri and later the "URI Sibling" attributes, a @qcode and other QCodeType attributes (collectively termed "QCode") remained mandatory for some properties. From v2.20 this constraint is lifted and the cardinality of QCode attributes in these properties is changed from (1) to (0..1) in order to allow @uri and "URI sibling" attributes to be used on their own. The table Properties affected by changed cardinality of QCode attributes below lists the properties affected by lifting the mandatory use of QCodes. The rules are now as follows, according to the version of NewsML-G2 being used:
| NewsML-G2 version | Rule |
|---|---|
Up to 2.11 |
A QCode is mandatory for the affected attributes. |
2.11 to 2.19 |
A QCode AND a full URI MAY be used. The QCode is mandatory. (from 2.18, some URI Sibling attributes were constrained by this rule.) |
2.20 onwards |
A QCode OR a full URI MUST be used for the affected properties. A QCode AND a URI MAY be used together but this is not recommended and in this case the QCode value takes precedence. |
13.12. Literal Identifiers
The NewsML-G2 Standard recognises that it is not always possible to use a QCode or URI as an identifier, therefore the NewsML-G2 Flexible Property type allows a @literal identifier or no identifier at all. For example, a CV may be understood by both receivers and providers, but the mapping of identifiers to concepts is managed and communicated outside NewsML-G2. Many long-established CVs such as these pre-date NewsML-G2. In other circumstances, the identifier may add no value, because only some basic property, such as <name> needs to be conveyed.
A @literal is an identifier which is intended to be processed by software; it is not intended to be a natural-language label. If the name of a concept identified by @literal is intended for display, the IPTC recommends that providers SHOULD add the <name> child element for inter-operability and language-independent processing. If no human-readable property is available, receivers MAY use the @literal value for display purposes.
13.12.1. Use of @literal in a NewsML-G2 Item
Literals may be used as in the following cases:
1. As an identifier for linking with an assert element inside a NewsML-G2 document. In this case the literal value could be a random one. If a literal value is used with an assert element then all instances of that literal value in that item must identify the same concept.
2. When a code from a vocabulary which is known to the provider and the recipient is used without a reference to the vocabulary. The details of the vocabulary are, in this case, communicated outside NewsML-G2. Such a contract could express that a specific vocabulary of literals is used with a specific property.
3. When importing metadata which may contain codes which have not yet been checked to be from an identified vocabulary: the code values are represented as literals until the vocabulary is identified; thereafter, a controlled identifier can be used.
The following rules govern the use of @literal:
-
A @literal value can only be used to identify a concept within the local scope of an Item.
-
The use of @literal and a controlled identifier (either @qcode, @uri or both) is mutually exclusive.
-
There can be no guarantee that all instances of a @literal value used in an Item identify the same concept. However, when @literal is used with an assert element, providers MUST ensure all instances of that literal value in the Item identify the same concept. If the provider uses the same literal value for different concepts, an assert element using this literal value MUST NOT be used, as the concept is indeterminate.
13.12.2. Properties with no identifier
It is permissible for a NewsML-G2 element with a Flexible Property type to have no concept identifier:
<provider>
<name>Getty Images North America</name>
</provider>As a special case, when a <bag> child element is used with a property to create a composite concept, a concept identifier MUST NOT be used with the parent property (neither @qcode, nor @uri nor @literal). The new composite concept is created by the multiple existing concepts identified by a @qcode in each <bit> element of the <bag>:
<subject>
<name>Bread</name>
<bag>
<bit qcode="ex-ingredient:flour"/>
<bit qcode="ex-ingredient:water"/>
<bit qcode="ex-ingredient:yeast"/>
</bag>
</subject>13.13. Full list of the QCode type attributes and their URI siblings
| Attribute Name | URI Sibling Attribute | Attribute Name | URI Sibling Attribute | |
|---|---|---|---|---|
qcode |
uri |
radunit |
radunituri |
|
accesstype |
accesstypeuri |
ratertype |
ratertypeuri |
|
aspect |
aspecturi |
ratingtype |
ratingtypeuri |
|
audiochannels |
audiochannelsuri |
rel |
reluri |
|
audiocodec |
audiocodecuri |
rendition |
renditionuri |
|
colourindicator |
colourindicatoruri |
renditionref |
renditionrefuri |
|
colourspace |
colourspaceuri |
reposrole |
reposroleuri |
|
confirmationstatus |
confirmationstatusuri |
representation |
representationuri |
|
creator |
creatoruri |
role |
roleuri |
|
durationunit |
durationunituri |
scaleunit |
scaleunituri |
|
encoding |
encodinguri |
scope |
scopeuri |
|
environment |
environmenturi |
severity |
severityuri |
|
format |
formaturi |
symbolsrc |
symbolsrcuri |
|
hashtype |
hashtypeuri |
target |
targeturi |
|
heightunit |
heightunituri |
tech |
techuri |
|
how |
howuri |
timeunit |
timeunituri |
|
idformat |
idformaturi |
type |
typeuri |
|
interactiontype |
interactiontypeuri |
valcalctype |
valcalctypeuri |
|
jobtitle |
jobtitleuri |
valueunit |
valueunituri |
|
layoutorientation |
layoutorientationuri |
videocodec |
videocodecuri |
|
market |
marketuri |
videodefinition |
videodefinitionuri |
|
marketlabelsrc |
marketlabelsrcuri |
videoscaling |
videoscalinguri |
|
mode |
modeuri |
why |
whyuri |
|
part |
parturi |
widthunit |
widthunituri |
|
pubconstraint |
pubconstrainturi |
13.14. Properties affected by changed cardinality of QCode attributes
(The mandatory use of the QCode Attribute was lifted.)
| Property Name | QCode Attribute Name | URI Attribute Name |
|---|---|---|
action |
qcode |
uri |
itemClass |
qcode |
uri |
pubStatus |
qcode |
uri |
…./itemMeta/role |
qcode |
uri |
…./partMeta/role |
qcode |
uri |
…./itemMeta/service |
qcode |
uri |
…./newsCoverage/service |
qcode |
uri |
signal |
qcode |
uri |
bit |
qcode |
uri |
conceptId |
qcode |
uri |
type |
qcode |
uri |
confirmation* |
qcode |
uri |
occurStatus |
qcode |
uri |
newsCoverageStatus |
qcode |
uri |
accessStatus |
qcode |
uri |
hash |
hashtype |
hashtypeuri |
userinteraction |
interactiontype |
interactiontypeuri |
circle |
radunit |
radunituri |
all <..ExtProperty> |
rel |
reluri |
group |
role |
roleuri |
rating |
scaleunit |
scaleunituri |
timedelim |
timeunit |
timeunituri |
eventDetails/dates/start |
confirmationstatus |
confirmationstatusuri |
endeventDetails/dates/ |
confirmationstatus |
confirmationstatusuri |
eventDetails/dates/duration |
confirmationstatus |
confirmationstatusuri |
*Note: property deprecated |
14. Events in NewsML-G2
14.1. A standard for exchanging news event information
The sharing of event-related information and planning of news coverage is a core activity of news organisations, without which they cannot function effectively.
News agencies need to keep their customers informed of upcoming events and planned coverage. News organisations publishing on paper and digital media need to plan and co-ordinate their operations in order to make optimum use of their available resources and ensure their target audiences will be properly served.
Historically, this was a paper-based exercise, with news desks maintaining a Day Book, or Diary, and circulating information to colleagues and partners using written memoranda, sometimes referred to as the Schedule, or Budget.
Many organisations have moved, or are moving, to electronic scheduling applications. With software developers and vendors working independently on these applications, there is a risk that incompatibility will inhibit the exchange of information and reduce efficiency.
Consequently, there has been a drive among IPTC members to formalise a standard for exchanging this information in a machine-readable events format using XML, allowing it to be processed using standard tools and enabling compatibility with other XML-based applications and popular calendaring applications such as Microsoft Outlook.
The related NewsML-G2 Planning Item can be combined with Event information so that news organisations can plan their response to news events, such as job assignments, content planning and content fulfilment, sharing this if required with partners in a workflow. (See Editorial Planning – the Planning Item)
NewsML-G2 Events may be used to send and receive all, or part of, the information about:
-
a specific news event.
-
a range of news events filtered according to some criteria – an event listing.
-
updates to news events.
-
people, organisations, objects and other concepts linked to news events.
14.1.1. Business Advantages
An event managed using NewsML-G2 can serve as the "glue" that binds together all of the content related to a news story. For example, a news organisation learns of the imminent merger of two companies. This story can be pre-planned using Events in NewsML-G2 and assigned a unique Event ID by the event planning workflow, in the form of a QCode. When content related to this event is created (text, pictures, graphics, audio, video and packages), all of the separately-managed content to be associated using the QCode as a reference.
The result is that when users view content about this story, they can be provided with navigation to any other related content, or they can search for the related content.
The NewsML-G2 Events standard is the result of detailed collaborative work by IPTC experts operating in diverse markets throughout North America, Europe and Asia Pacific, highly experienced in the planning of news operations and the issues involved.
Adopters therefore have access to an "off the shelf" data model built on the specific needs of the news industry that can nevertheless be extended by individual organisations where necessary to add specialised features. The Events model is evolving as new requirements become known, and the IPTC endeavours to main compatibility with previous versions, giving users a straightforward upgrade path.
The NewsML-G2 Events model complies with the Resource Description Framework (RDF) promulgated by the W3C, which is a basic building block of the Semantic Web, and aligns with the iCalendar.
| A mapping of iCalendar properties to NewsML-G2 properties can be found in the NewsML-G2 Specification Page on the NewsML-G2 web site. See also IETF iCalendar Specification RFC 5545 specification that is supported by popular calendar and scheduling applications. |
There is considerable scope for using events planning to improve the efficiency and quality of news production, since an estimated 50-80% of news provision is of events that are known about in advance. When a pre-planned event is accessible from an editorial system, metadata from the event may be inherited by the news content associated with that event; this makes the handling of the news faster and more consistent. There is also an improvement in quality, since the appropriateness and accuracy of metadata may be checked at the planning stage, rather than under the pressure of a deadline.
The advantages of using a common standard to promote the efficient exchange of information are well understood. Using NewsML-G2 Events, providers can develop planning and scheduling products with greater confidence that the information can be consumed by their customers; recipients can cut development costs and time to market for the savings and services that flow from an efficient resource planning system that aligns with their operational model.
14.1.2. Events Structure
Events in NewsML-G2 use the same building blocks as all other NewsML-G2 Items:
-
Events use NewsML-G2 identification and versioning properties.
-
The <itemMeta> block holds management information about the Item.
-
The <contentMeta> block holds common administrative metadata about the event, or events, conveyed by the NewsML-G2 object.
| Please read the NewsML-G2 Basics chapter before reading this Chapter. |
There are two methods for expressing events using NewsML-G2, each suited to a particular type of information, or application, as shown in the diagram below:
-
Persistent event information that will be referenced by other events and by other NewsML-G2 Items is instantiated as Concept Items containing an <eventDetails> wrapper, or as members of a set of Event Concepts in a Knowledge Item. Events expressed as a Concept with a Concept ID are persistent and can be unambiguously referenced by other Items over time.
-
Transient event information that is "standalone" and volatile can be conveyed in NewsML-G2 using an <events> structure inside a News Item. Events expressed as an <event> in a News Item have no Concept ID and cannot be referenced from other Items.
These differences are illustrated in the following diagram:
Managed (persistent) events would be appropriate when a provider makes each of the announced events uniquely identifiable. The event information can then be stored by the receivers and any updates to events can be managed. This model also enables content to be linked to events using the unique event identifier, and this enables linking and navigation of content related to news stories.
A "standalone" implementation would be used when an organisation periodically announces to its partners and customers lists of forthcoming events. These may be for information only and not managed by the provider. So, for example, a daily list may repeat items that appeared in a weekly list, but there is no link between them, and nothing to indicate when an event has been updated.
14.2. Event Information – What, Where, When and Who
In a news context, events are newsworthy happenings that may result in the creation of journalistic content. Since news involves people, organisations and places, NewsML-G2 has a flexible set of properties that can convey details of these concepts. There is also a fully-featured date-time structure to express event occurrences, which conforms to the iCalendar specification.
14.2.1. Complete Listing for an example Event
The following example shows a news event expressed as a Concept and conveyed within a Concept Item.
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-event, ex-frel and ex-ventyp.
<?xml version="1.0" encoding="UTF-8"?>
<conceptItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20160422:qqwpiruuew4711"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en">
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://www.example.com/events/event-catalog.xml" />
<itemMeta>
<itemClass qcode="cinat:concept" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-10-18T13:05:00Z
</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<urgency>5</urgency>
<contentCreated>2016-01-16T12:15:00Z</contentCreated>
<contentModified>2022-06-12T13:35:00Z</contentModified>
</contentMeta>
<concept>
<conceptId created="2022-01-16T12:15:00Z" qcode="ex-event:1234567" />
<type qcode="cpnat:event" />
<name>IPTC Autumn Meeting 2022</name>
<eventDetails>
<dates>
<start>2022-10-26T09:00:00Z</start>
<duration>P2D</duration>
</dates>
<location>
<name>86, Edgeware Road, London W2 2EA, United Kingdom</name>
<related rel="ex-frel:venuetype" qcode="ex-ventyp:confcentre" />
<POIDetails>
<position latitude="51.515659" longitude="-0.163346" />
<contactInfo>
<web>https://www.etcvenues.co.uk</web>
</contactInfo>
</POIDetails>
</location>
<participant qcode="eprol:director">
<name>Brendan Quinn</name>
<personDetails>
<contactInfo>
<email>mdirector@iptc.org</email>
</contactInfo>
</personDetails>
</participant>
</eventDetails>
</concept>
</conceptItem >The top level element of the Concept Item is <conceptItem>. The document must be uniquely identified using a GUID. By this means, event information re-sent using the same GUID and an incremented version number, allows the receiver to manage, update or replace the conveyed concept (event) information.
@guid and @version uniquely identify the Concept Item, for the purpose of managing and updating the event information. Items that reference the event itself MUST use the Concept ID. This is because the Concept ID uniquely references a persistent Web resource, whereas the GUID only identifies a document that may or may not persist.
To enable concepts to be identified by a Concept ID QCode, a reference to the provider’s catalog (or a catalog statement containing the scheme URI) MUST be included:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<conceptItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:iptc.org:20160422:qqwpiruuew4711"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en">
<catalogRef
href="http://www.iptc.org/std/catalog/IPTC-G2-standards_37.xml" />
<catalogRef
href="http://www.example.com/events/event-catalog.xml"
/>In the mandatory <itemMeta> wrapper the IPTC "Nature of Concept Item" NewsCodes expresses the type of Concept Item. (This is complementary to the "Nature of News Item" NewsCodes used with a News Item.) There are currently two values: "concept" and "scheme". (Scheme is used for Knowledge Items.)
<itemMeta>
<itemClass qcode="cinat:concept" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-10-18T13:05:00Z
</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>The Content Metadata for a Concept Item may contain only Administrative Metadata:
<contentMeta>
<urgency>5</urgency>
<contentCreated>2016-01-16T12:15:00Z</contentCreated>
<contentModified>2022-06-16T13:35:00Z</contentModified>
</contentMeta>14.2.2. What is the Event?
In order to convey event information, we first need to describe "what" the event is. In NewsML-G2, events MUST have at least one Event Name, a natural language name for the event. They MAY additionally have one or more natural language Definitions, properties that describe characteristics of the event, and Notes.
This Event content is contained in the <concept> wrapper. A Concept Item
has one, and only one, <concept> wrapper. Each Concept must carry a
<conceptId>, a QCode value that will provide a way for other Items to
reference the Concept. The type of concept being conveyed is expressed
using the <type> element with a QCode to tell the receiver that it
contains Event information, using the IPTC "Nature of Concept"
NewsCodes. (The applicable value for an Event Concept is "event")The
Scheme URI is http://cv.iptc.org/newscodes/cpnature/
and recommended Scheme Alias is "cpnat".
The event information is placed directly inside an <eventDetails> wrapper:
<concept>
<conceptId created="2012-10-16T12:15:00Z" qcode="ex-event:1234567"/>
<type qcode="cpnat:event" />
<name>IPTC Autumn Meeting 2022</name>
<eventDetails>
...
</eventDetails>
</concept>The generic properties of Events are similar to those of Concepts, covered in Concepts and Concept Items. In this framework, we can expand the "what" information of an Event by indicating one or more relationships to other events, using the properties of Broader, Narrower, Related and SameAs. (See Event Relationships)
14.2.3. When does the Event take place?
The "when" of an event uses the Dates wrapper to express the dates and times of events: the start, end, duration and recurrence.
<dates>
<start>2022-10-26T09:00:00Z</start>
<duration>P2D</duration>
</dates>Although start and end times may be specified precisely, in the real world of news, the timing of events is often imprecise. In the early stages of planning an event, the day, month or even just the year of occurrence may be the only information available. Providers also need to be able to indicate a range of dates and/or times of an event, with a "best guess" at the likely date-time. (See Dates and times for details)
14.2.4. Where does the Event take place?
The "where" of an event is expressed using Location, a rich structure containing detailed information of the event venue (or venues); including GPS coordinates, seating capacity, travel routes etc.
<location>
<name>86, Edgeware Road, London W2 2EA, United Kingdom</name>
<related rel="ex-frel:venuetype" qcode="ex-ventyp:confcentre" />
<POIDetails>
<position latitude="51.515659" longitude="-0.163346" />
<contactInfo>
<web>https://www.etcvenues.co.uk</web>
</contactInfo>
</POIDetails>
</location>Note that if in-depth location details are given in the Event structure, this is a "one-time" use of the information. This structure might be better used as part of a controlled vocabulary of locations, in which case the structures may be copied from a referenced concept containing the location information.
See Further Properties of Event Details for details of Location and a comprehensive list of other Event properties.
14.2.5. Who is involved?
Details of "who" will be present at an event are given using the Participant property. This can expressed simply using a QCode, URI or literal value, supplemented by a human-readable Name property, or optionally using additional properties describing the participants, their roles at the event, and a wealth of related information.
<participant qcode="eprol:director">
<name>Brendan Quinn</name>
<personDetails>
<contactInfo>
<email>mdirector@iptc.org</email>
</contactInfo>
</personDetails>
</participant>Note use of the IPTC Event Participant Role New Code (Scheme URI http://cv.iptc.org/eventparticipantrole/), with recommended Scheme Alias of "eprol" The event organisers are also an important part of the "who" of an event. A set of Organiser and Contact Information properties can give precise details of the people and organisations responsible for an event, and how to contact them. See Further Properties of Event Details for details
14.3. Event Coverage
The NewsML-G2 Planning Item is used to inform customers about content they can expect to receive and if necessary the disposition of staff and resources. (See Editorial Planning – the Planning Item).
The link between an Event and the optional Planning Item is created using the Event ID. The Planning Item conveys information about the content that is planned in response to the Event, including the types of content and quantities (e.g. expected number of pictures). The Planning Item also has a Delivery structure which enables the tracking and fulfilment of content related to an Event.
14.4. Event Properties in more detail
The examples below show the basic properties of events, starting with the Name and Definition of the event, with other descriptive details, moving on to show how relationships, location, dates and other details may be expressed.
14.4.1. Event Description
In the code sample that follows, we will begin to create an event using four properties:
-
Event Name is an internationalised string giving a natural language name of the event. More than one may be used, for example if the Name is expressed in multiple languages.
-
Definitions, two differentiated by @role ("short" and "long") will be created using the Block element template (which allows some mark-up).
-
Notes – also Block type elements – give some additional natural language information, which is not naturally part of the event definition, again using @role if required.
-
Using Related, the nature of the Event can be refined and other properties of an Event can be expressed.
| Property | Type | Cardinality | Notes |
|---|---|---|---|
<name> |
Intl String |
1..n |
The name of the event, with optional @role for each <name> used |
<definition> |
Block |
1..n |
A natural language definition. |
<related> |
Flexible |
0..n |
The nature of the event, and other information. The property is repeatable and may have a @rel attribute to indicate the relationship to the characteristic. See the examples for alternative ways to express related concepts. |
<note> |
Block |
0..n |
A repeatable natural language note of additional information about the event, with an optional @role. |
For example:
<name xml:lang="en">
Bank of England Monetary Policy Committee
</name>
<definition xml:lang="en" role="ex-definitionrole:short">
Monthly meeting of the Bank of England committee
that decides on bank lending rates for the UK.
</definition>
<definition xml:lang="en" role="ex-definitionrole:long">
The Bank of England Monetary Policy Committee meets each
month to decide on the minimum rate of interest that will
be charged for inter-bank lending in the UK financial
markets. <br />
</definition>
<!-- Using related with a QCode -->
<related qcode="ex-eventrel:meeting" />
<!-- alternative using URI -->
<related uri="http://www.example.com/meeting" />
<!-- alternative using value and valuedatatype -->
<related rel="ex-csrel:admission" value="7.0" valueunit="iso4217a:EUR"
valuedatatype="xs:decimal" />
<note role="ex-noterole:toeditors">
Note to editors: an embargoed press release of the +
minutes of the meeting will be released by the COI +
within two weeks.
</note>
<note role="ex-noterole:general">
The meeting was delayed by two days due to illness.
</note>14.4.2. Event Relationships
Large news events may be split into a series of smaller, manageable events, arranged in a hierarchy which can express parent-child and peer relationships.
A "master" event may be notionally split into sub-events, which in turn may be split into further sub-events without limit. Each event instance can be managed separately yet handled and conveyed within the context of the larger realm of events of which it forms a part using the concept relationships <broader>, <narrower>, <related> and <sameAs> relationship properties.
It is important to note from the above diagram that Broader, Narrower and Same As have specific relationships to the same type of Concept that is in this case Events. Related has no such restriction. thus:
-
Aquatics is Broader than Breast Stroke or Swimming or Diving, but not Opening Speech.
-
Diving is Narrower than Aquatics, but not Archery.
-
Aquatics may be the Same As Aquatics in some other taxonomy, but not necessarily the Same As Swimming or Diving in some other taxonomy.
-
Breast Stroke may be Related to an Event, a Person or other Concept Type.
The examples below show the use of the event relationship properties for the fictional Economic Policy Committee event:
| Property | Type | Notes |
|---|---|---|
<broader> |
Related Concept |
Repeatable. The event may be part of another event, in which case this can be denoted by <broader>. |
<narrower> |
Related Concept |
Repeatable. May be used to indicate that the event has related child events. In this case we want to notify the receiver that a child of this event is the scheduled medal ceremony. |
<related> |
Related Concept |
Repeatable. May be used to denote a relationship to another concept or event. In this case, we want to link the event to an organisation which is not a participant, but may later form part of the coverage of the event. We qualify the relationship using @rel and the IPTC Item Relation NewsCodes: |
<sameAs> |
Related Concept |
Repeatable. May be used to denote that this event is the same event in another taxonomy, for example another governing body’s taxonomy of events: |
For example:
<broader
type="cpnat:event" qcode="ex-events:TR2012-34625">
<name>Olympic Swimming Gala</name>
</broader>
<narrower qcode="ex-events:TR2012-34593">
<name>Men’s 100m Freestyle Medal Ceremony</name>
</narrower>
<related
rel="irel:seeAlso"
type="cpnat:organisation"
qcode="ex-org:asa">
<name>Amateur Swimming association</name>
</related>
<sameAs qcode="ex-iocevent:xxxxxx">
<name>Men’s 100m Freestyle</name>
</sameAs>14.4.3. Event Details Group
The first set of properties of Event Details is date-time information as described below. The further properties are described in Further Properties of Event Details
Dates and times
The IPTC intends that event dates and times in NewsML-G2 align with the iCalendar (iCal) specification. This does not mean that dates and times are expressed in the same FORMAT as iCalendar, but the implementation of NewsML-G2 properties that match iCalendar properties should be as set forth in the iCalendar specification.
The <dates> property contains the dates and times of the event, expressed using the child elements of <start>, <end>, and <duration>
-
The <start> is the date, optionally with a time, on which the event starts.
-
The <end> is the date, optionally with a time, at which the event finishes. Note that the end dates/times of events are non-inclusive. Therefore a one day event on September 14, 2011 would have a start date (2011-09-14) and would have EITHER an end date of September 15 (2011-09-15) OR a duration of one day (syntax: see in table below).
-
The <duration> of the event may be used in place of <end>. Either may be used, but not both.
The NewsML-G2 syntax for expressing start and end times of events is a valid calendar date with optional time and offset; the following are valid:
-
2011-09-22T22:32:00Z (UTC)
-
2011-09-22T22:32:00-0500
-
2011-09-22
The following are NOT valid:
-
2011-09-22T22:32Z (if time is used, all parts MUST be present.
-
2011-09-22T22:32:00 (if time is used, time zone MUST be present.
When specifying the duration of an event, the date-part values permitted by iCalendar are W(eeks) and D(ays). In XML Schema, the only permitted date-part values are Y(ears), M(onths) and D(ays). (The permitted time parts H(ours), M(inutes) and S(econds) are the same in both XML Schema and iCalendar.)
Note on iCalendar alignment
In order to remain aligned with the iCalendar specification, it is recommended that the date-time expressed by <end> is “exclusive”. For example, following the guidelines above, a one-day event could be expressed as:
<eventDetails>
<dates>
<start>2022-01-01</start>
<end>2022-01-02</end>
</dates>
...
</eventDetails>However, event information expressed like this would not be intuitive to the human reader, who could interpret this as a two-day event. The IPTC therefore strongly recommends when using <end>, that fully qualified date-times are expressed so that this event information is unambiguous, thus:
<eventDetails>
<dates>
<start>2022-01-01T00:00:00Z</start>
<end>2022-01-02T00:00:00Z</end>
</dates>
...
</eventDetails>
Alternatively, <start> and <duration> may be used:
<eventDetails>
<dates>
<start>2022-01-01</start>
<duration>1D</duration>
</dates>
...
</eventDetails>
The following table shows the permitted values for date-part in both standards
| Duration | XML Schema | iCalendar |
|---|---|---|
D(ays) |
||
W(eeks) |
||
M(onths) |
||
Y(ears) |
Since NewsML-G2 uses XML Schema Duration, ONLY the values listed as permitted under the XML Schema column can be used, and therefore W(eeks) MUST NOT be used.
In addition the IPTC recommends that to promote inter-operability with applications that use the iCalendar standard, Y(ears) or M(onths) SHOULD NOT be used; only D(ays) should be used for the date part of duration values.
Duration units can be combined, in descending order from left to right, for example:
-
P2D (duration of 2 days)
-
P1DT3H (1 day and 3 hours – note the "T" separator)
iCalendar specifies that if the start date of an event is expressed as a Calendar date with no time element, then the end date MUST be to the same scale (i.e. no time) or if using duration, the ONLY permitted values are W(eeks) or D(ays). In this case, only D(ays) may be used in NewsML-G2.
The following table lists the date-time properties of events details:
| Property | Type | Notes/Example | ||
|---|---|---|---|---|
<start> |
Approximate Date Time |
Mandatory, non-repeatable property has optional attributes: @approxstart, @approxend and @confirmationstatus (or its URI sibling @confirmationstatusuri). The date part may be truncated, starting on the right (days) according to the precision required, but MUST, at minimum, have a year, (However, note the IPTC recommendation on iCalendar alignment). For example:
The value of <start> expresses the date, optionally with a time, on which the event starts. With the information available, this might be a "best guess". By using @approxstart and @approxend it is possible to qualify the start date-time by indicating the range of date-times within which the start will fall. (Note: these are NOT the approximate start and end of the event itself, only the range of start date-times) @approxstart indicates the start of the range. If used on its own, the end of the range of dates is the date-time value of <start> For example, a possible start of an event on June 12, 2011, not before June 11, 2011, and no later than June 14 2011, would be expressed as: The Confirmation Status of <start> is expressed by a QCode using one of the recommended IPTC Event Date Confirmation NewsCodes (Scheme Alias http://cv.iptc.org/newscodes/eventdateconfirm/, recommended scheme alias "edconf"). This has values:
The @confirmationstatus may also be applied to <end> or <duration>, described below. |
||
<end> |
Approximate Date Time |
Non-repeatable element to indicate the exclusive end date and time of the event, and optionally a range of values in which it may fall, using the same property type and syntax as for <start> (See recommendation on iCalendar alignment) |
||
<duration> |
XML Schema Duration |
Non-repeatable. The time period during which the event takes place is expressed in the form:
* The IPTC recommends that these units should NOT be used. Example: The event will last for three hours. Note use of the "T" time separator even though no Date part is present. The <dates> wrapper may contain either an <end> date, or a <duration> but not both. |
||
<confirmation> |
QCode |
DEPRECATED as of NewsML-G2 v2.24 - the <confirmation> property is replaced by a @confirmationstatus attribute (alternative: confirmationstatusuri) on the Events Details properties of <start>, <end>, and <duration>. See the description of these properties, above. |
Recurrence Properties
This is a group of optional properties that may be used to specify the recurring instances of an event, and conforms to the iCalendar specification, including the use of the same enumerated values for properties such as Frequency (@freq). Recurrence MUST be expressed using EITHER
<rDate>: one or more explicit date-times that the event is repeated, OR
<rRule>: one or more rules of recurrence.
| Property | Type | Notes/Example |
|---|---|---|
<rDate> |
Date with optional Time |
Recurrence Date. Repeatable. If the recurrence occurs on a specific date, with an optional time part, or on several specific dates and times. |
<rRule> |
Recurrence Rule |
Repeatable. The property has a number of attributes that may be used to define the rules of recurrence for the event. The only mandatory attribute is @freq, an enumerated string denoting the frequency of recurrence. The enumerated values of @freq are:
@interval indicates how often the rule repeats as a positive integer. The default is "1" indicating that for example, an event with a frequency of DAILY is repeated EACH day. To repeat an event every four years, such as the Summer Olympics, the Frequency would be set to ‘YEARLY" with an Interval of "4": @until sets a Date with optional Time after which the recurrence rule expires: @count indicates the number of occurrences of the rule. For example, an event taking place daily for seven days would be expressed as: A group of @byxxx attributes (as per the iCalendar BYxxx properties) are evaluated after @freq and @interval to further determine the occurrences of an event: @bymonth, @byweekno, @byyearday, @bymonthday, @byday, @byhour, @byminute, @bysecond, @bysetpos. The following code and explanation is based on an example from the iCalendar Specification at http://www.ietf.org/rfc/rfc5545.txt First, the interval="2" would be applied to freq="YEARLY" to arrive at "every other year". Then, bymonth="1" would be applied to arrive at "every January, every other year". Then, byday="SU" would be applied to arrive at "every Sunday in January, every other year". Then, byhour="8 9" (note that all multiple values are space separated) would be applied to arrive at "every Sunday in January at 8am and 9am, every other year". Then, byminute="30" would be applied to arrive at "every Sunday in January at 8:30am and 9:30am, every other year". Then, lacking information from rRule, the second is derived from <start>, to end up in "every Sunday in January at 8:30:00am and 9:30:00am, every other year". Similarly, if any of the @byminute, @byhour, @byday, @bymonthday or @bymonth rule part were missing, the appropriate minute, hour, day or month would have been retrieved from the <start> property. The @bysetpos attribute contains a non-zero integer "n" between ‑366 and 366 to specify the nth occurrence within a set of events specified by the rule. Multiple values are space separated. It can only be used with other @by* attributes. For example, a rule specifying monthly on any working day would be /> The same rule to specify the last working day of the month would be @wkst indicates the day on which the working week starts using enumerated values corresponding to the first two letters of the days of the week in English, for example "MO" (Monday), SA (Saturday), as specified by iCalendar. |
<exDate> |
Date with optional Time |
Excluded Date of Recurrence. An explicit Date or Dates, with optional Time, excluded from the Recurrence rule. For example, if a regular monthly meeting coincides with public holidays, these can be excluded from the recurrence set using <exDate> |
<exRule> |
Recurrence Rule |
Excluded Recurrence Rule. The same attributes as <rRule> may be used to create a rule for excluding dates from a recurring series of events. For example, a regular weekly meeting may be suspended during the summer. Note the order of the above statement: the <rRule> elements must come before <exRule> The meaning being expressed is: "The event occurs weekly until Dec 24, 2011 with a break from after July 23, 2011 until September 3, 2011." |
Further Properties of Event Details
The event details group are wrapped by the <eventDetails> element
| Property | Type | Notes/Example |
|---|---|---|
<occurStatus> |
QCode |
Optional, non-repeatable property to indicate the provider’s confidence that the event will occur. The IPTC Event Occurrence Status NewsCodes scheme has values indicating the provider’s confidence of the status of the event, for example "Planned, occurrence uncertain" |
<newsCoverageStatus> |
Qualified Property |
Optional, non-repeatable element to indicate the status of planned news coverage of the event by the provider, using a QCode and (optional) <name> child element: |
<registration> |
Block |
Optional, repeatable indicator of any registration details required for the event: The property optionally takes a @role attribute. IPTC Registration Role NewsCodes may be used, which currently has four values:
|
<accessStatus> |
QCode |
Optional, repeatable property indicating the accessibility, the ease (or otherwise) of gaining physical access to the event, for example, whether easy, restricted, difficult. The QCodes represent a CV that would define these terms in more detail. For example, "difficult" may be defined as "Access includes stairways with no lift or ramp available. It will not be possible to install bulky or heavy equipment that cannot be safely carried by one person". Note that the IPTC does not currently define such a vocabulary. |
<subject> |
Flexible Property |
Optional, repeatable. The subject classification(s) of the event, for example, using the IPTC Subject NewsCodes: |
<location> |
Flexible Property/ |
Repeatable property indicating the location of the event with an optional <name>. |
<participant> |
Flexible Property/ |
Optional, repeatable, The people and/or organisations taking part in the event. The type of participant is identified by @type and a QCode. The following example indicates a person, an organisation would be indicated (using the IPTC NewsCodes) by type="cpnat:organisation" An IPTC Event Participant Role NewsCode is available: that holds roles such as "moderator", "director", "presenter" |
<participationRequirement> |
Flexible Property |
Optional, repeatable element for expressing any required conditions for participation in, or attendance at, the event, expressed by a URI or QCode. The IPTC does not currently define a vocabulary of possible participation requirements. |
<organiser> |
Flexible Property/ |
Optional, repeatable. Describes the organiser of the event. The IPTC Event Organiser Role NewsCodes, viewable at http://cv.iptc.org/newscodes/eventorganiserrole/ lists types of organiser such as, "venue organiser", "general organiser", "technical organiser". |
<contactInfo> |
Wrapper element |
Indicates how to get in contact with the event. This may be a web site, or a temporary office established for the event, not necessarily the organiser or any participant. See Contact Information |
<language> |
- |
Optional, repeatable element describes the language(s) associated with the event using @tag with values that must conform to the IETF’s BCP 47. An optional child element <name> may be added. |
<newsCoverage> |
DEPRECATED. News Coverage is part of the NewsML-G2 Planning Item. (See Editorial Planning – the Planning Item) |
Contact Information
Contact information associated solely with the event, not any organiser or participant. For example, events often have a special web site and an event office which is independent of the organisers’ permanent web site or office address.
The <contactInfo> element wraps a structure with the properties outlined below. An event may have many instances of <contactInfo>, each with @role indicating the purpose. These are controlled values, so a provider may create their own CV of address types if required, or use the IPTC Event Contact Info Role NewsCodes (http://cv.iptc.org/newscodes/eventcontactinforole/ with recommended Scheme Alias of "ecirol"), which has values of "general contact", "media contact", ticketing contact".
Each of the child elements of <contactInfo> may be repeated as often as needed to express different @roles.
| Property Name | Element | Type | Notes |
|---|---|---|---|
Email Address |
<email> |
Electronic Address |
An “Electronic Address” type allows the expression of @role (QCode) to qualify the information, for example: <email role=“addressrole:office”> info@ecb.eu </email> |
Instant Message Address |
<im> |
Electronic Address |
<im role=“imsrvc:reuters”> jc.trichet.ecb.eu@reuters.net </im> |
Phone Number |
<phone> |
Electronic Address |
|
Fax Number |
<fax> |
Electronic Address |
|
Web site |
<web> |
IRI |
<web role=“webrole:corporate”> www.ecb.eu </web> |
Postal Address |
<address> |
Address |
The Address may have a @role to denote the type of address is contains (e.g. work, home) and may be repeated as required to express each address @role. |
Other information |
<note> |
Block |
Any other contact-related information, such as “annual vacation during August” |
For example:
<email role="ecirol:media">
office@iptc.org
</email>
<im role="ecirol:general">
jdoe.iptc.org@reuters.net
</im>
<phone role="ecirol:general">
1-123-456-7899
</phone>
<phone role="ecirol:media">
1-123-456-7898
</phone>
<web role="ecirol:ticketing">
www.iptc.org/springmeeting.html
</web>Address details <address>
The Address Type property may have a @role to indicate its purpose; the following table shows the available child properties. Apart from <line>, which is repeatable, each element may be used once for each <address>
For example:
<address role="ciprol:office">
<line>20 Garrick Street</line>
<locality>
<name xml:lang="en">London</name>
</locality>
<country qcode="iso3166-1a2:UK">
<name xml:lang="en">United Kingdom</name>
</country>
<postalCode>WC2E 9BT</postalCode>
</address>14.5. Multiple Event Concepts in a Knowledge Item
Information about multiple events can be assembled in a Knowledge Item, which conveys a set of one or more Concepts. In this example, we will use a Knowledge Item to convey two related events.
The top-level <knowledgeItem> element contains identification, version and catalog information, in common with other NewsML-G2 Items:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<knowledgeItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="urn:newsml:iptc.org:20110126:qqwpiruuew4712"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en">
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://www.example.com/events/event-catalog.xml"
/>The <itemMeta> block conveys Management Metadata about the document and the <contentMeta> block can convey Administrative Metadata about the concepts being conveyed, and in this case we can show Descriptive Metadata that is common to all of the concepts in the Knowledge item,
The Core Descriptive Metadata properties common to all NewsML-G2 Items that may be used in a Knowledge Item are: <language>, <keyword>, <subject>, <slugline>, <headline> and <description>.
<itemMeta>
<itemClass qcode="cinat:concept" />
<provider qcode="nprov:IPTC" />
<versionCreated>2021-18-10T12:00:00Z</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<urgency>5</urgency>
<contentCreated>2016-01-16T12:15:00Z</contentCreated>
<contentModified>2022-10-12T14:35:00Z</contentModified>
<subject qcode="medtop:20000304">
<name>media</name>
</subject>
<subject qcode="medtop:20000309">
<name>news agency</name>
</subject>
<subject qcode="medtop:20000763">
<name>IT/computer sciences</name>
</subject>
</contentMeta>The two events in the listing are related, with the relationship indicated by the second event using the <broader> property to show that it is an event which is part of the three-day event listed first
First event:
<conceptSet>
<concept>
<!-- FIRST EVENT! -->
<conceptId created="2022-10-26T12:15:00Z" qcode="ex-event:1234567" />
<name>IPTC Autumn Meeting 2022</name>
<eventDetails>
...Second event: a session on news gathering and verification below (ex-event:91011123) has a ‘broader’ relationship to the IPTC Autumn Meeting above (ex-event:1234567).
<concept>
<!-- SECOND EVENT! -->
<conceptId created="2022-09-36T12:00:00+00:00" qcode="ex-event:91011123" />
<name>Newgathering and Verification Strategy</name>
<broader type="cpnat:event" qcode="ex-event:1234567">
<name>IPTC Autumn Meeting 2022</name>
</broader>
<eventDetails>
...14.5.1. Full listing of the Event Knowledge Item
Note that although Knowledge Items are a convenient way to convey a set of related events, there is no requirement that all of the events in a KI must be related, or even that other concepts conveyed by the Knowledge Item are events; they may be people, organisations or other types of concept.
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-accst, ex-frel, ex-ventyp and ex-event.
<?xml version="1.0" encoding="UTF-8"?>
<knowledgeItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20101019:qqwpiruuew4712"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en">
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://www.example.com/events/event-catalog.xml" />
<itemMeta>
<itemClass qcode="cinat:concept" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-10-18T13:05:00Z
</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<urgency>5</urgency>
<contentCreated>2016-01-16T12:15:00Z</contentCreated>
<contentModified>2022-10-12T13:35:00Z</contentModified>
<subject qcode="medtop:20000304">
<name>media</name>
</subject>
<subject qcode="medtop:20000309">
<name>news agency</name>
</subject>
<subject qcode="medtop:20000763">
<name>information technology and computer science</name>
</subject>
</contentMeta>
<conceptSet>
<concept>
<!-- FIRST EVENT! -->
<!-- x -->
<conceptId created="2022-01-16T12:15:00Z" qcode="ex-event:1234567" />
<name>IPTC Autumn Meeting 2022</name>
<eventDetails>
<dates>
<start>2022-10-26T09:00:00Z</start>
<duration>P2D</duration>
</dates>
<registration>Registration with the IPTC office is required.
A <a href="https://iptc.org/moz/events/annual-general-meeting-2022/">
web form</a> may be used until 18 October 2022
</registration>
<participationRequirement>
<name>Membership</name>
<definition>Only members of the IPTC and their invited
guests may attend.
</definition>
</participationRequirement>
<accessStatus qcode="ex-access:easy" />
<language tag="en" />
<organiser qcode="nprov:IPTC" role="eorol:general">
<name>International Press Telecommunications Council</name>
<organisationDetails>
<founded>1965</founded>
</organisationDetails>
</organiser>
<contactInfo>
<email>mdirector@iptc.org</email>
<note>Brendan Quinn, Managing Director</note>
<web>http://www.iptc.org</web>
</contactInfo>
<location>
<name>86, Edgeware Road, London W2 2EA, United Kingdom</name>
<related rel="ex-frel:venuetype" qcode="ex-ventyp:confcentre" />
<POIDetails>
<position latitude="51.515659" longitude="-0.163346" />
<contactInfo>
<web>https://www.etcvenues.co.uk</web>
</contactInfo>
</POIDetails>
</location>
<participant qcode="eprol:moderator">
<name>Robert Schmidt-Nia</name>
<definition>Chairman of the Board of the IPTC</definition>
</participant>
<participant qcode="eprol:director">
<name>Brendan Quinn</name>
<definition>Managing Director</definition>
</participant>
</eventDetails>
</concept>
<concept>
<!-- SECOND EVENT! -->
<!-- x -->
<conceptId created="2022-01-16T12:00:00Z" qcode="ex-event:91011123" />
<name>Newgathering and Verification Strategy </name>
<broader type="cpnat:event" qcode="ex-event:1234567">
<name>IPTC Autumn Meeting 2022</name>
</broader>
<eventDetails>
<dates>
<start>2022-10-27T14:30:00Z</start>
<duration>PT30M</duration>
</dates>
<participationRequirement>
<name>Registration</name>
<definition>Pre-registration required for all attendees
</definition>
</participationRequirement>
<accessStatus qcode="ex-access:easy" />
<language tag="en" />
<participant qcode="eprol:presenter">
<name>Evi Varsou</name>
<definition>Presenter</definition>
</participant>
<participant qcode="eprol:moderator">
<name>Brendan Quinn</name>
<definition>Moderator</definition>
</participant>
</eventDetails>
</concept>
</conceptSet>
</knowledgeItem>14.5.2. Indicating changes to part of a Knowledge Item
When multiple Events are conveyed as Concepts in a Knowledge Item, and a sub-set of the Event Concepts is updated, providers may use the <partMeta> helper element to inform customers WHAT has changed in the new version of the Knowledge Item.
The <partMeta> element uses the standard XML ID/IDREF; the example shows the Event with @id="eventA" was modified on ‘2016-09-15’, as indicated by the Part Meta with @contentrefs="eventA":
<knowledgeItem
...>
<itemMeta>
...
</itemMeta>
<contentMeta>
...
</contentMeta>
<partMeta contentrefs="eventA">
<contentModified>2022-09-15</contentModified>
</partMeta>
<conceptSet>
<concept id="eventA">
<!-- FIRST EVENT! -->
<!-- x -->
<conceptId created="2022-08-30T12:00:00+00:00"
qcode="ex-event:1234567" />
...
</concept >
<conceptid="eventB">
<!-- SECOND EVENT! -->
<!-- x -->
<conceptId created="2022-08-30T12:00:00+00:00"
qcode="ex-event:91011123" />
...
</concept>
</conceptSet>
</knowledgeItem>14.6. Conveying Events in a NewsML-G2 Package
A news provider may wish to create a service that consists of collections of events that are significant to a specific editorial theme, for example, this could be the day’s Top Finance Events.
When such Events are available as Concept Items, they may be referenced in a Package using <itemRef> and @residref. (See the Packages chapter for details of the Package Item structure and Item references)
Alternatively, because they are managed and persistent Events identified using URIs, or their short format QCodes, collections of event concepts may be referenced within a Package <group> using Concept Reference <conceptRef> as follows:
<groupSet root="G1">
<group id="G1" role="ex-group:main">
...
<conceptRef type="cpnat:event"
qcode="ex-iptcevents:20081007135637.12">
<name xml:lang="fr">Barack Obama arrive à Washington</name>
</conceptRef>
...
</group>
</groupSet>Note the optional @type indicating that the referenced concept is an Event, and the optional <name> child element is a natural-language name for the event extracted from the concept being referenced.
Note the following guidelines on packaging Event Concepts:
-
"Hint" properties – these are properties extracted from the original concept and conveyed with the reference to the concept – are restricted to <name> only when using <conceptRef>. When using <itemRef>, ANY property may be extracted from the referenced Concept Item.
-
The provider must take care that "Hint" properties do not re-define the original concept. When a provider distributes concepts using Concept Items or Knowledge Items, changes to the original concept MUST be issued via an updated Concept Item and/or Knowledge Item and if a @version is used with the <itemRef>, @residref must be updated to correspond with the revised concept’s version.
-
If for the referenced concept a Concept Item is available then this concept’s Item MAY be referenced by <itemRef>; this is the preferred option. This MAY include Hint properties copied from the Concept Item.
-
If for the referenced concept a Concept Item is available then this concept MAY be referenced using <conceptRef> as a valid alternative option, for example when a package includes a mix of concepts for which some Concept Items are available and some are not available, but the provider wants to express the references in a consistent way. However, in a case such as this the constraint on the use of Hints has to be accepted.
-
If for a referenced concept there is no Concept Item and only a URI as identifier is available, then <conceptRef> MUST be used; no Hint properties, except a name, are available as there is no Concept Item available as a source for copying Hints.
The standard method for exchanging concept information in the NewsML-G2 context is the Knowledge Item, which is a container for concepts and the detailed properties of each concept being conveyed. A provider would use Knowledge Items to send comprehensive information about many events, and receivers might incorporate this information into their own editorial diary, or Day Book.
By contrast, when a Package is employed to reference Event concepts, this represents an Editorial product, in which a discrete number of events considered to be significant or pertinent to a particular topic, are selected and published.
The Events Package has the following characteristics:
-
The value of the package is in the journalistic judgement used to select the events, not in the compilation of the event information itself.
-
When using <conceptRef>, the package is a lightweight container that references each event and a human-readable name; no further details of the events are given. In this case, the package is transient in nature: it will not be referenced over time except as an archived item of editorial content.
-
It may be ordered to indicate the relative significance of the events in the context of the package, but no other relationship between the events is expressed or implied.
-
New versions of the Package may be published; events may be replaced or deleted from the package, but details of the events themselves cannot be changed.
The characteristics of a KI are:
-
It represents Knowledge; the value is in the compilation of the details about each event in the KI: the "when and where" and other practical information about each event.
-
The KI contains persistent information about each event concept that may be expected to be frequently used and if necessary updated over time.
-
The concepts in the KI cannot be ordered, but may be related.
-
New versions of the KI can be published and the concepts that it contains can be updated, but they must not be deleted, as this would break existing references to the concepts.
14.7. Events Workflow
The flow diagram shows how the News Provider creates and compiles event information and publishes it in a Knowledge Item, and that the Customer’s events management system subscribes to this information.
Later, the News Provider’s editorial team reviews the events database and creates an ordered list of the "Top Ten" news events of the day. The News Provider publishes the list as a Package Item. The Package Item is ingested by the Customer’s editorial system, and the Customer’s journalists use it as a guide in planning the news coverage of the day, looking up details of each event (hosted in the Knowledge Item) as needed.
14.8. Events in a News Item
Many news providers, particularly news agencies, provide their customers with event information as a list of events, for example a list of cultural events taking place in a city’s theatres. In many cases, these were provided as a text story, with minimal mark-up.
Conveying these events in a News Item as described below can be useful, as the structured mark-up enables them to be re-formatted by software, for example as tables or listings in print and online media. Note, however, that this is a limited and specific use case; events in this form are NOT persistent, and cannot be managed as part of the News Planning process (as described in Editorial Planning – the Planning Item).
The Content Set of the Events News Item uses the <inlineXML> element to convey an <events> wrapper containing one or more <event> instances, each of which is a separate self-contained set of event information:
<contentSet>
<inlineXML>
<events>
<event>
<name>NewSgathering and Verification Strategy</name>
<eventDetails>
<dates>
<start>2022-10-27T14:00:00Z</start>
<end>2022-10-27T14:30:00Z</end>
</dates>
</eventDetails>
</event>
</events>
</inlineXML>
</contentSet>The full listing is shown below. Note the Item Class of this News Item is "ninat:composite".
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-frel, ex-ventyp and ex-facilncd.
<?xml version="1.0" encoding="UTF-8"?>
<newsItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20090122:qqwpiruuew4711"
version="15" standard="NewsML-G2" standardversion="2.31" conformance="power"
xml:lang="en">
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<itemMeta>
<itemClass qcode="ninat:composite" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-10-18T12:44:00Z
</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentSet>
<inlineXML>
<events>
<!-- x -->
<!-- FIRST EVENT! -->
<!-- x -->
<event>
<name>IPTC Autumn Meeting 2022</name>
<eventDetails>
<dates>
<start>2022-10-26T09:00:00Z</start>
<duration>P2D</duration>
</dates>
<location>
<name>86, Edgeware Road, London W2 2EA, United Kingdom</name>
<related rel="ex-frel:venuetype" qcode="ex-ventyp:confcentre" />
<POIDetails>
<position latitude="51.515659" longitude="-0.163346" />
<contactInfo>
<web>https://www.etcvenues.co.uk</web>
</contactInfo>
</POIDetails>
</location>
</eventDetails>
</event>
<!-- x -->
<!-- SECOND EVENT! -->
<!-- x -->
<event>
<name>Annomarket text analytics EU project</name>
<eventDetails>
<dates>
<start>2022-10-22T10:00:00-04:00</start>
<end>2022-10-22T11:00:00-04:00</end>
</dates>
</eventDetails>
</event>
<!-- x -->
<!-- THIRD EVENT! -->
<!-- x -->
<event>
<name>Accidental Heroes</name>
<definition>
News stories and random incidents provide the inspiration behind
this new production from the Lyric Young Company, which blends the
inconsequential with the life-defining in a physical and visually
arresting new show.
<br />
The Lyric Young Company has worked with award-winning
writer/director Mark Murphy to create Accidental Heroes.
<br />
</definition>
<related rel="ex-frel:facility" qcode="ex-facilncd:Food" />
<related rel="ex-frel:facility" qcode="ex-facilncd:AirConditioning" />
<eventDetails>
<dates>
<start>2022-10-23T19:30:00Z</start>
<end>2022-02-05T23:59:59Z</end>
<rRule freq="DAILY" byday="TH FR SA" />
</dates>
</eventDetails>
</event>
</events>
</inlineXML>
</contentSet>
</newsItem>14.8.1. Adding event concept details to a News Item
Expressing Events as Concepts in a Concept Item gives implementers great scope for including and/or referencing events information in other Items, such as News Items conveying content. This is achieved by adding the event as a <subject> element of the <contentMeta> container. For example in 0 an event was conveyed as a concept within the Concept Set of a Knowledge Item:
<knowledgeItem
...>
<conceptSet>
<concept>
<!-- FIRST EVENT! -->
<!-- -->
<conceptId created="2022-01-16T12:15:00Z" qcode="ex-event:1234567" />
<name>IPTC Autumn Meeting 2022</name>
<eventDetails>
...
</eventDetails>
...
</knowledgeItem>The QCode ex-event:1234567 uniquely identifies the event, and later news coverage of the event can reference it using the <subject> element, as shown below:
<newsItem
...>
<contentMeta>
...
<subject type="cpnat:event" qcode="ex-event:12345657">
<name>IPTC Autumn Meeting 2022</name>
</subject>
...
</contentMeta>
...
</newsItem>Referencing an event using Subject enables News Items to be searched and/or grouped by event, and also helps end-users manage the content for events with a wide coverage and many delivered Items.
14.8.2. Using <bag> to create a composite concept
Providers can put an event and related concepts together to create a new composite concept using a <bag> child element of <subject>.
For example, a financial news service sends a News Item conveying content about a takeover of a small company by a larger global company. This takeover story has an event concept, which enables the provider to add a subject property containing the QCode of the Event:
<subject type="cpnat:event" qcode="ex-finevent:takeover123AB" />-
together with subject properties for each company:
<subject type="cpnat:organisation" qcode="isin:exampleSmallCompany" />
<subject type="cpnat:organisation" qcode="isin:exampleGlobalCompany" />However, a new, richer, composite concept combining the concept IDs for the Event and the two companies could be created instead using <bag>:
<newsItem ...>
...
<contentMeta>
...
<subject type="cpnat:abstract">
<name>GlobalCompany takes over SmallCompany</name>
<bag>
<bit type="cpnat:event" qcode="ex-finevent:takeover123AB" />
<bit type="cpnat:organisation" qcode="isin:exampleSmallCompany" />
<bit type="cpnat:organisation" qcode="isin:exampleGlobalCompany" />
</bag>
</subject>
...
</contentMeta>
...
</newsItem>Note that in this case, the <subject> does not have its own
identifier; these properties must NOT be used when <subject>
has a <bag> element
Using @significance with <bag>
An advantage of using the composite structure of <bag> is that implementers can "fine tune" the subject properties using @significance. This enables receiving applications to be more discerning on behalf of end-users, about how they filter and select news.
The significance of an event to all the concepts in a <bag> is not necessarily equal: for an end-user interested in news about a small company, the fact that it has been taken over by a large company is very significant. To the follower of news about the large company, the story may be less significant.
The code snippet below shows how the significance attribute would be used to refine the previous example, such that the event is more significant to the SmallCompany (100) compared to the GlobalCompany (10):
<subject type="cpnat:abstract">
<name>GlobalCompany takes over SmallCompany</name>
<bag>
<bit type="cpnat:event" qcode="ex-finevent:takeover123AB" />
<bit type="cpnat:organisation" qcode="isin:exampleSmallCompany" significance="100"/>
<bit type="cpnat:organisation" qcode="isin:exampleGlobalCompany" significance="10"/>
</bag>
</subject>|
The <bag> MUST contain one <bit> of type "cpnat:event" This feature was added from NewsML-G2 2.7 onwards. ONLY for the special case where the <bag> contains a <bit> referencing an event, may a @significance attribute be added to the other <bit> members of the <bag>. |
15. Editorial Planning – the Planning Item
News-gathering is not an ad-hoc process; as outlined in How News Happens, professional news organisations need to be well-organised so that resources are used effectively, customers get the news they need, in time, and editorial standards and quality are maintained.
News planning information can improve collaboration, and thus efficiency, in B2B news exchange, and for some news agencies and their media customers, this has become an important area of development.
The Planning Item addresses this need. As a "top level" NewsML-G2 Item, it is a sibling of News Item, Concept Item, Package Item and Knowledge Item.
The Planning Item carries the News Coverage information that was previously expressed by Event Concept Items under the <eventDetails> wrapper, and has also been expanded to include additional features, such as the ability to track news deliverables against a previously-announced manifest of objects.
There are a number of advantages to the separation of Events and Planning information, including:
-
News coverage information may change frequently in response to a news event. Previously, this would have meant re-sending all of the event information whenever the news planning changed. Now only the planning information is re-sent – a lighter processing overhead.
-
News coverage is not always in response to a news event taking place at a specific place and time; it is also topic-based, such as "The best ski resorts for this winter". Without the Planning Item, topic-based coverage such as this would require the creation of a "dummy" event as a placeholder for the coverage information. Now, no event information is required, merely a Planning Item that can carry the description of the topic and can be linked to the content once it is created.
-
Organisations needed a way to announce planned coverage of an event, in terms of (say) a number of pictures, then inform receivers of progress and fulfilment. A Planning Item can provide a list of Items that have been delivered. The complementary "Delivery Of" property, which has been added as a property of other Items, can also link individual Items back to a Planning Item.
-
Having news coverage information tightly-bound to an event caused issues when events span more than one news cycle. A single event may have multiple Planning Items spanning different time periods, so multiple <planning> child elements of <newsCoverage> can specify @coversfrom and @coversto attributes.
Planning Items typically focus on the delivery of coverage for a single event or topic, but can be linked to other Planning Items to facilitate the coverage of more complex or long-term events.
The structure of a Planning Item is common to other NewsML-G2 Items:
-
The top level <planningItem> properties of conformance, identification and versioning that we associate with "anyItem"
-
Item Metadata contained in the <itemMeta> wrapper
-
Administrative and Descriptive information related to the content wrapped in the <contentMeta> element.
-
Special-purpose elements <assert> and <inlineRef> to group details of concepts and to provide references from content to metadata (see 25.2 and 25.3 for details on the use of these elements)
-
Extension Points for providers to add properties from non-IPTC namespaces.
-
A wrapper for the content payload, in this case a <newsCoverageSet>.
15.1. Item Metadata <itemMeta>
The standard properties of <itemMeta> are available for use in a Planning Item. The <itemClass> property uses a mandatory planning-specific IPTC "Planning Item Nature" NewsCodes. The Scheme URI is: http://cv.iptc.org/newscodes/plinature/ and recommended Scheme Alias is "plinat":
<itemClass qcode="plinat:newscoverage" />15.2. Content Metadata <contentMeta>
The standard properties of the Administrative Metadata group may be used; a restricted set of Descriptive Metadata properties (the Core Descriptive Metadata Group, may be used. The Core Group is: <language>, <keyword>, <subject>, <slugline>, <headline>, <description>
15.3. <newsCoverageSet>
The <newsCoverageSet> wraps one or more <newsCoverage> components (see the diagram below). Typically, each <newsCoverage> component is bound to each different class of Item to be delivered, i.e. a Planning Item for two texts, ten pictures and one graphic could have three <newsCoverage> components.
15.4. <newsCoverage>
Each <newsCoverage> component MUST contain at least one <planning> element and optionally a <delivery> element.
15.5. <planning>
At its simplest level of implementation, planning information may be expressed using a repeatable Block type <edNote> to give a natural language description of the planned coverage, optionally with some mark-up:
<edNote>Picture scheduled 2022-11-06T13:00:00+02:00</edNote>Below is a complete example:
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies.
<?xml version="1.0" encoding="UTF-8"?>
<planningItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20101025:gbmrmdreis4711"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en">
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://www.example.com/events/event-catalog.xml" />
<itemMeta>
<itemClass qcode="plinat:newscoverage" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-10-18T13:45:00Z
</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<urgency>5</urgency>
<contentCreated>2016-10-16T12:15:00Z</contentCreated>
<contentModified>2022-10-16T13:35:00Z</contentModified>
</contentMeta>
<newsCoverageSet>
<newsCoverage>
<planning>
<edNote>Text 250 words</edNote>
</planning>
</newsCoverage>
<newsCoverage>
<planning>
<edNote>Picture scheduled 2022-11-06T13:00:00+02:00</edNote>
</planning>
<delivery>
<deliveredItemRef
guidref="tag:example.com,2008:ART-ENT-SRV:USA20081220098658">
</deliveredItemRef>
</delivery>
</newsCoverage>
</newsCoverageSet>
</planningItem>15.5.1. Advanced features of <planning>
Planning is able to populate a customer’s resource management applications with machine-readable information and detailed descriptive metadata, ready to be inherited by the arriving content, thus speeding up news handling and potentially increasing consistency and quality.
Used in this way, the Planning Item can bridge the workflows of provider and customer: the provider is seen as an available resource on the customer system with coverage information and news metadata capable of being updated in near real-time.
A key feature of the <planning> element is the ability to use <newsContentCharacteristics> to express comprehensive information about physical characteristics of the planned content, using the News Content Characteristics group of attributes. These are described in detail in the News Content Characteristics section of the NewsML-G2 Specification Document, which may be obtained by following the link at the IPTC NewsML-G2 resource page.
The attributes include physical properties of still images, video and audio, the line count of text content and the page count for content rendered as pages. Examples of their usage are given in the table below.
From NewsML-G2 version 2.23, the <planning> and <assignedTo> elements of <newsCoverage> have been extended to enable the planning of events to be split into multiple parts. This may be needed if, for example, a long-running event spans more than one news cycle. The cardinality of <planning> is extended from (1) to (1..∞) and new attributes @coversfrom and @coversto are added to the <planning> and <assignedTo> elements of the <newsCoverage> wrapper. These express the date (and optionally the time) of the start and end of coverage. See the code listing below for example usage.
Additional properties of <planning>:
| Property | Type | Notes/Example |
|---|---|---|
<g2ContentType> |
String |
Optional, non-repeatable element to indicate the Media Type of the intended coverage. The example below indicates that the content to be delivered is a NewsML-G2 News Item. |
<itemClass> |
QCode |
Optional, non-repeatable element indicates the type of content to be delivered, using the IPTC News Item Nature NewsCodes. Since the example will show a text article, the Item Class is "text" |
<itemCount> |
Empty |
The number of items to be delivered, expressed as a range: Both attributes @rangefrom (non-negative integer) and @rangeto (positive integer) MUST be used. The values are inclusive: rangefrom="2" rangeto="5" means 2 to 5 items will be delivered. |
<assignedTo> |
Flex1 Party Property |
The Flex1 Party Property Type extends the Flex Party Property Type by allowing a @role attribute to be a space separated list of QCodes. <assignedTo> is an optional, non-repeatable element that holds the details of a person or organisation who has been assigned to create the announced content. It may hold as child elements any property from <personDetails> or <organisationDetails>, and properties from the Concept Definitions Group, and Concepts Relationships Group (see Concepts and Concept Items for details. The example shows the details of a person assigned to create the content: This information may be required internally by a news organisation as part of its event planning process, but perhaps may not be distributed to customers. Customers may be informed of the intended author/creator of planned coverage using the <by> property (see below) |
<scheduled> |
Approx. Date Time |
Optional, non-repeatable. Indicates the scheduled time of delivery, and may be truncated if the precise date and time is not known. For example, if the content is scheduled to arrive at some unspecified time on a day, the value would be, for example: |
<service> |
Qualified Property |
Optional, repeatable. The editorial service to which the content has been assigned by the provider and on which the receiver should expect to receive the planned content. |
<newsContentCharacteristics> |
Empty |
An element that enables providers to express physical properties of the planned item using attributes from the News Content Characteristics group:
|
<audience> <exclAudience> |
To support further information about the intended content of a Planning Item, and in alignment with <contentMeta>, the one or more <audience> and/or <exclAudience> properties may be added as shown in the example below: |
|
<planningExtProperty> |
For example, the planned item has a proprietary content rating. The rating is expressed using @rel with a QCode indicating the nature of the proprietary property, a @value and a @valuedatatype: <planningExtProperty rel="ex-mediarel:hasParentalAdvisory" value="6" valuedatatype="xs:positiveInteger"/> |
Descriptive Metadata for <planning>
Metadata "hints" may also be added to assist receivers in preparing for the planned item, using the Descriptive Metadata Properties group:
| Property | Type | Notes/Example |
|---|---|---|
<by> |
Label |
Optional, repeatable. Natural language author/creator information: |
<creditline> |
String |
Optional, repeatable. A freeform expression of the credit(s) for the content: |
<dateline> |
Label |
Optional, repeatable. Natural language information traditionally placed at the start of a text by some news agencies, indicating the place and time that the content was created: |
<description> |
Block |
Optional, repeatable. A free form textual description of the intended news coverage, with minimal mark-up permitted. The optional @role may use a value from the IPTC Description Role NewsCodes: |
<genre> |
Flex1 Concept Property |
Optional, repeatable. The nature of the journalistic content that is intended for the news coverage. May be expressed by a QCode or URI value, with optional @type. Child elements may be any from the Concept Definition Group and the Concept Relationships Group (see Concepts and Concept Items): |
<headline> |
Label |
Optional, repeatable. Headline that will apply to the content: |
<keyword> |
String |
Optional, repeatable. A freeform term to assist in indexing the content: |
<language> |
- |
Optional, repeatable. The language of the intended coverage, May have a @role to inform the receiver of the use of the language. The IPTC Language Role NewsCodes currently has two values, "Subtitle" and "Voice Over" that apply to video content. The language @tag MUST be expressed using IETF BCP 47 and may have a child element of <name>: |
<slugline> |
Internationalised String |
Optional, repeatable. May have a @role and a @separator which indicates the character used as a delimiter between words or tokens used in the slugline: |
<subject> |
Flex1 Concept Property |
Optional, repeatable. Indicates the subject matter of the intended coverage. Child elements may be any from the Concept Definition Group and the Concept Relationships Group (see Concepts and Concept Items): Or |
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<planningItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20101025:gbmrmdreis4711"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en">
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://www.example.com/events/event-catalog.xml" />
<itemMeta>
<itemClass qcode="plinat:newscoverage" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-10-18T13:45:00Z
</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<urgency>5</urgency>
<contentCreated>2015-10-16T12:15:00Z</contentCreated>
<contentModified>2022-10-16T13:35:00Z</contentModified>
<headline>The 12 Days of Christmas</headline>
</contentMeta>
<newsCoverageSet>
<newsCoverage id="ID_1234568" modified="2021-09-26T13:19:11Z">
<planning>
<g2contentType>application/nitf+xml</g2contentType>
<itemClass qcode="ninat:text"/>
<assignedTo
coversfrom="2022-12-24T06:00:00Z"
coversto="2022-12-24T23:00:00Z"
qcode="ex-santastaff:ceo">
<name>Chief Elf Officer</name>
</assignedTo>
<scheduled>2021-12-24T23:30:00Z</scheduled>
<headline>All Wrapped Up in Lapland</headline>
<edNote>Text 250 words</edNote>
</planning>
<planning>
<g2contentType>application/nitf+xml</g2contentType>
<itemClass qcode="ninat:text"/>
<assignedTo
coversfrom="2022-12-24T23:00:00Z"
coversto="2022-12-25T12:00:00Z"
qcode="ex-santastaff:santa">
<name>Santa Claus</name>
</assignedTo>
<scheduled>2021-12-25T06:30:00Z</scheduled>
<headline>Santa’s Sleigh Ride</headline>
<edNote>Text 250 words</edNote>
</planning>
</newsCoverage>
<newsCoverage id="ID_1234569" modified="2021-09-26T15:19:11Z">
<planning>
<g2contentType>image/jpeg</g2contentType>
<itemClass qcode="ninat:picture"></itemClass>
<scheduled>2021-12-25T00:00:00Z</scheduled>
<edNote>Picture will be Santa Claus departing with reindeer</edNote>
</planning>
</newsCoverage>
</newsCoverageSet>
</planningItem>15.6. The <delivery> component
The optional <delivery> component tells the receiver which parts of the planned coverage has been delivered. The delivered item(s) are referenced by one or more <deliveredItemRef> elements, each of which points to a delivered Item.
The complementary <deliverableOf> property may be added to the <itemMeta> of the corresponding delivered Item. This enables receivers to track back from delivered content to a specific News Coverage component. Although providers should keep the item references synchronised, it provides a bi-directional method for receivers to track the deliverables of a Planning Item, for example, if a News Item is delivered before the associated Planning Item is updated.
15.7. Delivered Items - <deliveredItemRef>
A set of properties to identify, locate and describe the delivered Item. In addition to the properties listed below, a child <title> element may be added as metadata "hint" to the receiver.
| Property | Type | Notes/Example |
|---|---|---|
@rel |
QCode |
Indicates the relationship between the current Planning Item and the target Item |
@href |
URL |
Locator for the target resource: |
@residref |
String |
The provider’s identifier for the target resource, i.e. the @guid of the Item: |
@version |
String |
The version of the target resource: the @version of the Item |
@contenttype |
String |
The Media Type of the target resource: |
@format |
QCode |
A refinement of the Media Type, taken from a CV |
@size |
String |
Indicates the size of the target resource in bytes: |
@persistentidref |
String |
Reference to an element inside the target resource bearing an @id attribute, whose value must be persistent for all versions, i.e. for its entire lifecycle. |
@validfrom, @validto |
DateOpt |
Date range (with optional time) for which the Item Reference is valid: |
@id |
XML ID |
A local identifier for the <deliveredItemRef> |
@creator |
QCode |
If the property value is not defined, specifies which entity (person, organisation or system) will edit the <deliveredItemRef> value - expressed by a QCode or IRI. If the property value is defined, specifies which entity (person, organisation or system) has edited the <deliveredItemRef> value. |
@modified |
DateOpt |
The date with optional time that this <deliveredItemRef> was last changed |
@xml:lang |
BCP47 |
The language used for this <deliveredItemRef> |
@dir |
Enumeration |
The directionality of text, either "ltr" or "rtl" (left-to-right or right-to-left) |
@rank |
Non-negative |
The rank of the <deliveredItemRef> among others in the Planning Item |
15.8. Hint and Extension Point
Child elements from the NAR namespace or any other namespace may optionally be added. When using elements from the NAR, follow the rules set out in Adding Hints from the NAR namespace.
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<planningItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:iptc.org:20101025:gbmrmdreis4711"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en">
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://www.example.com/events/event-catalog.xml" />
<itemMeta>
<itemClass qcode="plinat:newscoverage" />
<provider qcode="nprov:IPTC" />
<versionCreated>2022-10-18T13:45:00Z
</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<urgency>5</urgency>
<contentCreated>2016-10-16T12:15:00Z</contentCreated>
<contentModified>2022-10-16T13:35:00Z</contentModified>
</contentMeta>
<newsCoverageSet>
<newsCoverage id="ID_1234568" modified="2021-09-26T13:19:11Z">
<planning>
<g2contentType>application/nitf+xml</g2contentType>
<itemClass qcode="ninat:text"/>
<scheduled>2021-12-25T12:30:00-05:00</scheduled>
<headline>Robinson: Must preserve bailout funds</headline>
<edNote>Text 250 words</edNote>
</planning>
</newsCoverage>
<newsCoverage id="ID_1234569" modified="2021-09-26T15:19:11Z">
<planning>
<g2contentType>image/jpeg</g2contentType>
<itemClass qcode="ninat:picture" />
<scheduled>2021-12-25T12:00:00-05:00</scheduled>
<edNote>Picture will be Robinson at today's news conference</edNote>
</planning>
<delivery>
<deliveredItemRef
guidref="tag:example.com,2008:ART-ENT-SRV:USA20081220098658">
<title>Henry Robinson pictured today in New York</title>
</deliveredItemRef>
</delivery>
</newsCoverage>
</newsCoverageSet>
</planningItem>16. Exchanging News: News Messages
16.1. Introduction
News communication is often by means of a provider’s broadcast or multicast feed, with transactions carried out by a separate sub-system that has its own specific identification and transmission methods, independent of NewsML-G2.
The News Message (<newsMessage>) facilitates these transactions, enabling the exchange of any number of NewsML-G2 Items by any kind of digital transmission system.
The use of <newsMessage> is entirely optional: items may also be exchanged using SOAP, Atom Publishing Protocol (APP) or other suitable content syndication method.
News Messages are a convenient wrapper when sending a Package Item and all of its referenced content in a single transaction (but note that it is not necessary to send packages and associated content together in this manner).
The News Message properties are transient; they do not have to be permanently stored, although it may be useful if transmission/reception records are maintained, at least for a limited period during which requests for re-sending of messages may be made. If the content items carried by the message have a dependency on news message information, this information should be stored with the items themselves.
16.2. Structure
A diagram of the structure of a News Message and its payload of Items is shown below.
A News Message MUST have a <header> component, which MUST contain a <sent> transmission timestamp. These are the only mandatory requirements.
The News Message payload is the <itemSet> component, which may have an unbounded number of child <newsItem>, <packageItem>, <conceptItem> and <knowledgeItem> components in any combination and in any order.
16.2.1. News Message Header <header>
The Header contains a set of properties useful for managing the transmission and reception of news. The simple implementation of News Message uses elements with string values, e.g.
<sender>reuters.com</sender>Optionally, providers can use more semantically defined values for header properties, either using URI, QCode or literal values, and also use other QCode type properties to add further detailed information, e.g.:
<sender qcode="ex-sndr:rtr">reuters.com</sender>or
<sender literal="reuters">reuters.com</sender>If using controlled values for properties of the News Message, providers should note the following conditions:
-
If QCode values are used: either a <catalog> or a <catalogRef> child elements of <header> MUST be present to provide the required Scheme URIs of the controlled vocabularies used. (see Creating and Managing Catalogs for details) The scope of the <header> catalog is limited to the News Message header only, and is NOT inherited by any of the Items under <itemSet>.
-
If a @literal attribute is used together with a string value for a property: the value of the @literal and of the string should be identical (as in the second example of <sender> above); if not, then the value of @literal takes precedence.
| <catalog> or <catalogRef> are optional for News Messages, but mandatory for Items. |
The child elements of <header> that may use qualifying attributes are:
-
sender
-
origin
-
channel
-
destination
-
timestamp (optional @role, see below)
-
signal (may use @qcode only)
The following qualifying attributes are defined:
| Name | Cardinality | Datatype | Definition |
|---|---|---|---|
qcode |
0..1 |
QCodeType |
A qualified code assigned as a property value. |
uri |
0..1 |
XML Schema anyURI |
A URI which identifies a concept. |
literal |
0..1 |
XML Schema normalizedString |
A free-text value assigned as a property value. |
type |
0..1 |
QCodeType |
The type of the concept assigned as a controlled or an uncontrolled property value. |
role |
0..1 |
QCodeType |
A refinement of the semantics of the property. |
Both string values of properties and the use of qualifying attributes are given as examples below. Note that unless stated otherwise, the scheme aliases used in QCode type properties are fictional.
Sent timestamp <sent>
Mandatory, non-repeatable. The transmission timestamp is in ISO8601 format. Note that if a news message is re-transmitted, the sender is NOT required to update this property.
<sent>2022-10-19T11:17:00.100Z</sent>Catalog <catalog>
An optional reference to the Scheme URI of a Controlled Vocabulary to enable the resolution of QCode values of properties used in the document:
<catalog>
<scheme alias="nmsig" uri="http://cv.example.com/newscodes/newsmsgsignal/" />
</catalog>Remote Catalog <catalogRef>
An optional reference to a remote catalog containing one or more scheme URIs for the CVs used in the document:
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />Message Sender <sender>
An optional, non-repeatable string. Best practice is to identify the sender (not necessarily the same as the provider in <itemMeta>) by domain name:
<sender>reuters.com</sender>Transmission ID <transmitId>
An optional, non-repeatable string identifying the news message. The ID must be unique for every message on a given calendar day, except that if a message is re-transmitted, it may keep the same ID. The structure of the string is not specified by the IPTC.
<transmitId>tag:reuters.com,2016:newsml_OVE48850O-PKG</transmitId>Priority <priority>
Optional, non-repeatable. The sender’s indication of the message’s priority, restricted to the values 1-9 (inclusive), where 1 is the highest priority and 9 is the lowest. Priority would be used by a transmission system to determine the order in which a message is transmitted, relative to others in a queue. Urgency is an editorial judgement expressing the relative news value of an item.
<priority>4</priority>Note that message Priority is not the same as the <urgency> of an individual Item within the news message, although they may be correlated. A typical example is that the Priority may be set to the highest Urgency value associated with any of the Items carried by the message.
Message Origin <origin>
An optional, non-repeatable string whose structure is not specified by the IPTC. It could denote the name of a channel, system or service, for example.
<origin>MMS_3</origin>or
<origin qcode="nmorgn:mms3 />Channel Identifier <channel>
An optional, repeatable string that gives the partners in news exchanges the ability to manage the content, for example as part of a permissions or routing scheme. The notion of a channel has its origins in multiplexed systems, but may be an analogy for a product – a virtual <channel> delivered within a physical stream identified by <destination>.
<channel>email</channel>or
<channel qcode="ex-nmchan:smtp" />Destination <destination>
An optional, repeatable, destination for the news message, using a provider-specific syntax. In broadcast delivery systems, this may be one or more physical delivery points:
<destination>foo.bar@example.com</destination>or
<destination role="ex-nmdest:foobar">UKI</destination>Timestamps <timestamp>
An optional and repeatable <timestamp> property may be used to indicate the date-time that a <newsMessage> was received and/or transmitted. The values must be expressed as a date-time with time zone. The property may be refined using the optional @role, which may be a literal or QCode value, but note that if using a QCode the string that should be interpreted as a QCode MUST be defined outside the NewsML-G2 specification by the provider of the News Message:
<timestamp role="received">2022-10-18T11:17:00.000Z</timestamp>
<timestamp role="transmitted">2022-10-19T11:17:00.100Z</timestamp>Signal <signal>
Optional, repeatable; the <signal> element can be used to indicate any special handling instruction to the receiver’s NewsML-G2 processor:
<signal qcode="nmsig:atomic" />There is a recommended IPTC News Message Signal NewsCodes CV with a Scheme URI of: http://cv.iptc.org/newscodes/newsmsgsignal/
The recommended scheme alias is "nmsig" and there is currently one member of the CV: "atomic" which signals to the receiving processor that the content of the News Message should be processed together. This enables providers to indicate that a Package Item and all of the Items that are referenced by that Package should be processed as a single "atomic" (i.e. indivisible) bundle.
16.2.2. News Message payload <itemSet>
Each <newsMessage> MUST have one <itemSet> component, which wraps the NewsML-G2 Items that are to be transmitted.
The contents of <itemSet> can be "any" component or property from the NAR namespace. This is to enable schema-based validation of the content of the Items in the message.
The IPTC recommends that the child elements of <itemSet> be any number of <newsItem>, <packageItem>, <conceptItem>, and/or <knowledgeItem> components, in any combination, in any order.
The listing below shows a "skeleton" News Message containing a Package Item that references four News Items, together with the referenced items themselves, as an "atomic" package, with some of the <header> properties using a QCode value, which requires a reference to a Catalog (in this case two Remote Catalogs referenced using <catalogRef>).
QCodes used in listing below are from IPTC NewsCodes vocabularies, except for ex-nmdest.
<?xml version="1.0" encoding="UTF-8"?>
<newsMessage
xmlns="http://iptc.org/std/nar/2006-10-01/">
<header>
<sent>2022-10-19T11:17:00.150Z</sent>
<catalogRef href="http://www.example.com/std/catalog/NewsNessages_1.xml" />
<catalogRef href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<sender>thomsonreuters.com</sender>
<transmitId>tag:reuters.com,2016:newsml_OVE48850O-PKG</transmitId>
<priority>4</priority>
<origin>MMS_3</origin>
<destination role="ex-nmdest:foobar">UKI</destination>
<channel>TVS</channel>
<channel>TTT</channel>
<channel>WWW</channel>
<timestamp role="received">2022-10-19T11:17:00.000Z</timestamp>
<timestamp role="transmitted">2022-10-19T11:17:00.100Z</timestamp>
<signal qcode="nmsig:atomic" />
</header>
<itemSet>
<packageItem>
<itemRef residref="N1" />
<itemRef residref="N2" />
<itemRef residref="N3" />
<itemRef residref="N4" />
</packageItem>
<newsItem guid="N1"> ..... </newsItem>
<newsItem guid="N2"> ..... </newsItem>
<newsItem guid="N3"> ..... </newsItem>
<newsItem guid="N4"> ..... </newsItem>
</itemSet>
</newsMessage>17. Migrating IPTC 7901 to NewsML-G2
17.1. Introduction
The text transmission standard IPTC 7901 (and ANPA1312, with which it is closely associated) were a mainstay of the exchange of text for 30 years. The following tables map IPTC 7901 fields to their equivalent in either NewsML-G2 News Item or News Message.
In some cases there is a choice of field mappings. For example there is only one timestamp field in IPTC 7901, but several in NewsML-G2.
When providers convert to NewsML-G2, they should determine the source of the metadata used to populate the IPTC 7901 field. For example, if from an editorial system, the field label or usage may indicate the NewsML-G2 property to which the 7901 timestamp should be mapped.
Customers converting IPTC 7901 fields to NewsML-G2 properties should consult their providers’ documentation, or make inquiries about the mapping of IPTC 7901 fields in the provider’s systems.
17.2. Message Header
| Field Name | Example | NewsML-G2 Property and Example |
|---|---|---|
Source Identification |
FRS |
The 7901 definition is “to identify the news service of the originator and the message.” An equivalent NewsML-G2 property would be the <destination> property of News Message: <destination>FRS</destination> An alternative property would be <channel> <channel>FRS</channel> Within a News Item, there is a <service> property that may also be used, however, the IPTC recommends that Source Identification expressed a distribution intention, not merely a service description. Therefore its natural home is in News Message. |
Message Number |
9999 |
In IPTC 7901, this may be up to four digits and therefore cannot be guaranteed to be unique. Some providers reset the counter to zero every 24 hours. The intention is to be able to identify a message within a sequence of messages. The equivalent NewsML-G2 field would be <transmitId> of News Message IPTC 7901 specifies a single digit of value 1 to 6 inclusive. |
Priority of Story |
3 |
NewsML-G2 has two equivalents: <urgency> in the Administrative Metadata group of <contentMeta> <urgency>3</urgency> <priority> in the <header> of News Message. <priority>3</priority> If the 7901 field is mapped from an editorial system and is under the control of journalists, then <urgency> would seem to be appropriate, since this expresses a journalistic intention. |
Category of Story |
POL |
In IPTC7901, this could be up to three characters. A provider converting its categories for NewsML-G2 would create a Controlled Vocabulary mapping the legacy codes to a Knowledge Item – thus allowing the receiver to get more information about the code, or to download all of the codes in order to populate a GUI menu. The CV would be expressed using <subject> in Content Metadata <subject type=“cpnat:abstract” qcode=“cat:POL”> <name>Politics</name> </subject> |
Word Count |
195 |
The maximum value allowed in IPTC 7901 is 9999. Word Count is one of the properties of News Content Characteristics group of properties. (The NewsML-G2 Specification can be downloaded by visiting www.newsml-g2.org/spec.) The plain text of IPTC 7901 is an attribute of the Inline Data component <inlineData> <inlineData wordcount=“195”> Text text text </inlineData> There is no limit to the number of words that can be conveyed in NewsML-G2 |
Optional Information |
(optional) |
These two fields are sometimes used by providers in their own specific format or syntax, so it is not possible to give a definitive mapping from IPTC 7901 to NewsML-G2. Providers converting from IPTC 7901 to NewsML-G2 should determine the source of the information that is being put into the 7901 fields, and map to the appropriate NewsML-G2 property. Customers converting an IPTC 5901 service into NewsML-G2 and who are unsure about which of NewsML-G2’s properties to populate with the 7901 information should consult the provider’s documentation, or inquire of the provider. Part of the content of the Keyword/Catch-Line field may be equivalent to the NewsML-G2 <slugline> property in the Descriptive Metadata group of <contentMeta>. |
Keyword/Catch-Line |
<slugline separator=“-”>US-POLITICS/BUSH</slugline> |
17.3. Message Text
If the message text is to be conveyed as plain text, then the <inlineData> wrapper would be used. If the migration to NewsML-G2 also involves migration of the text to some mark-up such as NITF or XHTML, this would be conveyed in the <inlineXML> wrapper.
17.4. Post-Text Information
The IPTC7901 post-text fields all relate to date-time. As previously recommended, providers should examine the origin of the information being used to fill the IPTC 7901 day and time field, and use the appropriate NewsML-G2 field for that information. The following are possibilities:
-
If Day and Time is populated by the transmission system, the <sent> property of News Message would be an appropriate mapping.
-
If the IPTC 7901 field represents the only timestamp information available from the provider’s system, then the provider MUST put this information in the <versionCreated> timestamp property of <itemMeta> since its use is a mandatory requirement of NewsML-G2,
-
If versioning of Items is being implemented, then the original timestamp may be preserved in <firstCreated>
These properties are of XML date time type so must express the FULL date and a time with time zone:
<versionCreated>2009-02-09T12:30:00Z</versionCreated>If the provider believes that the IPTC 7901 day and time is being populated from the timestamp on the story itself, then subject to the rule of <versionCreated> being followed, the appropriate properties would be <contentCreated> or <contentModified>.in the Management Metadata group of <contentMeta>.
If versioning is being implemented, the original day and time may be preserved in <contentCreated>, If <contentModified> is used, then <contentCreated> SHOULD also be present
Both properties use TruncatedDateTime property type, allowing the value to be truncated from the right.
<contentCreated>2009-02-09</contentCreated>| Field Name | Example | NewsML-G2 Property and Example |
|---|---|---|
Day and Time |
91230 |
Six digits are be used to express the day and time in IPTC 7901, in practice this means a format of DDHHMM, where DD is the day of the month, HH is the hour, MM minutes. In NewsML-G2, there are more timestamp fields available, |
Time Zone |
GMT |
Three-alpha character field. Optional in IPTC 7901. No separate equivalent in NewsML-G2 (none needed) |
Month of Transmission |
Feb |
Three-alpha character field. Optional in IPTC 7901. No separate equivalent in NewsML-G2 (none needed) |
Year of Transmission |
9 |
Two-digit field. Optional in IPTC 7901. No separate equivalent in NewsML-G2 (none needed) |
18. Designing a NewsML-G2 feed from scratch
18.1. Introduction
When designing a NewsML-G2 feed, some fundamental questions need to be asked, such as:
-
What is the provider’s business value proposition and how must this be supported by the NewsML-G2 implementation?
-
What are the needs and capabilities of customers? Sometimes, it is the customers who are driving the move the NewsML-G2; if so, happy days! But more often, customers will have some issues and will need sympathetic handling.
-
What limitations – if any – do the provider’s existing systems and processes impose on the NewsML-G2 project?
This chapter gives general guidance on the issues an implementer of a feed might encounter, and where necessary points to more detailed information on specific topics described elsewhere in the Guidelines.
As a general principle, the IPTC recommends that providers strive for inter-operability, so where possible, stick to using the recommended "mainstream" properties as identified by the Property Usage sheet below. The sheet lists the NewsML-G2 properties which are most widely used by currently existing NewsML-G2 feeds. As there may be more than one way to implement a feature; in such cases the IPTC recommends choosing the most widely-used property as indicated by the sheet.
Also consider using existing IPTC NewsCodes Schemes for property values where appropriate, in preference to creating proprietary schemes that accomplish a similar purpose. A table showing IPTC Controlled Vocabulary Usage is shown below.
18.2. Content-driven design
The design of a NewsML-G2 feed will depend on the content type being conveyed, since each type will have specific metadata and processing needs.
For all content types, note the basic NewsML-G2 rule: a single logical item of content per News Item, which can be represented by more than one technical representation. For multiple pieces of content in a named relationship, use the Package Item, and for sending one or more NewsML-G2 Items in a transmission workflow, the News Message may be used.
18.2.1. Content choices
Text
The most commonly-used NewsML-G2 container for text is <inlineXML> wrapping XHMTL content, although NITF is also used. Note that any well-formed XML may be conveyed in <inlineXML> so this can be aligned to a more specific business purpose such as XBRL (Extended Business Reporting Language).
It is also possible to convey a text-based object as binary content, for example as a PDF, using <remoteContent> or as plain text using <inlineData>.
When converting from legacy text formats such as IPTC7901, the initial advantages of NewsML-G2 include the ability to separate metadata from the content, and the use of globally-unique controlled values to classify content.
Going further, there are more specialised structures available for implementers to provide financial information, express quantitative data, and give precise geographic details in a machine-readable form.
Pictures
As binary content, pictures (and graphics) are conveyed using the <remoteContent> wrapper. The Pictures and Graphics chapter gives an overview of NewsML-G2 features and the relationship between NewsML-G2 metadata and embedded metadata such as the "IPTC Core" fields in JPEG/TIFF files. There is also a chapter on Mapping Embedded Photo Metadata to NewsML-G2 that provides more detailed information on this issue.
Video
The first consideration for video is the business requirement, since this drives the technical design in one of two directions:
-
Simple one-part video – probably delivered in multiple formats to suit different technical platforms
-
Multi-part video delivered as a reference to a single file (and potentially multiple technical renditions) that requires each part or shot to have its own administrative and descriptive metadata.
NewsML-G2 serves both of these content models, which are described in the Video chapter.
18.3. The Basics
The Chapter on NewsML-G2 Basics has a description of the mandatory and commonly-used properties.
18.4. Identification and version control
Choose a scheme for generating the @guid of NewsML-G2 Items. The IPTC has registered a namespace urn "newsml" and a specification for this purpose (see Item Identifier) but other schemes such as TAG URI are available.
Decide how Item version will be generated: it must start at "1" and ideally should increment by "1" each time a new version is published, although a new version may have any number that is greater than the previous version number. Providers may also use <link> to inform receivers of the previous version and provide a location or id for it (see Using Links for more details on this)
18.5. Conformance
Since version 2.24, NewsML-G2 supports only one schema (the "All-Power" schema), therefore the conformance attribute must be present with a value of "power".
18.6. Validation
When designing and testing the feed, validation against the IPTC scheme files will be essential. The IPTC recommends that validation should not be required in production: it can be resource intensive and introduces a potential point of failure. If a provider chooses to validate production documents, they must NOT validate against the schema files hosted by the IPTC.
18.7. Catalogs and Controlled Vocabularies
Even after following the advice about using NewsCodes (above) it is almost certain that some provider specific schemes will be needed. See the section on Controlled Vocabularies and QCodes for detailed information on how to create and maintain CVs and Catalogs.
18.8. Rights Information
See Chapter on Rights Metadata to go beyond the basics of expressing rights information.
18.9. Management Metadata
18.9.1. Timestamps
There are four timestamps available in NewsML-G2 documents, two are properties of Item Metadata and relate to management of the Item; two are properties of Content Metadata and are part of the Administrative properties of the Item’s content. The four properties are:
-
itemMeta/firstCreated
-
itemMeta/versionCreated
-
contentMeta/contentCreated
-
contentMeta/contentModified
NewsML-G2 timestamps in Item Metadata express the full date and time of the creation or update of the Item. Content Metadata timestamps may be truncated from the right because the precise date and time of the creation of content (for example an historic photograph) may be unknown. Note that any timestamp that contains the time MUST contain a time offset or Z for UTC, for example the format YYYY-MM-DDThh:mm:ss(+-)hh:mm:ss, or YYYY-MM-DDThh:mm:ssZ.
The single mandatory timestamp for a NewsML-G2 document is <versionCreated>, but the following rules MUST be followed when any other timestamp is present.
Data Value rules
-
If <contentCreated> is used, it MUST NOT be later than <versionCreated>.
-
If <contentModified> is present, <contentCreated> SHOULD also be present and MUST be earlier than <contentModified>.
-
If <contentModified> is present, it MUST NOT be later than <versionCreated>.
-
If <firstCreated> is present, it MUST NOT be later than <versionCreated>.
Data Processing rules
-
The recipient processor MUST first check if a <contentModified> element is present.
-
If not it MUST check if a <contentCreated> element is present.
-
If not it SHOULD assume that the content was created at the time indicated by <versionCreated> element in itemMeta.
For a full description of the timestamps and processing rules, see the NewsML-G2 Specification, which may be downloaded. This can be downloaded by visiting newsml-g2.org/spec.
A number of existing implementations use only itemMeta/versionCreated for text, but for picture, graphics and video, it is generally accepted that contentMeta/contentCreated and contentMeta/contentModified should be used as, for example, the moment when a picture is taken is considered significant.
18.9.2. Publishing Status/Embargoed
Both properties of <itemMeta> have "implied" values, in that there are default values that are assumed if the actual properties are absent. Publishing Status defaults to "usable" and Embargoed to "none". There are separate topics for these properties in the chapter on Generic Processes and Conventions.
18.9.3. Links
Links identify and can also locate NewsML-G2 Items and other non-G2 resources that may be used to supplement the understanding of an Item’s content. The default relationship to the target Item is "See Also" but other relationships such as "Translated From" and "Derived From" are defined in the IPTC Item Relationship NewsCodes.
18.10. Property Usage
The following property usage table was compiled from a survey of IPTC members.
| Property name | Text | Photo / Graphic | Video | News Package |
|---|---|---|---|---|
News Message |
||||
header |
High |
High |
High (in package) |
Medium |
sent |
Mandatory |
Mandatory |
Mandatory |
Mandatory |
sender |
High |
Medium+ |
High |
Medium |
transmitId |
Medium |
Medium+ |
High |
High |
priority |
High |
Medium |
Medium |
Medium |
origin |
Medium |
Medium |
No |
Medium |
timestamp |
Medium |
Low+ |
Medium |
No |
destination |
High - with channel |
Medium+ - with channel |
Medium |
Medium |
channel |
High - with destination |
Medium+ - with destination |
High |
Medium |
News Item |
||||
@guid |
Mandatory |
Mandatory |
Mandatory |
Mandatory |
@version |
Always |
Always |
Always |
Always |
Catalogs/Hop History |
||||
catalogRef |
Mandatory |
Mandatory |
Mandatory |
Mandatory |
catalog |
Mandatory |
Mandatory |
Mandatory |
Mandatory |
hopHistory |
Low |
Low |
No |
No |
rightsInfo |
||||
accountable |
Low |
Low |
No |
Medium |
copyrightHolder |
High |
High |
High |
High |
copyrightNotice |
High |
High |
High |
Medium |
usageTerms |
Medium |
Low+ |
Medium |
Low+ |
itemMeta |
||||
itemClass |
Mandatory |
Mandatory |
Mandatory |
Mandatory |
provider |
Mandatory |
Mandatory |
Mandatory |
Mandatory |
versionCreated |
Mandatory |
Mandatory |
Mandatory |
Mandatory |
firstCreated |
Medium |
High |
High |
Medium+ |
embargoed |
Always |
Always |
Always |
Always |
pubStatus |
High |
High |
High |
High |
role |
Medium |
Low+ |
High |
Medium |
fileName |
Medium |
Medium |
Medium |
Medium |
generator |
Medium |
Medium |
High |
High |
profile |
Medium |
Low+ |
High |
Medium+ |
service |
Medium |
Low+ |
High |
Medium |
title |
Medium |
Low |
No |
Medium |
edNote |
High |
Low+ |
Low+ |
No |
memberOf |
Medium |
Low |
No |
No |
instanceOf |
Medium |
Low |
No |
No |
signal |
High |
Medium+ |
High |
Medium |
altRep |
No |
No |
No |
No |
deliverableOf |
No |
No |
No |
No |
hash |
No |
No |
No |
No |
link |
Medium |
Low |
Medium |
Low |
contentMeta |
||||
icon |
No |
Low |
Low |
No |
urgency |
High |
Medium+ |
High |
Medium |
contentCreated |
Medium |
Medium+ |
Medium |
Medium |
contentModified |
Medium |
Medium |
Low |
Low+ |
located |
High |
Low |
High |
Low+ |
infoSource |
High |
High |
High |
Medium |
creator |
High |
High |
Medium |
Medium |
contributor |
Medium |
Medium+ |
Medium |
Low+ |
audience |
Medium |
No |
No |
Low+ |
exclAudience |
Low |
Low |
No |
No |
altId |
High |
High |
High |
Medium+ |
rating |
No |
Low |
No |
No |
userInteraction |
No |
No |
No |
No |
language |
Medium |
Medium |
High |
Medium+ |
genre |
Medium+ |
Low |
Medium |
No |
keyword |
Medium+ |
Low |
No |
Medium |
subject |
High |
High |
High |
High |
bag |
No |
No |
No |
No |
slugline |
High |
Medium+ |
High |
High |
headline |
High |
High |
High |
High |
dateline |
Medium+ |
Low |
Low |
Medium+ |
by |
Medium |
Medium+ |
Medium |
No |
creditline |
Medium |
High |
No |
Medium |
description |
Medium |
High |
High |
Medium |
partMeta |
No |
Low |
Low |
No |
Helper structures |
||||
assert |
~ |
~ |
~ |
~ |
inlineRef |
~ |
~ |
~ |
~ |
derivedFrom |
Low |
No |
No |
No |
contentSet |
||||
inlineXML |
High |
n/a |
n/a |
n/a |
inlineData |
Low |
n/a |
n/a |
n/a |
remoteContent |
No |
High |
n/a |
n/a |
groupSet |
||||
main/root Group |
n/a |
n/a |
High |
High |
subgroups |
n/a |
n/a |
High |
High |
itemRef |
n/a |
n/a |
High |
High |
Key |
||||
Mandatory |
Mandatory per the NewsML-G2 specification |
|||
Always |
Explicitly defined or implied by absence |
|||
High |
Expected to be present |
|||
Medium |
May be present |
|||
Low |
Unlikely to be present (currently) |
|||
No |
Not present (currently) |
|||
~ |
Technical helpers: These provide richer information about another explicit property |
|||
n/a |
Not applicable |
|||
red |
Mandatory mark-up |
|||
18.11. IPTC Controlled Vocabulary Usage
The table below compares the usage of IPTC CVs (where available) and proprietary CVs for commonly-used and mandatory properties, compiled from a survey of IPTC members.
| Property name | IPTC CV(s) | Scheme Alias | Provider CVs |
|---|---|---|---|
News Message header |
|||
destination |
n/a |
~ |
Medium |
News Item |
|||
catalog info |
~ |
~ |
|
rightsInfo |
~ |
No |
|
itemMeta |
|||
itemClass |
|
~ |
|
provider |
|
No |
|
pubStatus |
|
~ |
|
role |
~ |
Medium |
|
generator |
~ |
Medium |
|
service |
~ |
High |
|
edNote |
~ |
Medium |
|
memberOf |
~ |
High |
|
instanceOf |
~ |
High |
|
signal |
|
High |
|
link |
|
High |
|
contentMeta |
~ |
||
located |
~ |
High |
|
infoSource |
|
Medium |
|
creator |
~ |
High |
|
contributor |
~ |
High |
|
audience |
~ |
Medium |
|
exclAudience |
~ |
High |
|
altId |
~ |
Medium |
|
genre |
|
High |
|
subject |
|
~ |
|
|
~ |
||
|
~ |
||
|
~ |
||
|
~ |
||
description |
|
Medium |
|
partMeta |
~ |
Medium |
|
tech helpers |
|||
assert |
~ |
High |
|
contentSet |
|||
remoteContent |
|
High |
|
groupSet |
|||
itemRef |
~ |
High |
| Key | |
|---|---|
|
Mandatory per specification |
High |
Expected to be present |
Medium |
May be present |
Low |
Rarely present |
No |
Available but not used |
~ |
Unavailable or not applicable |
19. News Industry Text Format (NITF)
19.1. Introduction
| This Guide refers to NITF v 3.5. A new version 3.6 was released in January 2012. Please visit www.iptc.org/standards and follow the link to NITF for further details of NITF and to download a package of the new version and its documentation |
NITF is an XML-based standard for marking up text articles that includes the ability both to create a structure for the content, and to provide a clear separation of content and metadata.
NITF differs from NewsML-G2:
-
NITF provides a mark-up structure for text; NewsML-G2 is a container for news, is content-agnostic and has no mark-up for text content.
-
NITF expresses a single piece of content and does not support, for example, alternative renditions or different parts of the same content.
-
NITF properties have tightly-defined meanings; NewsML-G2 makes more use of generic structures that can be adapted for different uses. Therefore there may not be a direct equivalent in NewsML-G2 for a given NITF property, but a generic structure may be used to express the provider’s intention equally effectively.
The following table summarises the major differences between the two standards.
| Feature | NITF | NewsML-G2 |
|---|---|---|
Content mark-up |
||
Content structure |
||
Extensible |
||
Any content |
||
Management metadata |
||
Administrative metadata |
||
Descriptive metadata |
||
Packages |
||
Alternative renditions |
||
Concepts/Relationships |
NITF is a popular and valid choice for the management and mark-up of text in a news environment. This Chapter assumes that organisations wish to continue to use NITF for the mark-up of text, but to migrate to NewsML-G2 as a management container. There are three basic migration paths:
-
Minimum migration: retain NITF and all of its structures in place, and use a minimal NewsML-G2 News Item as a container for NITF documents. NewsML-G2 would convey the complete original NITF document.
-
Partial migration: copy or move some of NITF’s metadata structures to the equivalent NewsML-G2 properties, retaining some or all NITF metadata structures and structural mark-up of the text content.
-
Complete migration: move the NITF metadata to the NewsML-G2 equivalents, using NewsML-G2 to convey a text document with NITF content mark-up.
For a minimum migration, implementers need only to refer to the NewsML-G2 Basics and Text chapters.
For partial or complete migration, the starting point is a consideration of how the structure of NITF relates to NewsML-G2, to form a high-level view of which NITF properties are to be migrated, and where they fit in NewsML-G2 framework.
19.2. Overview of NITF and NewsML-G2 equivalents
NITF documents are composed of the following components:
-
The root element: <nitf>
-
<head>, a container for metadata about the document as a whole
-
<body> a container for content and metadata which is intended for display to the user. The <body> component is further split into:
-
<body-head> Metadata about the content
-
<body-content> The content itself
-
<body-end>Information that is intended to appear at the end of the article.
19.2.1. Root element <nitf>
The root element may uniquely identify the document using @uno, which is equivalent to NewsML-G2 @guid.
19.2.2. Document metadata <head>
<head> may have a @id attribute, a local identifier for the element. Most of the child elements of <head> have equivalents in the NewsML-G2 <itemMeta> component, with exceptions noted in the following table:
| NITF element | NewsML-G2 equivalent | Comment |
|---|---|---|
<title> |
<title> |
The properties are equivalent in NITF and NewsML-G2 |
<meta> |
<itemClass> |
<itemClass> uses the IPTC News Item Nature NewsCodes to identify the type of content. |
<tobject> |
<subject> |
This is part of NewsML-G2 <contentMeta> |
<iim> |
None |
Deprecated in NITF, no NewsML-G2 equivalent |
<docdata> |
Various |
A container for detailed metadata for the document. contains child elements as tabled in 21.2.2.1below |
<pubdata> |
None |
NewsML-G2 contains no direct equivalent of Publication Metadata. In NITF, the property has many attributes intended to convey information about print publications |
<revision-history> |
Attributes can express the date and reason for the revision, the name and job title of the person who made the revision |
<docdata> child elements
These convey detailed management information about the document.
| NITF element | NewsML-G2 equivalent | Comment |
|---|---|---|
<correction> |
<signal> |
Indicates that the item is a correction, identifies the previously published document and any correction instruction. NewsML-G2 <signal> contains a QCode so that processing instructions are constrained by a controlled vocabulary. The property may have a <name> child element and be accompanied by <edNote> conveying a human-readable message about the instruction. |
<ev-loc> |
<subject> |
<ev-loc> contains information about where the news event took place. The NewsML-G2 equivalent of <subject> may use a @role to indicate that the subject is a geographic place. If used, the IPTC Concept Type NewsCodes would be either “geoArea” or “poi” (Point of Interest) |
<doc-id> |
G2 Item @guid |
Unique persistent identifier for the document |
<del-list> |
<timestamp> |
Audit trail of points involved in delivery of the document. May be expressed in the <timestamp> property of a NewsML-G2 News Message <header>. |
< urgency> |
< urgency> |
Editorial urgency of the document. NITF uses values 1-8, NewsML-G2 uses 1-9. The value may also be linked to Priority <priority>in a NewsML-G2 News Message. |
< fixture> |
< instanceOf> |
Regularly occurring and/or frequently updated content, for example “Noon Weather Report” or “Closing Stock Market Prices”. In NewsML-G2, this is a Flex1PropType property type, a template that allows the use of a controlled or uncontrolled value. |
< date.issue> |
Various |
The default NewsML-G2 property would be <versionCreated>, but depending on the provider’s intention, <firstCreated>, <contentCreated> or <contentModified> could be used. |
< date.release> |
Various |
NewsML-G2 does not have a direct equivalent for this property. In NITF, the default value is the time of receipt of the document. Where a provider wishes to specifically delay a release, the NewsML-G2 <embargoed> property may be used. If the provider wishes to express a timestamp of the time that the document was released, a timestamp property such as <sent> in News Message should be used. |
<date.expire> |
@validto |
The <remoteContent> wrapper may have a Time Validity Attribute of @validto. |
<doc-scope> |
<audience> |
Area of interest that is not a Category, for example geographic: “of interest to people living in Toronto”. This is not the same intention as a <subject> of Toronto, which means “about” or “linked to” Toronto. If content should be seen by “Equity Traders” but is not of the Subject “Equities”, then the NewsML-G2 <audience> property may be used. |
<series> |
<memberOf> |
In NITF, this is intended to indicate that the article is one of a series of articles, its place in the order of the series, out of a total number of articles in the series. The NewsML-G2 equivalent <memberOf> is a Flex1PropType which may take a controlled or uncontrolled value. |
<ed-msg> |
<edNote> |
As with NITF, the type of message may be indicated by @role in NewsML-G2 |
< du-key> |
None |
NITF uses this property for maintaining a network of relationships to other versions of the same article. NewsML-G2 uses GUID, versioning and, if necessary, Links, to maintain this information |
19.3. Content metadata <body.head>
The contents of <body.head> a broadly equivalent to those of <contentMeta>, although this is not universally true. The following table lists the child elements of <body.head> and their NewsML-G2 equivalents.
When conveying NITF in a NewsML-G2 document, some properties of <body.head> may be retained in the NITF document, since they may be part of the structural content of the article, such as <hedline> (note spelling) and <byline>. These properties may optionally be copied into their NewsML-G2 equivalents.
| NITF element | NewsML-G2 equivalent | Comment |
|---|---|---|
<hedline> |
<headline> |
NewsML-G2 <headline> is contained in <contentMeta> and may appear any number of times. It can be refined by using @role to express the NITF notions of main headline <hl1> and subhead <hl2> |
<note> |
Various |
An advisory for editors may be equivalent to NewsML-G2 <edNote>in <itemMeta>, but NITF <note> has a number of uses, including expressing copyright, and may also be publishable. Provider’s migrating from NITF to NewsML-G2 will need to identify the intention of their use of <note> and choose from several NewsML-G2 properties that express this intention, for example <rightsInfo> (a property of an Item root element), or <description> (part of <contentMeta>) with a @role defining its purpose. Customers converting an NITF service to NewsML-G2 will need to consult with their provider, either directly or via documentation. |
<rights> |
< rightsInfo> |
See section on <docdata> |
<byline> |
<by> |
Part of <contentMeta> |
<distributor> |
<provider> |
<provider> is a mandatory property of NewsML-G2 <itemMeta> |
<dateline> |
< dateline> |
NewsML-G2 <dateline> is part of <contentMeta> |
< abstract> |
< description> |
NewsML-G2 <description> is part of <contentMeta> and may be refined by @role. The IPTC Description Role NewsCodes value would be “summary” |
<series> |
<memberOf> |
See section on <docdata> |
19.4. Body Content <body. content>
NewsML-G2 has no specific mark-up for text, and NITF is a valid choice for marking up text to be conveyed by NewsML-G2 <inlineXML>.
<contentSet>
<inlineXML contenttype="application/nitf+xml">
<nitf xmlns="http://iptc.org/std/NITF/2006-10-18/"
xsi:schemaLocation="http://iptc.org/std/NITF/2006-10-18/
./nitf-3-6.xsd">
<body>
<body.head>
<hedline>
<hl1>Arizona Diamondbacks (29-23) at Philadelphia Phillies
(26-24), 7:05p.m.</hl1>
</hedline>
<byline>
<byttl>Sports Network</byttl>
</byline>
<abstract>
<p>A pair of teams coming off big weekend sweeps will square off
Tonight at Citizens Bank Park, where the Philadelphia Phillies
welcome the Arizona Diamondbacks for the start of a three-game
series.</p>
</abstract>
</body.head>
<body.content>
<p>(Sports Network) - With the Philadelphia Phillies picking
up momentum after their three-game sweep of the Atlanta Braves,
and the Arizona Diamondbacks capturing all four of their games
against the Houston Astros, tonight's game at Citizen Bank Park
looks set to be a clash of the Titans.</p>
</body.content>
</body>
</nitf>
</inlineXML>
</contentSet>19.5. End of Body <body.end>
There is no formal equivalent to the <body.end> container in NewsML-G2. It’s placement at the end of <body.content> expresses its significance in the format of an article. So it is possible that they would need to be retained in the NITF content conveyed in <inlineXML>, or expressed in another mark-up language.
The NewsML-G2 equivalent of <tagline> would be <by> with a @role if necessary to refine its use. <bibliography> may be expressed using NewsML-G2 <description> with a @role. Their placement relative to the parent text is a processing issue – NewsML-G2 is format-agnostic.
20. Mapping Embedded Photo Metadata to NewsML-G2
20.1. Introduction
Embedded metadata in JPEG and other file formats have been a de facto standard since the 1990s. In fact, the metadata schema adopted by Adobe Systems Inc for the original "File Info" dialog box in Photoshop is based on the IPTC Information Interchange Model (IIM). This standard for exchanging all types of news assets and metadata pre-dates XML-based standards such as NewsML-G2. The IIM-based embedded properties in images became known as the "IPTC Fields" or "IPTC Header" and they were widely adopted in professional workflows.
In about 2001, in order to overcome some technical limitations imposed by this legacy model, Adobe introduced the Extensible Metadata Platform, or XMP, to its suite of applications that includes Photoshop. Adobe also worked with the IPTC to migrate the properties of the legacy "IPTC Header" to XMP. Most of the original IIM-based metadata properties are contained in the IPTC Core Schema for XMP. Further IPTC properties that are derived from NewsML-G2 properties are available in the IPTC Extension Schema for XMP.
| Although developed by Adobe, XMP is an open technology like its IIM-based predecessor, and has been adopted by other software vendors and manufacturers. Adobe and others, including Microsoft, Apple and Canon, have formed the Metadata Working Group, a consortium that promotes preservation and inter-operability of digital image metadata. The MWG web site is www.metadataworkinggroup.org. |
However, when IIM-based properties were added to software packages such as Photoshop, the original semantic definitions of IIM were left behind, and in the absence of formal definitions, the use of these properties among vendors and agencies began to diverge as semantics of the labels were interpreted differently. The IPTC addressed this in 2005 by bringing interested parties together to agree the IPTC Photo Metadata Standard, based on recognised current industry practice. The latest version (as of this edition of the Guidelines) was approved in 2016. (For more information on the Standard visit the IPTC website www.iptc.org and navigate to Photo Metadata.)
A mapping of IIM legacy properties to NewsML-G2 is given below in IIM to NewsML-G2 Field Mapping Reference, but this can only be regarded as "the basics". A full mapping of the IPTC Photo Metadata Standard backwards to IIM (where feasible) and forwards to NewsML-G2 may be found at IPTC Photo Metadata Mapping on the IPTC website. Note that because the photo metadata world has moved on since the original IIM specification, the semantic interpretation of IIM in the mapping guide follows the Photo Metadata Standard, which is in some cases slightly different to the IIM 4.2 Specification.
20.2. IPTC Metadata for XMP
To use the IPTC Photo Metadata in Adobe CS3 and CS4 a set of custom panels for Bridge must be downloaded from the IPTC web site and installed on your Windows or Mac OS X computer. Adobe CS5 and higher provides built-in File Info panels covering both IPTC Core and Extension. Be aware that these custom panels only work up to version CS 5.5 of Bridge. To download visit www.iptc.org and navigate to Photo Metadata.
The IPTC web site also lists image manipulation software packages that synchronize the legacy IIM-based header fields and XMP properties. The IPTC Custom Panels User Guide tabulates the field labels used by IIM, IPTC Core, and the equivalent fields of software packages such as Photoshop, iViewMedia, Thumbs, and Irfanview.
20.3. Synchronizing XMP and legacy metadata
When opening an image that contains the legacy IIM-based IPTC metadata, using an application that supports XMP, users may need to be aware of synchronization issues. Digital images that pre-date XMP contain the legacy IIM-based metadata in a special area of the JPEG, TIFF or PSD file called the Image Resource Block (IRB). XMP-aware applications store metadata in the file differently, in the XMP Packet.
Current versions of Adobe’s software such as Photoshop write the metadata to the IIM-header wrapped by the IRB, and to the XMP packet, when saving a file. Therefore, an image which contained only legacy metadata when opened could have metadata written to a new XMP packet (where an IIMXMP mapping exists) when saved.
If a picture with XMP metadata is modified by a non-compliant application (i.e. the IRB only is changed), this should be detected by the next XMP-compliant processor that opens the picture, using a checksum. The Metadata Working Group guidance document has a detailed chapter on these synchronization issues.
There is no guarantee that the synchronization of legacy and XMP metadata will be supported in future versions of Adobe software, or applications from other vendors.
20.4. Picture services using IIM/XMP
Many news and picture agencies deliver images to their customers using IIM. Customers receive these services in three variants:
-
As binary files such as JPEG that support embedded IIM metadata in the file header as "IPTC Fields" and/or XMP.
-
As binary files such as JPEG with additional embedded IIM fields beyond the set adopted by Adobe that are used by proprietary image-management software applications. These fields are not read by off-the-shelf software packages such as Photoshop. This format is used by the photo departments of many news agencies.
-
As binary IIM files which consist of the IIM envelope and associated object (picture) data. The conveyed picture may also contain embedded IPTC-IIM fields, but this metadata may not be synchronized with the IIM envelope in all instances. Providers’ synchronization practices vary.
20.5. Rationale for moving to NewsML-G2
It is probable that providers will continue to embed metadata in image and graphics files, but both providers and customers may derive benefits from exchanging this content using NewsML-G2:
-
metadata carried in a NewsML-G2 document is accessible without the need to retrieve and open the associated image file;
-
in some business applications, editors have to modify picture metadata but have no access or permission to modify the metadata in the image file, and the provider needs therefore to instruct receivers to use the NewsML-G2 metadata;
-
partners in an information exchange can standardise on a common method for managing all kinds of news objects.
-
Some news providers’ picture services are already being migrated to NewsML-G2. Some are already using NewsML-G2 as their internal standard for storing and exchanging all types of news objects; it makes sense to migrate to a common standard for customer-facing applications too.
-
IIM is a legacy format and has some inherent issues, such as limits on field lengths and difficulty with internationalization.
20.6. IIM resources
The IPTC web site has an IIM Home page. Visit www.iptc.org/standards and follow the link to IIM to view the Specification and other documents. These include a list of software packages that support IIM metadata fields, and a link to a document that maps IIM fields IPTC Core (XMP) Software Package labels, maintained by David Riecks at www.controlledvocabulary.com.
More about the use of IIM for photos can be found in the "Photo Metadata" section of the IPTC website.
20.7. Approach
Although IIM can handle any type of media object, its use for media types other than pictures is now rare, so this section will focus on the issue of migrating IIM picture metadata, chiefly those found in Adobe’s Photoshop "IPTC Header", to NewsML-G2 properties. It is NOT intended to describe a mapping of the complete IIM envelope or IPTC Photo Metadata Standard to NewsML-G2. (Available at IPTC Photo Metadata Mapping)
20.8. IIM to NewsML-G2 Field Mapping Reference
IIM is organised into Records and DataSets. The DataSets that are embedded in image files are in the Application Record (Record Two). Each IIM DataSet is labelled according to the parent Record and its position within the Record (these numbers are not necessarily contiguous). The IIM Specification contains details of the record structure.
The table below shows IIM DataSets that have been (with noted exceptions) adopted for the IPTC Photo Metadata. Each DataSet is shown with its IIM name, equivalent IPTC Photo Metadata Name (if available), and the corresponding NewsML-G2 Property.
| DataSet | IIM Name | IPTC Photo Metadata Name | NewsML-G2 Property |
|---|---|---|---|
2:05 |
Object Name |
Title |
itemMeta/title |
2:10 |
Urgency |
(Deprecated) |
contentMeta/urgency |
2:15 |
Category |
(Deprecated) |
contentMeta/subject |
2:20 |
Supplemental Category |
(Deprecated) |
contentMeta/subject |
2:25 |
Keywords |
Keywords |
contentMeta/keyword |
2:40 |
Special Instruction |
Instructions |
itemMeta/edNote Alternative: rightsInfo/usageTerms |
2:55 |
Date Created |
Date Created |
contentMeta/contentCreated |
3:20 |
By-Line |
Creator |
contentMeta/creator/name |
3:25 |
By-line Title |
Creator’s Jobtitle |
contentMeta/creator/related |
3:30 |
City |
City (legacy) |
if interpreted as city of the location the photo was taken contentMeta/located/POIDetails/address/locality/name OR if interpreted as city of the location shown contentMeta/subject -→ assert/POIDetails/address/locality/name |
3:32 |
Sub-location |
Sublocation (legacy) |
if interpreted as sublocation of the location the photo was taken contentMeta/located/POIDetails/address/line OR if interpreted as sublocation of the location shown contentMeta/subject -→ assert/POIDetails/address/line |
3:35 |
Province/State |
Province or State (legacy) |
if interpreted as province of the location the photo was taken contentMeta/located/POIDetails/address/area/name OR if interpreted as province of the location shown contentMeta/subject -→ assert/POIDetails/address/area/name |
3:40 |
Country/Primary Location Code |
Country Code (legacy) |
if interpreted as country of the location the photo was taken contentMeta/located/POIDetails/address/country/@uri OR if interpreted as country of the location shown contentMeta/subject -→ assert/POIDetails/address/country/@uri |
3:41 |
Country/Primary Location Name |
Country (legacy) |
if interpreted as country of the location the photo was taken contentMeta/located/POIDetails/address/country/name OR if interpreted as country of the location shown contentMeta/subject -→ assert/POIDetails/address/country/name |
3:43 |
Original Transmission Reference |
Job ID |
itemMeta/altId If the reference is a Job ID use itemMeta/ memberOf |
3:45 |
Headline |
Headline |
contentMeta/headline |
3:50 |
Credit |
Credit Line |
contentMeta/creditline |
3:55 |
Source |
Source |
contentMeta/infoSource |
3:56 |
Copyright Notice |
Copyright Notice |
rightsInfo/copyrightNotice |
4:00 |
Caption/Abstract |
Description |
contentMeta/description |
4:02 |
Writer/Editor |
Description Writer |
contentMeta/contributor (with @role to indicate the role of the contributor |
Note: deprecated properties are no longer supported in IPTC Photo Metadata |
20.9. IIM to NewsML-G2 Mapping Example
The screenshot below shows fields of the IPTC Panel in Adobe Photoshop’s File Info dialog, containing metadata from the IPTC Core metadata schema. Note the neighbouring tab labelled IPTC Extension that contains metadata fields of the IPTC Extension schema.
The table below maps the IIM DataSets from the example to NewsML-G2. In the succeeding paragraphs, the mapping discussed in more detail.
| DataSet | IIM Name | Value | Notes |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
20.9.1. Object Name / Title
The <title> element is a child of <itemMeta> and is intended to be a human-readable identifier. The <itemMeta> block also contains some mandatory NewsML-G2 elements, as shown:
<itemMeta>
<itemClass qcode="ninat:picture" />
<provider qcode="ex-prov:acmenews" />
<versionCreated>2022-10-19T02:20:00Z</versionCreated>
<pubStatus qcode="stat:usable" />
<fileName>USA-CRASH-MILITARY_001_HI.jpg</fileName>
<title>USA-CRASH/MILITARY</title>
<edNote />
</itemMeta>Some providers may additionally map this DataSet to the NewsML-G2 <slugline> property in <contentMeta>:
<slugline>USA-CRASH/MILITARY</slugline>20.9.2. Urgency
The DataSet Urgency has been deprecated in the latest version of the IIM, and in the IPTC Photo Metadata Standard. It may still be used in some services, and therefore if present may be mapped to the corresponding NewsML-G2 property, which is a child of <contentMeta>:
<urgency>4</urgency>20.9.3. Keywords
The semantics of keyword are somewhat open: some providers use keywords to denote "key" words that can be used by text-based search engines; some use "keyword" to categorise the content using mnemonics, amongst other examples. The IPTC recommends that the IIM/Photo Metadata Keywords property is mapped to the repeatable <keyword> element in NewsML-G2 (one <keyword> element per keyword)
If this mapping cannot be assumed, the IPTC suggests the following rules when configuring a mapping of Keywords metadata:
-
Assess if any existing NewsML-G2 properties align to this use of keyword. Typical examples are
-
Genres ("Feature", "Obituary", "Portrait", etc.)
-
Media types ("Photo", "Video", "Podcast" etc.)
-
Products/services by which the content is distributed
-
-
If the keyword expresses the subject of the content it MAY go into the <subject> property with the keyword string placed in a <name> child element of the subject with a language tag if required.
-
If migrated to <subject>, providers should also consider:
-
Adding @type if the nature of the concept expressed by the keyword can be determined
-
Using a QCode if there is a corresponding concept in a controlled vocabulary
-
If none of the above conditions are met, then implementers should default to using <keyword> with a @role if possible to define the semantic of the keywords.
The contents of the Keywords field in the example shown are intended to be used as natural-language "key" words that could be used by a text-based search engine to index the content. Therefore, they will be mapped to <keyword>.
<keyword role="ex-krole:index">us</keyword>
<keyword role="ex-krole:index">military</keyword>
<keyword role="ex-krole:index">aviation</keyword>
<keyword role="ex-krole:index">crash</keyword>
<keyword role="ex-krole:index">fire</keyword>In IIM, the Keywords DataSet is repeatable, with each holding one keyword; therefore each keyword is mapped to separate <keyword> properties, even though they may appear as a comma-separated list in software application dialogs.
20.9.4. Special Instruction
The contents of this field could go into <edNote>, a child of <itemMeta>, which is placed after the <title> element (if present), if the nature of the instruction is a generic message to the receiver or its nature is unknown:
<itemMeta>
...
<edNote>NO ARCHIVAL OR WIRELESS USE</edNote>
</itemMeta>If appropriate and advised by the provider, an alternative mapping for the contents of this field MAY be <usageTerms>, parts of the <rightsInfo> block:
<rightsInfo>
<copyrightHolder qcode="ex-prov:TR">
<name>Thomson Reuters</name>
</copyrightHolder>
<copyrightNotice>Copyright 2008 Thomson Reuters. </copyrightNotice>
<usageTerms>NO ARCHIVAL OR WIRELESS USE</usageTerms>
</rightsInfo>20.9.5. Date Created
This maps to <contentCreated>, a child of <contentMeta>, since it refers to the content itself, for example:
<contentMeta>
<contentCreated>2008-12-08</contentCreated>
...
</contentMeta>When there is a Time Created value present in the IIM Record, this should be merged with Date Created, as the NewsML-G2 property accepts a Truncated DateTime value (i.e. the value may be truncated if parts of the Date-Time are not available).
| If present, the time part must be used in full, with time zone, and ONLY in the presence of the full date. |
<contentMeta>
<contentCreated>2008-12-08T13:30:00-08:00</contentCreated>
...
</contentMeta>20.9.6. By-line, Credit, Source
These three IIM DataSets are complementary, but each has a distinct application:
-
By-line is intended to identify the creator of the content
-
Credit identifies the provider of the content
-
Source holds the identity of a party having a role in the supply chain of the content.
By-line
The recommended mapping for By-line (IIM 2:80) is to the <creator> child element of <contentMeta>, rather than <by>. This is because <creator> is an administrative property that is intended to be machine-readable; the IPTC recommends that controlled vocabularies should be used if possible. The NewsML-G2 <by> property is a human-readable natural language property that is intended for display, but does not unambiguously identify the creator.
The example below shows this identification metadata in its administrative context. Expressed in this way using QCodes, the metadata can be used for administration and search. Using a CV, the photographer can be uniquely and unambiguously identified. The optional <name> is shown, and the <creator> property also allows the use of the child element <related> which in this case is used to express the photographer’s job title, again using a QCode, from IIM DataSet 2:85 (By-line Title)
<creator qcode="ex-pers:JS001">
<name>John Smith</name>
<related rel="ex-personrel:jobtitle"qcode="ex-stafftitles:photo">
<name>Staff Photographer</name>
</related>
</creator>Credit
Credit should be mapped to the <creditline> child property of <contentMeta>. There is a <provider> property of <itemMeta>, but the Credit does necessarily reflect the provider. Many picture providers use IIM Credit to display the name of the person, organisation, or both, who should be credited when the picture is used. In this context, <creditline> is appropriate because it is a natural-language label that is intended to be displayed.
<creditline>Acme/John Smith</creditline>Source
In the original IIM specification up to 4.1, Source refers to the initial holder of the copyright. In IIM 4.2, the semantics of Source were changed to be "…a person or party who has a role in the content supply chain. This could be an agency, a member of an agency, an individual or a combination. Source could be different from Creator and from the entities in the Copyright Notice.". This more "open" definition reflects current usage by the broad range of users and aligns with the Photo Metadata Standard.
In some distribution systems, the original owner of the copyright (as distinct from the current owner) is important, and some providers use the Source field for this information. This was the original intention of the IIM Specification which used Source for the Original Owner, and the Copyright Notice (DataSet 2:116) to hold the copyright statement which includes the Current Owner.
Using the current definition of Source, the recommended mapping to
NewsML-G2 is the <infoSource> element, a child of <contentMeta> (OR if
the source is the original copyright owner
<rightsInfo> (with @validto time delimiter) with a <copyrightHolder>
child element).
In this case, the original copyright holder is Thomson Reuters, and the Source of the content (an image in this example) is Acme News. The following uses a controlled value to indicate the @role of the party named as the Information Source:
<contentMeta>
...
<infoSource role="cpprole:imgSupplier">
<name>Acme News LLC</name>
</infoSource>
...For more on this topic, see Identifying Sources and Workflow Actors
20.9.7. City, Province/State and Country
As discussed in Pictures and Graphics, geographical metadata in images may have different contexts:
-
The location from which the content originates, i.e. where the camera was located. NewsML-G2 has a <located> property to express this.
-
The location shown in the picture – in NewsML-G2 this is a <subject> property of the picture.
Although for the majority of pictures, these are effectively the same spot, one can envisage situations where these two semantically distinct locations are not in the same place: a picture of Mount Fuji taken from downtown Tokyo is one example which is often quoted.
When mapping from IIM or IIM-based Photoshop fields, we assume that the intention of the provider is to express the location shown in the image, as this is the more customary use of these fields. (Be aware that specific providers may have their own convention, and receivers are advised to check).
The location shown in the example image may be expressed using a single <subject> property for the location, linked to an <assert> block:
<contentMeta>
...
<subject type="cpnat:poi" literal="int001" />
...
</contentMeta>
<assert literal="int001">
<POIDetails>
<address>
<line>University City</line>
<locality qcode="ex-city:int002" type="ex-cpnatexp:geoAreaCity">
<name>San Diego</name>
</locality>
<area qcode="ex-state:int003" type="ex-cpnatexp:geoAreaProvState">
<name>California</name>
</area>
<country qcode="iso3166-1a2:US" type="ex-cpnatexp:geoAreaCountry">
<name>United States</name>
</country>
</address>
</POIDetails>
</assert>Using <assert> in this way can be an advantage if a concept is used more than once in the NewsML-G2 Item. For example if both the Location Shown and the Location Created are the same place, all of the required concept details can be grouped in one <assert> and shared by both properties, for example:
<located type="cpnat:poi" literal="int001" />
<!-- Camera location -->
...
<subject type="cpnat:poi" literal="int001" />
<!-- Subject of picture -->
...
<assert literal="int001">
<POIDetails>
...20.9.8. Original Transmission Reference
This is defined in IIM as "a code representing the location of original transmission", but in common usage this DataSet has a broader use as an identifier for the purpose of improved workflow handling (IPTC Photo Metadata: Job ID). These uses include:
-
As an identifier for the picture (perhaps on some content management system)
-
As an identifier for a series of pictures, of which this one is part, e.g. a group of pictures of the same event.
The first use should be mapped to the NewsML-G2 property <altId>, a child of <contentMeta>. <altId> has two attributes: @type indicates the context of the identifier using a QCode, and @environment indicates the business environment in which the identifier can be used. This is expressed using one or more QCodes (QCode List).
<altId type="ex-idtype:systemRef" environment="ex-acmesys:mdn ex-acmesys:iim">SAD02</altId>If the DataSet represents a Job ID, the recommended mapping is to the NewsML-G2 <memberOf> property, a child of <itemMeta>:
<memberOf type="ex-ref:jobref">
<name>SAD02</name>
</memberOf>20.9.9. Headline
Maps to the <headline> child of <contentMeta>, a block type element:
<headline xml:lang="en-US">A firefighter walks past the remains of a military jet that crashed into homes in the University City neighborhood of San Diego
</headline>Note the use of @xml:lang to declare the language and variant "en-US".
20.9.10. Copyright Notice
These fields correspond to the <copyrightNotice> element, a child of the <rightsInfo> block.
<copyrightNotice>
Copyright 2008 Thomson Reuters
</copyrightNotice>20.9.11. Caption/Abstract
The contents of this field are placed in the <description> element, part of <contentMeta> with a @role attribute to denote that the description is a picture caption:
<description xml:lang="en-US" role="drol:caption">
A firefighter in a flameproof suit walks past the remains of a military jet that crashed
into homes in the University City neighborhood of San Diego, California December 8, 2008.
The military F-18 jet crashed on Monday into the California neighborhood near San Diego
after the pilot ejected, igniting at least one home, officials said.
</description>20.9.12. Writer/Editor
The caption writer is often a different person to the photographer, so aligns with the NewsML-G2 <contributor> property, a child of <contentMeta>. If possible, use a QCode value to unambiguously identify the contributing person and a @role to describe their role in the workflow. This property may be extended to include contact details and other information such as job title.
<contributor role="cpprole:descrWriter" qcode="ex-pers:CK" />The listing below combines the examples above into a complete listing. The following options have been used:
-
<usageTerms> used for Special Instructions, instead of <edNote>
-
<assert> used in conjunction with <subject> to express the location shown in the image.
-
<altId> used for the Original Transmission Reference (instead of <memberOf>)
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values (note that they are prefixed "ex-" to aid readability): ex-acmesystem, ex-cat, ex-city, ex-cpnatexp, ex-idtype, ex-krole, ex-pers, ex-personrel, ex-prov, ex-stafftitles, ex-suppcat and ex-state.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="tag:acmenews.com,2008:WORLD-NEWS:USA20081208098658"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http:/www.acmenews.com/customer/cv/catalog4customers-1.xml" />
<rightsInfo>
<copyrightHolder qcode="ex-prov:TR">
<name>Thomson Reuters</name>
</copyrightHolder>
<copyrightNotice>
Copyright 2008 Thomson Reuters
</copyrightNotice>
<usageTerms>NO ARCHIVAL OR WIRELESS USE</usageTerms>
</rightsInfo>
<itemMeta>
<itemClass qcode="ninat:picture" />
<provider qcode="ex-prov:acmenews" />
<versionCreated>2022-10-19T02:20:00Z</versionCreated>
<pubStatus qcode="stat:usable" />
<fileName>USA-CRASH-MILITARY_001_HI.jpg</fileName>
<title>USA-CRASH/MILITARY</title>
<edNote />
</itemMeta>
<contentMeta>
<urgency>4</urgency>
<contentCreated>2008-12-08T17:30:00-08:00</contentCreated>
<infoSource role="cpprole:imgSupplier">
<name>Acme News LLC</name>
</infoSource>
<creator qcode="ex-pers:JS001">
<name>John Smith</name>
<related rel="ex-personrel:jobtitle" qcode="ex-stafftitles:photo">
<name>Staff Photographer</name>
</related>
</creator>
<altId type="ex-idtype:systemRef" environment="ex-acmesys:mdn ex-acmesys:iim">SAD02</altId>
<contributor role="cpprole:descrWriter" qcode="ex-pers:CK" />
<subject type="cpnat:poi" literal="int001" />
<headline xml:lang="en-US">A firefighter walks past the remains of a military
jet that crashed into homes in the University City neighborhood of San Bernardino
</headline>
<description xml:lang="en-US" role="drol:caption">A firefighter in a flameproof
suit walks past the remains of a military jet that crashed into homes in the
University City neighborhood of San Bernardino, California October 18, 2022. The
military F-18 jet crashed on Monday into the California neighborhood after the
pilot ejected, igniting at least one home, officials said.
</description>
<creditline>Acme/John Smith</creditline>
<keyword role="ex-krole:index">us</keyword>
<keyword role="ex-krole:index">military</keyword>
<keyword role="ex-krole:index">aviation</keyword>
<keyword role="ex-krole:index">crash</keyword>
<keyword role="ex-krole:index">fire</keyword>
<slugline>USA-CRASH/MILITARY</slugline>
</contentMeta>
<assert literal="int001">
<POIDetails>
<address>
<line>University City</line>
<locality qcode="ex-city:int002" type="ex-cpnatexp:geoAreaCity">
<name>San Diego</name>
</locality>
<area qcode="ex-state:int003" type="ex-cpnatexp:geoAreaProvState">
<name>California</name>
</area>
<country qcode="iso3166-1a2:US" type="ex-cpnatexp:geoAreaCountry">
<name>United States</name>
</country>
</address>
</POIDetails>
</assert>
<contentSet>
<remoteContent
href="http://www.acmenews.com/content/pictures/hires/20081208/USA-CRASH-MILITARY_001_HI.jpg"
rendition="rnd:highRes" size="3764418" contenttype="image/jpeg" width="2500"
height="1445" colourspace="colsp:USSWOPv2" />
</contentSet>
</newsItem>20.10. Reconciling NewsML-G2 with embedded metadata
Where equivalent properties exist in both NewsML-G2 metadata and embedded (XMP or EXIF) metadata, the IPTC recommends that embedded administrative metadata, such as <located>, MAY take precedence over NewsML-G2 metadata, subject to guidance from the provider, and always with caution.
For example, a picture may have GPS metadata embedded by the camera, which may be different from the <located> property entered by a journalist.
The difference may be one of precision: the GPS co-ordinates may be precise, but hardly useful to the ultimate consumer. Even if a human-readable value is derived from the GPS data, would this be better than the information, if accurate, provided by the journalist? If the difference is due to inaccuracy, the receiver would have no way of knowing whether the journalist has made a mistake, or whether the camera is incorrectly set.
21. Rights Metadata
Rights-related metadata has become increasingly important, and feedback to the IPTC from the news industry pointed to the need for a more granular design of applying <rightsInfo> to the item and/or content.
The IPTC has taken over responsibility for the management of the ACAP (Automated Content Access Protocol), the publisher-led project to develop tools for the communication of copyright permissions information on web sites. As a next step a news content specific Profile for Open Digital Rights Language (ODRL) version 2.0 has been defined, branded RightsML, which identifies those features of ODRL 2.0 that can most usefully be employed in news syndication and defines additional vocabulary for expressing the usage permissions and constraints that are particular to the news industry. RightsML enables a wide range of usage policies to be expressed in NewsML-G2. See the RightsML web site www.rightsml.org for further details.
While the NewsML-G2 <rightsInfo> wrapper and its properties are machine-readable, the assertion of rights within the NewsML-G2 properties is expressed in natural-language terms. However, the Extension Point of <rightsInfo> enables properties from another namespace to be added, and this would include ODRL and the RightsML Profile. A description of this implementation is outside the scope of these Guidelines.
Machine-reading of <rightsInfo> by a processor is targeted at being able to determine the following:
-
To which element(s) inside an item does a specific <rightsInfo> wrapper apply? (rights holder’s view)
-
Which is/are the <rightsInfo> wrapper(s) that apply to a specific element? (content user’s view)
21.1. Rights Info - simple implementation
The <rightsInfo> wrapper has child elements of
-
accountable (0..1) The person responsible for legal issues regarding the content (in some jurisdictions)
-
copyrightHolder (0..1) The person or organisation claiming intellectual property ownership of the content
-
copyrightNotice (0..unbounded) The formal statement claiming the Intellectual Property Ownership (IPO)
-
usageTerms (0..unbounded) A natural-language statement of how the content may be used.
For example:
<rightsInfo>
<copyrightHolder qcode="nprov:AcmeNews">
<name>Reuters</name>
</copyrightHolder>
<copyrightNotice>Copyright 2010 Reuters. Click For
Restrictions - http://about.reuters.com/fulllegal.asp
</copyrightNotice>
<usageTerms xml:lang="en">NO ARCHIVAL OR WIRELESS USE</usageTerms>
</rightsInfo>21.1.1. Link to an external Rights Information resource
A provider may need to refer to an external resource containing rights information and instructions. This can be accomplished using the <link> element of <rightsInfo>:
<rightsInfo>
<copyrightHolder uri="http://www.acmenews.com" />
<copyrightNotice>Copyright 2012 Acme Newswire</copyrightNotice>
<link
href="http://acmenews.com/rights/rightspolicy123.xml"
contenttype="text/xml"
/>
</rightsInfo>21.2. Advanced Rights Information implementations
More advanced Rights metadata may be added to <rightsInfo>:
-
By asserting rights separately to different parts and/or different aspects of the NewsM-G2 Item, for example by separating rights to the metadata from the content rights.
-
By using <rightsExpressionXML> and/or <rightsExpressionData> to assert rights using other rights expression languages and encodings.
-
Via the Extension Point to <rightsInfo>, but only as an XML-encoded structure.
21.2.1. Asserting separate rights to parts or aspects of an Item
Business Reasons
-
Business users potentially need to assert different rights to different parts of a News Item. For example, a photo library may not own the copyright to a picture, but does want to assert intellectual property ownership of the keywords (i.e. the metadata). This leads to the need to distinguish between rights to the content, and rights to metadata, or parts of the metadata. End users need a simple mechanism for addressing a whole group of XML elements as being governed by a <rightsInfo> expression.
-
Implementers need a clear set of rules for expressing rights to XML elements identified by an @id. The <partMeta> wrapper is an existing NewsML-G2 construct for this purpose and in order to have a consistent processing model, the <rightsInfo> wrapper expresses rights via <partMeta> to the target element, rather than directly to the target element.
Expressing Scope and Aspect properties of <rightsInfo>
Two attributes enable implementers to define the scope of a rights expression and assert the aspect of the intellectual property rights that are being claimed:
-
scope; (0..1), QCodeListType; allows a provider to indicate whether the rights expression is about the content, the metadata, or both. If the attribute is not present then<rightsInfo> applies to all parts of the Item. There is a mandatory NewsCodes scheme for the values, see below. The CV contains two values: "content" and "metadata".
-
aspect; (0..1), QCodeListType; allows the provider to assert rights to a specific intellectual effort. In terms of metadata, this can express rights to the actual metadata values used, and/or it can express rights to the work in applying metadata values. @aspect also enables providers to assert rights to the structure of content, for example the structure of a package of news. If the attribute does not exist then <rightsInfo> applies to all aspects. There is a mandatory NewsCodes scheme for the values, see below. The CV contains three values: "values", "selection" and "structure".
The optional @idrefs attribute is defined as:
"Reference(s) to the part(s) of an Item to which the <rightsInfo> element applies. When referencing part(s) of the content of an Item, @idrefs must include the @partid value of a partMeta element which in turn references the part of the content."
Rights Info Scope NewsCodes
Scheme URI: http://cv.iptc.org/newscodes/riscope/
Recommended scheme alias: riscope
| Code | Definition |
|---|---|
content |
Encompasses all child elements of a) <contentSet> in a News Item, b) <concept> in a Concept Item, c) <conceptSet> in a Knowledge Item and d) <groupSet> (except all children of <itemRef>) in a Package Item. Any parts of content which are described by <partMeta> elements are also included. |
metadata |
Encompasses all child elements of an item, except a) those that are in the scope of the 'content' scope indicator and b) all children of <itemRef> elements in a Package Item. |
Rights Aspect NewsCodes
Scheme URI: http://cv.iptc.org/newscodes/riaspect/
Recommended scheme alias: raspect
| Code | Definition |
|---|---|
values |
The <rightsInfo> element makes an assertion about metadata values including the details of concepts. This aspect applies only to the Rights Info Scope of “metadata”. |
selection |
The <rightsInfo> element makes an assertion about selecting and applying metadata values or selecting and applying item references in a Package Item. This aspect applies a) to the Rights Info Scope of “metadata” and b) to the Rights Info Scope of “content” for Package Items. |
structure |
The <rightsInfo> element makes an assertion about the design of the structure of the content, e.g. the structure of a Package Item. This aspect applies only to the Rights Info Scope of “content”. |
21.2.2. Use cases for @scope and @aspect
Separating rights for "content" and "metadata"
A photo library sends a customer a picture. The Intellectual Property (IP) in the picture itself (the content) is owned by a third party. The photo library wants to assert the rights to the metadata that accompanies the picture. This is expressed by the following <rightsInfo> blocks:
<newsItem>
...
<!-- Content: Third Party -->
<rightsInfo scope="riscope:content">
<copyrightHolder>
<name>Example Pictures</name>
</copyrightHolder>
<copyrightNotice>Copyright 2008 Example Pictures Ltd. Click For
Restrictions - http://about.example.com/legal.asp
</copyrightNotice>
<usageTerms xml:lang="en">MUST COURTESY PARAMOUNT PICTURES
FOR USE OF "THE CURIOUS CASE OF BENJAMIN BUTTON" WITH NO ARCHIVAL USE
</usageTerms>
</rightsInfo>
<!-- Metadata: Photo Library -->
<rightsInfo scope="riscope:metadata">
<copyrightHolder>
<name>The Picture Library</name>
</copyrightHolder>
<copyrightNotice>Copyright 2008 The Picture Library Ltd.
</copyrightNotice>
</rightsInfo>Separating rights for part of the metadata
The photo library sends a third-party picture (the content), but wishes to express rights to only a specific part of the metadata. The properties representing this part are identified by @idrefs, and the scope has been omitted, since the targets are the values of the specific referenced elements.
<newsItem>
...
<!-- All: Third Party -->
<rightsInfo>
<copyrightHolder>
<name>Example Pictures</name>
</copyrightHolder>
<copyrightNotice>Copyright 2008 Example Pictures Ltd. Click For
Restrictions - http://about.example.com/legal.asp
</copyrightNotice>
<usageTerms xml:lang="en">MUST COURTESY PARAMOUNT PICTURES
FOR USE OF "THE CURIOUS CASE OF BENJAMIN BUTTON" WITH NO ARCHIVAL USE
</usageTerms>
</rightsInfo>
<!-- Part of the Metadata: Picture Library -->
<rightsInfo idrefs="id001 id002 id003 id004 id005">
<copyrightHolder>
<name>The Picture Library</name>
</copyrightHolder>
<copyrightNotice>Copyright 2008 The Picture Library Ltd.
</copyrightNotice>
</rightsInfo>
...
<contentMeta>
...
<keyword id="id001" role="ex-krole:index">us</keyword>
<keyword id="id002" role="ex-krole:index">military</keyword>
<keyword id="id003" role="ex-krole:index">aviation</keyword>
<keyword id="id004" role="ex-krole:index">crash</keyword>
<keyword id="id005" role="ex-krole:index">fire</keyword>
...
</contentMeta>
...Separating rights for aspects of part of the metadata
The photo library sends a third-party picture (the content), expressing rights to part of the metadata. Since the IP of the scheme being used belongs to another party, the picture library expresses its ownership of rights associated with applying the metadata to the picture, and also acknowledges the Scheme Authority’s rights to the code values themselves.
<newsItem>
...
<!-- All: Third Party -->
<rightsInfo>
<copyrightHolder>
<name>Example Pictures</name>
</copyrightHolder>
<copyrightNotice>Copyright 2008 Example Pictures Ltd. Click For
Restrictions - http://about.example.com/legal.asp
</copyrightNotice>
<usageTerms xml:lang="en">MUST COURTESY PARAMOUNT PICTURES
FOR USE OF "THE CURIOUS CASE OF BENJAMIN BUTTON" WITH NO ARCHIVAL USE
</usageTerms>
</rightsInfo>
<!-- Part of the Metadata Values: Another Party -->
<rightsInfo idrefs="id001 id002" aspect="riaspect:values">
<copyrightHolder>
<name>International Press Telecommunications Council</name>
</copyrightHolder>
<copyrightNotice>
Copyright 2008 International Press Telecommunications Council.
</copyrightNotice>
</rightsInfo>
<!-- Part of the Metadata Selection: Picture Library -->
<rightsInfo idrefs="id001 id002" aspect="riaspect:selection">
<copyrightHolder>
<name>The Picture Library</name>
</copyrightHolder>
<copyrightNotice>Copyright 2008 The Picture Library Ltd.
</copyrightNotice>
</rightsInfo>
...
<contentMeta>
...
<subject id="id001" type"cpnat:abstract" qcode="medtop:20000106" />
<subject id="id002" type"cpnat:abstract" qcode="medtop:02000000" />
...
</contentMeta>
...Expressing rights to different parts of content
A news agency sends a text article (the content) that includes a substantial extract of content owned by another party. The overall rights to both the content and metadata of the article are expressed using a <rightsInfo> wrapper with no attributes. The rights owned by the third party to the extract are "carved out" by using a separate <rightsInfo> wrapper that references the extract within the article via <partMeta>:
<newsItem>
...
<!-- All: News Agency -->
<rightsInfo>
<copyrightHolder>
<name>Example News</name>
</copyrightHolder>
<copyrightNotice>Copyright 2010 Example News Ltd. Click For
Restrictions - http://about.example.com/legal.asp
</copyrightNotice>
<usageTerms xml:lang="en">
REGIONAL PRESS ONLY. NO BROADCAST OR WEB USE
</usageTerms>
</rightsInfo>
<!-- Part of the Content: Another Party -->
<rightsInfo idrefs="id001">
<copyrightHolder qcode="nprov:reuters">
<name>Thomson Reuters</name>
</copyrightHolder>
<copyrightNotice>Copyright 2010 Thomson Reuters.
</copyrightNotice>
</rightsInfo>
<contentMeta>
...
</contentMeta>
<partMeta partid="id001" contentrefs="p001"/>
<inlineXML>
...
<p>...still the aftershocks of the banking crisis continue to rumble,
With many analysts noting big changes in the role of sovereign wealth
funds.
... </p>
<p>According to a recent special report by Thomson Reuters: <br />
<span id="p001">"Dubai's crisis prompted a shift of power to the rulers in Abu
Dhabi, the wealthiest of the seven states that make up the United Arab
Emirates.Now a chastened Dubai is recovering some of its confidence as it
seeks to convince international investors it can deliver now where last
year it failed."</span></p>
...
</inlineXML>
</newsItem>Expressing rights to aspects of content
A news provider operates a distribution platform where third-party companies can sign up to provide their own news and information packages to the subscriber base. The platform provider has created standard package templates using NewsML-G2, which the other companies populate with their chosen topics. The provider asserts its right to the structure of the news packages, whilst the rights to the selection of the news belong to the third party, as shown:
<packageItem>
<!-- A Package Item is a selection of references to NewsML-G2 Items organised -->
<!-- into a structure of Groups, each with a @role, within a Group Set. -->
...
<!-- Structure: News Provider -->
<rightsInfo scope="riscope:content" aspect="riaspect:structure">
<copyrightHolder>
<name>The News Provider</name>
</copyrightHolder>
<copyrightNotice>
Copyright asserted to the structure of the package<groupSet>
</copyrightNotice>
<usageTerms xml:lang="en">
Usage terms in natural language
</usageTerms>
</rightsInfo>
<!-- Selection: Third Party -->
<rightsInfo scope="riscope:content" aspect="riaspect:selection">
<copyrightHolder>
<name>The News Selector</name>
</copyrightHolder>
<copyrightNotice>
Copyright asserted to the selection of the Item References.
</copyrightNotice>
<usageTerms xml:lang="en">
Usage terms in natural language
</usageTerms>
</rightsInfo>
<!-- Metadata: News Provider -->
<rightsInfo scope="riscope:metadata">
<copyrightHolder>
<name>The News Provider</name>
</copyrightHolder>
<copyrightNotice>
Copyright to the package metadata asserted here.
</copyrightNotice>
</rightsInfo>
...
<groupSet root="root">
<group id="root" role="ex-group:root" mode="pgrmod:bag">
<groupRef idref="grp1" />
<groupRef idref="grp2" />
</group>
<group id="grp1" role="ex-group:main">
<itemRef ...>
...
</itemRef>
<itemRef ...>
...
</itemRef>
</group>
<group id="grp2" role="ex-group:sidebar">
<itemRef ...>
...
</itemRef>
<itemRef ...>
...
</itemRef>
</group>
</groupSet>
</packageItem>Note that the rights expressed about the package content selection and structure are NOT inherited by the Items referenced by the package in each <itemRef>.
21.2.3. Using other machine-readable rights expression languages
XML-serialised rights expressions <rightsExpressionXML>
The optional element <rightsExpressionXML> may be repeated within the <rightsInfo> wrapper and indicates a rights expression as defined by a rights expression language and serialised using XML encoding. The mandatory @langid identifies for the rights expression language using a URI.
Other serialised (non-XML) rights expressions <rightsExpressionData>
<rightsExpressionData> is also an optional, repeatable element indicating a rights expression encoded using any non-XML serialisation and qualified by two mandatory attributes: @langid uses a URI to identify the rights expression language, and @enctype identifies the type of encoding (for example JSON). The IPTC recommends that this is expressed using an IANA Media Type.
21.3. Processing models for extended Rights Info
Please see the Rights Information chapter of the NewsML-G2 Specification at www.newsml-g2.org/spec and also www.iptc.org/standards/rightsml
22. Expressing company financial information
22.1. Background
Company financial information is a common feature of news distributed by many news providers; company information is typically indexed in news using a "ticker symbol", for example:
Apple Inc (NYSE:AAPL) today announced the…
However, this easy and widely-used "shorthand" for indexing company information has a number of traps for those creating machine-readable metadata, especially when dealing with global markets and diverse customer requirements.
Ticker symbols are NOT unambiguous identifiers for companies; they identify specific financial instruments belonging to companies, usually tied to specific markets or exchanges. For example, the ticker symbol for Rio Tinto is "RIO" in London, but "RTP" in New York; similarly NYSE:AAPL identifies shares of Apple Inc. traded on the New York Stock Exchange, not the company. Other issues include:
-
A company may have many different financial instruments, all identified by specific ticker symbols.
-
A company’s shares may be traded on many different markets; the ticker symbols may or may not be the same across markets. For example IBM has the same ticker symbol IBM on the New York, Amsterdam, Frankfurt, London and Mexico Exchanges; as mentioned above, Rio Tinto has the ticker symbol RIO in London, but RTP on the New York, Frankfurt and Mexico exchanges.
-
There are many different schemes for labelling financial markets, for example the London Stock Exchange is variously identified as "LON", "LSE" and "LN" to give only three examples.
The NewsML-G2 <hasInstrument> structure addresses these issues by enabling providers to use a globally unique identifier for companies, and linking each of the company ticker symbols to this identifier, while giving extensive and unambiguous information about each of the ticker symbol. It is a child of the Organisation Details wrapping element <organisationDetails>.
22.2. <hasInstrument> properties (as attributes)
| Definition | Name | Cardinality | Datatype | Example/Notes |
|---|---|---|---|---|
A symbol for the financial instrument |
symbol |
-1 |
String |
symbol="RIO" |
The source of the financial instrument symbol |
symbolsrc |
(0..1) |
QCodeType |
symbolsrc="ex-symsrc:MDNA" |
A venue in which this financial instrument is traded |
market |
(0..1) |
QCodeType |
market="mic:XLON" |
The scheme alias “mic” refers to the ISO-supported Market Identification Code scheme |
||||
The label used for the market |
marketlabel |
(0..1) |
String |
marketlabel="LSE" |
The source of the market label |
marketlabelsrc |
(0..1) |
QCodeType |
marketlabelsrc="ex-mlsrc:MDNA" |
The type(s) of the financial instrument |
type |
(0..1) |
QCodeListType |
type="ex-instrtype:share" |
The rank of the associated financial instrument symbol amongst other symbols |
rank |
(0..1) |
NonNegativeInteger |
rank=1 |
22.2.1. Examples
At its simplest, a symbol for the financial instrument and a label for the market on which it is traded may be sufficient:
<hasInstrument
symbol="AAPL"
marketlabel="NYSE" />It is recommended that the optional @symbolsrc should be used to identify the authority for the symbol. This will disambiguate similar symbols that identify different financial instruments.
<hasInstrument
symbol="AAPL"
symbolsrc="ex-symsrc:MDNA"
marketlabel="NYSE" />Other share identifiers may be used. In this example the ISIN (International Stock Identification Number) is used, and the authority for the symbol is identified as the ISO. Note that the CV only identifies the authority, not the authority’s scheme; which may not be available to the end user. This example does not give a market label, but unambiguously identifies the market on which the instrument is traded using @market and a value from the Market Identification Codes (an ISO scheme) using the scheme alias "mic".
<hasInstrument
symbol="12345678"
symbolsrc="ex-symsrc:ISO"
market="mic:XLON" />The @marketlabel enables the provider to denote the market on which the financial instrument is traded from their own or another’s scheme, and to identify the scheme using the @marketlabelsrc. For example the following identifies the Toronto Stock Exchange from Bloomberg’s CV of market labels:
<hasInstrument
symbol="12345678"
symbolsrc="ex-symsrc:ISO"
marketlabel="####@CN"
marketlabelsrc="_mlsrc:bbg"_ />Financial instruments are identified on many platforms and it may be necessary to indicate the preferred symbol amongst a group of symbols given for a single financial instrument. For example, if the symbols used on a proprietary news platform (for example Reuters or Bloomberg) link to further platform functions, the platform provider will wish to indicate that the use of their symbol is preferred. Rank is used to indicate this preference; in the following example, only one instrument has a rank:
<hasInstrument
symbol="RTO.L"
symbolsrc="ex-symsrc:reuters"
marketlabel="LSE"
rank="1" />
<hasInstrument
symbol="12345678"
symbolsrc="ex-symsrc:ISO"
marketlabel="XLON" />22.3. Adding <hasInstrument> to a NewsML-G2 item
The <hasInstrument> property can be used within a NewsML-G2 News Item in two ways: by reference in Content Metadata from a <subject> element, or from the Content itself via <inlineRef>, In both cases, one or more <hasInstrument> elements are conveyed within an <assert> wrapper element. For more details on the use of <assert> see The Assert wrapper: in a nutshell assertions such as these enable supplementary information about a concept to be carried locally within a NewsML-G2 Item. Into the <assert> wrapper we can place a further wrapping element <organisationDetails> which can contain the <hasInstrument> information:
<assert literal="Acme Widget">
<organisationDetails>
<contactInfo>
<phone>+1 (416) 922 5834</phone>
<email>info@acmewidgets.com</email>
</contactInfo>
<hasInstrument
symbol="AWG"
symbolsrc="ex-symsrc:MDNA"
market="mic:XTSE"
marketlabel="TSX"
marketlabelsrc="ex-mlsrc:MDNA"
type="ex-instrtype:share" />
</organisationDetails>
</assert>The <assert> in this example is identified by a @literal, and is referenced by the same literal value in a <subject> element:
<contentMeta>
<contentCreated>2011-12-06T07:55:00+00:00</contentCreated>
<subject type="cpnat:organisation" literal="Acme Widget">
<name>Acme Widget Sales Inc</name>
</subject>
<headline>
Acme Widgets announces annual results
</headline>
<description role="ex-ANDescRole:abstract">
Acme Widgets (XTSE:AWG), a leader in the
production of quality metal widgets, announced a six per cent increase in profits....
</description>
<language tag="en-US" />
</contentMeta>Note that either a @qcode or @uri could have been used as the identifier, instead of @literal.
Many companies may be mentioned in the content of the News Item; it would be limiting to have to place all of them into <subject> elements. Using <inlineRef>, the <hasInstrument> elements can be referenced from the content, but in order to do so, @idrefs must be added to the assert for each organisation that is referenced in the content:
<assert idrefs="w001" literal="Acme Widget">
<organisationDetails>
<contactInfo>
<phone>+1 (416) 922 5834</phone>
<email>info@acmewidgets.com</email>
</contactInfo>
<hasInstrument
symbol="AWG"
symbolsrc="ex-symsrc:MDNA"
market="mic:XTSE"
marketlabel="TSX"
marketlabelsrc="ex-mlsrc:MDNA"
type="ex-instrtype:share" />
</organisationDetails>
</assert>The organisation is tagged with the corresponding @id in the content (in this case as an attribute of the HTML <span> element).
<h1>Acme Widgets announces annual results </h1>
<p>TORONTO (Agencies) – Leading widget manufacturer <spanid="w001"> Acme Widgets +
(XTSE:AWG)</span> today announced a six per cent jump in quarterly profits for +
Q3 2016 on the back of heavy demand for its latest widget technologyfrom +
automotive customers.</p>All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-ANDescRole, ex-symsrc, ex-mlsrc and ex-instrtype.
<?xml version="1.0" encoding="UTF-8" ?>
<newsItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:acmenews.com:20161019:201003230594296001"
version="15"
standard="NewsML-G2"
standardversion="2.31"
conformance="power"
xml:lang="en-US">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef
href="http://www.acmenews.com/NewsML/acmenews_NewsML-G2_Catalog_1.xml" />
<rightsInfo>
<copyrightHolder uri="http://www.acmenews.com" />
<copyrightNotice>Copyright 2022-23 - Acme Newswire</copyrightNotice>
<usageTerms>Not for distribution in the United
States</usageTerms>
</rightsInfo>
<itemMeta>
<itemClass qcode="ninat:text" />
<provider uri="http://www.acmenews.com" />
<versionCreated>2022-10-19T14:23:00Z</versionCreated>
<firstCreated>2016-10-19T13:15:00Z</firstCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<contentMeta>
<contentCreated>2016-10-19T13:00:00Z</contentCreated>
<subject type="cpnat:organisation" literal="Acme Widget">
<name>Acme Widget Sales Inc</name>
</subject>
<headline>
Acme Widgets announces annual results
</headline>
<description role="ex-ANDescRole:abstract">
Acme Widgets (XTSE:AWG), a leader in the
production of quality metal widgets, announced a six per cent increase in
profits....
</description>
<language tag="en-US" />
</contentMeta>
<assert literal="Acme Widget">
<organisationDetails>
<contactInfo>
<phone>+1 (416) 922 5834</phone>
<email>info@acmewidgets.com</email>
</contactInfo>
<hasInstrument
symbol="AWG"
symbolsrc="ex-symsrc:MDNA"
market="mic:XTSE"
marketlabel="TSX"
marketlabelsrc="ex-mlsrc:MDNA"
type="ex-instrtype:share" />
</organisationDetails>
</assert>
<contentSet>
<inlineXML contenttype="application/xhtml+xml">
<!-- Story text -->
</inlineXML>
</contentSet>
</newsItem>23. Advanced Metadata Techniques
23.1. Introduction
NewsML-G2 provides powerful tools for adding value and navigation to content, using the <assert> and <inlineRef> properties
In the following sections, we will show how implementers can add features such as text mark-up to highlight people and places in the news and provide navigation to further resources.
23.2. The Assert wrapper
The Assert wrapper is an optional and repeatable child of any root Item (<newsItem>, <conceptItem> etc.) and represents a concept that can be identified using either @uri, @qcode or @literal.
An Assert creates a one-time instance of supplementary information about a concept that is local to the Item and can be referenced by the Item’s other properties using either a @uri, @qcode or @literal identifier.
The other attributes of <assert> are (from the Edit Attributes group):
| Name | Datatype |
|---|---|
id |
XML Schema ID |
creator |
QCode |
creatoruri |
IRI |
modified |
DateOptTime |
and from the Internationalization group (i18nAttributes):
| Name | Datatype |
|---|---|
xml:lang |
XML Schema language |
dir |
XML Schema string Enumeration ltr, rtl |
The content model for <assert> allows it to contain any element from the IPTC’s "NAR" namespace, (and from any another namespace). To avoid ambiguity, the rules that MUST be followed when adding NewsML-G2 elements to an Assert are:
-
Immediate child elements from <itemMeta>, <contentMeta> or <concept> may be added directly to the Assert without the parent element;
-
All other elements MUST be wrapped by their parent element(s), excluding the root element.
23.2.1. Reasons for using Asserts
Sometimes it is impractical, inefficient or undesirable to expect receivers of Items to retrieve rich structured information about concepts from remote resources. In these cases a sub-set of metadata relevant to the Item can be stored directly in the Item using Assert. For example:
-
A provider may decide that it is important to convey supplementary information locally within a News Item, such as how to contact an organisation that requires a more comprehensive property structure "borrowed" from the Concept wrapper.
-
A provider needs to convey a one-time transient value, such as a company’s latest share price, directly within the NewsML-G2 document.
-
A news organisation may wish to add value to stories using supplementary information about concepts that are part of controlled vocabularies, but does not wish to give unrestricted access to the knowledge bases that the information is drawn from.
-
A provider wishes to embed supplementary information about concepts that are NOT part of controlled vocabularies.
-
Performance or connectivity issues may restrict the ability of receivers to retrieve information that is stored remotely.
For example, a Subject property can reference a local Assert, allowing the use of properties that are not directly supported by the <subject> element:
<contentMeta>
...
<subject type="cpnat:organisation" literal="Acme Widget">
<name>Acme Widget Sales Inc</name>
</subject>
...
</contentMeta>
<assert literal="Acme Widget">
<organisationDetails>
<contactInfo>
<phone>+1 (416) 922 5834</phone>
<email>info@acmewidgets.com</email>
</contactInfo>
</organisationDetails>
</assert>This example shows how a concept identified by "Acme Widget" which is a Subject of the Item, can be expanded locally using an Assert.
It illustrates the use of @literal as an identifier whose scope is purely local to the Item. Both @qcode and/or @uri may be used as globally-unique identifiers but note that the concept information contained in an Assert in an Item is ALWAYS local in scope, whatever the type of identifier. Receivers must NOT use the information contained in the <assert> outside the scope of the Item providing the information, for example by extracting it and storing it in a cache of concepts, or in a knowledge base.
This is because the <assert> is intended to be a single-use "snapshot" of information about a concept, if the information needs to used permanently and periodically updated, the full Concept Item or Knowledge Item, which also convey management metadata, should be used instead.
Merging concept information that is used by multiple properties
If a document, for example, has <subject> and <located> properties that reference a single geographical location (i.e. a picture SHOWS Stonehenge and was taken AT Stonehenge). The <assert> wrapper can provide information about this location that is shared by both properties.
<contentMeta>
...
<located type="ex-cpnatexp:geoAreaSublocation"
qcode="ex-myalias:int001" />
<!-- Camera location -->
...
<subject type="ex-cpnatexp:geoAreaSublocation" qcode="ex-myalias:int001" />
<!-- Subject of picture -->
...
</contentMeta>
<assert qcode="ex-myalias:int001">
<type qcode="ex-cpnatexp:geoAreaSublocation" />
<name>Stonehenge</name>
<broader type="ex-cpnatexp:geoAreaCity">
<name>Amesbury</name>
</broader>
<broader type="ex-cpnatexp:geoAreaProvState">
<name>Wiltshire</name>
</broader>
<broader qcode="iso3166-1a3:GBR" type="ex-cpnatexp:geoAreaCountry">
<name>United Kingdom</name>
</broader>
</assert>Example: Merged POI Details
In the example below an <address> wrapper has been added as an optional child of <POIDetails> to convey the postal address of the location of the POI., It is recommended that the address wrapped by <contactInfo> should NOT be used to express the location of the POI.
<contentMeta>
<located qcode="ex-artven:int014" />
<subject type="cpnat:abstract" qcode="medtop:20000030">
<name>music theatre</name>
</subject>
<subject type="cpnat:poi" qcode="ex-artven:int014" />
</contentMeta>
<assert qcode="ex-artven:int014">
<name>The Metropolitan Opera House</name>
<definition xml:lang="en-US">
The Metropolitan Opera House is situated in the Lincoln Center for the +
Performing Arts on the Upper West Side of Manhattan, New York City.<br/> +
The Opera House is located at the center of the Lincoln Center Plaza, at +
the western end of the plaza, at Columbus Avenue between 62nd and +
65th Streets. <br/>
</definition>
<POIDetails>
<address>
<line>Lincoln Center</line>
<locality type="loctyp:City" literal="int015">
<name>New York</name>
</locality>
<area type="loctyp:Sublocation" literal="int016">
<name>New York</name>
</area>
<country literal="US">
<name role="nrol:display">United States</name>
</country>
<postalCode>10023</postalCode>
</address>
<contactInfo>
<web>http://www.themet.org</web>
</contactInfo>
</POIDetails>
</assert>Using concept details in <assert> in previous versions
Up to NewsML-G2 2.4, the <concept> wrapper has mandatory elements of <conceptId> and <name>, and therefore omitting these properties would cause errors if validating against these versions of the schema. The workaround to avoid validation errors is to add a "dummy" Concept ID, using a randomly-generated code added to a dummy Scheme URI provided by the IPTC.
Now, immediate child properties of <concept> may be used directly in <assert>, as is already the case for <itemMeta> and <contentMeta>, so the need for this workaround is removed.
Example: Using the <concept> wrapper with valid ID
In the following example, the <concept> wrapper is used, but the assertion is about a concept from a controlled vocabulary, so the concept ID makes sense. This assertion will contain supplementary information about a concept identified as "ex-artven:int014": used in a <located> and a <subject> properties of <contentMeta>. (Note that the scope of the information in the <assert> wrapper is LOCAL to the document, and may only be updated when the containing Item is modified.)
The example in more detail:
<contentMeta>
<located qcode="ex-artven:int014" />
<subject type="cpnat:abstract" qcode="subj:01017001">
<name>music theatre</name>
</subject>
<subject type="cpnat:poi" qcode="ex-artven:int014" />
</contentMeta>
<assert qcode="ex-artven:int014">
<concept>
<conceptId qcode="ex-artven:int014" />
<name>The Metropolitan Opera House</name>
<definition xml:lang="en-US">
The Metropolitan Opera House is situated in the Lincoln Center for the +
Performing Arts on the Upper West Side of Manhattan, New York City.<br/> +
The Opera House is located at the center of the Lincoln Center Plaza, at +
the western end of the plaza. <br/>
</definition>
<POIDetails>
<contactInfo>
<web>http://www.themet.org</web>
<address>
<line>Lincoln Center</line>
<locality type="loctyp:City">
<name>New York</name>
</locality>
<area type="loctyp:Sublocation">
<name>New York</name>
</area>
<country>
<name role="nrol:display">United States</name>
</country>
<postalCode>10023</postalCode>
</address>
</contactInfo>
</POIDetails>
</concept>
</assert>Example: Using a "dummy" ID
If the <located> and <subject> properties use a @literal value and the concept itself is not part of a controlled vocabulary, then the Concept ID has no meaning. However, it is still needed for the document to be valid NewsML-G2.
The QCode is created by generating a random string, or one that can be guaranteed unique within the scope of the Item, and appending this to the scheme alias "dummy" with the colon separator:
<assert literal="int014">
<concept>
<conceptId qcode="dummy:091013121256" />
<name>The Metropolitan Opera House</name>The scheme alias "dummy" resolves to a scheme URI hosted for this purpose by the IPTC. The scheme alias is part of the IPTC remote catalog:
<catalog ...>
...
<scheme alias="dummy"
uri="http://cv.iptc.org/newscodes/dummy/"
/>
...If a provider wishes to use a different scheme alias with the scheme URI defined by the IPTC, they would need to create an entry in their catalog:
<catalog ...>
...
<scheme alias="other"
uri="http://cv.iptc.org/newscodes/dummy/"
/>
...23.2.2. Using Assert to map from IIM or XMP
Many media organisations use the IPTC’s IIM standard (Information Interchange Model), particularly for pictures. IIM has been embedded into professional picture workflows because it was adopted by Adobe for the "IPTC Header" fields in Photoshop. This has been succeeded by Adobe XMP and IPTC Core for XMP, (See Mapping Embedded Photo Metadata to NewsML-G2)
When migrating IIM or IPTC Core (XMP) metadata to NewsML-G2, <assert> offers a convenient method for conveying the contents of some fields which express the location shown by a picture using machine-readable or human-readable values.
For example, the location of the subject of a picture is conveyed using the NewsML-G2 <subject> property. However, <subject> cannot directly include detailed geographic information that may be contained in the embedded metadata. An Assert can be used to convey this information:
<contentMeta>
...
<subject type="cpnat:geoArea" qcode="ex-geocodes:abc" />
...
</contentMeta>
<assert qcode="ex-geocodes:abc">
<type qcode="cpnat:geoArea" />
<geoAreaDetails>
<position latitude="35.689962" longitude="139.691634"/>
</geoAreaDetails>
</assert>23.3. Inline Reference
The NewsML-G2 <inlineRef> element complements the <assert> property described above. Whereas <assert> carries supplementary information about concepts referred to in NewsML-G2 metadata, <inlineRef> performs a similar function for concepts found in the content of the document, such as is carried in inlineXML, and Label or Block type elements.
For example, the payload of a News Item might be text in XHTML; part of the text may refer to the Metropolitan Opera House. That portion of the text can be linked to information about "The Met", by placing the supplementary information in an Inline Reference,
An <inlineRef> wrapper refers to tags with local identifiers (XML Schema IDREFS). The content associated with the Inline Reference must be tagged by an element that supports an attribute of type ID (not necessarily named "id"), examples include the XHTML <span> element, and the NITF <org> element
The <inlineRef> element is of Flex1PropType, with additional attributes of @idrefs, as noted above, and any members of the Quantify Attributes Group, which allows a provider to express, for example, the relevance of the supplementary information provided.
23.3.1. Quantify Attributes Group
| Name | Datatype | Note |
|---|---|---|
confidence |
Int100 |
An integer from 0 to 100 expressing the provider’s confidence in the information provided. A value of 100 indicates the highest confidence |
relevance |
Int100 |
An integer from 0 to 100 expressing the relevance of the information provided. A value of 100 indicates the highest relevance. |
23.3.2. Linking text content to an Inline Reference
A simple example illustrates the use of <inlineRef> to provide supplementary information about a concept found in an XHTML press release. In this case, the article refers to "the Met". With 100% confidence, the provider declares that the name of this concept is "The Metropolitan Opera" (linking @id and @idrefs highlighted in bold):
<inlineRef idrefs="xyz" confidence="100" (1)
qcode="ex-acmeorg:int020">
<name role="nrol:display">Metropolitan Opera</name>
<name xml:lang="en-US" role="nrol:full">
New York Metropolitan Opera
</name>
</inlineRef>
<contentSet>
<inlineXML contenttype="application/xhtml+xml">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Free Tosca Open House Announced</title>
</head>
<body>
<h1>New York Met Announces Free Tosca Open House</h1>
<p>NEW YORK (Agencies) - On Thursday, September 17, the +
<span id="xyz">Met</span> will launch its fourth season of + (2)
free Open Houses, with the final dress rehearsal of Luc +
Bondy’s new staging of Puccini’s opera, starring Karita +
Mattila and conducted by Music Director James Levine. +
</p>
<p>Three thousand free tickets, limited to two per person,
will be available beginning at noon on Sunday,
September 13, at the Met box office only. The rehearsal
starts at 11am on September 17, with doors opening at 10:30am.
</p>
</body>
</html>
</inlineXML>
</contentSet>| 1 | Identifier of the inline reference |
| 2 | The inline concept being referenced |
23.3.3. Using <inlineRef> and <assert> together
Inline Ref can provide basic information about a concept, but more detailed information can be expressed by linking the concept in the content, via <inlineRef>, to an <assert> element, using @literal or @qcode.
Example 1: simple story mark-up
The following shows how part of a story text section is associated via an inlineRef to a concept for President George W Bush:
<assert qcode="ex-pers:gw.bush"> (1)
<name>President George W. Bush</name>
<type qcode="cpnat:person"/>
</assert>
<inlineRef idrefs="x1" qcode="ex-pers:gw.bush" confidence="50"/> (2)
...
<inlineXML contenttype="application/xhtml+xml" xml:lang="en"
...>
<html xmlns="http://www.w3.org/1999/xhtml">
<head><title/><head>
<body>
<!-- Inline2 -->
<p><span id="x1">President Bush</span> makes a speech about Iran (3)
today at 14:00.</p>
...
</body>
</html>
</inlineXML>| 1 | Local assertion of the concept |
| 2 | The inline reference links the text to the concept with a 50% confidence that the person referred to in the text is G. W. Bush, rather than the elder President George Bush. |
| 3 | The part of the content referenced by <inlineRef> |
Example 2: complex story mark-up
The following expands on Example 1, providing further story text section mark-up, and indicating the associated <inlineRef> and <assert> to the concepts of President George Bush and Iran.
<assert qcode="ex-pers:gw.bush">
<name>President George W. Bush</name>
<type qcode="cpnat:person"/>
</assert>
<assert qcode="ex-pers:g.bush">
<name>President George Bush</name>
<type qcode="cpnat:person"/>
</assert>
<assert qcode="ex-N2:IR">
<name>Iran</name>
<type qcode="cpnat:geoArea"/>
</assert>
...
<inlineRef idrefs="x1" qcode="ex-pers:gw.bush"
confidence="50"/> (1)
<inlineRef idrefs="x1 x3" qcode="ex-pers:g.bush"
confidence="70"/> (2)
<inlineRef idrefs="x7" qcode="ex-N2:IR" confidence="100"/> (3)
...
<inlineXML contenttype="application/xhtml+xml" xml:lang="en"
...>
<html xmlns="http://www.w3.org/1999/xhtml">
<head><title/><head>
<body>
<!-- Inline2 -->
<p> <span id="x1">President Bush</span> makes a speech about
<span id="x7">Iran</span> today at 14:00.</p>
<p> Later, <span id="x3">Bush</span> indicated that there were
still many issues to be addressed.</p>
...
</body>
</html>
</inlineXML>The mark-up associated with ‘President Bush’ implies:
| 1 | a 50% confidence in ‘President George W. Bush’ (via inlineRef/@idrefs="x1"), and |
| 2 | a 70% confidence in ‘President George Bush’ (via inlineRef/@idrefs="x1 x3"). |
| 3 | a 100% confidence in ‘Iran’ (via inlineRef/@idrefs="x7"), indicating it is a concept type of Geopolitical Unit (cpnat:geoArea), refined as a Country (ex-geoProp:5). |
Example 3: label mark-up
The following shows how a label is associated with an inlineRef (and therefore associated with an assert) as per Example 2:
<!-- contentMeta -->
<headline><span id="x8">President Bush</span> in
<span id="x7">Iran</span>.</headline>
...
<assert qcode="ex-pers:gw.bush">
<name>President George W. Bush</name>
<type qcode="cpnat:person"/>
</assert>
<assert qcode="ex-N2:IR">
<name>Iran</name>
<type qcode="ex-geoProp:5" />
</assert>
...
<inlineRef idrefs="x8" qcode="ex-pers:gw.bush"
confidence="50"/>
<inlineRef idrefs="x7" qcode="ex-N2:IR" confidence="100"/>
...23.4. Why and How metadata has been added: @why and @how
If a provider needs to express reasons for the presence of particular metadata values, @how and @why attributes may be used with most elements as part of the Common Power Attributes (see table below).
The @why tells the end-user what caused the corresponding property to be added to the Item, for example that a person added the property based on their editorial judgement; @how tells the end-user the means by which the metadata value was extracted, for example that it was looked up from a database.
The properties are inter-dependent and used mutually exclusively: when the value of @why is "direct" (the default or "implied" value), meaning that the metadata was added by a person and/or a software tool directly from the content of the Item, it should be omitted and @how used to describe the method of extraction, as shown in the following code snippet illustrating its use with <subject>:
<subject
type="cpnat:abstract"
qcode="ex-mysubject:JVN"
<!-- @why omitted, as @how only used with @why value "direct" -->
how="howextr:assisted>
<name> JOINT VENTURES</name>
</subject>If the value of @why is other than "direct", this implies that the value was extracted by a tool and therefore @how should be omitted because it would be redundant:
<subject
type="cpnat:abstract"
qcode="ex-mysubject:JVN"
<!-- @how omitted, as @why value "inferred" implicitly used a tool -->
why="why:inferred">
<name>JOINT VENTURES</name>
</subject>To promote interoperability the IPTC recommends that implementers use the IPTC NewsCodes How Extracted (http://cv.iptc.org/newscodes/howextracted/) with a Scheme Alias of "howextr" and Why Present (http://cv.iptc.org/newscodes/whypresent/) with a Scheme Alias "why".
The Why Present CV contains three values:
-
direct: the value is directly extracted from the content by a tool and/or by a person.
-
ancestor: the value is an ancestor of another property value already assigned to the content (this implies that the ancestor was derived by a tool)
-
inferred: the value was derived by look-up in a taxonomy/database (also implicitly by a tool).
The How Extracted CV also contains three values, used only with a @why value of "direct":
-
assisted: the value was extracted by a person assisted by a tool.
-
person: the value was extracted by a person.
-
tool: the value was extracted by a tool.
See also Implied Values of NewsML-G2 Properties in the chapter NewsML-G2 Basics.
23.5. Adding customer-specific metadata
In cases where customers have their own private metadata added by the provider of NewsML-G2 Items, in order to facilitate processing and/or routing, the provider may not want to create specific versions of the NewsML-G2 Item for each customer.
The solution is to use @custom, available to most elements (see details below) in conjunction with the attributes @how and @why to add the custom metadata.
23.5.1. Example: Use a customer’s rule to express <memberOf> information
A news provider uses a customer’s metadata rules to signal to the customer that the content is part of a collection of news entitled "Greek Debt". In the code snippet below, @creator expresses that the client rule was used to add this metadata, and @modified contains the date that the property was added. The @literal contains the customer’s code for "Greek Debt" (also given in the name child element)
When @custom is set to "1" or "true" as in this example, this is a signal to receivers that the metadata may NOT exist in other instances of a NewsML-G2 Item of the same guid and version number.
The @why attribute uses the "inferred" value from the IPTC Why Present NewsCodes, and this defines that the property was derived by lookup in a taxonomy or database. The @how attribute is not used as it is implied that the property was extracted using a tool.
<memberOf
literal="greek-dbt"
creator="ex-clientrule:r49"
modified="2012-01-13T16:36:00Z"
custom="true"
why="why:inferred">
<name xml:lang="en">Greek Debt</name>
</memberOf>23.5.2. Common Power Attributes group
The @custom attribute is one of several grouped under the Common Power Attributes, available to ALL elements in NewsML-G2 except the root elements of Items, elements of Ruby mark-up and a few elements of the News Message that are not root elements. The following table details the Group:
| Definition | Name | Cardinality | Datatype | Notes |
|---|---|---|---|---|
The local identifier of the element |
id |
(0..1) |
XML Schema ID |
|
The person, organisation or system that created or edited the property. |
creator |
(0..1) |
QCodeType |
If the property value is not defined, specifies which entity (person, organisation or system) will edit the property value - expressed by a QCode or URI. If the property value is defined, specifies which entity (person, organisation or system) has edited the property value. |
The date (and, optionally, the time) when the property was last modified. The initial value is the date (and, optionally, the time) of creation of the property. |
modified |
(0..1) |
DateOptTimeType |
|
If set to true the corresponding property was added to the NewsML-G2 Item for a specific customer or group of customers only. |
custom |
(0..1) |
Boolean |
The default value of this property is false which applies when this attribute is not used with the property. |
Why the metadata has been included. |
why whyuri |
(0..1) |
QCodeType IRIType |
The recommended IPTC CV is http://cv.iptc.org/newscodes/whypresent/ with a scheme alias of “whypresent” |
The means by which the value was extracted from the content. |
how howuri |
(0..1) |
QCodeType IRIType |
The recommended IPTC CV is http://cv.iptc.org/newscodes/howextracted/ with a Scheme Alias of “howextr” |
One or more constraints that apply to publishing the value of the property. Each constraint also applies to all descendant elements |
pubconstraint pubconstrainturi |
(0..1) |
QCodeList IRIListType |
Use case: a publishable NewsML-G2 document may contain metadata, or content references that are private, or restricted to certain audiences. |
23.5.3. Aligning Descriptive Metadata properties
Since the <keyword> property was added to NewsML-G2 in v 2.4, we learned that its use case aligns closely with the pre-existing <subject> element. In v 2.10, the attributes @confidence and @relevance were added to <keyword>, and @why and @how were added to both elements.
From version 2.27 of the Standard onwards, @confidence and @relevance have also been added to <slugline>, <headline> and <description>, thus aligning these properties with <subject>, <keyword> and <genre> in the Descriptive Metadata Group. With the increased use of automated metadata generation by software tools, it helps both providers and end-users to be able to express these values as an aid to processing of Items.
Relevance is a measure of the usefulness of the concept to the user who wants to learn more about the principal subject matter of the content. A high relevance indicates that the metadata truly expresses the essence of the content, while a low relevance indicates a low correlation between the metadata and the content. For example, a concept that references Barack Obama would be 100 per-cent relevant to an article that about the 2012 U.S. presidential election. This would be represented as:
relevance="100"A concept referencing The White House would be less relevant, and might be represented as:
relevance="60"Confidence asserts the reliability of the association between the concept and the content and is usually obtained by software engines that automatically categorise news, where "100" is the highest value and "0" the lowest:
confidence="75"Example 1: Keyword
In the code snippet, the first keyword was extracted directly from the content by a person with 100% relevance and confidence. The second keyword was "inferred" from the content (@how not present as it defaults to "tool") with 100 per cent relevance but 75 per cent confidence.
<contentMeta>
...
<keyword
role="ex-keyrole:TOPIC"
relevance="100"
confidence="100"
how="howextr:person">
Armed Conflict
</keyword>
<keyword
role="ex-keyrole:TOPIC"
relevance="100"
confidence="75"
why="why:inferred">
Civil Unrest
</keyword>
...
</contentMeta>Example 2: Subject
In this snippet taken from an announcement by a company, the subject property relating to the company is clearly highly relevant and could trigger the inclusion of further information about the company being included, for example in an <assert> wrapper. However, another company that is only mentioned in passing is only given a relevance of 50 per cent.
<contentMeta>
...
<subject
type="cpnat:organisation"
relevance="100"
confidence="100"
how="howextr:assisted"
literal="More Widgets">
<name>More Widgets Corp</name>
</subject>
<!-- Secondary company - relevance < 100 -->
<subject
type="cpnat:organisation"
relevance="50"
confidence="100"
how="howextr:assisted"
literal="First Acme">
<name>First Acme Mercantile Bank</name>
</subject>
...
</contentMeta>Note that the value of @how in both cases is "assisted" and the confidence is 100 per cent, but the relevance is not a reflection of the method used to extract the metadata.
23.6. The derivation of metadata
Although fixed taxonomies have their place in helping end-users classify news, there is common use of automation to "mine" news for concepts that can be used to create links and relationships. In such cases, it can be useful – in some cases essential – to create an "audit trail" of the derivation of metadata.
For example, if a journalist adds a subject code to an article, it is possible to express the reason that concept was added using the attributes @why and @how (see above)
23.6.1. The <derivedFrom> element
In NewsML-G2 v 2.10, an attribute @derivedfrom was added to elements that supported the attribute @why. However, this restricted the expression of the derivation to property values expressed as QCodes: in fact the use case for derivation is often to give this attribution to metadata encoded outside the NewsML-G2 framework.
In NewsML-G2 v 2.12, with an extension of @why to almost all NewsML-G2 elements, it was decided to add a specific <derivedFrom> element to NewsML-G2 as a child of the root element and using IDREFS to express the relationship between the derivedFrom element and the referring property. NOTE: The attribute @derivedfrom is deprecated from NewsML-G2 v 2.11 on.
Note the direction of the relationship, as illustrated by the following snippet: an article about an event in Barcelona uses the event’s Twitter hashtag "#sgbcn" as a keyword. The editor of the article subsequently creates a NewsML-G2 Event with a Concept ID of "ex-myevents:SGBCN" and indicates by the derivedFrom element that the <keyword> with the hashtag was derived from this concept. This is done by applying the keyword’s id "s1" to the idrefs of the <derivedFrom> element which represents the event in Barcelona:
<newsItem>
...
<contentMeta>
<keyword id="s1" role="drol:hashtag">#sgbcn</keyword>
<derivedFrom idref="s1" qcode="ex-myevents:SGBCN" />
</contentMeta>
...
</newsItem>Based on this it can be asserted that the value of the keyword property with the id "s1" has been derivedFrom the event concept identified by the QCode "ex-myevents:SGBCN".
See also Hashtags
23.6.2. The <derivedFromValue> element
The <derivedFromValue> element, introduced in NewsML-G2 v2.28, represents the non-Concept value used to derive the value of one or more properties in a NewsML-G2 Item. This complements the <derivedFrom> element (above), which represents the concept value used to derive the value of an element.
The derivedFromValue element is a child of any NewsML-G2 Item except <catalogItem> and may be inserted after <inlineRef> and <derivedFrom>. It is optional and repeatable. The mandatory attribute @sourceidref refers to the id of the element that provides the value used for the derivation; the mandatory attribute @idrefs refers to the ids of elements whose values have been derived from the value represented by this property.
For example, the following <slugline> has an @id="slug1"
<slugline id="slug1">MIDEAST-CRISIS/</slugline>The Item contains the following <subject> properties:
<subject id="i314d1" qcode="ex-G:Q" confidence="100" relevance="100" how="howextr:tool" why="why:inferred"/>
<subject id="i314d2" qcode="ex-M:LK" confidence="100" relevance="100" how="howextr:tool" why="why:inferred"/>
<subject id="i314d3" qcode="ex-M:N5" confidence="100" relevance="100" how="howextr:tool" why="why:inferred"/>
<subject id="i314d4" qcode="ex-M:EL" confidence="100" relevance="100" how="howextr:tool" why="why:inferred"/>The derivedFromValue shows that the Subjects were derived from the value "MIDEAST-CRISIS" of the Slugline:
<derivedFromValue idrefs="i314d1 i314d2 i314d3 i314d4" sourceidref="slug1" />23.6.3. The Creator of Metadata
Automated processing using rules or AI tools has also led to a need to attribute the creation of a set of metadata properties. The new element <metadataCreator>, an optional child element of <itemMeta> complements the existing {element}/@creator attribute of an element, as follows:
-
If the {element} specifies the {element}/@creator: the {element} creator is the @creator value.
-
If the {element} does not specify the {element}/@creator and the metadataCreator is specified: the {element} creator is the metadataCreator value.
-
If the {element} does not specify the {element}/@creator and the metadataCreator is not specified: the {element} creator value is indeterminate.
Thus, for example:
<itemMeta>
...
<metadataCreator qcode="ex-NS:DJN" creator="ex-sys:Swift" />
...
</itemMeta>
<contentMeta>
...
<!-- Creator (Default): ex-NS:DJN, from the metadataCreator -->
<subject qcode="ex-R:TRI.TO" />
<!-- Creator (Overridden): ex-sys:Swift, from @creator -->
<subject qcode="ex-P:4295861160" creator="ex-sys:Swift" />
...
</contentMeta>| The <creator> element is used to identify the party (person or organisation) who created the Content. |
23.7. Hints and Extension Points in NewsML-G2
23.7.1. Adding Hints from the NAR namespace
Hint Points allow NewsML-G2 properties to be extracted from a target resource and added to the local document as an aid to processing. For example the caption of a remote picture may be displayed without loading the picture itself.
Hint properties must be consistent with the target resource but do not have to be extracted directly from it. For example a <headline> may not be available for a referenced image, but it is permissible to add <headline> at the Hint Point.
When using a property as a Hint it MUST be wrapped by its parent element(s) (excluding the root element), EXCEPT for the immediate child elements of <itemMeta>, <contentMeta> or <concept>. For example, to add a copyright notice Hint, the parent element <rightsInfo> must be supplied, as shown in the following examples of <itemRef> in a Package Item:
<groupSet root= ...">
...
<group id= ...>
<itemRef residref=...>
...
<rightsInfo>
<copyrightNotice>
Copyright 2022-23 Example Enews LLP, all rights reserved
</copyrightNotice>
</rightsInfo>
...
</itemRef>
</group>
...
</groupSet>A <headline> is added directly because it is an immediate child element of <contentMeta>:
<groupSet root= ...>
...
<group id= ...>
<itemRef residref=...>
...
<headline>
EU President Claude Juncker today
</headline>
...
</itemRef>
...
</group>
</groupSet>-
Most child elements of <partMeta> are shared with <contentMeta> or <itemMeta>, but they MUST be used with the <partMeta> parent element, and <partMeta> should include the required delimiter elements <timeDelim> or <regionDelim>.
-
When implementing Hint Points, providers are advised to the use NewsML-G2 version 2.23 (and up) as it is "globalised", that is all of the elements that may be used as Hints are defined at a global level in the XML schema. Using Hint properties in prior versions of NewsML-G2 MAY not validate correctly in some circumstances.
The following elements have a Hint Point. Follow the links to see more information about each of them. Note that, apart from Assert, they are Link 1 Type properties.
| Element | Description | Further information |
|---|---|---|
<assert> |
Assertion about a concept |
Assert Wrapper |
<itemRef> |
Reference in a Package to an external NewsML-G2 Item or web resource |
Item Reference |
<deliverableOf> |
Reference from an Item to a News coverage property of a Planning Item |
Delivery wrapper |
<deliveredItemRef> |
Reference from a News Coverage element to Item(s) that have been delivered |
Delivery wrapper |
<remoteInfo> |
Link from a Concept to an Item or web resource providing further information |
Remote Info |
<link> |
Link from the current Item to an external Item or web resource |
Using Links |
Permitted Hint Properties
Any of the following properties may be used at the Hint Point, subject to the rules outlined above.
| Wrapper | Property | Wrapper | Property | |
|---|---|---|---|---|
itemMeta |
itemClass |
contentMeta |
altId |
|
itemMeta |
provider |
contentMeta |
rating |
|
itemMeta |
versionCreated |
contentMeta |
userInteraction |
|
itemMeta |
firstCreated |
contentMeta |
language |
|
itemMeta |
embargoed |
contentMeta |
genre |
|
itemMeta |
pubStatus |
contentMeta |
keyword |
|
itemMeta |
role |
contentMeta |
subject |
|
itemMeta |
fileName |
contentMeta |
slugline |
|
itemMeta |
generator |
contentMeta |
headline |
|
itemMeta |
profile |
contentMeta |
dateline |
|
itemMeta |
service |
contentMeta |
by |
|
itemMeta |
title |
contentMeta |
creditline |
|
itemMeta |
edNote |
contentMeta |
description |
|
itemMeta |
memberOf |
contentMeta |
contentMetaExtProperty |
|
itemMeta |
instanceOf |
concept |
conceptId |
|
itemMeta |
signal |
concept |
type |
|
itemMeta |
altRep |
concept |
name |
|
itemMeta |
deliverableOf |
concept |
definition |
|
itemMeta |
hash |
concept |
note |
|
itemMeta |
expires |
concept |
facet-DEPRECATED |
|
itemMeta |
origRep |
concept |
remoteInfo |
|
itemMeta |
incomingFeedId |
concept |
hierarchyInfo |
|
itemMeta |
link |
concept |
sameAs |
|
itemMeta |
itemMetaExtProperty |
concept |
broader |
|
contentMeta |
icon |
concept |
narrower |
|
contentMeta |
urgency |
concept |
related |
|
contentMeta |
contentCreated |
concept |
personDetails |
|
contentMeta |
contentModified |
concept |
organisationDetails |
|
contentMeta |
located |
concept |
geoAreaDetails |
|
contentMeta |
infoSource |
concept |
POIDetails |
|
contentMeta |
creator |
concept |
objectDetails |
|
contentMeta |
contributor |
concept |
eventDetails |
|
contentMeta |
audience |
concept |
conceptExtProperty |
|
contentMeta |
exclAudience |
23.7.2. Adding special-use properties
Adding elements from other namespaces
NewsML-G2 implementers will sometimes encounter a use case that does not fit the defined semantics of an existing NewsML-G2 metadata property. Using a property under an Extension Point is an option, since any user-defined structure may be added, but this requires the extension properties to be created in a different namespace. Receivers of proprietary properties may be unable to use a standard NewsML-G2 property software module for processing such proprietary properties.
Adding NewsML-G2 Extension properties
Most NewsML-G2 elements that wrap a group of metadata properties have a generic extension property named after the parent element suffixed with "ExtProperty", for example <rightsInfo> has <rightsInfoExtProperty>. This enables a special-use property to be expressed using a common type which includes @rel to define the relationship with the target concept, for example:
<contentMeta>
...
<contentMetaExtProperty
rel="ex-mediarel:suitableAudience"
value="PG"
valuedatatype="xs:string"
/>
...
</contentMeta>This fictional example shows a provider-specific "audience suitability" property added to Content Metadata. The semantics of the extension property are defined using @rel, followed by the value of the property and its datatype.
Where there are time restrictions on the use of the extension property, these may be expressed using @validfrom and @validto.
Even though the property conveys proprietary data, such properties can now be processed in a consistent manner by a generic NewsML-G2 processor.
Full list of available extension properties
| Wrapper | Extension Property | Affected Item(s) |
|---|---|---|
rightsInfo |
rightsInfoExtProperty |
all |
itemMeta |
itemMetaExtProperty |
all |
contentMeta |
contentMetaExtProperty |
All except catalogItem |
partMeta |
partMetaExtProperty |
All except catalogItem |
remoteContent |
remoteContentExtProperty |
newsItem |
concept |
conceptExtProperty |
conceptItem, knowledgeItem |
group |
groupExtProperty |
packageItem |
newsCoverage |
newsCoverageExtProperty |
planningItem |
planning |
planningExtProperty |
planningItem |
header |
headerExtProperty |
newsMessage |
schemeMeta |
schemeMetaExtProperty |
knowledgeItem |
23.8. Special processing instructions for metadata about a part of the content
Implementers need to be aware of how property values about the content as a whole are inherited by individual parts of the content.. All property assertions in elements such as <itemMeta> or <contentMeta> are inherited by any <partMeta> element and are specifically over-ridden for that part of the content when re-stated in a partMeta element.
An example of such inheritance is the use of the <signal> element as a child of <itemMeta> and/or <partMeta>:
The <signal> element instructs the NewsML-G2 processor to handle an Item or its content in a specific way. When used as a child element of <itemMeta> its scope is the entire Item; when used as a child of <remoteContent> its scope is the specific rendition of the content. By introducing <signal> at the <partMeta> level, providers can specify processing instructions for any part of the content.
When used in a <partMeta> element, any processing instructions expressed at a higher level in the item are over-ridden for that specific part of the content. Thus, using <signal> as an example processing instruction:
<itemMeta....>
<!-- A applies to the whole item, unless overridden -->
<signal... A/>
</itemMeta>
<partMeta id="_1_">
<!-- A does NOT apply to this content part -->
<!-- B applies to this content part only -->
<signal... B/>
</partMeta>
<partMeta id="_2_">
<!-- inherits only the signal A from Item Metadata-->
<!-- B does NOT apply to this content part -->
</partMeta>Where a processing instruction (from a higher level) is NOT to be inherited for a specific part of the content, that processing instruction needs to be explicitly ‘’nulled’’ within that specific part of the content. Using <signal> again as an example processing instruction, a ‘’null’’ value is added to the content part:
<partMeta id="_3_">
<signal qcode="gen:null" />
<!-- nulls inheritance of any signal(s)
from the Item Metadata level -->
</partMeta>In NewsML-G2 version 2.21 the elements <link> and <edNote> from <itemMeta> have also been added to <partMeta>.
24. Generic Processes and Conventions
This Chapter discusses some processes, procedures and conventions which are generic to all NewsML-G2 Items, and relate to best practice in the wider context of news processing.
24.1. Processing Rules for NewsML-G2 Items
NewsML-G2 is designed for maximum inter-operability, however, providers are strongly recommended to document their implementations of NewsML-G2 and the provider-specific rules and conventions used.
This information must be provided to receivers so that generic NewsML-G2 processors can be parameterised accordingly
An obvious example is Packages (see Package Processing Considerations) where the structure and content types must be pre-arranged between provider and receivers in order to facilitate correct processing.
Another example is the use of property attributes such as @role and @type which refine the semantic of the property. There needs to be a clear understanding of the concepts being used in these circumstances for the full value of the information to be useful.
24.2. Using Links
24.2.1. Introduction
The <link> property is used in the <itemMeta> section of a NewsML-G2 document to create a navigable link between the Item and a related resource. Examples of the target of a link could be a Web page, a discrete object such as an image file, or another NewsML-G2 Item.
Valid uses of <link> include:
-
To indicate a supplementary resource, for example a picture of a person mentioned in an article.
-
To identify the resource that an Item is derived from, for example if providing a translation.
-
where systems do not support versioning, to provide a link to the previous version of an Item.
-
To identify the previous "take" of a multi-page article, or the previous Item in a series of Items. (Note that these use cases are not explicitly supported by the current version of the IPTC Item Relationship NewsCodes. The <memberOf> property of Item Metadata expresses that an Item is part of a series of Items, but not its sequence.)
-
Where a News Item conveys formatted text which references an illustration, a dependency link from the article to the illustration is indicated using <link>.
24.2.2. Link properties
Link uses the Link1Type datatype, with optional attributes for Item Relation (@rel) and the Target Resource Attributes group, optionally with more extensive attributes which permit any property consistent with the structure of the target resource to be used as a processing Hint. See Adding Hints from the NAR namespace
Item Relation @rel and the Item Relationship NewsCodes
A QCode indicating the relationship of the current Item to the target resource. For example, if the current Item is a translation from an original article, the relationship may be indicated using the IPTC Item Relation NewsCodes, for example:
<link rel="irel:translatedFrom">The default relationship between the host Item and a resource identified by a <link> is "See also". The CV broadly defines three types of relationship:
-
Navigation: "See Also".
-
Dependency: "Depends On".
-
Derivation: includes "Derived From" and other refinements of derivation relationships.
The IPTC recommends that for derivation relationships, implementers should use the most specific available representation. For example if a picture conveyed by the item is a crop of the image indicated by <link>, "Derived From" is not inaccurate, but "Cropped From" is preferred as it is more specific.
It is recommended to use the IPTC Item Relationship NewsCodes (Scheme URI http://cv.iptc.org/newscodes/itemrelation/)
Target Resource Attributes
These are property attributes that enable the receiver to accurately identify the remote resource, its content type and size. See Target Resource Attributes for further information.
Item Title <title>
A short natural language name describing the link, intended to be displayed to users. It is not necessary that this <title> should be extracted from the target resource. For example, a journalist may wish to add a link and write a title for it.
<title xml:lang="en-GB">File picture of President Obama</title>Hint and Extension Point
Any number of metadata properties from the IPTC’s News Architecture (NAR) namespace may be included. For example, a picture referenced by a link may have the recommended filename extracted from the target resource as an aid to processing. See Hints and Extension Points in NewsML-G2 for detailed guidance on this feature.
24.2.3. Link examples
A supplemental picture with a text article
The sender of a News Item containing a text article wishes to include a link to a picture that may optionally be retrieved to illustrate the article. The relationship to the target resource is "see also".
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="tag:acmenews.com,2008:TX-PAR:20090529:JYC85"
version="1"
...>
<itemMeta>
<itemClass qcode="ninat:text" />
...
<edNote>With picture</edNote>
<link
rel="irel:seeAlso" Item relation
residref="tag:acmenews.com,2008:TX-PAR:20090529:JYC80"> Item ref
<title>
File picture of President Obama
<title />
<link />
...
</itemMeta>
...
</newsItem>A required picture with a text article
A News Item contains a text article which is marked up explicitly to reference a picture (for example in XHTML). The picture is required for correct display of the text-with-picture story, therefore the relationship to the target resource is "depends on".
A NewsML-G2 processor should be enabled to pre-fetch this required target resource before the content of the news item is processed. As shown in the example below, the "real world" link between the article and the picture is established using the filename of the linked resource.
In this example, we extract the <itemClass> property and <filename>, the recommended filename of the target resource (a News Item), from the Item’s <itemMeta> wrapper and add these as child elements of <link>.
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="tag:acmenews.com,2008:TX-PAR:20090529:JYC85"
version="1"
standard="NewsML-G2" standardversion="2.31" conformance="power"
...>
<itemMeta>
<itemClass qcode="ninat:text" />
...
<edNote>With picture</edNote>
<link
rel="irel:dependsOn" Item relation
residref="tag:acmenews.com,2008:TX-PAR:20090529:JYC80"> Item ref
<itemClass qcode="ninat:text" />
<filename>
obama-omaha-20090606.jpg File name
</filename>
</link>
...
</itemMeta>
<contentSet>
<inlineXML>
<html xmlns="http://www.w3.org/1999/xhtml">
...
<p>At Omaha Beach, President Obama led a ceremony to mark the landing of
thousands of U.S. troops on D-Day.</p>
<img style="position: absolute; left: 0px; top: 0px;"
src="file:///obama-omaha-20090606.jpg" Picture ref />
...
</inlineXML>
</contentSet>
/newsItem>Linking to previous versions of an Item
(See also Processing Updates and Corrections) Some content manage ent systems do not maintain a common identifier for successive versions of an information asset (such as text or picture), but maintain a link to the identifier of the previous version of the asset. In these circumstances, a <link> can inform recipients that the current Item is a new version of a previously published Item, and provide a navigation to retrieve the previous version of the Item, if required. The relationship between the current item and the previous version is "previousVersion".
| Even where providers use the same ID, it is not mandatory to use a consecutive ascending sequence of numbers to indicate successive versions of an Item. Where it is required to positively identify the previous version of an Item, a provider SHOULD add a <link> to the previous version. |
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="tag:acmenews.com,2008:TX-PAR:20090529:JYC85" new item
version="1" first version
...>
<itemMeta>
<itemClass qcode="ninat:text" />
...
<edNote>Replaces previous version. MUST correction, updates name of
minister</edNote>
<signal qcode="sig:correction" />
<link
rel="irel:previousVersion"
residref="tag:acmenews.com,2008:TX-PAR:20090529:JYC80" previous item
version="1"> first version
<itemClass qcode="ninat:text" /
</link>
...
</itemMeta>
...
</newsItem>Using this method, other target resources such as previous "takes" of a multi-page article, the original picture from which the current item was cropped, or the original text from which a translation has been made, can be expressed using <link>
24.3. Publishing Status
The NewsML-G2 <pubStatus> property uses a mandatory IPTC CV that contains three values:
-
usable
-
withheld
-
canceled
These terms have a specific meaning in a professional news workflow, and it is the IPTC’s intention in designing NewsML-G2 that they be interpreted by software systems. They are NOT intended as advisory notices to journalists, although of course the Publishing Status may well be a read-only property displayed by an editing system.
If no <pubStatus> property is present in an Item, the default value is "usable", meaning that the item and its contents may be published.
If an Item has a publishing status of "withheld", this signals that the Item and its contents MUST NOT be made public by whatever means until further notice, and if the Item has been published, the publisher MUST take immediate action to withdraw or retract it. The Item may be made public ONLY after receipt of a new version of the Item – using the same GUID – that has a status of "usable".
For example, a provider may send an item of news (version 1), and subsequently decided that a correction or amplification is needed, which requires the sending of a new version of the Item. If the new version will not be ready for an appreciable time, the provider may send a new version (version 2) of the Item with a status of "withheld". When the corrected version is ready, it will be sent – using the same GUID – with a status of "usable" (version 3).
If an Item cannot be corrected, or the Item needs to be permanently withdrawn for some other reason, the provider should use "canceled" the third value of <pubStatus> (note U.S. spelling). An Item that is "canceled" MUST NOT be made public by whatever means. If the Item has been published the publisher MUST take immediate action to withdraw or retract it. All versions of the Item MUST be deleted from all locations, including archives. News organisations have faced legal action arising from the inadvertent re-publication of defamatory content from an archive.
As the State Transition diagram shows, an Item that is "withheld" may have its Publication Status changed to "usable" or "canceled" in subsequent versions, but a "canceled" Item CANNOT have its status changed back to "usable" or "withheld".
The <pubStatus> property is part of the <itemMeta> component, and uses a QCode value. The scheme alias for the IPTC Publishing Status NewsCodes is "stat":
<pubStatus qcode="stat:usable" />24.4. Embargo
Professional, or business-to-business, news organisations often make use of an embargo to release information in advance, on the strict understanding that it may not be released into the public domain until after the embargo time has expired, or until some other form of permission has been given.
Embargo is NOT the same as the Publishing Status. Some systems process the embargo time using software in order to trigger the release of content when the embargo time is passed, but the intention of embargo is also as an information management feature for journalists.
Embargos are generally an unwritten agreement and have no legal force. Their success depends on cooperation between parties not to abuse the system. Possible abuses include imposing unnecessary embargos in order to manage the impact of news, or by breaking embargos and releasing news into the public domain too early.
NewsML-G2 uses the optional <embargoed> property in <itemMeta> to indicate whether an item is under an embargo. If the property is absent there is no embargo:
<embargoed>2022-10-23T12:00:00Z</embargoed>If the property is present AND empty, this enables providers to release an item under embargo when the precise date and time that the embargo expires is not known. In these circumstances, an <edNote> or some contractual agreement between the provider and customer will specify the conditions under which the embargo may be lifted.
For example, a provider may release an advance copy of a speech which may not be released to the public until the speaker has finished delivering it. The provider would have no way of knowing exactly when this would be. Therefore some other means of authorising the release may be negotiated between the parties, such as email or a phone call:
<embargoed />
<edNote>
Note to editors: STRICTLY EMBARGOED. Not for release until authorised.
Our +
News Desk will advise your duty editor by email. Release expected
about +
12noon on Monday, February 9.
</edNote>The processing model is illustrated in the diagram below.
Check the corresponding NewsML-G2 Specification Document for further information regarding processing rules for <embargoed>.
24.5. Geographical Location
There are two properties of <contentMeta> that express the geographic location(s) associated with a NewsML-G2 Item, with a distinction between their uses.
The Located <located> property expresses the origin of the content: where the content was created, for example a text article written or a picture taken. The intention of <located> is as a machine-readable equivalent to the location given in a Dateline. (The NewsML-G2 <dateline> property is also available as a natural-language string. for example "MOSCOW, Monday (Reuters)")
The accepted convention, which in some news organisations is formalised as part of a code of practice, is that the Dateline identifies the place where content is created, NOT the place where an event takes place. They may be the same, but this is not necessarily the case.
-
In conflict zones, journalists may not have access to the area where reported events are taking place.
-
Even when physical access is not an issue, journalists may have relied on interviewing people by telephone or on reports from freelance correspondents in order to get the material used to write an article.
The Located property is therefore provided to express the place of origin of content as part of Administrative Metadata:
<located type="loctyp:City" qcode="ex-city:75000">
<name>Paris</name>
</located>To express the geographical information that is important in the context of the article or picture, the Subject property <subject> is used, optionally using a Concept type (@type) In the example below "cpnat:geoArea" from the IPTC Concept Nature NewsCodes, is used, but providers may have their own scheme(s).
The Subject property is Descriptive Metadata:
<subject type="cpnat:geoArea" qcode="ex-city:Tblisi">
<broader qcode="ex-cntry:Georgia">
<name>Georgia</name>
</broader>
</subject>This news story fragment from Reuters and the accompanying code listing illustrate the use of <located> and <subject>. The geographical subjects of the report are Georgia and South Ossetia, but the report was written in Moscow:
MOSCOW, Monday (Reuters) - The breakaway Georgian region of South Ossetia alleged today that two unexploded Georgian shells landed in its capital Tskhinvali, but Tbilisi dismissed the claim as nonsense.
Both sides have regularly...
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for the following alias values: ex-city, ex-cntry, ex-reg and ex-web.
<contentMeta>
<contentCreated>2016-02-09T09:17:00+03:00
</contentCreated>
<located qcode="ex-city:Moscow">
<broader qcode="ex-cntry:Russia" />
</located>
<creator qcode="ex-web:thomsonreuters.com">
<name>Thomson Reuters</name>
</creator>
<language tag="en-US" />
<subject type="cpnat:geoArea" qcode="ex-city:Tskhinvali">
<broader qcode="ex-reg:SouthOssetia" >
<name>South Ossetia</name>
</broader>
</subject>
<subject type="cpnat:geoArea" qcode="ex-city:Tblisi">
<broader qcode="ex-cntry:Georgia" >
<name>Georgia</name>
</broader>
</subject>
<dateline>MOSCOW, Monday (Reuters)</dateline>
</contentMeta>24.6. Processing Updates and Corrections
By its nature, news may need frequent updating, and in some cases correcting, as new facts emerge. The simplest NewsML-G2 mechanism for dealing with updated content is to re-issue an Item using the same GUID with a new Version.
In the absence of any specific instructions from the provider, a "usable" item should be regarded as replacing any previous version of the Item with the same GUID. In practice, a provider is likely to provide some supplementary information in the form of a human-readable <edNote> which can be displayed to inform recipients of the reason for the update.
NewsML-G2 also provides machine-readable features to express whether a new version updates or corrects previous versions of an Item and a further indication of the impact of the change, using the <signal> property under Item Metadata.
Signal may use a QCode to identify an action from a CV. To promote interoperability, the IPTC maintains the Signal NewsCodes (see below) for this purpose, but note it is up to the provider to specify the rules for applying the codes so that their end-users can correctly process the instruction.
24.6.1. Signalling an Update or Correction
Any version of an Item except the initial version is implicitly an update of the previous version. It is not required to use the update signal, but it is not always possible to infer from the version number whether a document is an initial version or is implicitly an update. Therefore the IPTC recommends that <signal> is used with the IPTC Signal NewsCodes (Scheme URI http://cv.iptc.org/newscodes/signal/ and recommended Schema Alias "sig"). The relevant members of the Scheme are:
| Code | Definition | Note |
|---|---|---|
update |
This version of the Item includes an update of some part of the previous version of the Item. |
Implies that this version of the Item is not the initial version |
correction |
This version of the Item corrects some part of a previous version of the Item. |
Implies that this version of the Item is not the initial version. This Correction signal does not indicate in which version(s) of the Item the corrected error existed. |
In addition, the Editorial Note <edNote> property under Item Metadata may be used to provide natural language details about the update or correction, such as specifying a name in the text that has been corrected or whether a paragraph with updated information has been added to the text.
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="tag:afp.com,2008:TX-PAR:20090529:JYC80" current item
version="2" new version
...>
<itemMeta>
...
<edNote>Updates previous version by appending these paragraphs</edNote>
<signal qcode="sig:update" />
...24.6.2. Signalling the impact of an update
It’s possible to express the impact of an update or correction using @severity and one of the Severity NewsCodes (http://cv.iptc.org/newscodes/severity/), recommended Scheme Alias "sev" .
The two (self-explanatory) NewsCodes for Severity are:
-
Major
-
Minor
For example:
<newsItem xmlns="http://iptc.org/std/nar/2006-10-01/"
guid="tag:afp.com,2008:TX-PAR:20090529:JYC80" (1)
version="234256" (2)
...>
<itemMeta>
...
<link
guidref="tag:afp.com,2008:TX-PAR:20090529:JYC80"
version="1234" />
<edNote>URGENT: Appends judge’s statement to previous version</edNote>
<signal qcode="sig:update" severity="sev:major" />
...| 1 | current item |
| 2 | new version |
24.7. Content Warning
The <signal> property in Item Metadata may be used to inform end-users that the nature of the content being sent may be perceived as being offensive to some audiences. This uses the IPTC Signal NewsCodes, with Scheme URI http://cv.iptc.org/newscodes/signal and recommended Schema Alias "sig" with a code of "cwarn" (Content Warning):
<signal qcode="sig:cwarn" />Optionally, the nature of the warning can be expressed using the Exclude Audience property <exclAudience> and using the IPTC Content Warning NewsCodes. The Scheme URI is http://cv.iptc.org/newscodes/contentwarning/ and recommended Scheme Alias is "cwarn". The Scheme values are:
| Code | Definition |
|---|---|
death |
The content could be perceived as offensive due to the discussion or display of death. |
language |
The content could be perceived as offensive due to the language used.. |
nudity |
The content could be perceived as offensive due to nudity. |
sexuality |
The content could be perceived as offensive due to the discussion or display of sexuality. |
violence |
The content could be perceived as offensive due to the discussion or display of violence. |
For example:
<signal qcode="sig:cwarn" />
<exclAudience qcode="cwarn:nudity"/>
<exclAudience qcode="cwarn:language"/>24.8. Working with Social Media
24.8.1. Ratings
The ability for end-users to rate or interact with content has undergone enormous growth as part of social media and the "socialising" of the Web, and has led to a clear business need that user actions and ratings must be expressed as part of the metadata for all kinds of content.
G2 provides a set of properties for implementers for a flexible use in expressing actions and ratings:
-
The <userInteraction> element can be used to express interactions with the content of this item such as Facebook "likes", tweets, and page views.
-
The <rating> element contains means to express a rating value that applies to the content of this item, such as a star rating, and includes the ability to convey how many "raters" led to the rating, plus information about how the rating system is constructed and how the rating value was calculated.
Both elements are children of <contentMeta> in any type of NewsML-G2 Item, and of <partMeta> in any NewsML-G2 Item except for Concept Items and Planning Items.
The <userInteraction> element
This element expresses the number of times that end-users have interacted with content in the form of "Likes", votes, tweets and other metrics. If the element is used, it has two mandatory attributes:
-
interactions: the count of executed interactions (expressed as a non-negative integer)
-
interactiontype: a QCode indicating the type of interaction which is reflected by this property. The proposed IPTC CV is User Interaction Type, Scheme URI http://cv.iptc.org/newscodes/useractiontype/ with a recommended Scheme Alias of "useracttype"
The example below expresses the number of Facebook "Likes", Google+ "+1" and tweets garnered by the content conveyed in the NewsML-G2 document.
<contentMeta>
...
<userInteraction
interactions="36"
interactiontype="useracttype:fblike" />
<userInteraction
interactions="22"
interactiontype="useracttype:googleplus" />
<userInteraction
interactions="1203"
interactiontype="useracttype:tweets" />
...
</contentMeta>The User Action Type NewsCodes have a Scheme URI of http://cv.iptc.org/newscodes/useractiontype/ and a recommended Scheme Alias of "useracttype". NewsCodes in the scheme are:
| NewsCode | Name | Definition |
|---|---|---|
fblike |
Facebook Like |
Indicates that the user interaction was measured by Facebook’s I Like feature. |
googleplus |
Google +1 |
Indicates that the user interaction was measured by Google’s +1 feature. |
retweets |
Twitter re-tweets |
Indicates that the user interaction was measured by re-tweets of a Twitter tweet. |
tweets |
Twitter tweets |
Indicates that the user interaction was measured by tweets which mention the subject of the content. |
pageviews |
Page views |
Indicates that the user interaction was measured by the number of page views of the content. |
The <rating> element
Ratings such as "five stars" have existed for many years, in the news domain they have been a long-standing feature of image management software. Now they are used on the Web for all kinds of content as providers seek to engage audiences and promote feedback. However, different types of rating are needed – for example content may be rated in terms of how "useful" it was to the user – so the NewsML-G2 <rating> element is a wrapper for attributes that can define different rating models, including :
-
How the rating is expressed
-
How many individual ratings exist
-
How the rating was calculated
For ease of reading, the full attributes of <rating> are tabulated below:
| Definition | Name | Cardinality | Datatype | Notes |
|---|---|---|---|---|
The rating of the content expressed as decimal value |
value |
-1 |
Decimal |
|
How the value is calculated such as median, sum |
valcalctype |
(0..1) |
QCodeType |
Proposed IPTC CV (see below). |
Minimum rating value. |
scalemin |
-1 |
Decimal; |
The value representing the lowest, or worst, rating that can be given |
Maximum rating value. |
scalemax |
-1 |
Decimal; |
The value representing the highest, or best, rating that can be given |
Rating units |
scaleunit |
-1 |
QCodeType |
Two values in the proposed IPTC CV are “star” and “numeric”.(see below) |
The number of parties who contributed a rating. |
raters |
(0..1) |
NonNegativeInteger |
If not present, defaults to 1. |
The type of the rating parties. |
ratertype |
(0..1) |
QCodeType |
Proposed IPTC CV (see below). |
Full definition of the rating. |
ratingtype |
(0..1) |
QCodeType |
The rating engine or method used, for example Amazon star rating or Survey Monkey. |
The following example expresses a star rating with a minimum rating of one star and a maximum of 5. The rating is 4.5 (the provider and end-user may need to agree on how to handle values that are not a whole star, for example by rounding and/or using half-stars). The rating was calculated from the arithmetic mean of ratings by 123 users.
<contentMeta> … <rating value="4.5" valcalctype="rcalctype:amean" scalemin="0" scalemax="5" scaleunit="rscaleunit:star" raters="123" ratertype="rtype:user" /> … </contentMeta>
24.8.2. Content Rating NewsCodes
As an aid to interoperability, the IPTC has created Controlled Vocabularies (NewsCodes) for the properties @valcalctype, @scaleunit and @ratertype:
Rating Calculation Type NewsCodes
These NewsCodes indicate how the applied numeric rating value was calculated from a sample of values. The Scheme URI is http://cv.iptc.org/newscodes/rcalctype/ and the recommended Scheme Alias is "rcalctype". NewsCodes in the scheme are:
| NewsCode | Name | Definition |
|---|---|---|
amean |
arithmetic mean |
Indicates that the numeric value was calculated by applying the arithmetic mean algorithm to a sample. |
gmean |
geometric mean |
Indicates that the numeric value was calculated by applying the geometric mean algorithm to a sample. |
hmean |
harmonic mean |
Indicates that the numeric value was calculated by applying the harmonic mean algorithm to a sample. |
median |
median |
Indicates that the numeric value is the middle value in a sorted list of sample values. |
sum |
sum |
Indicates that the numeric value was calculated as the sum of a sample. |
unknown |
unknown |
Indicates that the algorithm for calculating the numeric value from a sample is not known. |
Rating Scale Unit NewsCodes
These NewsCodes indicate the units used to express the rating value. The Scheme URI is http://cv.iptc.org/newscodes/rscaleunit/ and the recommended Scheme Alias is "rscaleunit". NewsCodes in the scheme are:
| NewsCode | Name | Definition |
|---|---|---|
star |
star |
Star rating |
number |
number |
Numeric rating |
Rater Type NewsCodes
These indicate the type of the party or parties that contributed to a rating. The Scheme URI is http://cv.iptc.org/newscodes/ratertype/, recommended Scheme Alias: "rtype". Scheme NewsCodes are:
| expert | expert | The persons who rated are experts in what they rated. |
|---|---|---|
user |
user |
The persons who rated are using what they rated. |
customer |
customer |
The persons who rated have bought and are using what they rated. |
mixed |
mixed |
The persons who rated are not of the same rater type. |
24.8.3. Hashtags
As these are essentially uncontrolled values, at least within the scope of NewsML-G2, so the recommended way to add these social media tags is by using the <keyword> property with a @role to indicate their purpose. A new NewsCode has been added to the IPTC Description Role scheme to enable implementers to do this in a standard way:
| NewsCode | Name | Definition |
|---|---|---|
hashtag |
Hashtag |
A word or phrase (with no spaces) which is prefixed with the hash character "#" |
| Description Role NewsCodes may be used with other elements when a descriptive qualifier is required. |
The Scheme URI is http://cv.iptc.org/newcodes/descriptionrole/ and the recommended Scheme Alias is "drol", thus:
<contentMeta>
...
<keyword role="drol:hashtag">#iptcrocks</keyword>
...
</contentMeta>24.9. Indicating that a News Item has specific content
In some workflows, the content of a News Item may not be available at the time of the distribution of its first version. For example, if an organisation normally provides a video in HD and SD, but the HD rendition is not yet available, there is a lightweight way to inform end-users that the content is planned, using @hascontent.
This optional attribute may be added to any child element of <contentSet> (inlineXML, inlineData, remoteContent) as a flag to indicate whether the element contains content/content reference or is either empty/only metadata . @hascontent is simply a Boolean flag with a default of "1" or "true", and "0" or "false" to indicate that this element contains no content.
The example below is a <remoteContent> showing that an HD rendition of the existing SD rendition of a video will follow soon. To make the receiver aware of the planned release of the additional rendition, the wrapper has been added to contentSet with only metadata defined, and no actual content being provided, and a @hascontent value of "isfalse":
<contentSet>
<remoteContent
href="http://www.example.com/video/2008-12-22/20081222-PNN-1517-
407624/20081222-PNN-1517-407624.avi"
format="frmt:MPEG"
duration="111" durationunit="timeunit:seconds"
videocharacteristic="videodef:SD"
videoframerate="25"
videoaspectratio="16:9" />
<remoteContent
hascontent="false"
format="frmt:MPEG"
duration="111" durationunit="timeunit:seconds"
videocharacteristic="videodef:HD"
videoframerate="25"
videoaspectratio="16:9" />
</contentSet>25. Identifying Sources and Workflow Actors
25.1. Introduction
NewsML-G2 contains a number of features designed to help providers and end-users maintain an audit trail for an Item, its payload and metadata, and in some cases to maintain document/content security.
25.2. Information Source <infoSource>
The <infoSource> property, together with its @role, enables finely-grained identification of the various parties who provided information used to create and develop an item of news. The definition of <infoSource> was extended in NewsML-G2 v2.10. It had previously been defined as the party that originated or enhanced the content. This was extended to "A party (person or organisation) which originated, modified, enhanced, distributed, aggregated or supplied the content or provided some information used to create or enhance the content."
This extension required that the @role attribute of Information Source be more rigorously defined in order to maintain inter-operability between providers and receivers, and promote a better understanding of the part played by the various actors identified in multiple <infoSource> elements.
The value of @role should be taken from the recommended IPTC Content Production Party Role NewsCodes created and maintained for this purpose. The Scheme URI is http://cv.iptc.org/newscodes/contentprodpartyrole/ and the recommended Scheme Alias is "cpprole".
The assumed value of @role is "cpprole:author" indicating that the party created the content, and may be omitted. If a party did anything more than originate information, one or more @role attributes MUST be applied.
25.3. Identifying workflow "actors" – a best practice guide
The <infoSource> property is one of a set of properties in NewsML-G2 that are used to identify the actors in the creation and evolution of an item of news. The following table is a guide to how these properties should be used:
| Property | Location in an Item | Usage notes |
|---|---|---|
News Message |
||
Message Sender |
header/sender |
Party sending the itemsin the message, which may be an organisation or a person. Best practice is to identify a sender by a domain name. |
Item |
||
Hop History |
hopHistory |
Identifies the actions and sequence of actions by parties who created, enhanced or transformed the content and/or metadata of the Item.(See Transaction History <hopHistory> below) |
Copyright Holder |
rightsInfo/copyrightHolder |
Party claiming, or responsible for, the intellectual property for the content. |
Copyright Notice |
rightsInfo/copyrightNotice |
The appropriate copyright text claiming the intellectual property for the content. The copyright notice may be refined by the Usage Terms. |
Item Provider |
itemMeta/provider |
The party responsible for the management and the release of the NewsML-G2 Item. This corresponds to the publisher of the Item. |
Item Generator |
itemMeta/generator |
The name and version of the system or application that generated the NewsML-G2 Item. Where a role IS NOT specified, the Generator Tool applies to the most recent item generation stage. |
Incoming Feed Identifier |
itemMeta/incomingFeedId |
The incoming feed identifier may be defined by i/ the provider of the feed and/or ii/ the processor of the feed. (See Incoming Feed Identifier <incomingFeedId>, below) |
Content |
||
Content Creator |
contentMeta/creator |
The party (person or organisation) that created the content. This MAY also be indicated textually in <by> |
Information Sources |
contentMeta/infoSource |
Person or organisation which originated, modified, enhanced, distributed, aggregated or supplied the content or provided some information used to create or enhance the content, qualified by @role, for example role="cpprole:origcont" indicates the original content owner using the Content Production Party Role NewsCodes. |
Content Contributors |
contentMeta/contributor |
Person or organization that modified or enhanced the content, preferably the name of a person. Typical contributor types represented by @role: The Editor of the content. An additional Reporter of the content. |
Creditline |
contentMeta/creditline |
Free-text expression of the credit(s) for the content; |
Byline |
contentMeta/by |
Free-text expression of the person or organisation that created the content– see also Content Creator above. |
25.4. Transaction History <hopHistory>
Content may traverse many organisations and workflows in its journey to an end user. A news organisation may have third-party providers in addition to in-house contributors and editors. There are a number of reasons why it may be necessary to document the actions involved in the evolution of a news object, for example auditing and payment, or for editorial attribution. Hop History provides a machine-readable way of capturing and expressing metadata describing these actions.
Using Hop History, the receiver of a NewsML-G2 Item should be able to answer questions such as the following:
-
Has the object been transformed?
-
Who transformed the object (and when)?
-
Has the object been enhanced?
-
Who enhanced the object (and when)?
-
Did a specific Party perform a specific Action on a specific Target (the object and/or content and/or metadata)?
-
Has the object been processed (any Action or Target) by a specific Party?
-
What sequence of Party(ies) has processed (any Action or Target) the object?
The object of the actions does not have to be a NewsML-G2 Item; the object of the actions may be the content only, or the content plus the metadata of the Item even if its format was different in a previous hop. Hop History usage is subject to these rules:
-
Hop History does not replace any information that may exist in other formal metadata blocks (itemMeta, contentMeta, partMeta). For example: the Content Creator (a Party in the Hop History with an associated Action of ‘created’) MUST be the same as the Party identified as contentMeta/creator and the provider MUST ensure these facts are consistent.
-
It MUST be possible to remove the Hop History without degrading the formal metadata blocks described above.
Each Item can have one <hopHistory> element, which contains one or more <hop> elements. Each <hop> may have a @seq attribute to indicate its place in a sequence of Hops, and may optionally have a @timestamp.
Each Hop element may identify the <party> involved in the Hop, either as a @literal, or @qcode, and an unbounded number of <action> elements that describe the action(s) the Party took. Each <action> element may identify the type of action, using a @qcode, and the @target of the action: whether the action was performed on the full item, the content only, or the metadata.
The Scheme URI of the Hop Action CV (referenced by the @qcode of the action element) is:
http://cv.iptc.org/newscodes/hopaction/ with a recommended alias of "hopaction". The members of the CV are defined as follows:
| Code | Definition |
|---|---|
created |
A Party has created the target of the action. |
transformed |
A Party has transformed the target of the action. Transforming means that an existing target was changed in data format. |
enhanced |
A Party has enhanced the target of the action. |
The default action – indicated by the absence of the <action> element – is that the Party forwarded the object without making any changes.
The Scheme URI of the Hop Action Target CV (referenced by @target) is: http://cv.iptc.org/newscodes/hopactiontarget/ with a recommended scheme alias of "hatarget". The members of the CV are defined as:
| Code | Definition |
|---|---|
metadata |
Any metadata associated with the content of the object. |
content |
The content of the object, which could be present in different renditions. |
The default target – indicated by the absence of the @target attribute, is metadata AND content.
In the Listing below, the provider (Acme Media) expresses a Hop History for the News Item as follows:
-
The original content was created by Thomson Reuters (note the use of EITHER @qcode OR @literal to identify the Party.)
-
The next Party in the sequence, identified as "ex-comp:bwire", transformed the content into another format, and enhanced the metadata.
-
The following Party ("ex-comp:acquiremedia") created new metadata.
-
The final Party in the sequence of Hops ("ex-comp:AP), enhanced the content and metadata.
All Scheme Aliases used in the listing below indicate IPTC NewsCodes vocabularies, except for ex-comp which is a fictional vocabulary.
<?xml version="1.0" encoding="UTF-8" ?>
<newsItem
xmlns="http://iptc.org/std/nar/2006-10-01/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/
./NewsML-G2_2.31-spec-All-Power.xsd"
guid="urn:newsml:acmenews.com:20161019T1205:HOP-HISTORY-EXAMPLE"
version="15"
standard="NewsML-G2"
standardversion="2.31" xml:lang="en-US">
<catalogRef
href="http://www.iptc.org/std/catalog/catalog.IPTC-G2-Standards_37.xml" />
<catalogRef href="http://www.acmenews.com/synd/catalogs/anmcodes.xml" />
<hopHistory>
<hop seq="1" timestamp="2018-10-19T16:15:00Z">
<party qcode="ex-comp:TR">
<name>Thomson Reuters</name>
</party>
<action qcode="hopaction:created" target="hatarget:content" />
</hop>
<hop seq="2" timestamp="2018-10-19T16:18:00Z">
<party qcode="ex-comp:bwire" />
<!-- transformed content e.g. to a different format -->
<action qcode="hopaction:transformed" target="hatarget:content" />
<!-- enhanced existing metadata -->
<action qcode="hopaction:enhanced" target="hatarget:metadata" />
</hop>
<hop seq="3" timestamp="2018-10-19T18:15:00Z">
<party qcode="ex-comp:acquiremedia" />
<!-- added metadata -->
<action qcode="hopaction:created" target="hatarget:metadata" />
</hop>
<hop seq="4" timestamp="2018-10-19T19:15:00Z">
<party qcode="ex-comp:AP" />
<!-- enhanced content e.g. links to the text of the article -->
<action qcode="hopaction:enhanced" target="hatarget:content" />
<!-- enhanced existing metadata -->
<action qcode="hopaction:enhanced" target="hatarget:metadata" />
</hop>
</hopHistory>
<rightsInfo>
<copyrightHolder uri="http://www.thomsonreuters.com" />
</rightsInfo>
<itemMeta>
<itemClass qcode="ninat:text" />
<provider qcode="nprov:REUTERS" />
<versionCreated>2022-10-19T20:15:00Z</versionCreated>
<pubStatus qcode="stat:usable" />
</itemMeta>
<!-- metadata and content -->
<!-- metadata and content -->
<!-- metadata and content -->
</newsItem>25.4.1. Expressing further information about an Action
A child <related> element may be used where further informaton about an action needs to be added, for example as shown here, where the system that acted is identified:
<hopHistory>
...
<hop seq="2">
<party qcode="ex-NS:RTRS"/>
<action qcode="ex-trhopaction:map-isin-to-R" target="hatarget:metadata"
why="why:inferred" how="howextr:tool">
<name>Map ISIN To RIC</name>
<related rel="ex-cptrel:hasWorker" qcode="ex-sys:RDS"/> (1)
</action>
</hop>
</hopHistory>| 1 | The news provider Reuters (ex-NS:RTRS) maps ISINs (Financial Instrument Identifiers) to proprietary Instrument Codes (ex-trhopaction:map-isin-to-R) using its RDS System (ex-sys:RDS) as the mapping worker. |
25.5. Incoming Feed Identifier <incomingFeedId>
Some content providers, notably content aggregators, may need to identify the incoming news feed that is the source for a NewsML-G2 Item. The <incomingFeedId>, a child property of <itemMeta> enables an aggregator to combine the property value with a @role:
-
To apply the provider’s feed identifier to the inbound content as it processed into a NewsML-G2 Item, and
-
To apply the aggregator’s feed identifier for the content in the NewsML-G2 Item.
Attributes of <incomingFeedId>
| Attribute | Definition |
|---|---|
role orroleuri |
The role of this feed identifier, for example to assert that this is the originator’s identifier for the source feed that created the content. |
qcode oruri |
The unique identifier for the incoming feed. |
The following example is courtesy of Thomson Reuters:
A news story is received from PR Newswire on its UK Regulatory News service. The provider’s feed identifier is "PRNUKReg". Thomson Reuters applies this code to the resulting Item, and adds its own Incoming Feed Identifier "RRR". The resulting code in <itemMeta> would be:
<itemMeta>
...
<incomingFeedId role="ex-feedIdRole:srcFeedId"
qcode="ex-PRNFeedId:PRNUKReg" />
<incomingFeedId role="ex-feedIdRole:TRFeedId" qcode="ex-TRFeedId:RRR"
/>
</itemMeta>Note that @role and @qcode are used in the example, but their IRIType siblings @roleuri and @uri may be used instead.
25.6. Original Representation of an Item <origRep>
The <origRep> property adds the ability for a provider to specify a globally unique (and persistent) URL for retrieving a NewsML-G2 Item by interactive means, enabling providers to create a retrieval model for distributing NewsML-G2 Items, as an alternative to the widely used data feed method. Providers may also specify the technical means of retrieval. <origRep> is an optional child property of <itemMeta>, which may contain many <origRep> properties each specifying a different retrieval method and/or the role of the repository hosting the Item amongst many possible repositories.
Attributes of <origRep>
| Name | Cardinality | Definition |
|---|---|---|
Common Power |
- |
Inherited attribute group |
Time Validity |
- |
Inherited attribute group |
accesstype or accesstypeuri |
0..1 |
A qualifier that indicates the technical variant for accessing this item (for example communication protocols like “http”) - expressed by a QCode or URI |
reposrole or reposroleuri |
0..1 |
A qualifier which indicates the role of the stated repository - expressed by a QCode or URI. |
Example
<itemMeta>
...
<origRep accesstype="ex-acctype:http" reposrole="ex-reprol:mirror">
http://cdn2.example.com/items/dkad19383
</origRep>
</itemMeta>Note that <origRep> references a NewsML-G2 Item; use <altRep> to specify an alternative representation of the Item, for example in a different format such as IIM.
25.7. Hash Value <hash>
The optional <hash> element, a child element <itemMeta>, <assert> and <remoteContent>, contains a digital "fingerprint" generated from content, that enables end users to verify that the content of a NewsML-G2 Item, or an object referenced by an Item, has not been changed
The <hash> property has two attributes: the @hashtype tells the receiver the algorithm that was used to generate the hash, and @hashscope tells the receiver the parts of the content that were used to create the hash, and that therefore can be verified.
There are two recommended IPTC CVs for the <hash> properties. The first is Hash Type NewsCodes; Scheme URI http://cv.iptc.org/newscodes/hashtype/ with a recommended scheme alias of "hashtype":
| Code | Definition |
|---|---|
MD5 |
The MD5 hash function |
SHA-1 |
The SHA-1 hash function |
SHA-2 |
The SHA-2 hash function |
The second is the Hash Scope NewsCodes; Scheme URI http://cv.iptc.org/newscodes/hashscope/ with a recommended scheme alias of "hashscope". Scheme values are:
| Code | Definition |
|---|---|
content |
Content only (Default case, if @hashscope omitted) |
provmix |
Provider specific mix of content and metadata |
In the example below, the <hash> is a child of Item Metadata and the scope is a provider-specific mix of metadata and the payload of a News Item. The content would be contained in either an <inline> or <inlineXML> element, and it would be the responsibility of the provider to define (outside NewsML-G2) which metadata properties were in scope for creating the hash. For example they may advise customers that the <headline> and <by> of a NewsItem are included when generating the hash value of the content.
<hash hashtype="hashtype:md5"
hashscope="hashscope:provmix">hash-code</hash>A <hash> element may also be added to <remoteContent> indicating that the hash was generated from the content of the referenced object. In the example below, the target is the thumbnail of an image. The hash scope is omitted and defaults to "content":
<remoteContent residref="urn:foobar" rendition="rnd:thumbnail">
...
<hash hashtype="hashtype:md5">hash-code</hash>
...
</remoteContent>When applying a hash value for the content of a NewsML-G2 document, it makes sense to place the <hash> in <itemMeta> only for content payloads of <inlineXML> or <inlineData>. For Remote Content, where there could be multiple renditions of the content, the <hash> should be a child of each <remoteContent> wrapper.
26. Changes to NewsML-G2 and related Standards
26.1. Introduction
The following is a summary of changes to the NewsML-G2 Specification since Revision 1 of the Guidelines. Please check the Specification documents available by visiting www.newsml-g2.org/spec. The latest changes are in the topmost section, followed by earlier changes in descending order. Details of the changes list below may also be found at http://dev.iptc.org/G2-Approved-Changes
26.2. Guidelines release 15 – covers NewsML-G2 2.31
Please see What’s New in NewsML-G2 2.31
26.3. Guidelines release 14 – covers NewsML-G2 2.30
26.3.1. Optional Catalog references (catalog and catalogRef)
As it is now possible to use fully expanded versions of NewsML-G2 attributes (for example @role or its sibling attribute @roleuri), implementers who chose exclusively to use the URI siblings of attributes were forced to use a redundant scheme reference, since the use of either <catalog> or <catalogRef> was mandatory. These elements are now optional if only URI attributes are used.
26.3.2. Specifying the format of a Resource Reference
The "residref" attribute is used in elements to convey "the provider’s identifier of the target resource", however there was no way for a provider to explicitly express how the reference should be interpreted. To overcome this limitation, the companion attribute residrefformat (and its URI sibling residrefformaturi) have now been added to the Target Resource Attributes Group.
The recommended CV to be used is https://cv.iptc.org/newscodes/valueformat/ with a recommended scheme alias of "valfmt":
<remoteContent residref="tag:example.com,2008:PIX:FOO20081220098658"
residrefformat="valfmt:uri"26.4. Guidelines release 13 – covers NewsML-G2 2.29
26.4.1. Affiliation for organisation details
Up to an including v2.28, Affiliations could be expressed only for Persons, using <personDetails>. Recent user cases pointed to the need for Affiliations to be added to Organisations. In order to do this, a new Property Type, OrganisationAffiliationType, has been created. This is a copy of PersonAffiliationType, with the addition of a new attribute group, FlexOrganisationPropType, which enables @role/@roleuri to be used.
26.4.2. Example: Organisation affiliated with another Organisation
Acme Financials is a member of Financial Group ABC
<assert qcode="ex-org:123">
<name>Acme Financials</name>
<organisationDetails>
<affiliation role="ex-affrole:memberOf" type="cpnat:organisation" qcode="ex-fingroup:ABC"/>26.4.3. Example: Person affiliated with an Organisation
John Smith is:
-
Employed by Club A
-
Supporter of Club B
<assert qcode="ex-pers:22">
<name>John Smith</name>
<personDetails>
<affiliation role="ex-affrole:employedBy" type="cpnat:organisation" qcode="ex-club:A"/>
<affiliation role="ex-affrole:supporterOf" type="cpnat:organisation" qcode="ex-club:B"/>26.4.4. Retiring a Scheme
In its initial design, NewsML-G2 provided for Concepts to be retired, by using the @retired attribute of conceptId. As the standard has matured, we have reached the point where entire Schemes need to be retired. The issue, as with retiring Concepts, is how this can be done without breaking existing NewsML-G2 Items.
There are two changes that support this use case:
-
Add the attributes @schemecreated, @schememodified and @schemeretired to
schemeto be used in Catalogs -
Add the attributes @schemecreated, @schememodified and @schemeretired to
schemeMetato be used in Knowledge Items.
For details, see Scheme Metadata and <scheme> properties.
26.5. Guidelines release 12 – covers NewsML-G2 2.28
26.5.1. Derive the value of a property from a non-Concept value
The derivedFromValue element represents the non-Concept value that was used for deriving the value of one or more properties in this NewsML-G2 Item. See The Derivation of Metadata
Corresponding IPTC Change Request: G2 CR00205: new element derivedFromValue
26.5.2. Attribution of metadata creation
The entity (person, organisation, system) responsible for creating metadata is expressed by the metadataCreator element, which is used in conjunction with the creator attribute (note: NOT the creator element) See The Creator of Metadata
Corresponding IPTC Change Request: G2 CR00206: add metadataCreator property
26.5.3. Fix DateTime datatype errors
The attributes of some NewsML-G2 elements have a definition of "the date, and optionally, the time" but were erroneously given a datatype of xs:datetime. This is corrected in v2.28 to assigning the NewsML-G2 data type DateOptTimeType to these attributes:
-
the coversfrom and coversto attributes of
planning(child ofnewsCoverage) -
the coversfrom and coversto attributes of
assignedTo(child ofplanning) -
the timestamp attribute of
hop(child ofhopHistory) -
the timestamp attribute of
action(child ofhop)
Corresponding IPTC Change Request: G2 CR00207: fix date/time related XML Schema data type errors
26.6. Guidelines release 11 – covers NewsML-G2 2.26 → NewsML-G2 2.27
26.6.1. Change of datatype of action
Corresponding IPTC Change Request: CR00197
The <action> child element of <hopHistory> already has qualifying elements of <name> and <hierachyInfo>, but providers asked for this to be extended so that further information about an action could be conveyed. This is enabled through changing the datatype of <action> from Qualified Property Type (QualPropType) to Qualified Related Property Type (QualRelPropType) which also includes the <related> child element.
26.6.2. Add audience and exclAudience to planning
Corresponding IPTC Change Request: CR00198
To support further information about the intended content of a Planning Item, and in alignment with <contentMeta>, the <audience> and <exclAudience> properties are added as shown in Additional Properties of Planning.
26.6.3. Add support of faceted concepts to Flex1ConceptPropType
Corresponding IPTC Change Request: CR00199
The elements <mainConcept> and <facetConcept> are added to the Flex1ConceptPropType which is currently used by <genre> and <subject>.
A faceted concept is a combination of a main concept (which requires a facet) and another concept which provides the facet to the main concept. See Faceted Concepts for details.
26.6.4. Clarify the processing model of Publish Status
Corresponding IPTC Change Request: CR00200
The Specification of Publish Status required clarification because real-world experience showed that the existing definition was open to various interpretations. The amended text follows, with the important changes highlighted in italic.
For the Publish Status of a NewsML-G2 Item, the IPTC makes these values normative for the exchange of Items between a provider and its customers:
-
Usable: The Item MAY be published without restriction.
-
Withheld: Until further notice, the Item MUST NOT be made public by whatever means.
If the Item has been published the publisher MUST take immediate action to withdraw or retract it. -
Canceled: The Item MUST NOT be made public by whatever means.
If the Item has been published the publisher MUST take immediate action to withdraw or retract it.
The use of Withheld or Canceled can be interpreted as indicating that parts of the previous version of the Item were not correct (in the case of Canceled, cannot be corrected), and therefore cannot be considered as reliable information.
This raises the issue as to which parts of the Item version with a publish status of Withheld or Canceled should be considered as correct and reliable. These attributes and elements MUST be considered as correct and reliable: the Item @guid and @version, the pubStatus element including the @qcode and/or @uri attributes. The edNote element SHOULD be considered as reliable.
All other metadata properties of the Item MAY be considered as reliable, but the element(s) conveying the content of the Item SHOULD NOT be considered as reliable.
See Publishing Status.
26.6.5. Add charcount attribute to newsContentCharacteristics
Corresponding IPTC Change Request: CR00201
The @charcount attribute is added to the News Content Characterstics group to complement the existing attributes for words, lines and pages of textual content. See Additional Properties of Planning.
26.6.6. Adjust the semantics of the time delimiters of partMeta
Corresponding IPTC Change Request: CR00202
Discussions on the <timeDelim> element for expressing the temporal properties of content such as video and audio revealed that the existing definitions in the Specification needed clarifying: whether to count the value of the @start and @end points as part of the timeline, and also a note on the use of Edit Unit to clarify its indivisible character. The revised definitions are:
-
@start: The start time of the part in a timeline. The expressed value is excluded from the timeline part. Using the Edit Unit requires the frame rate or sampling rate to be known; this must be defined by the referenced rendition of the content.
-
@end: The end time of the part in a timeline. The expressed value is included in the timeline part. Using the Edit Unit requires the frame rate or sampling rate to be known; this must be defined by the referenced rendition of the content.
See more in Part Metadata in the Video chapter.
26.6.7. Change of datatype of signal
Corresponding IPTC Change Request: CR00203
The datatype of <signal> is changed so that it may now take a @literal value; for example in the case where a provider is simply passing on a literal value from a third party. The new datatype is Flex1PropType, which is extended to include @severity and @severityuri, which are existing attributes of signal.
26.6.8. Add confidence and relevance to slugline, headline and description
Corresponding IPTC Change Request: CR00204
Add @confidence and @relevance to the following:
-
<headline>
-
<slugline>
-
<description>, e.g. for a Summary
Currently these properties support attributes such as @how, @why and @role, but recent use cases have highlighted the need to also support @confidence and @relevance, typically for when automation creates multiple instances of these properties, each with varying confidence and relevance. This change also brings the above elements in line with others in the DescriptiveMetadataGroup; specifically subject, genre and keyword. See Aligning Descriptive Metadata properties.
26.7. Guidelines release 10 – covers NewsML-G2 2.24 → NewsML-G2 2.25
26.7.1. Development Freeze for Core Conformance (CCL)
There is to be no further development of the Core Conformance Level (CCL) of NewsML-G2, so the latest version that supports CCL is 2.25. Later versions of the standard only support Power Conformance (PCL). CCL remains as a minimal set of features that create a useful working implementation of NewsML-G2, but all recent developments have focused on adding features at PCL only, so the IPTC feels this is a useful and pragmatic step to simplify the standard going forward.
| The default conformance level remains CCL, therefore implementers must explicitly specify @conformance of any NewsML-G2 Item even though they are using a version beyond 2.25, as in: |
conformance="power"26.7.2. Add attributes for standard version of contenttype or format
When content has an IANA Media Type expressed for example as @contentype, there may be a need to qualify the attribute according to the standard used. The following attributes are added to all elements having a @contenttype, a @contenttypevariant, or a @format attribute:
-
@contenttypestandardversion
-
@contenttypevariantstandardversion
-
@formatstandardversion
The following table illustrates some use cases:
| Attribute | @contenttype | @contenttype standardversion | @contenttype variant | @contenttype variant standardversion | @format | @format standardversion |
|---|---|---|---|---|---|---|
Current definition by the XML Schema |
The IANA (Internet Assigned Numbers Authority) MIME type of the target resource. |
A refinement of a generic content type (i.e. IANA MIME type) by a literal string value |
A refinement of a generic content type (i.e. IANA MIME type) by a value from a controlled vocabulary - expressed by a QCode |
|||
Use Case Examples: the content is … |
||||||
NITF 3.4 |
text/vnd.IPTC.NITF |
3.4 |
||||
G2 v2.24 News Item |
application/vnd.iptc.g2.newsitem+xml |
2.24 |
||||
SportsML 3 |
application/xml |
1.0 (for xml) |
fmt:SportsML |
3.0 (for SportsML) |
26.7.3. Adding urgency to planning
The NewsML-G2 Planning Item already supports contentMeta/urgency, which indicates the Editorial Urgency of the content of the <planningItem>; this refers to the entire structure within the <newsCoverageSet>.
There is a need to be able to flag the Urgency (Importance) of News Coverage per Item Class associated with a Planning Item. Providers will not necessarily group <planning> by Item Class within <newsCoverage>, so this Urgency indication needs to be supported at the <planning> level, not the <newsCoverage> level. Example:
<newsCoverageSet>
<newsCoverage>
<planning>
<itemClass qcode="ninat:video" />
<scheduled>2013-10-12T11:00:00.000Z</scheduled>
...
<newsContentCharacteristics ... />
<urgency>3</urgency>
<planningExtProperty ... />
</planning>
</newsCoverage>
...
</newsCoverageSet>26.7.4. Add Publication History
The Publication History element <pubHistory> is a new child element of News Item and Package Item. It sits between <hopHistory> and <rightsInfo> and may be qualified by any of the Common Power Attributes group. It has a single child element <published>, which is qualified by a combination of @qcode, @uri, or @literal attributes according to the rules set forth in Change to cardinality of QCode Type attributes. There must be AT LEAST one <published> element per <pubHistory>. The <published> element may contains the following (optional) elements:
-
timestamp
-
name
-
related
-
publishedExtProperty
Example:
<pubHistory>
<published qcode="..">
<timestamp>2017-11-02T23:34:00Z</timestamp>
<name>SNAP</name>
</published>
</pubHistory>26.7.5. Adding role and version attribute to altId
The @role attribute is added so that information about the role of a specific Alternative Identifier among other Alternative Identifiers may be expressed in addition to the @type attribute, which provides information about the context of the <altId>.
The @version attribute is added because a genuine identifier may need to be accompanied by a version, and this was missing from <altdId>.
26.7.6. Refine event date confirmation
The current <confirmation> child element of eventDetails/dates is DEPRECATED from NewsML-G2 v2.24 on because it only supports a single value that applies to all dates, but providers need further granularity to support the confirmation status of any of the date and duration values for an event.
Therefore the optional attributes @confirmationstatus and @confirmationstatusuri are added to the following eventDetails/dates properties:
-
start
-
end
-
duration
To accompany the change the IPTC NewsCodes for Event Date Confirmation (Scheme URI http://cv.iptc.org/newscodes/eventdateconfirm/, recommended alias "edconf") is changed.
See Event Details Group for further details.
26.8. Guidelines release 9 – covers NewsML-G2 2.22 → NewsML-G2 2.23
26.8.1. Add “related” element to the Item Class property
This enables facets of an Item Class to be expressed using the <related> child element.
26.8.2. Add “worldRegion” to Address Types
The ability to express a World Region as part of an address is common to IPTC Standards, therefore the element <worldRegion> is added to Address Type elements so that the World Region may be added to the <POIDetails> and <contactInfo> wrapping elements. See Contact Info <contactInfo>.
26.8.3. Add Rights Expression properties to the Rights Info wrapper
Up to and including NewsML-G2 2.22, only XML-encoded rights expressions could be added to <rightsInfo> via the property’s Extension Point. The alternative was to add a reference using <link>. This change in version 2.23 enables XML and non-XML encoded rights expression to be added to <rightsInfo>, and the language of encoding to be specified.
Two new elements are added:
-
<rightsExpressionXML> indicates a rights expression as defined by a rights expression language and serialised using XML encoding. The mandatory @langid expresses an identifier for the rights expression language using a URI.
-
<rightsExpressionData> indicates a rights expression encoded using any non-XML serialisation and qualified by two mandatory attributes: @langid uses a URI to identify the rights expression language, and @enctype identifies the type of encoding (for example JSON). The IPTC recommends that this is expressed using an IANA Media Type.
See Rights Metadata.
26.8.4. Add concepttype attribute to the Scheme Metadata property
By adding @concepttype to <schemeMeta> (which expresses metadata about a scheme conveyed in a Knowledge Item), the concept types that are used within the Knowledge Item may be listed. Please note that the IPTC recommends that ALL concept types conveyed are added. See Scheme Metadata
26.8.5. Modify ratings attributes
The definition of the attributes of <rating> - @scalemin and @scalemax – were changed to make it clear that @scalemin is the value of the lowest, or worst, rating; @scalemax is highest, or best, rating. See Working with Social Media
26.8.6. Add time-frame attributes to aspects of News Coverage
Long-running events may need planning for their News Coverage split into chunks, for example as the coverage of separate days of a multi-day event is assigned to different persons. Therefore the optional attributes @coversfrom and @coversto are added to the <planning> and <assignedTo> elements of the <newsCoverage> wrapper to express the date (and optionally the time) of the start and end of coverage.
Accompanying this change, the cardinality of <planning> is extended from (1) to (1..∞)
26.8.7. Globalising Hint Elements
To fix potential validation issues when adding metadata or processing Hints, a few elements that were locally-defined in the NewsML-G2 XML schema have been globalised. See Adding Hints from the NAR namespace
26.8.8. SportML-G2 updated to v3.0
SportsML 3.0, an open and highly flexible standard for the interchange of sports data, was released in July 2016. It is a comprehensive update to SportsML 2.2. The SportML-G2 Chapter (previously in this document, now at https://iptc.org/std/SportsML/guidelines/) has been updated to the latest standard.
26.9. Guidelines release 8 – covers NewsML-G2 2.19 → NewsML-G2 2.21
26.9.1. Denote the preferred symbol (ticker) for a financial instrument
By adding @rank to the <hasInstrument> property, a provider can indicate which market symbol, or ticker, for a financial instrument is preferred where there is a group of symbols to choose from. See Expressing company financial information
26.9.2. Original Representation of an Item <origRep>
The <origRep> property adds the ability for a provider to specify a globally unique (and persistent) URL for retrieving a NewsML-G2 Item by interactive means, enabling providers to create a retrieval model for distributing NewsML-G2 Items, as an alternative to the widely used data feed method. Optionally, providers may also specify the technical means of retrieval. See Original Representation of an Item <origRep> for details.
26.9.3. Incoming Feed Identifier <incomingFeedId>
Some news providers, notably content aggregators, may need to identify the incoming news feed that is the source for a NewsML-G2 Item. The <incomingFeedId>, a child property of <itemMeta> enables an aggregator to apply the provider’s feed identifier to the inbound content as it processed, and also to apply its own feed identifier for the content. See Incoming Feed Identifier <incomingFeedId> for details.
26.9.4. Change to cardinality of QCode Type attributes
After the introduction of @uri and later the "URI Sibling" attributes, a QCode remained mandatory for some properties. From v2.20 this constraint is lifted and the cardinality of the QCode attribute in these properties is changed from (1) to (0..1). See Change to cardinality of QCode Type attributes for a full list of the properties and attributes affected by this change.
26.9.5. <link> and <edNote> added to <partMeta>
The partMeta element already supports contentMeta elements and the itemMeta <signal> element. In order to extend the capabilities of partMeta, the itemMeta elements <link> and <edNote> have also been added to <partMeta> in NewsML-G2 v2.21. See Special processing instructions for metadata about a part of the content
26.10. Guidelines release 7 – covers NewsML-G2 2.16 → NewsML-G2 2.18
26.10.1. Extending NewsML-G2
A new way to extend NewsML-G2 was added, using a set of generic properties created for this purpose, one for each NewsML-G2 "wrapper" element (for example the generic extension element for <itemMeta> is <itemMetaExtProperty>). The semantics of a generic property are defined by the concept referenced by the property’s @rel attribute. See Hints and Extension Points in NewsML-G2
When a Knowledge Item is used to deliver the complete set of concepts in a scheme, metadata for the scheme may be expressed using <schemeMeta>, rather than relying on the use of <scheme> in a Catalog. See Scheme Metadata
26.10.2. Time precision improvement for video
Alternative renditions of a video may use different frame rates, and in these circumstances a single value denoting the time delimiter for the different shots of a multipart video will not be frame-accurate. This was corrected by the addition of @renditionref to the <timeDelim> element of part metadata. See Timing metadata
26.10.3. Enhancements to news coverage
The <newsCoverage> element had Extension Points added and the <newsContentCharacteristics> element allows the expression of physical properties of the planned news coverage (for example the height and width of an image) for video and still images. See Advanced features of <planning>
26.10.4. Special processing can be signalled for part of content
Specific processing instructions can be applied to different parts of an Item’s content. See Special processing instructions for metadata about a part of the content
26.10.5. Extending the use of full URIs as concept identifiers
The ability to express a property value as a full URI using @uri as an alternative to @qcode was extended by introducing a corresponding full URI type alternative for the existing QCodeType and QCodeListType attributes, for example @role gets a @roleuri sibling. See A generic way to express concept identifiers as URIs
26.11. Guidelines release 6 – covers NewsML-G2 2.13 → NewsML-G2 2.15
26.11.1. Add layoutorientation to contentCharacteristics
Expresses editorial advice about the use of a picture in a page layout.
26.11.2. Add signal to remoteContent
Enables specific processing instructions for separate renditions of remote content.
26.11.3. Add pubconstraint attribute
Applies a constraint to the publication of the value of a metadata property or content reference.
26.11.4. Add contenttypevariant attribute
Refines the @contenttype (Media Type) of the referenced resource.
26.11.5. Change data type of duration
By changing the data type from integer to string, enables the expression of values such as SMPTE time codes.
26.12. Guidelines release 5 – covered NewsML-G2 2.10 → NewsML-G2 2.12
26.12.1. Add a link property to rightsInfo
The link may be used by the receiver to access another rights expression resource.
26.12.2. Refine AddressType
Opening the cardinality of <area> and <locality> child elements to be unbounded, and add a @role to <line>, <area> and <locality>.
26.12.3. Expand geoAreaDetails
Adding three new child elements that express different geometries for defining a Geographical area:
<line>, <circle>, <polygon>, each with one or more <position> child elements.
26.12.4. Expressing Ticker Symbols
Adds the ability to express stock prices in a structure; see Expressing company financial information
26.12.5. Add sameAs to Relationship Group of properties
By adding a repeatable child element <sameAs> to the properties <broader>, <narrower> and <related>, a list of concept URIs can be provided in addition to the one expressed in the @qcode/@uri of these elements.
Example use: if using <broader> concept to express the country "parent" of a geographic region, a provider can use <sameAs> to express both two-letter and three-letter country codes in the same wrapper.
26.12.7. Adding descriptive properties to a package group
By adding <title>, <signal> and <edNote> as child elements of <groupRef>, descriptive metadata and special processing instructions may be provided with the Group References of Package Items. See http://dev.iptc.org/G2-CR00142-Adding-descriptive-properties-to-a-package-group for more details.
26.12.11. Extend the attributes of an icon
Extending the attributes of an icon in order to enable the selection of the appropriate icon for a specific purpose. See http://dev.iptc.org/G2-CR00144-extend-the-attributes-of-an-Icon
26.12.17. Add @title to Target Resource properties group
Aligns NewsML-G2 elements with similar properties provided by HTML5 and Atom. See http://dev.iptc.org/G2-CR00152-adding-title-attribute-to-targetResource-group
26.13. Guidelines release 4 – covered NewsML-G2 v2.7/EventsML-G2 1.6 → NewsML-G2/EventsML-G2 2.9
26.13.1. EventsML-G2 merged with NewsML-G2
Originally, NewsML-G2 conveyed content, while its sibling EventsML-G2 was a separate Standard for News Events, although both are children of the NAR model. With the introduction of the Planning Item with its News Coverage payload in NewsML-G2 v2.7 and EventsML-G2 v1.6, it became difficult to make a distinction between the two as separate Standards.
The IPTC members therefore decided to unify the Standards. From a non-technical “brand” standpoint, NewsML-G2 is now the “senior” umbrella Standard for all Items, whether they convey News or Events. SportsML-G2 continues to be a completely separate Standard, although it is always conveyed by NewsML-G2. From v2.9, all EventsML-G2 structures were merged in NewsML-G2.
26.13.2. Hint and Extension Point
Adding properties from the NewsML-G2 (NAR) namespace is a method of providing processing and metadata Hints, for example conveying the caption of a remote picture enables this to be displayed without loading the picture itself. However, providing Hints in a "flat" list without their parent wrapper element could cause ambiguities, so the inclusion of NewsML-G2 properties at the Extension Point must use the following rules:
-
Any immediate child element from <itemMeta>, <contentMeta> or <concept> may be added directly as a Hint and Extension Point without its parent element;
-
All other elements MUST be wrapped by their parent element(s), excluding the root element.
-
When inserting properties from a target NewsML-G2 resource as processing Hints, the properties do NOT have to be extracted directly from the target resource, but they MUST be consistent with the structure of the target resource.
|
The implementation of the metadata Hints was updated in version 2.23 onwards by the adoption of a schema with globalised properties. See Hints and Extension Points in NewsML-G2 |
26.13.3. Hop History
Add a machine-readable transaction log an Item. See Transaction History
26.13.4. Concept Reference
Enable Event Concepts to be referenced within NewsML-G2 Packages. See Packages and Events in NewsML-G2
26.13.5. Extend News Message Header
Enable News Messages to express more semantically-rich properties using QCode values. See News Message Header <header>
26.13.6. Hash value
Enable the receiver of a NewsML-G2 Item to determine whether the content has been altered. See Hash Value <hash>
26.13.7. Extend Icon attributes
Add properties of <icon> to enable a basis for choice when multiple icons for content are available. See Content Metadata <contentMeta> in the Video chapter.
26.13.8. Video Frame Rate datatype
Change the datatype of the Video Frame Rate attribute of the News Content Characteristics group from XML Positive Integer to XML Decimal, so that drop-frame frame rates (e.g. 29.97) can be expressed. See Video Framerate
26.13.9. Add video scaling attribute
Add an attribute to the News Content Characteristics group to indicate how the original content was scaled to fit the aspect ratio of a rendition. See Video Scaling
26.13.10. Colour v B/W image and video
Add an attribute to the News Content Characteristics group to indicate whether the content is colour or black-and-white. See Colour Indicator
26.13.11. Indicating HD/SD content
Add an attribute to the News Content Characteristics group to indicate whether the content is HD or SD (a non-technical "branded" description of the video content). See Video Definition
26.13.12. Content Warning Best Practice
Add Best Practice for expressing a warning about content and for adding refinements to the warning. Content Warning
26.13.13. Expressing updates and corrections
Best Practice and structures for expressing that a previous Item has been updated or corrected by the received version. Processing Updates and Corrections
The changes below were covered by Guidelines revision 3 and earlier:
News Architecture (NAR) v1.7 v1.8 ~~~~~~~~~~~
26.13.14. Redesign planning information: the Planning Item
A new Planning Item is added to the set of NewsML-G2 items for the purpose of providing information about planned coverage and distributed deliverables independently of the definition of an event.
All NewsML-G2 Items, including News Items, get an element added under item metadata to reference to Planning Items under which control this item was created and distributed.
This feature is fully documented in Editorial Planning – the Planning Item
26.13.15. Add a @significance attribute to the <bit> elements of a <bag>
This attribute is assigned to a special use case of a bag with subject properties: the bag includes one bit representing an event and one or more other bits representing entities which are related to this event. Only in this case the significance attribute may be used to express the significance of this event to the concept of the bit carrying this attribute.
See Using @significance with <bag> for a use case and sample code.
26.13.16. Persistent values of @id
A new attribute is added to the Link1Type of property (PCL) that meets the requirement in some circumstances for an @id to be persistent throughout the lifetime of a NewsML-G2 Item.
For example, the new generic <deliverableOf> element of all Items points to a specific <newsCoverage> element of a Planning Item. It is required to make the value persistent over time and versions in order to assure consistency in pointing to the same <newsCoverage> element in different versions of an Item
The change also enables all elements of the Link1Type to point to specific renditions within a News Item, by making the @ids of <inlineXML>, <inlineData> and <remoteContent> persistent in the same way.
26.13.17. Changes to @literal
Implementers commented that the definition on the use of @literal identifiers in some properties was too strict and did not take account of some use cases, specifically:
-
literal values could be defined in a provider’s controlled vocabulary which is defined by other means than NewsML-G2
-
the absence of @qcode or <bag> should not mandate the use of a @literal.
Therefore some statements about the use of @literal have been redefined and some more precise statements added to avoid ambiguity.
All statements on the literal value in NewsML-G2 documents should comply with these rules and guidelines:
-
If a literal value is not used with an assert property then it is not required that all instances of that literal value in that item identify the same concept.
-
If a literal value is used with an assert property then all instances of that literal value in that item must identify the same concept.
-
If a <bag> is used with a property then @qcode and @literal attributes must not be used with the property.
-
If a <bag> is not used with a property then the property may have a @qcode attribute or a @literal attribute or neither.
Literals may be used as in the following cases:
-
When a code from a vocabulary which is known to the provider and the recipient is used without a reference to the vocabulary. The details of the vocabulary are, in this case, communicated outside of NewsML-G2. Such a contract could express that a specific vocabulary of literals is used with a specific property.
-
When importing metadata the values of literals may contain codes which have not yet been checked to be from an identified vocabulary.
-
As an identifier for linking with an assert element. In this case the value could be a random one. If a literal value is used with an assert property then all instances of that literal value in that item must identify the same concept.
26.13.18. Deprecate <facet>, extend <related>
The <facet> and <related> properties describe the relationship between two concepts, with <facet> describing an "intrinsic" property of a concept. In practice, it was found that no clear distinction between the use of <facet> and <related> could be made.
It was therefore decided to simplify the standard by deprecating <facet> and using only <related>, which has also been extended to express arbitrary values as well as content relationships.
The new features of <related> are documented in Relationships between Concepts
26.13.19. Extend <contentMeta> for Concept Items and Knowledge Items
This change creates a group of core descriptive metadata properties for NewsML-G2 items that are available for use with the Planning Item, Concept Item and Knowledge Item.
This makes the Descriptive Metadata Core Group under <contentMeta> consistent across the Planning Item, Concept Item and Knowledge Item. In NAR versions prior to 1.8, the Concept Item has no Descriptive Metadata and the Knowledge Item has a more limited set. The properties are set out below:
Descriptive Metadata Core Group
| Title | Name | Cardinality |
|---|---|---|
Language |
language |
0..unbounded |
Keyword |
keyword |
0..unbounded |
Subject |
subject |
0..unbounded |
Slugline |
slugline |
0..unbounded |
Headline |
headline |
0..unbounded |
Description |
description |
0..unbounded |
26.13.20. Add concept details to make them more consistent across concept types
This change aims at applying a consistent design to the details of the different concept types: all should have a date when it was created and one when it ceased to exist.
-
Add a <founded> and a <dissolved> property to <geoAreaDetails>.
-
Add a <ceasedToExist> property to <objectDetails>.
-
Add a <created> and a <ceasedToExist> property to <POIDetails>.
26.16. News Architecture (NAR) v1.6 v1.7
26.16.1. Move <partMeta> from NewsML-G2 to NAR and extend it
NAR 1.6 moves <partMeta> from being a "NewsML-G2 only" element to inclusion in the overall News Architecture framework so that it is available to be used by all Items in addition to the News Item, specifically Package Items and Knowledge Items, including EventsML-G2 Knowledge Items.
The change also extended <partMeta>, adding a @contentrefs attribute, so that it can reference any element in the content section of an item which is identified by @id. For a News Item, these are the child elements of <contentSet>; for the Package Item, the child elements of <groupSet>; and for the Knowledge Item, the child elements of <conceptSet>.
Accompanying this change, the structure of <concept> was also modified to include an optional @id property, enabling it to be referenced from a <partMeta> element of a Knowledge Item.
A use case for this feature is documented in Handling Updates to Knowledge Items using @modified
26.16.2. Extended Rights Information <rightsInfo>
The <rightsInfo> wrapper is extended to enable providers to differentiate between the rights to content and the rights to metadata.
This feature is fully documented, including process models, in Rights Metadata
26.19. News Architecture (NAR) v1.5 v1.6
26.19.1. Hierarchy Info element <hierarchyInfo>
The <hierarchyInfo> element was added as a child of <concept> to indicate the position of the concept in a hierarchical taxonomy tree using a sequence of QCodes indicating the ancestor concepts to the left of the target concept. The element is available at CCL and PCL.
For example, From the Media Topic NewsCodes (alias="medtop") using assumed codes: The concept "adoption" has QCode "medtop:20000781".
Its parent is the concept "family" with the QCode "medtop:20000780".
The parent of "family" is the top level concept "society" with the Qcode "medtop:14000000".
The resulting Hierarchy Info value is:
<hierarchyInfo>medtop:14000000 medtop:20000780 medtop:20000781</hierarchyInfo>26.19.2. Hint and Extension Point
The NewsML-G2 design provides for XML Extension Points, allowing elements from any other namespaces, and in some cases also from the NAR namespace, to be added to a NewsML-G2 element. These Extension Points are now termed "Hint and Extension Points".
Adding properties from the NAR namespace is a method of providing processing and metadata Hints, for example conveying the caption of a remote picture enables this to be displayed without loading the picture itself In NAR 1.5 a change allows any immediate child element from <itemMeta> or <contentMeta> to be added directly as a Hint and Extension Point without its parent element.
In NAR 1.6, this rule is amended to include the <concept> wrapper. The rule for this feature is now re-stated as follows:
-
Immediate child properties of <itemMeta>, <contentMeta> or <concept> – optionally with their descendants – may be used directly under the Hint and Extension Point.
-
All other properties require the full path excluding only the item’s root element.
All other elements MUST be wrapped by their parent element(s), excluding the root element.
Please note that the implementation of the
metadata Hints was updated in version 2.23 onwards by the adoption
of a schema with globalised properties.
See Hints and Extension Points in NewsML-G2
26.19.3. Add address details to a Point of Interest (POI)
Up to NAR 1.5 only a position expressed in latitude and longitude values is available to define the location of a POI. In NAR 1.6, a postal address is added to add flexibility to the method of giving details of a location. Note that the address of an organisation given in <contactInfo>may well be different to the actual location of the POI associated with the organisations, e.g. the New York Met location on the map is different to the postal address used for correspondence.
26.21. News Architecture (NAR) v1.4 v1.5
The following changes are inherited by NewsML-G2 2.4 and EventsML-G2 1.3
26.21.1. @rendition
The content wrappers <inlineXML>, <inlineData> and <remoteContent> may appear multiple times under <contentSet>, each having a @rendition attribute as processing Hint. For example, a picture may have three renditions: "web", "preview" and "highRes".
The avoid ambiguity, the NewsML-G2 Specification allows a specific rendition value to be used only once per News Item, i.e. there could not be two "highRes" renditions in a content set.
26.21.2. <assert>
The original intention of <assert> was to allow the details of a concept occurring multiple times within a NewsML-G2 Item to be merged into a single place. However, it was realised that <assert> could also be used to convey rich details of a concept for properties that provided only a limited set of details: name, definition and note.
However, prior to NAR 1.5, the <assert> wrapper could only identify an inline concept using @qcode., whereas a concept can be identified by both @qcode and @literal.
This limitation was removed and <assert> may have EITHER a @qcode or @literal identifier.
26.21.3. Hint and Extension Point
The NewsML-G2 design provides for XML Extension Points, allowing elements from any other namespaces, and in some cases also from the NAR namespace, to be added to a NewsML-G2 element. These Extension Points are now termed "Hint and Extension Points".
Adding properties from the NAR namespace is a method of providing processing and metadata Hints, for example conveying the caption of a remote picture enables this to be displayed without loading the picture itself. Prior to NAR 1.5, Hints extracted from a target NewsML-G2 resource could be used freely, i.e. without the need for their parent wrapper element. However, providing Hints in a "flat" list could cause ambiguities.
In NAR 1.5 the inclusion of NewsML-G2 properties at the Extension Point is according to the following rule:
-
Any immediate child element from <itemMeta> or <contentMeta> may be added directly as a Hint and Extension Point without its parent element;
-
All other elements MUST be wrapped by their parent element(s), excluding the root element.
Please note that the implementation of the
metadata Hints was updated in version 2.23 onwards by the adoption
of a schema with globalised properties.
See Hints and Extension Points in NewsML-G2
26.21.4. Scheme Code Encoding
A full processing model for Scheme URIs and QCodes was defined. See Best Practice in QCode exchange
26.21.5. Add @rendition to the icon property
The <icon> property is a child of <link> or <remoteContent> which identifies an image to be used as an iconic identifier for the target resource. If the target resource has multiple renditions, it makes sense to identify which rendition to use for the <icon>
26.21.6. Ranking Multiple Elements
Up to NAR 1.5, the elements that support a @rank attribute are:
-
<link>
-
<broader> | <narrower> | <sameAs>
-
<itemRef>
NAR 1.5 adds the ability to add @rank to the members of the Descriptive Metadata Group, allowing properties such as <language> and <headline> to be ranked by the provider according to an importance that is defined by the provider.
26.21.7. Keyword property
A specific Keyword property was added in NAR 1.5. One reason for the addition was to provide backward compatibility with standards such as IPTC7901, IIM and NITF, which provide a keyword property.
The semantics of keyword are somewhat open: some providers use keywords to denote "key" words that can be used by text-based search engines; some use "keyword" to categorise the content using mnemonics, amongst other examples.
Therefore IPTC suggests the following rules when implementing the Keyword property:
-
Assess if any existing NewsML-G2 properties align to the use of the metadata. Typical examples are:
-
Genres ("Feature", "Obituary", "Portrait", etc.)
-
Media types ("Photo", "Video", "Podcast" etc.)
-
Products/services by which the content is distributed
-
-
If the metadata expresses the subject of the content it could go into the <subject> property with the keyword string itself in a @literal attribute, but it may be better expressed if the keyword string is placed in a <name> child element of the subject with a language tag if required.
-
If migrated to <subject> property, providers should also consider:
-
Adding @type if the nature of the concept expressed by the keyword can be determined
-
Using a QCode if there is a corresponding concept in a controlled vocabulary
-
If none of the above conditions are met, then implementers should default to using the <keyword> property with a @role if possible to define the semantic of the keywords.
The contents of the Keywords field in the example shown below have blurred application: they could properly be regarded as subjects, but the provider intends that they be used as natural-language "key" words that can be used by a text-based search engine to index the content:
<keyword role="ex-krole:index">us</keyword>
<keyword role="ex-krole:index">military</keyword>
<keyword role="ex-krole:index">aviation</keyword>
<keyword role="ex-krole:index">crash</keyword>
<keyword role="ex-krole:index">fire</keyword>26.22. NewsML-G2 v2.3 v2.4
Inherits changes from NAR v1.5 plus the following changes specific to NewsML-G2 2.4
26.22.1. New dimension unit indicators for visual content
Some elements holding or referring to news content have the dimension-related attributes Image Height (@height) and Image Width (@width) which are currently defined to be the "number of pixels" of the content dimension. However, some content types require non-pixel units, such as ‘points’ for Graphics; analogue video uses different units for Image Width and Image Height.
Therefore in NewsML-G2 2.4 additional attributes have been added to define the Width Unit (@widthunit) and Height Unit (@heightunit). These attributes have QCode values, and the mandatory IPTC CV is http://cv.iptc.org/newscodes/dimensionunit/
The following table shows the default dimension units per visual content type:
| Content Type | Height Unit (default) | Width Unit (default) |
|---|---|---|
Picture |
pixels |
pixels |
Graphic: Still / Animated |
points |
points |
Video (Analog) |
lines |
pixels |
Video (Digital) |
pixels |
pixels |
The following example uses the implied default dimension unit of pixels for a still image:
<remoteContent
residref="tag:reuters.com,0000:binary_BTRE4A31LE800-THUMBNAIL"
rendition="rnd:thumbnail"
contenttype="image/jpeg"
format="frmt:JPEG_Baseline"
width="100"
height="100"
/>The following example uses explicit dimension units:
<remoteContent
residref="tag:reuters.com,0000:binary_BTRE37913MM00-THUMBNAIL"
rendition="rnd:thumbnail"
contenttype="image/gif"
format="frmt:GIF87a"
width="100" widthunit="dimensionunit:points"
height="100" heightunit="dimensionunit:points"
/>26.24. News Architecture (NAR) 1.3 1.4
The following changes are inherited by NewsML-G2 2.3 and EventsML-G2 1.2
26.24.1. Revised Embargo
An embargo can now have an undefined date and time. See Embargo
26.24.2. New Remote Info element
The <remoteInfo> wrapper is a child of <concept>. It complements the <link> child of <itemMeta> in allowing the creation of links to supplementary resources. Remote Info was added to <concept> so that this information is held within the <concept> structure and therefore retained if the Concept is extracted from the Concept Item and conveyed in a Knowledge Item. See Relationships between Concepts
26.25. NewsML-G2 v2.2 v2.3
Inherits the changes from NAR 1.4. plus the following changes specific to NewsML-G2 2.3
26.25.1. Add <role> to partMeta.
This is in order to indicate the role that part of the content identified by the parent <partMeta> has within the overall content stream. (e.g. "sting". "slate")
26.25.2. Revised Time Delimiter
The <timeDelim> property provides information about the start and end timestamps for parts of streamed content. The @timeunit attribute identifies the units used for the timestamps, defined by the mandatory IPTC Scheme whose URI is http://cv.iptc.org/newscodes/timeunit/ . In NewsML-G2 2.3, new values were added to the Scheme to cater for additional business requirements that were identified by members.
See Timing metadata
26.25.3. Revised @duration property and new @durationunit
The duration property was defined as the duration in seconds of audio-visual content, but in practice is was found that sub-second precision for measuring time duration was required. The revised definition expresses the duration in the time unit indicated by the new @durationunit.
The duration unit attribute uses the integer value time units of the recommended IPTC Scheme (URI: http://cv.iptc.org/newcodes/timeunit/), e.g. seconds, frames, milliseconds, defaulting to seconds if omitted.
See Duration
26.27. SportsML-G2 v2.0 v2.1
A number of detailed changes were made to the "plug-in" schemas for individual sports, such as Ice Hockey, Basketball, Tennis and Baseball. Details of these can be found at: http://www.iptc.org/std/SportsML/2.1/documentation/sportsml-2.1-changes-additions.html
A new Tournament Structure was added that will allow implementers to precisely express the Format, Group Stage and Standings of tournaments such as the 2010 FIFA World Cup.
A structure for Series Scores and Results enables the status of a playoff or tournament series to be expressed. Details of the new Tournament Structure are documented at: http://www.iptc.org/std/SportsML/2.1/documentation/tournament-structure.html.
Additional Resources
On the Web
The IPTC web site www.iptc.org has a wealth of resources for implementers. The page www.iptc.org/standards summarises all of the IPTC’s standards and provides links to further resources for each, including NewsML-G2, SportsML-G2 and RightsML.
There are also user groups at Groups.io for all those seeking answers to questions about the NewsML-G2 Standards, and for those who would like to participate in development work:
-
https://groups.io/g/iptc-newsml-g2/ is the public group for NewsML-G2 and Events in NewsML-G2 topics.
-
https://groups.io/g/iptc-sportsml/ is the public group for SportsML-G2. There is also a GitHub repository for SportsML-G2 development at https://github.com/iptc/sportsml-3.
-
https://groups.io/g/iptc-news-architecture-dev/ is the developer group for NewsML-G2 which is open to IPTC members only, see below.
-
https://groups.io/g/iptc-sportsml-dev/ is the developer group for SportsML-G2 which is open to IPTC members only, see below.
Join the IPTC
The IPTC welcomes new members. Membership is the backbone of the IPTC, and levels vary for both organizations and individuals. Additionally, several "working parties" and "working groups" focus on specific topic areas and standards. IPTC also hosts two face-to-face meetings a year around the globe, where its working parties discuss and develop their ideas to support information exchange and the rapid innovation of media.
To find out more, visit www.iptc.org/participate