[OAI-implementers] doubts about xmlschema in OAI
Sat, 17 Nov 2001 13:53:39 -0000
If I understand your query correctly, Chris (of e-prints) and I had a
discussion about this some time ago.
The conclusion we came to was that you should use the namespace attribute
rather than the name of the metadata enclosure (be it "dc" or "oai_dc"), to
identify the type of metadata.
I believe you can perform XSLT based on attribute values?
All the best,
----- Original Message -----
From: "Xiaoming Liu" <firstname.lastname@example.org>
Sent: Saturday, November 17, 2001 7:11 AM
Subject: [OAI-implementers] doubts about xmlschema in OAI
> In OAI_GetRecord.xsd, it specifies
> <complexType name="metadataType">
> <any namespace="##other" processContents="lax"/>
> and in dc.xsd, it specifies like
> <element name="dc" type="dc:dublincoreType"/>
> <complexType name="dublincoreType">
> The question is: If we use "processContents="lax" in OAI_GetRecord.xsd,
> xmlschema validator will treat
> <GetRecord>....<xxx_dc><title>...</title></xxx_dc>..</GetRecord> as
> but <xxx_dc>...</xxx_dc> may not be the right format in our intention, it
> passes schema validator only because processContents="lax" is used in
> Get_Record.xsd. We probably want to always use <dc>....<dc>.
> I have this doubt when I try to process OAI response with XSLT, the arXiv
> uses <oai_dc>...</oai_dc>, it passed oaiexplorer test and other schema
> validator (oracle and XMLSpy). But this really brings some troubles to
> XSLT processing.
> If I change Get_record.xsd to processContents="strict", this problem will
> be reported by schema validator.
> Do we have special reason of using processContents="lax"?
> Xiaoming Liu
> OAI-implementers mailing list