Hi Creighton,
Both validation errors are caused by the attribute value of "No_linguistic_content," which isn't permitted by the schema. In this case, there are two bugs: one in the AT (which is not using the appropriate code, zxx, as far as I understand things (http://www.loc.gov/marc/languages/language_code.html#z); and one in the EAD XSD schema (which doesn't list that code as an acceptable value, and so, doesn't fully implement ISO 639-2).
For my purposes, I've been planning to convert this type of output to the following:
<language>No linguistic content</language>
...removing the @langcode value in the process.
Mark
-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Creighton Barrett
Sent: Thursday, September 27, 2012 11:39 AM
To: [log in to unmask]
Subject: Validation error on langcode attribute
I have some EAD exported from the Archivists Toolkit that is not validating in Oxygen. We have a few photographs where the "No linguistic content" language was selected. Here is a sample:
<c id="ref33" level="file">
<did>
<unittitle>Photograph of a painting of the barque "Scots Bay"</unittitle>
<langmaterial>
<language langcode="No_linguistic_content"/>
</langmaterial>
Oxygen is showing errors with the langcode attribute. I am getting two different errors:
E [Xerces] cvc-attribute.3: The value 'No_linguistic_content' of attribute 'langcode' on element 'language' is not valid with respect to its type, 'null'.
E [Xerces] cvc-enumeration-valid: Value 'No_linguistic_content' is not facet-valid with respect to enumeration
Any ideas? I can't see why I am getting two different errors or why the option is included in the AT language drop-down if it doesn't validate.
Cheers,
Creighton
--
Creighton Barrett
Archives Specialist
Dalhousie University Archives and Special Collections
Tel: 902.494.6490 | Fax: 902.494.2062
Email: [log in to unmask]
www.dal.ca/duasc
www.facebook.com/duasc
|
