Importing Schema = no element name

[Fezboy]

Greetings!

I'm trying to import elements declared in the METS and MODS XML Schema
into my own. I've gotten to the point where the xsd validates, but when
I try to validate a document against it, it expects element '' in place
of mets:fileGrp. The same error obtains for mets:structMap if I comment
out the mets:fileGrp code.

Can an insightful person tell me why it will wants '' instead of the
actual Qname I use to identify it?

TIA!
Nick
Relevant markup:

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http ://www.w3.org/2001/XMLSchema"
xmlns="http://www.indiana.edu/~eviada"
xmlns:xlink="ht tp://www.w3.org/TR/xlink"
xmlns:mets="htt p://www.loc.gov/METS/"
xmlns:mods="htt p://www.loc.gov/mods/v3"
targetNamespace ="http://www.indiana.edu/~eviada"
elementFormDefa ult="qualified"
attributeFormDe fault="unqualif ied">
<xsd:import namespace="http ://www.loc.gov/METS/"
schemaLocation= "http://www.loc.gov/standards/mets/mets.xsd"/>
<xsd:import namespace="http ://www.loc.gov/mods/v3"
schemaLocation= "http://www.loc.gov/standards/mods/v3/mods-3-0.xsd"/>

<xsd:element name="head" type="headType"/>
<xsd:element name="fileGrpID " type="xsd:strin g"/>
<xsd:element name="fileUriPr efix" type="xsd:strin g"/>
<xsd:element name="collectio nID" type="xsd:strin g"/>
<xsd:element name="collector " type="xsd:strin g"/>
<xsd:element name="relatedSe gments" type="relatedSe gmentsType"/>
<xsd:element name="segment" type="segmentTy pe"/>
<xsd:element name="title" type="xsd:strin g"/>
<xsd:element name="uri" type="xsd:anyUR I"/>

<xsd:complexTyp e name="headType" >
<xsd:sequence >
<xsd:element ref="fileGrpID"/>
<xsd:element ref="fileUriPre fix"/>
<xsd:element ref="collection ID"/>
<xsd:element ref="collector"/>
<xsd:element ref="mets:fileG rp" type="mets:file GrpType"/>
<xsd:element ref="mets:struc tMap" type="mets:stru ctMapType"/>
<xsd:element ref="relatedSeg ments"/>
</xsd:sequence>
</xsd:complexType >

<!-- ... -->

Full URLs can be found:

My xsd file:
http://bl-ldlp-boblee.ads.iu.edu/bul...backSchema.xsd

METS xsd file:
http://www.loc.gov/standards/mets/mets.xsd

XMLSpy generated sample XML file:
http://bl-ldlp-boblee.ads.iu.edu/bullpen/sample4NG.xml

[Henry S. Thompson]

You don't say which schema processor you're using, which makes it hard
to respond in detail.

Your schema document is however _not_ valid. For example:

<xsd:element ref="mets:fileG rp" type="mets:file GrpType"/>

is broken -- xsd:element can have _either_ a 'ref' attribute _or_ a
'name' and a 'type' attribute, but you can't mix the two.

So I suggest

a) Getting a better schema processor, i.e. one which reports this
error and
b) removing the 'type' attribute from your mets: references.

ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: [phone], e-mail: [e-mail]
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]

[Fezboy]

Henry S. Thompson wrote:

Your schema document is however _not_ valid. For example:

<xsd:element ref="mets:fileG rp" type="mets:file GrpType"/>

is broken -- xsd:element can have _either_ a 'ref' attribute _or_ a
'name' and a 'type' attribute, but you can't mix the two.

Thanks for pointing this out. I'm new to the schema side of XML
processing--I primarily do XSLT.

I've been using XMLSpy write the schema and testing it by having XMLSpy
generate sample XML based on that schema. This is where I came across
the '' element problem. I went back and tried using only the ref
attribute but was getting an error that the schema was not valid on its
own, but might be if part of another...

I think the problem stems from the fact that I was using the imported
fileGrpType in an improper context. I solved this by creating a local
containing element based on the mets:metsType which then holds
mets:fileGrp, etc. I cannot vouch for the accuracy of my interpretation
of the problem, but I do know that I now have a working schema.

Thanks for the advice, HST.
-Nick