NewsML-G2 2.27 Specification

To be answered: How to apply rightsInfo elements referencing only a part of a NewsML-G2 Item?

To be answered: To which markup does this specific rightsInfo apply?

To be answered: For a specific element, which rightsInfo is applicable?

Management metadata is bound to the Item as a whole and reflects its processing in a professional workflow.

The order of the properties in this set is imposed by the W3C XML Schema.

Table 1. Item Management Group Elements

The IPTC provides a mandatory standardised scheme applicable to the itemClass property of a newsItem, identified by the URI http://cv.iptc.org/newscodes/ninature/.

Each provider may add a set of metadata properties which have to be defined in a non-IPTC-G2 namespace. See also XML Namespaces and Extension Points in XML.

The IPTC makes these values normative for the exchange of Items between a provider and its customers:

Embargoes are managed by the embargoed property. At the level of the data model the embargoed element could be linked now to an edNote element if the existing embargoed is empty (<embargoed />).

Details are described in the Processing model below.

State Transition Diagram

This depicts the state transition diagram reflecting the ways in which the pubStatus values are intended to be used. Thus, upon creation of an Item, allowed statuses are usable and withheld. It is possible to withhold a usable document; it is possible to release a withheld document; it is possible to cancel a usable or withheld document. Once an Item has had its status set to canceled, it has reached a final state.

Figure 1. State Transition Diagram

