Carl

thank you for your valuable detailled input. See a few replies below:

On 25 Apr 2008 at 17:33, Carl Rambert wrote:

> IPTC Extension Specification Version 1.0 Document Revision 2, dated
> 2008-04-25
>
> Page 30, Digital Source File Type, Required CV is detailed as literal
> values.
> - - Does this imply that the XMP Type should be Closed Choice Text
> instead of URI?
> - - Or do you intend the Values to be encoded as URIs?

Right, IPTC's CVs are base on URIs to comply with RDF.

> Page 34, Licensor, XMP Value Type
> - - should read "Bag LicensorDetail", not "struc LicensorDetail"

Right, to be fixed.

> Page 40, Country ISO-Code, Required CV -- no entry
> - - Should this be the combination of ISO 3166-1 alpha-2 and 3166-1
> alpha-2? as described for Iptc4XMPCoreCountryCode?

Right, this addition is currently still missing.

> Page 44, References
> - - It might be useful if the "Adobe XMP" reference (September 2005)
> had a note that it severs as the authority for the photoshop
> (Photoshop) and dc (Dublin Core) XMP schema definitions. It could be
> implemented as two more rows in the table, both with duplicate Source.

Well, there is a couple more schema definitions in the Adobe document. We'll
consider this -
and not to overload the reference section.

> - - PLUS - it might be best to reference a specific version of PLUS.
> The current version is 1.2.0 Revision 2, published in 2008-01-29,
> however, it deprecated the plus:ImageSource field referenced at the
> bottom of Page 31. So, this specification must refer to one of the
> Version 1.1.0 Revisions, perhaps Revision 6 dated 2007-12-24?

We will align the final IPTC specs with the latest PLUS specs.

> Page 30, Digital Image GUID, Implementation Note(s) (continued from
> Page 29), Last sentence refers to Exif/technical metadata. Are there
> specific fields that should be documented

There is a field for a unique identifier in the Exif specs, we currently
investigate how it is
actually used before we recommend to map it into the IPTC schema.

>
> Page 31 Image Registry Id, Implementation Note(s). (I figured it out
> from the Cardinality fields) Each Image Registry Id entry must be a
> complete matching pair.

We'll clarify this.

Michael

> Carl Rambert, Pound Hill Software
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

==================================================
Sent by:
Michael Steidl
Managing Director of IPTC <mdirector@...>
International Press Telecommunications Council
Working to improve the efficiency of News exchange.
Visit our Web Site at http://www.iptc.org