Hi, all,
It doesn't look like this question was ever addressed on list. I assume
that at this point we just follow the schema even though the schema does not
follow the standard?
In addition to the text-vs-coded-values problem, the text value
corresponding to "1" in the schema is "normal*". In the NISO Data
Dictionary, that asterisk points the reader to a footnote defining "normal"
in this context. I doubt it was intended to be part of the value, even if
the values were text strings.
We're also interested in knowing who is using MIX.
Thanks,
Robin
Robin Wendler
Library Technology Services
Harvard University
[log in to unmask]
617-495-3724
On Wed, 6 May 2009 18:46:23 +0200, Michael Steidl (IPTC)
<[log in to unmask]> wrote:
>Group:
>
>the MIX specifications (Z39-87-2006) define in 8.5 an "orientation"
element. Its type is
>enumerated, the list of values read
>1 = normal*
>2= normal, flipped image
>and so on.
>
>To my understanding this is an enumeration of integer values.
>
>The MIX 2.0 XML Schema specifies an orientation type like this:
>
><xsd:simpleType name="orientationType">
> <xsd:restriction base="xsd:string">
> <xsd:enumeration value="normal*"/>
> <xsd:enumeration value="normal, image flipped"/>
> <xsd:enumeration value="normal, rotated 180°"/>
> <xsd:enumeration value="normal, image flipped,
rotated 180°"/>
> <xsd:enumeration value="normal, image flipped,
rotated cw 90°"/>
> <xsd:enumeration value="normal, rotated ccw 90°"/>
> <xsd:enumeration value="normal, image flipped,
rotated ccw 90°"/>
> <xsd:enumeration value="normal, rotated cw 90°"/>
> <xsd:enumeration value="unknown"/>
> </xsd:restriction>
> </xsd:simpleType>
>
>Here it is an enumeration of string values, the integers got lost.
>
>Ain't this wrong?
>
>Thanks for clarifying
>
>Michael
>
>
>==================================================
>Sent by:
>Michael Steidl
>Managing Director of the IPTC <[log in to unmask]>
>International Press Telecommunications Council
>"Information Technology for News"
>Visit us on the web at http://www.iptc.org
>
>
|