Query on elementFormDefault & Restrictions (using AltovaXmlSpy)

[dickster]

I have a query surrounding about elementFormDefault

I have abbreviated the schemas - and hopefully have included all the
relevant information

I get the following error message (AltovaXmlSpy-when I click validate)
in Schema1.xsd:
"The content model of complex type '{no name}' is not a valid
restriction of the content model of complex type 'origo:TimePeriod'"

What does this mean? - when I switch elementFormDefault to "qualified"
I DONT GET ANY ERROR MESSAGE :-|

---------------------------------------------------------------------------------------
Schema1.xsd
---------------------------------------------------------------------------------------
<xsd:schema
xmlns:origo="http://www.origoservices.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.origoservices.com"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">

<xsd:include schemaLocation="Schema2.xsd"/>

<xsd:complexType name="product">
<xsd:sequence>

[Martin Honnen]

dickster wrote:

I have a query surrounding about elementFormDefault I get the following error message (AltovaXmlSpy-when I click validate)
in Schema1.xsd:
"The content model of complex type '{no name}' is not a valid
restriction of the content model of complex type 'origo:TimePeriod'"

What does this mean? - when I switch elementFormDefault to "qualified"
I DONT GET ANY ERROR MESSAGE :-|
You might want to use that then, if you want to define elements in a
namespace then using elementFormDefault="qualified" is usually what you
want and need to easily and consistently define your elements in the
target namespace specified.
<xsd:schema
xmlns:origo="http://www.origoservices.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.origoservices.com"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<xsd:element name="start_date" type="origo:Date"/>

If you use elementFormDefault="unqualified" then I think you need
<xsd:element name="origo:start_date"
to fit the definitions in the other included schema.
--

Martin Honnen
http://JavaScript.FAQTs.com/

[Henry S. Thompson]

dickster writes:

I have a query surrounding about elementFormDefault

I have abbreviated the schemas - and hopefully have included all the
relevant information

I get the following error message (AltovaXmlSpy-when I click validate)
in Schema1.xsd:
"The content model of complex type '{no name}' is not a valid
restriction of the content model of complex type 'origo:TimePeriod'"

The base complex type includes an element declaration which accepts
EIIs whose expanded name is {http://www.origoservices.com, start_date}

Your restriction attempts to restrict that with an element declaration
which accepts EIIs whose expanded name is {[none],start_date}.

The difference arises because only elementFormDefault is 'qualified'
in the base schema document and 'unqualified' in yours, and that's
what determines whether element declarations within complex type
definitions acquire the target namespace of the enclosing schema
document.

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]

[dickster]

Thanks for your reply Martin.

When I keep the elementFormDefault attribute consistent between each
Schema it works fine.

dickster