Bruce -- What Andrew is referring to is that mods uses
http://www.loc.gov/standards/mods/xlink.xsd as its xlink schema:
<xsd:import namespace="http://www.w3.org/1999/xlink"
schemaLocation="http://www.loc.gov/standards/mods/xlink.xsd"/>
this is conformant with the xlink spec, which doesn't mandate any specific
xlink schema, and there is precedent for this, as mets does this too
http://www.loc.gov/standards/mets/xlink.xsd, and oaisis has it's own
(diffently) tailored xlink schema:
http://www.oasis-open.org/committees/ebxml-msg/schema/xlink.xsd
etc.
--Ray
----- Original Message -----
From: "Bruce D'Arcus" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, April 04, 2005 8:20 AM
Subject: Re: [MODS] xlink
> On Apr 4, 2005, at 4:39 AM, Andrew E Switala wrote:
>
> > See the schema. The xlink:type attribute is there, but its value is
> > fixed (to "simple") and so doesn't need to be explicit in the instance
> > document.
>
> I didn't know this. But I'm afraid this another of those details I'm
> going to need to object to. Once again, it assumes a) that people will
> be using XML Schema to validate MODS, and b) that that schema will be
> present in whatever processing context. Neither of these assumptions
> are reasonable from my perspective.
>
> Soo ... a suggestion: require the attribute value until the spec itself
> is fixed.
>
> Bruce
|