The use of Withheld or Canceled indicates that parts of the previous version of the Item were not correct (and 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.

Here is the processing model on the recipient side and relies on the pubStatus and embargoed properties:

Table 2. Test pubStatus = Usable

If the value provided by any date/time field does not conform to the appropriate syntax (e.g. format “YYYY-MM-DDTHH:MM:SS[+-]HH:MM:SS”) it MUST be considered as being not existent.

In the case of the mandatory versionCreated property the full Item MUST be considered as being void.

An Update is expressed by using the concept URI http://cv.iptc.org/newscodes/signal/update (as QCode with the recommended scheme alias: sig:update) as value of the signal property under the Item Meta of an Item. This signal indicates that some part of the item has been updated. This implies that this version of the item is not the inital version.

A Correction is expressed by using the concept URI http://cv.iptc.org/newscodes/signal/correction (as QCode with the recommended scheme alias: sig:correction) as value of the signal property under the Item Meta of an Item. This signal indicates that some part of the item has been corrected. This implies that this version of the item is not the inital version. This Correction signal does not indicate in which version(s) of the item the corrected error existed.

In addition a concept from the Severity NewsCodes (http://cv.iptc.org/newscodes/severity/) may be used as a refinement of how severe the impact of this update or change is. The IPTC acknowledges that the rules for applying the severity are set by the news provider of the item.

Further the Editorial Note (edNote) property under Item Meta may be used to provide details about the update or correction like pointing at a name in the text which has been corrected of if paragraph with updated information has been added to the text.

A Content Warning is expressed by using a QCode for the concept URI http://cv.iptc.org/newscodes/signal/cwarn with the signal property. (With the recommended alias the QCode is “sig:cwarn”.) This signal indicates that the content of the item should be reviewed as it may be perceived as being offensive.

In addition, refinement of the reason(s) for the content warning MAY be expressed by using concept(s) from the Content Warning NewsCodes http://cv.iptc.org/newscodes/contentwarning/ with the exclAudience property.

Examples:

This is a set of properties associated with the administrative facet of content, i.e. data that cannot be inferred from “consuming” (reading, listening to, watching) the content.

All properties are optional. The order of the properties in this set is flexible: the non-repeatable properties MUST come first and then the repeatable properties may be inserted in any order.

Table 3. Administrative Metadata Group Elements

This is a set of properties associated with the descriptive facet of news content, i.e. data that can be inferred from “consuming” (reading, listening to, watching) the news.

All properties are optional, repeatable and may be inserted in any order.

Table 4. Descriptive Metadata Group Elements

Each provider may add a set of metadata properties which have to be defined in a non-IPTC-G2 namespace. See also XML Namespaces and Extension Points in XML.

It is recommended that time and durations are expressed in “Edit Units” (editUnit), which represent the smallest editable portion of content, i.e. a video frame or an audio sample.

\$Edit Unit = 1 div(Edit Rate)\$.

For video, the Edit Rate is the Frame Rate (frames per second). For audio, the Edit Rate is the Sample Rate (Hz).

The use of Edit Unit is independent of the mode of representation of time (e.g. timecode) in editing devices. The timecode associates one value to each video frame or audio sample.

For video, the usual timecode format is HH:MM:SS:FF (Hours:Minutes:Seconds:Frames).

In the case of simple frame rates (e.g. 25 fps, 30 fps, 50 fps or 60 fps), the conversion of a number of EditUnits to timecode is simple.

However, there exist other frame rates (e.g. 29.97 fps, 59.94fps) for which this calculation requires more attention. A precise calculation would consist of replacing e.g. 29.97 fps by its exact value 1.001/30 fps and multiplying the number of Edit Units by 1.001 before conversion on the basis of 30 fps. Another method consists of calculating the timecode using the drop frame method defined in SMPTE 12M. The drop frame method is an approximation based e.g. on 29.97 fps (1.001001001/30 fps). The drop frame timecode is not systematically used, particularly if content is of a short duration with insignificant drift with the actual clock time. SMPTE 12M will evolve as it doesn’t address higher frame rates with progressive scanning.

For audio, the usual video timecode (HH:MM:SS:FF) is used if the content also contains video. A time restricted timecode (HH:MM:SS) is often used for audio only content.

The time reference will be the one of reception or edition in the production system, which should be able to locate content in time based on the number of Edit Units.

The format of the Start Timestamp (start) and/or End Timestamp (end) is implied by the associated Time Unit type (timeunit), see the Time Delimiter element timeDelim.

Table 5 defines the processing of values of the three related attributes but be aware: they are required by the XML Schema but may either show invalid values or be empty.

Table 5. Time Unit Type and Start/End Value Processing

newsContentCharacteristics are the physical properties of media content like the height and width of a picture, the word count of a news story or the duration of an audio clip, that help in making selections among different renditions of the same logical news content.

The characteristics defined by the IPTC are a small and typical set of properties. Individual providers may add more characteristics they consider reasonable, i.e. audio data for professional broadcasting may require a different set from audio content for a podcast.

Some binary streams support the notion of channel or track: for example DVDs are MPEG-2 encoded and provide several audio tracks in different languages. It may be important to indicate media characteristics on a per-channel level.

A repeatable channel {News Item}] element MAY therefore be defined as a child of a remoteContent element.

Each logical channel MAY have a local identifier (chnid), an indication of the media type of the data conveyed by the channel and an indication of the role the data plays in the scope of the full content, for example “voice over”.

Each logical channel MAY be additionally described by the news content characteristics corresponding to the media conveyed in the channel.

EventsML-G2 is:

EventsML-G2 may express facts and information about events by concepts identified either by literal text (free text) or by codes from controlled vocabularies.

EventsML-G2 provides flexible date types:

EventsML-G2 reuses building blocks from the common NewsML-G2 Architecture allowing for the reuse of software components, making implementation cheaper.

EventsML-G2 makes use of industry standards: allows processing with standard tools. The EventsML-G2 syntax is built on XML, the Extensible Markup Language of the W3C; furthermore, EventsML-G2 makes use of W3C XML Schema and complies with the basic notion of the Semantic Web, the Resource Description Framework (RDF). This allows an easy transfer of EventsML-G2 structures to other XML-based standards and the integration of information about an event into the Semantic Web.

An event is “something that happens” by definition. For the news industry, it is “something that happens and is subject to news coverage.” All the events in a day make up a “daybook”, which can be a marketable product sold to clients or simply an internal daybook used by editors to organise their work.

An event is planned or unplanned, with breaking news capable of overshadowing everything on the schedule.

Automated systems need to store and exchange information about news events. This is currently done in an ad-hoc manner, leading to overly-specialized formats and incompatible data exchange. From that the IPTC learned that the industry would benefit from an event information interchange standard. Such a standard would facilitate the efficient exchange of event information, and the creation of better tools to support event management.

The event information describes a particular event in detail. This includes the “who”, “what”, “when”, and “where” information for the event along with identification and publication (news management) information. The event information also includes facilities for relating events to each other and relating news items (both complete and incomplete) to the event information.

The old-style coverage information describes the plan of news coverage for this event but it is highly recommended to adopt the new-style Planning Item.

The data model for EventsML-G2 has to cover two different facets of event information which relate to a basic distinction made for all G2 standards:

The most important thing to note about the EventsML-G2 data model is that the core structures holding information about an event are identical for both the content plugged into a News Item and the extension of a Concept Item. Hence it is very easy to build a single EventsML-G2 processor for topical and persisting information about an event.

Persisting knowledge about an Event is represented as a Concept (see *Representing Concept Information - concept Component)

As with all other concepts a single Event Concept can be managed by a Concept Item, see (Managing Individual Concepts - conceptItem), and subsequently many Event Concepts by a Knowledge Item, see (Managing Sets of Concepts - knowledgeItem).

Any Concept Item or Knowledge Item provides a group of generic definitions and a set of details specific to a kind of concept, in this case specific to an event.

Event concepts use the generic part of a concept in order to define:

In Event Concept Items the value of the type of a concept (conceptItem/concept/type) must be set to the concept URI of http://cv.iptc.org/newscodes/cpnature/event which may translate to a QCode of cpnat:event.

Figure 2. Event Information in a concept element

The event specific details are expressed by an eventDetails structure plugged into the “concept” of a Concept Item or a Knowledge Item. The eventDetails used there are completely identical to the structure with the same name used for the “event” element in the content set of a News Item.

The Concept Identifier of an event can be used by other items (e.g. News Items or Concept Items) to reference this event. From a purely technical view this Concept Identifier can be used as the value of any property referring to a concept. At a semantic level is is required that the semantics of this property permits the expression of an event as a concept – for example NOT a property that is limited to persons or locations by its semantics.

Examples are:

Knowledge Items with event concepts should be used to distribute event information if this information is planned to be updated as this requires an identifier for each event.

A provider could think of this use case scenario: a "top events of the next weekend" Knowledge Item is circulated with event concepts on Monday. On Wednesday, a new version of this Knowledge Item is sent with updated events, and cancelled events removed.

Topical event information may be conveyed by using the NewsML-G2 NewsItem see (Representing News newsItem). The structure of a NewsItem defines a special node where content plug-ins can be attached: the inlineXML element.

For EventsML-G2 an events element is added as a child of inlineXML as a wrapper of one-to-many event elements, each representing the topical information of a single event.

Figure 3. Event Information in a News Item

The event element wraps a group of more generic descriptions and a couple of details about an event. The first group is made of a short name which can be displayed as a one-liner, a more comprehensive definition of the event and a note with supplemental information.

A sibling to this generic group is eventsDetails, which wraps all the details of the event, when and where it happens, who is involved and how to get there.

Finally optional information about the planned news coverage of this Item may be added.

contactInfo is repeatable in the definition of a person, an organisation and a Point of Interest, and each set of properties supports a role attribute which makes it possible to group together all information belonging of the same nature.

Contact information includes email addresses, instant messaging addresses (im), international phone numbers, international fax numbers, web addresses, postal addresses and notes. These are qualified by a role attribute which specifies the nature of the address, e.g. home or work.

The definition of a Postal Address (address) includes repeatable free-text line (in the format expected by a recipient postal service), the indication of a locality (such as city, town, village, and so on), a subdivision of a country (area), a country and a postal code (postalCode).

A postal address is structured as a set of properties likely edited and displayed as a form. The relative order of its properties is not universal, and if used for traditional postal mail, presentation algorithms are to be developed which depend on the source and recipient countries.

The city, country area and country may be indicated as a name or as a controlled value. The use of an ISO compliant country code is recommended.

Each concept has its globally unique concept identifier, a conceptId which is part of the concept structure and defined by the authority of the scheme.

Additionally, a conceptItem has its globally unique identifier (guid) attribute which is assigned by a system managing G2 items.

Be aware that these two identifiers must not be mixed up, all references to a concept MUST use the concept identifier and not the guid of the conceptItem.

The IPTC provides a mandatory standardised scheme applicable to the itemClass property, identified by the URI: http://cv.iptc.org/newscodes/cinature/.

The set of administrative metadata is common to all classes of Items.

The set of descriptive metadata for a Concept Item is listed below. All properties are optional, repeatable and may be inserted in any order.

Table 8. Descriptive Metadata Core Group Elements

Each provider may add a set of metadata properties which have to be defined in a non-IPTC-G2 namespace. See also XML Namespaces and Extension Points in XML.

Please review News Content Metadata of the News Item chapter for more information.

The conceptItem includes three properties which are available to help make metadata assertions:

The IPTC provides a mandatory standardised scheme applicable to the itemClass property, identified by the URI http://cv.iptc.org/newscodes/cinature/.

Metadata about the whole set of concepts held by a Knowledge Item are wrapped by the contentMeta element.

Metadata about specific concepts held by a Knowledge Item are wrapped by one to many partMeta elements. A typical use case of partMeta is to indicate when several concepts were modified at the same time, by associating those concepts with a specific partMeta which has the associated contentModified property.

The set of administrative metadata is common to all classes of Items.

The set of descriptive metadata for a Knowledge Item is listed below. All properties are optional, repeatable and may be inserted in any order.

Table 9. Descriptive Metadata Core Group Elements

Each provider may add a set of metadata properties which have to be defined in a non-IPTC-G2 namespace. See also XML Namespaces and Extension Points in XML.

Please review News Content Metadata of the News Item chapter for more information.

The knowledgeItem includes three properties which are available to help make metadata assertions:

A conceptSet wrapper element contains a set of concept components (see Concept Component). Their order of appearance in conceptSet is not relevant.

The IPTC provides mandatory standardised schemes applicable to the itemClass property of a packageItem, identified by the URI http://cv.iptc.org/newscodes/ninature/ and http://cv.iptc.org/newscodes/cinature/.

The set of administrative and descriptive metadata is common between packageItems and newsItems. Please review News Content Metadata of the News Item chapter for more information.

The packageItem includes three properties which are available to help make metadata assertions:

A groupSet represents a tree of components, a component can be:

All G2 items included into a package are included by reference, as physical inclusion would break the capability to manage inner Items independently of the outer Package Item.

The groupSet is optional. This allows for a lightweight and progressive representation of information.

There MUST be at least one group element in the groupSet but there could also be many of them. In any case the value of root attribute of the groupSet element MUST be the id attribute value of the group acting as a root.

A group component may contain references to other group components (using a groupRef element with its idref attribute) of the same package item and/or references to Items or Web resource (using the itemRef element with its guidref and href attributes), in any order.

Each group MUST have an id attribute which identifies this group, and each group MUST have a role attribute which indicates the part this group plays within its container.

The order of the sub-groups and references to Items MAY be significant; a mode attribute indicates whether the elements in the group are complementary and unordered, complementary and ordered or a set of alternative elements. In the absence of a mode attribute the group is treated as complementary and unordered implementing the mode “bag”.

The itemRef element MAY contain metadata extracted from the target Item or Web resource. The recipient MUST NOT consider that such hints constitute a complete representation of the Item.

The itemRef element MAY have a rank attribute which represents the rank of the Item among other Items in each group.

The itemRef element MAY also have time validity attributes (validfrom and validto) which express the date and time between which the reference is active.

Other attributes are available, please see the schema documentation for a complete list and details. The following is an example of groupSet:

The IPTC provides a mandatory standardised scheme applicable to the itemClass property of a planningItem, identified by the URI http://cv.iptc.org/newscodes/plinature/.

The set of administrative metadata is common to all classes of Items.

The set of descriptive metadata is listed below. All properties are optional, repeatable and may be inserted in any order.

Table 10. Descriptive Metadata Core Group Elements

Each provider may add a set of metadata properties which have to be defined in a non-IPTC-G2 namespace. See also XML Namespaces and Extension Points in XML.

Please review News Content Metadata of the News Item chapter for more information.

The planningItem includes three properties which are available to help make metadata assertions:

A newsCoverageSet wrapper element contains a set of newsCoverage components (see below). Their order of appearance in conceptSet is not relevant. The major reason for having multiple newsCoverage components in this set is that each newsCoverage may be bound, for example, to a specific itemClass. Thus, to express the coverage of an event by two text stories, 10 photos and one graphic, one would used three newsCoverage components.

The newsCoverage {Planning} component holds the mandatory planning property and the optional delivery property.

At least one planning property must be present; this wrapper provides a rich set of properties to inform the receiver what kind of coverage to expect from the provider:

The g2contentType and the itemClass properties tell what type of G2 deliverables to expect, and the itemCount adds how many of them to expect. The properties scheduled and service add when and by which service, or feed, the coverage will be delivered. A group of Descriptive Metadata gives a hint for the metadata which will be used with the delivered Items, allowing the receiver to build a filter or to forward this planning information to the proper editorial destination. The assignedTo property holds the person, organisation or company responsible for the content; this property can be used internally by the news provider or may be used to let receivers know that, for example, a particular named journalist will write a review of a cultural event. For information that cannot be expressed by these machine readable properties, the natural language edNote property may be used.

The delivery property specifies which Items of the planned coverage have been delivered, using a set of deliveredItemRef properties.

It can be expected that Planning Items will have a high frequency of updates. The first version may be sent when the first outline of covering an event or a topic has been completed by the editorial of the news provider. Updates could and should be sent when types of planned G2 Items is extended, for example when text only coverage is planned, later extended to text plus photos. Updates should also be sent when the number of planned Items changes or when typical metadata values for the Items are assigned. In the course of creating and delivering the Items the Planning Item should be updated each time an Item, or group of items, is released.

Concatenate the Scheme Alias, a colon and the Code to form a QCode.

Concatenate the Scheme URI and the Code to obtain the Concept URI.

If provided Concept URIs are IRIs per RFC 3987 then they must be compared for equivalence as defined per RFC 3987, section 5.

If provided Concept URIs are URIs per RFC 3986 then they must be compared for equivalence as defined per RFC 3986, section 6.

A catalog MUST have one or more scheme elements. A catalog MAY have one or more titles in different languages. It MAY also have a pointer to some additional information available on the Web, and especially its evolution by identifiers of a web location from where it can be retrieved, an identifier of the catalog and the version, and an identifier of the authority which manages this catalog. Such information will help people follow the evolution of a shared catalog like the IPTC G2 catalog, and include in their Items a reference to the latest version if they wish. A catalog may be managed by a provider by using a Catalog Item (available only at PCL) see Managing Catalogs - catalogItem.

The mandatory scheme element MUST have a scheme alias attribute and a corresponding scheme uri attribute. It MAY have a name, a definition and a note element to provide human readable information about the scheme. And the authority governing the scheme MAY be indicated by the authority attribute. A sameAsScheme element MAY be used by applying a URI which identifies another scheme with concepts that use the same codes and are semantically equivalent to the concept of this scheme.

Each instance of an Item defines its own set of scheme definitions, and there is no interaction between scheme definitions in different Items. Scheme alias declarations are local to the Item in which they appear and cannot be overridden in a given Item.

By activating the hyperlink of a remoteCatalog using catalogRef, a plain catalog structure is returned, and MUST be processed as if were locally defined.

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.

As the IPTC Catalog is required for NewsML-G2 processing because it enables the resolution of mandatory properties such as pubstatus, it MUST be retrieved and cached (or otherwise stored locally) by the processor. Each version of the IPTC Catalog (catalog.IPTC-G2-Standards_nn.xml) may be retained in the cache indefinitely as its contents will never change. It is best practice to retain a local copy of the Catalog indefinitely in order to continue operations should the remote Catalog be unavailable.

When a processor opens an Item, it MUST check the URL(s) of the catalog(s) found in its header. If a catalog has not been previously retrieved, the processor MUST fetch it, check it, and store its content in cache/local storage.

Different remote catalogs MAY define different mappings for a given scheme alias. An entry in a remote catalog cache is therefore a triple \{remote catalog URL, scheme alias, scheme URI}.

It is OK for one scheme URI to have two aliases. It is an error if one alias is mapped to two different URIs in the scope of a single Item (an issue called alias collision). Note that this error may arise within a catalog, as well as across a set of catalogs (local or remote) declared in a given Item.

Before processing an Item, a processor MUST check its catalogs. If an alias collision is found, the processor MUST reject the Item as it can lead to misinterpretation of the information.

Schemes evolve: terms are added, names are changed, terms are retired. An authority will release a new version after each update. A provider may not want to adopt the latest version of a scheme. The scheme URI MUST be stable as long as the evolution does not break backward compatibility rules.

Here we are interested in schemes defined as an explicit list of terms. Schemes defined via an algorithm are out of scope of this section. A scheme definition is defined as the finite set of terms composing a scheme. A scheme definition MAY be a subset of an original scheme, for example maintained by an external authority.

A provider SHOULD make a scheme definition available for its users for operational use as the content of a knowledgeItem, where each term is represented as a concept component, i.e. a concept identifier, a list of names in one or more languages, plus additional properties of the concept (all but the identifier being optional).

An authority MAY provide different variants of a scheme definition, e.g. a list of codes, a list of codes plus a name in a specific language, a list of codes plus names in all available languages.

For each variant of a scheme definition, the URL of the corresponding knowledgeItem SHOULD be available using e.g. content negotiation.

Selection from among the renditions MAY be performed automatically (if the processor is capable of doing so) or manually by the user selecting from a hypertext menu.

In a professional and collaborative news workflow, it makes sense to identify all elements defined by the model in order to later act on them individually. Also, metadata is not always entered by one person at one time, but may be entered by different people, organisations or systems at different time. Therefore it may be needed to keep track of who is assigned the editing of specific properties, and when and by whom a property has been given a value.

For this purpose, all metadata properties share the Common Power Attributes Group, which includes an optional local identifier (id) and the optional indication of the creator and the date (and, optionally, the time) when the property was last modified. (Beyond that the group includes more attributes for other purposes.)

The IPTC provides a mandatory standardised scheme applicable to the itemClass property of a catalogItem, identified by the URI http://cv.iptc.org/newscodes/catinature/.

The set of metadata related to the catalog content is listed below. All properties are optional. The order of the properties in this set is flexible: the non-repeatable properties MUST come first and then the repeatable properties may be inserted in any order.

Table 11. Content Metadata Elements

Each provider may add a set of metadata properties which have to be defined in a non-IPTC-G2 namespace. See also XML Namespaces and Extension Points in XML.

A Catalog Item includes a mandatory catalogContainer element which contains a single mandatory catalog element as the content of the Item.

Table 12. XML Namespace

Table 13. IANA Media Types (so called MIME Types)

All these Media Types are registered with IANA, see http://www.iana.org/assignments/media-types/

For attributes: each element of a G2-Standard allows to add provider specific attributes from any other XML namespace than the News Architecture for G2 namespace.

For elements: Some elements which have child elements allow to add provider specific elements from any namespace other than the News Architecture for G2 namespace. A few elements allow adding any element from any XML namespace including the News Architecture for G2 namespace but this is a special case only, see below.

To act as an Extension Point, properties from any other XML namespace than the News Architecture (NAR) namespace may be added.

To act as a Hint Point, properties from the NAR namespace may be added.

The purpose of properties from the NAR namespace is to add a set of hints, i.e. properties which have to comply with the structure of the NewsML-G2 Item target resource but do not have to be extracted from it. These properties must be added this way:

User Note: This property answers to a legal issue. In some countries (e.g. Germany, Sweden) it is needed to designate a person accountable for any legal issue related to the published content. The full translation from the German term is: accountable person in terms of the press law (For reference in German: Verantwortlich im Sinne des Presserechts -acronym = ViSdP), in Swedish it is called “Ansvarig utgivare”. In practice today, a news provider may send out a message each day which indicates the "accountable person". This may work for traditional feed services, but fails with profiled services (content selections) which filter such messages. The solution is to include this information in the Items themselves.

Recommended IPTC NewsCodes CV for the target attribute: http://cv.iptc.org/newscodes/hopactiontarget/

If there is more than one alternative identifier, they SHOULD be qualified using the type qualifier to distinguish between different identification schemes.

If there is more than one alternative locator, they SHOULD be qualified using the type attribute to distinguish between different identification schemes.

This property is particularly useful if the Item is available in different formats (for example NewsML 1, IIM or NITF) or with different levels of details (for instance with different granularity of metadata).

The assertion about the concept may be used to merge multiple occurrences of concept details in properties into a single place or to extend the details of an assertion beyond the limited details other properties can provide. Rule for @qcode and @uri in an element:

User Note: The significance attribute 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.

If the bag includes more than one event, any significance attribute of bits in the bag SHALL be ignored.

Example 1:

A merger of two companies which is differently significant to the two parties of the merger: the significance of the merger for the small company is high while it is low to the global player company.

User Note: The rank attribute of broader is suitable for use in a Knowledge Item representing a scheme. It is used when it is important that the Child Elements of a particular term are displayed in a user interface in a predefined order. For example, the major currencies could be given a rank of “1”, while all other currencies could be given a rank of “2”. Terms of the same rank are ordered alphabetically by name if this is available. If the name is not available, the terms are ordered by code value. Terms without a rank are treated as if they all have the same rank, which is higher than the rank of all other terms. The same concept may have different ranks in different concept trees. A lower rank results in a placement earlier in a display.

User Note: The by label provides a natural-language statement of the author/creator information (commonly called the byline); it may include a byline title, i.e. the author’s job title. Examples of bylines are RUPAK DE CHOWDHURI (a person), isotype.com (a provider) or STR (a stringer). It is up to the provider to decide if the label starts with a word like “By”.

User Note: A channel identifier is used to provide recipients with information for selecting, routing, or handling otherwise the content of the message. The channels represent streams in a multiplex: a message may be sent on different channels – e.g. one for text, one for pictures – and each reception point will be able to filter on channel values. The structure of this string is not specified by the IPTC.

Rule for @qcode and @uri in an element: * An element SHOULD NOT use both a @qcode and a @uri. * If both attributes, @qcode and @uri, are present the @qcode takes precedence.

User Note: The position element defines the centre of the circle.

Example:

User Note: A natural-language definition of the semantics of the concept. This definition is normative only for the scope of the use of this concept.

Recommended IPTC NewsCodes CV for the part attribute: http://cv.iptc.org/newscodes/namepart/

The confirmation element is deprecated from NewsML-G2 version 2.24 onwards and replaced by the attribute confirmationstatus (with URI sibling confirmationstatusuri), added to start, end and duration, the child elements of eventDetails/dates.

Recommended IPTC NewsCodes: http://cv.iptc.org/newscodes/eventdateconfirm/

User Note: The role attribute addresses the role of the full set of contact information with regards to the entity defined by the concept. Examples: “privateOffice” vs “companyOffice” or “GlobalHeadquarters” vs “localHeadquarterUK”.

Recommended IPTC NewsCodes for the "role" of an event’s contact information: http://cv.iptc.org/newscodes/eventcontactinforole/

A party (person or organisation) which modified or enhanced the content, preferably the name of a person.

User Note: One may specify the role the party plays in the creation of the content (e.g. a caption writer for photos) at the PCL.

Recommended IPTC NewsCodes: http://cv.iptc.org/newscodes/contentprodpartyrole/ with recommended Scheme Alias cpprole.

A party (person or organisation) which created the resource.

User Note: One may specify the role the party plays in the creation of the content (e.g. a caption writer for photos) at the PCL.

A free-text expression of the credit(s) for the content.

User Note: This property corresponds to the publisher of the Item.

The creation date of the first version of the NewsML-G2 Item expressed as a date/time value in the format “YYYY-MM-DDTHH:MM:SS[+-]HH:MM:SS”.

The use of versionCreated is mandatory. If the expressed date/time value does not follow the format “YYYY-MM-DDTHH:MM:SS[+-]HH:MM:SS” then the full NewsML-G2 Item MUST be considered void.

User Note: In the case of a photo or live footage for audio and video, this date (and time) is always the same as the date (and time) of the event covered by the content. In the case of text and any audio and video report about an event, this date (and time) can be different from the date (and time) of the event covered by the content. This date (and time) may also be different from the date (and time) of the creation of an Item holding the content.

User Note: The value of this property should be updated each time the content is modified in any manner, but should not be updated if only metadata are changed.

The date and time (with the time zone) before which all versions of the Item are embargoed. If the element is absent, the Item is not embargoed. If the element exists but is empty the end of the embargo is defined by the language in an edNote element.

User Note: May not be updated in case of retransmission of the message.

User Note: The dateline provides a natural-language statement of the date and/or place of the news content creation, to be displayed in situations where an abstract of the content is shown (case of search results) or the content is remote.

Traditionally a dateline indicates when and where news content is created, not necessarily the time and place relative to the news event.

As an example a dateline BAGHDAD, March 26, 2007 (AFP) could head a story about blast in Mosul, because the story was actually written in Baghdad. Also, by tradition a dateline will follow the stylebook of the information provider and possibly leave out certain time and location information that could be useful for specifying searches of a database. Editorial policy dictates the dateline; it is not automatically derivable from other markup (location, date, etc.). The dateline should not end with a separating character (of the kind that separates the dateline from the first sentence in a traditional wire story).

A reference to the Planning Item and to one of its newsCoverage properties under which control this item has been published.

A free-form textual description of the content of the Item. (For a Knowledge Item the content is its set of concepts as a whole.)

Recommended IPTC NewsCodes for the role attribute: http://cv.iptc.org/newscodes/descriptionrole/

User Note: In a broadcast delivery system, the destination is a group of reception points (using a provider-specific syntax, often geographically oriented). This is a way to address customers. Examples are “England”, “USA”, “Austria/Vienna”, “France/Paris/LeParisien”. The structure of this string is not specified by the IPTC.

Rule for qcode and uri in an element:

User Note: If both are present the literal and the property string value SHOULD be identical. If both are present but not identical literal takes precedence.

A note addressed to the editorial people receiving and processing the Item. If edNote is a child element to plannedCoverage this property provides additional natural language information about the planned coverage.

User Note: The values of this property are defined by each provider, and are often associated with the notion of a desk or a feed. Some examples are a “French wire service”, an “international picture service” or a “mobile news service”.

Implementation Note: This event structure is used within an events wrapper to be plugged into an inlineXML property of a News Item.

Implementation Note: This events wrapper is made to be plugged into an inlineXML property of a News Item.

The recommended file name for this Item.

Any of the NewsML-G2 specific IANA Media (MIME) Types like application/vnd.iptc.g2.*item+xml.

See: http://www.iana.org/assignments/media-types/application/

User Note: Where a role IS NOT specified, the Generator Tool applies to the most recent Item generation stage. Where a role IS specified, the Generator Tool applies to the Item generation stage identified by the role.

A nature, intellectual or journalistic form of the news content.

User Note: These properties follow the syntax used by the major geocoders on the Web. Latitudes north of the equator shall be designated by use of the plus sign (+), latitudes south of the equator shall be designated by use of the minus sign (-). The equator shall be designated by use of the plus sign (+).

Longitudes east of Greenwich shall be designated by use of the plus sign (+), longitudes west of Greenwich shall be designated by use of the minus sign (-). The Prime Meridian shall be designated by use of the plus sign (+). The 180th meridian shall be designated by use of the minus sign (-).

The altitude is given in meters. A positive integer means a position above the zero elevation, a negative value below the zero elevation. In the absence of the gpsdatum attribute, WGS84 is the default system

User Note: Group Mode: By default the group is “complementary and unordered”. The following modes are supported:

A hash value of parts of an item as defined by the hashscope attribute

User Note: The symbolsrc and symbol attributes are a pair of values which define the authority which issued a symbol and the issued symbol. The market can be defined in two ways: either by the market attribute which requires an identifier from a controlled vocabulary; or by a pair of marketlabelsrc and marketlabel values which define the authority which issued the Market Label and the issued Market Label

A brief and snappy introduction to the news content, designed to catch the reader’s attention.

User Note: Represents the position of a concept in a hierarchical taxonomy tree by a sequence of QCode tokens representing the ancestor concepts and this concept.

Example: From the Media Topic NewsCodes (alias="mtp") using assumed codes:

The concept "adoption" has QCode mtp:2788

Its parent is the concept "family" with the QCode mtp:2780

The parent of "family" is the top level concept "society" with the QCode mtp:1400

The resulting Hierarchy Info value is

User Note: The timestamp of the hop element reflects the time of forwarding the object while the timestamp of an action reflects the time of performing that individual action.

Implementation Note: For the encoding attribute at the CCL only the QCode for “base64” may be used. If the attribute does not exist, this QCode must be assumed as default. In the absence of the encoding attribute, the content must be plain text, and the content type must be set accordingly.

A frequently updated information object of which this Item is an instance.

User Note: The tech attribute indicates the provider of the service (for example Twitter, WhatsApp, and so on).

User Note: If no role is applied the information source provided some information used to create or enhance the content and played no other role. Omitting role is equivalent to applying http://cv.iptc.org/newscodes/contentprodpartyrole/originfo as the only role value.

If a party did anything other than originate information a role attribute with one or more roles must be applied. The recommended vocabulary is the IPTC Content Production Party Role NewsCodes at http://cv.iptc.org/newscodes/contentprodpartyrole/

To indicate that a party has modified or enhanced the content use the contributor property.

If an entity plays more than one role, the infoSource element has to be included multiple times, with different values of role.

Recommended IPTC NewsCodes for the role attribute: http://cv.iptc.org/newscodes/contentprodpartyrole/ with recommended Scheme Alias cpprole.

Mandatory IPTC NewsCodes for News Items or Package Items: http://cv.iptc.org/newscodes/ninature/

Mandatory IPTC NewsCodes for Concept Items, Knowledge Items or Package Items: http://cv.iptc.org/newscodes/cinature/

Mandatory IPTC NewsCodes for Catalog Items: http://cv.iptc.org/newscodes/catinature/

User Note: This property gives a hint on the nature of the Item. IPTC values for News Items correspond to the media type of the original content component, i.e. “text”, “photo”, etc. Concept Items adopt the static value concept. The class of a Package Item reflects the nature of the items it contains, i.e. either one of the values above or the value “composite” which indicates that the package handles Items of different natures. A recipient system may use this information to make a coarse selection of Items, based on their nature, without having to inspect the structure.

XML Schema Notes: To allow the validation of the structure beyond the root elements of the different items the extension point “any” for the nar XML namespace is the only child element. This allows schema based validation of the content of the Items as the validation of the extension point is set to “lax”.

User Note: This property may be used in parallel with other properties that describe content such as subject or genre, which use QCodes or literals to identify an assigned concept. Providers should define if and how the values of keyword properties contained in their Items complement, or overlap with, the values of properties such as subject or genre.

Implementation Note(s) Be aware of the lexical space restrictions for an XML Schema Normalized String type. See XML Schema specifications.

tag values must be valid BCP 47 language tags.

Recommended IPTC NewsCodes for the role attribute: http://cv.iptc.org/newscodes/languagerole/

Implementation Notes: Order of positions has to be considered, a minimum of two position elements is mandatory

User Note: They are different variants of links:

Links may allow for navigation from a newsItem to another related Item or a Web resource, and its title be displayed as supplemental information to the final user. Example: a News Item representing a section of a transcript (a “take” in the news language) may be linked to the previous and next take; an article about a person may be linked to the biography of this person.

Links may express a parent-child relationship. Example: a News Item representing an article may be linked to the article it is a translation of; a wrap-up may be linked to the previous stories used as source material for the article; a cropped picture may be linked to its source picture.

Links may express dependency on external Items which are required in order to fully present the composite content of the Item. If some target Items are not retrievable, then the recipient processor should fail gracefully. The most obvious example is a newsItem representing an illustrated article. The textual content of the News Item (usually formatted as NITF or XHTML) includes a reference to a photo which is represented by another News Item. As the NAR recipient processor is content agnostic, it cannot infer this dependency from processing the content. A dependency link from the article to the picture indicates that the recipient processor must retrieve the target newsItem before the article can be fully displayed.

Pointing at the latest version of an Item while exposing content metadata may lead to unwanted display or selection criteria if these metadata were subsequently modified; therefore only the stable content properties should be exposed in a link.

User Note: This information applies especially to news, and may also be expressed as free text in the “dateline” of a story, along with a date of content creation and the name of the content provider. The rules for determining the location are provider-dependent. The location is typically determined differently for different types of content:

Text: The practices of news providers either identify the location the content relates to or the location the content was created by a reporter or a writer. If a correspondent is resident in town A but writes about an event in town B the name of town A or B can be used. But the provider’s policy should be available as written document.

Photo: The location of origin of content is the place shown in the photo image.

Graphics The location of origin of content should be the editorial office from where this graphics are distributed.

Audio and video: In the case of raw footage the location of origin of the content should be the place of event, if people can be heard/are shown from different places the news provider can decide by its own policy, but this policy should be available as written document.

A set of Items around the same theme of which this Item is a part.

Implementation Notes: If any QCode is used within the News Message header then a catalog and/or a catalogRef element MUST be included in the header. The scope of the scheme elements of the local and/or remote catalog(s) is limited to the header element and its descendants.

Mandatory IPTC NewsCodes: http://cv.iptc.org/newscodes/dimensionunit/

Implementation Note: Be aware that in EventsML-G2 version 1.6 this element was classified as LEGACY. From that version on a standalone Planning Item is available to hold an even extended set of information about planned coverage. Its major advantage is that coverage can be planned without having to update and version Concept Items for event concepts.

User Note: A new newsCoverage property must be created for each set of planning details which contains different values. Different would be typically the g2contentType and/or the itemClass; or one or more of the descriptive metadata properties for the planned Items.

User Note: Indicating a decision of coverage:

If a specific coverage was agreed by the news provider the newsCoverageStatus value should be set to “int” (coverage intended) and at least one newsCoverage element with coverage details MUST be added to the eventDetails.

Highly recommended IPTC NewsCodes: http://cv.iptc.org/newscodes/newscoveragestatus/

User Note: This string’s structure is not specified by the IPTC.

Rule for qcode and uri attributes of an element:

Implementation Note: If both are present the literal and the property string value SHOULD be identical. If both are present but not identical literal takes precedence

Recommended IPTC NewsCodes for the role attribute: http://cv.iptc.org/newscodes/eventorganiserrole/

Recommended IPTC NewsCodes for role attribute: http://cv.iptc.org/newscodes/eventparticipantrole/

User Note: The tech attribute indicates a land-line, cellular or other service.

Implementation Note: Order of positions has to be considered, a minimum of three position elements is mandatory

User Note: A special value of the role attribute may indicate that this information is not used to make contacts but e.g. is the registered address of a company.

User Note: This address may be different from an address required to contact the Point Of Interest or the organisation running or maintaining it, that address is provided under a contactInfo element.

User Note: This property gives information about the precise structure of an Item, e.g. a simple package, article with one picture, and may be the name of the transformation stylesheet used for the generation of the Item.

Mandatory IPTC NewsCodes: http://cv.iptc.org/newscodes/pubstatusg2/

User Note: On the raters attribute:

Implementation Note: on valcalctype:

A CV for the calculation type should include: mean, median, sum, unknown

This group of properties defines the information required to specify a recurrence set. The recurrence set is the complete set of recurrence instances for a dates component. The model follows the iCalendar specification RFC2445.

Recurrence properties are optional children of dates/start or dates/end If used, at least one rDate OR rRule element MUST be present. These elements MUST come first in the group. Then the exDate and exRule elements MAY be inserted in any order.

This group includes these elements:

Recommended IPTC NewsCodes: http://cv.iptc.org/newscodes/eventregrole/

User Note: To identify the remote resource either the residref attribute or the href attribute MUST be set, optionally both MAY be used in parallel. The residref attribute identifies a managed remote resource by its globally unique identifier (if the resource has such an identifier), while the href attribute identifies the location of the remote resource in e.g. a (remote) file system. If the remote resource is managed like an Item and consequently residref is used, a version attribute MAY indicate the resource’s version; in the absence of version information, the remote resource is the latest version available.

The width and height may be specified when appropriate to the target resource, and MAY be accompaied by a dimensionunit that takes the following values, taken from an IPTC defined controlled vocabulary: lines, pixels, points (more units are defined by this CV, check the most recent version).

Mandatory IPTC NewsCodes: http://cv.iptc.org/newscodes/dimensionunit/

If dimensionunit is absent, the default units for each content type are:

User Note: This property may indicate the role of the content part in a piece of streaming media.

Examples (video): “sting”, “slate”, etc.

User Note: Among other possibilities this property may indicate the importance of the Item in a feed by concepts like “flash”, “bulletin”, “alert”, “urgent”, “newsbreak”, and so on.

Implementation Note: This implementation aligns with the Simple Ruby markup with and without parentheses of the W3C (see http://www.w3.org/TR/ruby/#simple-ruby1).

XML Schema Note: The alternative simple Ruby markup with and without parentheses is expressed by the use of either a single rt element or a single <rp> - <rt> - <rp> sequence of elements. Ruby parentheses (<rp>, empty elements) must be used as a pair: either both are present or none is present.

Implementation Note: This element SHOULD NOT be used in NewsML-G2 2.11 and higher, the element sameAsScheme should be used instead.

Implementation Note: This element replaces the sameAs element as child of a scheme element.

User Note: The structure of this string is not specified by the IPTC. Best practice is to identify a sender by its domain name.

Rule for qcode and uri attributes of an element:

Implementation Note: If both are present the literal and the property string value SHOULD be identical. If both are present but not identical literal takes precedence

User Note: This property might indicate major rewriting of the content, important correction, urgent handling etc. The processor might be required to perform specific actions, depending on the contract between the provider and the recipient. Users should be alerted of the reception of an Item containing a signal by some UI mechanism (sound or display). An editorial note (edNote) may be used to convey additional natural language information related to the processing of the content.

User Note on separator. Providers may choose to use more complex separation rules. In such a case the meaning of the separators must be conveyed by some other means.

An important topic of the content; what the content is about. For a Knowledge Item the content is the set of concepts, for an event the content is the event as such.

User Note: The time unit may take the following values, taken from an IPTC defined controlled vocabulary:

timecode: An SMPTE timecode containing a string encoded identification. Timestamp format: hh:mm:ss:ff (ff for frames).

timeCodeDropFrame: An SMPTE timecode containing a string encoded identification.

Timestamp format: hh:mm:ss:ff (ff for frames). The drop frame flag should be set.

editUnit: The editUnit is the amount of time per video frame (1s / number of frames per second) or the amount of time per audio sample (1s / number of samples per second), for which the video frame rate or audio sample rate must be known. Timestamp format: long unsigned integer.

normalPlayTime: Indicates the position relative to the beginning of the presentation. Timestamp format: hh:mm:ss.mmm (mmm for milliseconds). See also: RFC 2326.

seconds: Time given in full seconds. Timestamp format: long unsigned integer.

milliseconds: Time given in full milliseconds. Timestamp format: long unsigned integer.

Implementation Note: If a time unit IS NOT present, the value editUnit MUST be assumed. Any timestamps MUST be formatted appropriately for the time unit (as detailed above). All timestamps SHOULD be zero-padded from the left as applicable, e.g. a normalPlayTime value starting at 12 seconds would be represented as ‘00:00:12.000’.

Mandatory IPTC NewsCodes: http://cv.iptc.org/newscodes/timeunit/

A short, natural-language name for the Item.

User Note: This string’s structure is not specified by the IPTC. No two News Messages sent by the same sender on the same date may have the same identifier. In case of retransmission it is not required to update this identifier.

The editorial urgency of the content. A value of 1 corresponds to the highest urgency, a value of 9 to the lowest.

User Note: This property includes the type of usage to which the rights apply, the geographical area or areas to which specified usage rights pertain, the indication of the rights holder, restrictions on the use of the content and the time period over which the stated rights apply. If no usage terms are specified, then no specific restrictions on use of the content beyond contractual ones are being asserted.

User Note: If a start and/or end attribute exists, then the date is approximate, else it is defined precisely by the property’s date. If only the approximation start date is provided the range ends with the property value; if only the approximation end date is provided the approximation range starts with the property value.

User Note:

significance: 1 – corresponds to the highest significance.

significance: 9 – corresponds to the lowest significance.

User Note: Blocks are primarily used for notes, comments or instructions created by a news provider for use by recipient editorial teams.

User Note: Rule for qcode and uri in an element: If both attributes, qcode and uri, are present the qcode takes precedence.

User Note: The time may be expressed in Universal Time Coordinates (UTC), or in local time together with a time zone offset in hours and minutes

Included: Flex1PropType, Flex1ConceptPropType, FlexLocationPropType, FlexOrganisationPropType, FlexPartyPropType, FlexPersonPropType, FlexPropType, FlexProp2Type

User Note: Rule for qcode and uri in an element:

User note for Flex1ConceptPropType: If a mainConcept element is used by an element of Flex1ConceptPropType (subject, genre or eventDetails\subject) this indicates that the value of the property is a faceted concept. In this case a qcode or uri attribute must NOT be used, a literal attribute may be used only in the scope of this Item (for example in order to reference an assert element).

User Note: Labels are assertions expressed as natural language strings intended to be consumed by human beings. They are typically displayed alongside the content of an Item or in place of Items in a list, providing a means of selection among them.

User Note: To identify the target resource either the residref attribute or the href attribute MUST be set, optionally both MAY be used in parallel. The residref attribute identifies the target resource by its globally unique identifier (if the resource has such an identifier), while the href attribute identifies the location of the target resource in e.g. a (remote) file system. If the target resource is an Item and the residref attribute is used, a version attribute MAY indicate the target Item version; in the absence of version information, the target resource is the latest version available.

User Note: The different datatypes of the attributes of this data type correspond to iCalendar datatypes and enumerations.

Implementation Note: TruncatedDateTimePropType is used as a property datatype.

Example valid values:

YYYY-MM-DD"T"hh:mm:ss.sssTZ

YYYY-MM-DD"T"hh:mm:ssTZ

YYYY-MM-DD

YYYY-MM

YYYY

Notes:

Processing rules for the rank attribute:

Properties with a lower value of the rank attribute have a higher importance than properties with a higher value of this attribute. All properties with the same value of rank have the same importance.

All properties without a rank have the same importance, which is lower than the importance of all properties with this attribute.

If relative importance is being used to determine display order, then:

Examples (using rank with the language property):

Notes:

The table below enumerates the allowed values for the orientation attribute. The values are integers from 1 to 8 and reflect the TIFF 6.0 and Exif 2.3 specification. Orientation 1 is considered as default value.

Remark on the Definition column: by the Exif specification the "0th row" is the first row which has been scanned for the digital image and the "0th column" the first column. The hint describes how a picture of this orientation has to be flipped and/or rotated to show as the default orientation 1.

The column "Visual example" shows a picture of the character F having an orientation aligning with the value. The letters T(op), L(eft), R(ight) and B(ottom) represent the visual aligment of the image with orientation 1.

Table 14. Image Orientation Values