What does elementFormDefault do for XML/When is it used?

Question

So I found some definitions for elementFormQualifed values:

qualified - elements and attributes are in the targetNamespace of the schema

unqualified - elements and attributes do not have a namespace

So from that definition I would think that if a schema is set to qualified then why must you prefix the type with the namespace? And what are the scenarios that you would even have one set to unqualified for that matter? I tried Googling, but all I got were a couple W3C pages that were extremely hard to understand.

This is the file I am working with right now, why do I need to declare the type as 'target:TypeAssignments' when I declare the targetNamespace as the same one as xmlns:target?

<?xml version="1.0" encoding="UTF-8"?>
<schema 
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:target="http://www.levijackson.net/web340/ns"
    targetNamespace="http://www.levijackson.net/web340/ns" elementFormDefault="qualified"
    >

<element name="assignments">
    <complexType>
     <sequence>
      <element name="assignments" type="target:TypeAssignments" minOccurs="1" maxOccurs="unbounded"></element>
     </sequence>
    </complexType>
</element>

<complexType name="TypeAssignments">
    <sequence>
     <element name="assignment" type="target:assignmentInfo" minOccurs="0" maxOccurs="unbounded"></element>
    </sequence>
</complexType>

<complexType name="assignmentInfo">
    <sequence>
      <element name="name" type="string"></element>
      <element name="page" type="target:TypePage"></element>
      <element name="file" type="target:TypeFile" minOccurs="0" maxOccurs="unbounded"></element>
    </sequence>
    <attribute name="id" type="string" use="required"/>
</complexType>

<simpleType name="TypePage">
    <restriction base="integer">
     <minInclusive value="50" />
     <maxInclusive value="498" />
    </restriction>
</simpleType>

<simpleType name="TypeFile">
    <restriction base="string">
     <enumeration value=".xml" />
     <enumeration value=".dtd" />
     <enumeration value=".xsd" />
    </restriction>
</simpleType>

</schema>

Thanks in advance,
Levi

Answer 1

ElementFormDefault has nothing to do with namespace of the types in the schema, it's about the namespaces of the elements in XML documents which comply with the schema.

Here's the relevent section of the spec:

Element Declaration Schema

Component Property  {target namespace}
Representation      If form is present and its ·actual value· is qualified, 
                    or if form is absent and the ·actual value· of 
                    elementFormDefault on the <schema> ancestor is qualified, 
                    then the ·actual value· of the targetNamespace [attribute]
                    of the parent <schema> element information item, or 
                    ·absent· if there is none, otherwise ·absent·.

What that means is that the targetNamespace you've declared at the top of the schema only applies to elements in the schema compliant XML document if either elementFormDefault is "qualified" or the element is declared explicitly in the schema as having form="qualified".

For example: If elementFormDefault is unqualified -

<element name="name" type="string" form="qualified"></element>
<element name="page" type="target:TypePage"></element>

will put expect "name" elements to be in the targetNamespace and "page" elements to be in the null namespace.

To save you having to put form="qualified" on every element declaration, stating elementFormDefault="qualified" means that the targetNamespace applies to each element unless overridden by putting form="unqualified" on the element declaration.