IPTC - International Press Telecommunications Council - www.iptc.org

NAR Specification Errata

This documents records all known errors in the NAR 1.1 and later versions specification documents in http://www.iptc.org/std/NAR/

Please email error reports to office@iptc.org

Errata page last edited on: 2009-05-20

------------------

Erratum number 1
Entry date 2008-11-11
Issue

Incorrect structure in the newsMessage and NAR Framework XSD schemas - simpleContent
For some element the IPTC found that they are an extension of a simpleContent instead of complexContent as the XML Schema files for version 1.1. and 1.2 define, as e.g. DateTimePropType has itself simple content (even if it is a complexType).

Planned correction

Change the extension statement from "complexContent" to "simpleContent"
Note This error originating from the graphic user interface of Altoval XML Spy was fixed in the Framework files of version 1.3

 

Erratum number 2
Entry date 2008-11-11
Issue Incorrect structure in the framework XSD schema – mixed content
Some datatypes and element are defined as extensions of BlockType. BlockType is defined as mixed content. The extensions do not include a mixed=”true” attribute. Some validating parsers are fine with that (e.g. Altova XML Spy) others are not (e.g. the built-in parser of Microsoft SQL Server 2005)
Planned correction mixed = “true” will be added to all datatypes and elements that are extensions of BlockType which are: RightsBlockType, definition, note.
Note This error was fixed in the Framework files of version 1.3

 

Erratum number 3
Entry date 2008-12-09
Issue XML Schema files, spec version 1.3:
All elements with a Target Resource Attributes group at the Core Conformance Level (CCL) -e.g. remoteContent and Link - "lost" the attributes @format and @version which existed in previous versions thus causing backward compatibility problems.
Planned correction Reinstate the attributes @format and @version in the Target Resource Attributes group.
Note This error was fixed in the Framework files of version 1.3 - XML-Schema-FileVersion 2 on 2008-12-19

 

Erratum number 4
Entry date 2009-02-27
Issue Specification document + XML Schema files, spec version 1.3:
the <facet> element of a concept is of TypedQualPropType. This does not align with the datatype of equivalent properties which provide a @literal attribute.
Planned correction Change datatype of <facet> to FlexPropType.
Note This error was fixed in the Framework files of version 1.3 - XML-Schema-FileVersion 3 on 2009-03-20

 

Erratum number 5
Entry date 2009-04-15
Issue EventsML-G2 1.2 and NewsML-G2 2.3 specification documents for the CCL - table of the Assertion property <assert>:
The Extension Point definition reads: "Any set of provider-defined properties."
This is wrong, as it allows to include elements from G2 items.
Planned correction Reword to: "Any set of properties from any namespace".
Note Will be fixed in the next release of the specification documents.

 

Erratum number 6
Entry date 2009-05-20
Issue EventsML-G2 1.2 and NewsML-G2 2.3 specification documents for the PCL:
Table of the Broader element includes a @rank attribute, while the element is of data type RelatedConceptType which itself has a @rank attribute.
Planned correction Remove the @rank in the Broader element spec table.
Note Will be fixed in the next release of the specification documents.