title: Why do we need targetNamespace?
body: <p>I would like to understand the purpose of targetNamespace as used both in XML Schema and in WSDL. In fact, to keep things simple, let's limit this question to XML Schema.</p>
  
  <p>I feel like I fully understand the notion of (simple) XML namespaces. By convention we use URI/URLs, but we could use any string, which we then assign to a prefix for reuse by XML nodes and attributes, or use simply as the default namespace for the scope at hand. So far, so good ?</p>
  
  <p>Now enters XML Schema. For some reason the inventors of XML Schema felt the notion of simple namespaces wasn't enough and they had to introduce the targetNamespace. My question is : what significant benefit does a targetNamespace introduce that couldn't be provided by a normal XML namespace ? If an XML document references a xsd document, either by schemaLocation or with an import statement, in either case I give the path to the actual xsd document being referenced. This is what uniquely defines the Schema I want to refer to. If in addition I want to bind this Schema to a particular namespace in my referencing document, why should I be obliged to replicate the precise targetNamespace already defined in the XML Schema I am referencing? Why couldn't I simply redefine this namespace however I want within the XML document in which this namespace will be used to refer to that particular XML Schema document I want to reference ?</p>
  
  <p>Update:</p>
  
  <p>To give an example, if I have the following in an XML instance document:</p>
  
  <pre><code>&lt;p:Person
     xmlns:p="http://contoso.com/People"
     xmlns:v="http://contoso.com/Vehicles"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation=
      "http://contoso.com/schemas/Vehicles
       http://contoso.com/schemas/vehicles.xsd
       http://contoso.com/schemas/People
       http://contoso.com/schemas/people.xsd"&gt;
     &lt;name&gt;John&lt;/name&gt;
     &lt;age&gt;28&lt;/age&gt;
     &lt;height&gt;59&lt;/height&gt;
     &lt;v:Vehicle&gt;
        &lt;color&gt;Red&lt;/color&gt;
        &lt;wheels&gt;4&lt;/wheels&gt;
        &lt;seats&gt;2&lt;/seats&gt;
     &lt;/v:Vehicle&gt;
  &lt;/p:Person&gt;
  </code></pre>
  
  <p>Why does e.g. the people.xsd Schema need to define a targetNamespace which is "http://contoso.com/schemas/People"? Why do we need the targetNamespace definition in the xsd document at all? It seems to me all you have to gain from the namespace part of the schemaLocation is already contained in the XML instance document. What is the benefit of enforcing the existence of a targetNamespace with equal value over in the xsd document ?</p>
  
  <p>Follow-up question to Paul's answer:</p>
  
  <p>Can you give me a concrete example where such "clashes" between xsd element names becomes apparent and that would explain the need for targetNamespace ?</p>
  
  <hr>
  
  <p>Ok, here's an attempt to answer my own question. Let me know if it seems coherent to you. Looking at the examples on the page linked by Paul helped me.</p>
  
  <p>If we take the XML instance example in the original question above, we have two references to the definition of the vehicle element. One is explicit and visible in the XML instance document itself, but we must also imagine that the person.xsd XML Schema references the same vehicle definition again as an allowed child element of person. If we were to use normal namespaces where each document were allowed to define its own namespace for vehicle, how would we know that the XML instance is referencing the same XML Schema definition for vehicle as is the person.xsd ? The only way is by enforcing a concept of namespace which is stricter than the original simple one and which must be written exactly the same way across multiple documents.</p>
  
  <p>If I wasn't writing this on a tablet I would provide a code example, but here I will just attempt to describe the example I have in mind.</p>
  
  <p>Imagine that we have two different XML Schema definitions for a vehicle element. location1/vehicles.xsd would contain the definition that validates the example from the question of this post (containing color, wheels, and seats child elements), whereas location2/vehicles.xsd would contain an entirely different definition for a vehicle element, (say, with child elements year, model, and volume). Now, if the XML instance document refers to the location1 Schema, as is the case in the example above, but person.xsd says that the person element can contain a vehicle child element of the type defined in the location2 Schema, then without the notion of a targetNamespace, the XML instance would validate, even though it clearly doesn't have the right kind of vehicle as a child element of its person element.</p>
  
  <p>Target namespaces then help us make sure that if two different documents are referencing the same third XML Schema, that they are both in deed referencing the same Schema and not just a Schema that contains elements that are similar, but not identical to one another...</p>
  
  <p>Does that make any sense ?</p>