Hello Ko -- 

The two  "type" attributes in question here are from different namespaces,
mods and xlink, so there is no conflict.  

--Ray

-----Original Message-----
From: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]] On
Behalf Of Ko van der Sloot
Sent: Friday, January 27, 2006 6:14 AM
To: [log in to unmask]
Subject: MODS/XMLSchema question

Hello,
I am aware that this is not realy an appropriate list to post this question,
but OTOH, I expect to find some knowledgeable people here.

We plan to use the MODS schema in our SRU/SRW frontens to an Oracle XML
backend, but we encountered the following problem:

In the http://www.loc.gov/standards/mods/v3/mods-3-1.xsd "nameType"
definition you can find:

<xsd:complexType name="nameType">
.
.
  <xsd:attribute name="type" type="nameTypeAttribute" use="optional"/> .
.
  <xsd:attributeGroup ref="xlink:simpleLink"/> .
.
</xsd:complexType>

In http://www.loc.gov/standards/mods/xlink.xsd we find:
<attributeGroup name="simpleLink">
  <attribute name="type" type="string" fixed="simple" form="qualified"/>
  <attribute ref="xlink:href" use="optional"/>
  <attribute ref="xlink:role" use="optional"/>
  <attribute ref="xlink:arcrole" use="optional"/>
  <attribute ref="xlink:title" use="optional"/>
  <attribute ref="xlink:show" use="optional"/>
  <attribute ref="xlink:actuate" use="optional"/> </attributeGroup>

The problem/question is:
There are TWO ATTRIBUTES defined with name="type". ONE in the definiton of
nameType, and one in the simpleLink attributeGroup.
Is this allowed? How should we interpret this?

I ask this mainly because our Oracle backend doesn't like it at all.
several validators seem to be very happy with it.

any comment welcome.

Ko vd Sloot
Tilburg University
Netherlands