- From: Dave Beckett <dave.beckett@bristol.ac.uk>
- Date: Fri, 11 Jan 2002 17:17:17 +0000
- To: ht@cogsci.ed.ac.uk (Henry S. Thompson)
- cc: xmlschema-dev <xmlschema-dev@w3.org>
>>>Henry S. Thompson said:
> --=-=-=
>
> I think this is important enough that I've taken the time to produce
> what I am _guessing_ you want. I attach three schema documents and an
> example, which is valid.
>
> Hope this helps.
Thanks a lot Henry; this looks just what I need
So checking my understanding
dcmes-xml-xsd.xsd
imports
dcmes-rdf.xsd (rdf: namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#)
which imports
dcmes-dc.xsd (dc: namespace http://purl.org/dc/elements/1.1/)
and user documents (as shown in dcmes-xmpl.xml) should be validated
using the dcmes-xml-xsd.xsd schema
The old schema had <complexType>s for each of the Dublin Core
elements, since I was told, that made it easier to re-use the
schema(s) by redefining and/or restricting them.
The example I was given was, having made <complexType> dc:title
like:
<complexType name="dc:title" mixed="true">
<sequence>
<any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute ref='xml:lang'/>
</complexType>
<element name="dc:title" type="dc:title"/>
(or somesuch) it allowed in another schema:
<complexType name="title">
<complexContent>
<restriction base="dc:title">
<sequence>
<element name="mainTitle" type="string"/>
<element name="secondaryTitle" type="string"/>
</sequence>
<attribute ref='xml:lang'/>
<restriction>
<complexContent>
<complexType>
Does that make sense to change the same to continue to do?
Great stuff; thanks again.
Dave
Received on Friday, 11 January 2002 12:17:22 UTC