IPTC - International Press Telecommunications Council
This documents records all known errors in the NAR 1.0 specification documents in http://www.iptc.org/std/NAR/1.0/specification/
Please email error reports to office@iptc.org
Errata page last edited on: 2007-09-21
------------------
Issue: The NAR model states that all aggregate components provide extension points which support the addition of provider defined properties. Two locations where this rule is not fulfilled were found: BlockType and Label1Type (PCL only) are defined as XML mixed content: it is acknowledged that any set of provider-defined content can be added, in any order, to the set of properties natively supported by these aggregate components, defined as XML complex data types.
Correction: Add the missing extension points in the model and XML schema.
Issue: The NAR CCL Model document states that NewsContentSetType (the datatype used for the newsItem/contentSet property) provides an original attribute, defined as “A local reference to the original piece of content, from which all renditions have been derived”.
Correction: Add the original attribute
to the newsItem Core XML Schema.
Note: in practice, the power qualifier is removed from the attribute
definition in the master schema.
Issue: The Core model defines EntityDetailsGroup, a structure used in the
concept property. Note that the list of entity details could grow in the future.
For the sake of clarity and future reusability, this structure should be also
defined in the schema, in replacement of the local choice of elements.
Correction: Define a EntityDetailsGroup in the XML Schema as a choice between personDetails, organisationDetails, geoAreaDetails and POIDetails. It is referenced from the global concept element.
Issue: At Core level anyItem@standard has "nar" as the default value. This doesn't make sense as the IPTC News Architecture is not a published IPTC standard but an internal framework - and hence the value violates the semantics of the attribute.
Correction: Suppress the default value of anyItem@standard.
Issue: The anyItem@standard attribute is missing in the Power level Model
Correction: Add the anyItem@standard attribute to the PCL Model document.
Issue: The anyItem@conformance attribute is defined as fixed with value of power in the Power level Model.
Correction: change the a default value of the anyItem@conformance attribute to core and drop the "fixed" in the Power level Model document.
Issue: At PCL, the contentMeta element supports i18nAttributes *only* in the newsItem, but not in the conceptItem, knowledgeItem and packageItem.
Correction: add i18nAttributes to contentMeta in the packageItem and knowledgeItem schema (it is already present in the conceptItem schema). The presence of I18N qualifiers on all elements with textual descendant nodes is already expressed in the PCL Model document; more precisly statements will added to the document in order to clarify the subject.
Issue: This section, which describes {scheme,code} pairs and concept URIs, uses a wrong example: in http://iptc.org/schemes/theme#15000000 , 1500000 is not usable as an @id value (but the URI is still valid).
Correction:
Modify the paragraph::
As an example, in the IPTC scheme defined for news categories, which could
be unambiguously identified by the URI “http://iptc.org/schemes/theme/”,
the code “15000000” is associated with the concept of “Sport”.
The corresponding concept URI would therefore be "http://iptc.org/schemes/theme/15000000".
Issue: The NAR specification document defines the inlineXML element by "Any XML mixed content from any namespace" (section 5.2.5, CCL specs) - while the XML Scheme does not enforce a mixed content model.
Correction: Change the NAR spec wording for inlineXML to "XML content from any namespace" to clarify the content model is not "mixed content".
------------------
END of document