Databases
StackOverflow2013
Postsdbo
POIgnoring supplied namespaces when validating XML with XSD
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIgnoring supplied namespaces when validating XML with XSD
    primarykey
    data
    text
    <p><strong>Background:</strong></p> <p>We're building an application that allows our customers to supply data in a predefined (ie. we don't control) XML format. The XSD is supplied to us by a Third Party, and we are expecting to receive an XML file that passes schema validation prior to us processing it.</p> <p><strong>The Problem:</strong></p> <p>The XSD that we are supplied with includes a default and target namespace, which means that if a customer supplies an XML file that doesn't include the namespace, then the validation will pass. We obviously don't want them to be supplying things that say they pass but shouldn't, but the bigger concern is around the mass of additional checks that we will need to do on each element if I can't find a solution to doing the XML validation.</p> <p><strong>The Questions:</strong></p> <p>Is it possible to force .NET to perform validation and ignore the namespace on the supplied XML and XSD. i.e. in some way "assume" that the namespace was attached.</p> <ol> <li>Is it possible to remove the namespaces in memory, easily, and reliably?</li> <li>What is the best practice in these situations?</li> </ol> <p><strong>Solutions that I have so far:</strong></p> <ol> <li>Remove the namespace from the XSD everytime it's updated (shouldn't be very often. This doesn't get around the fact that if they supply a namespace it will be still pass validation.</li> <li>Remove the namespace from the XSD, AND find a way to strip the namespace from the incoming XML everytime. This seems like a lot of code to perform something simple.</li> <li>Does some pre-qualification on the XML file before it validated to ensure that it has the correct namespace. Seems wrong to fail them due to an invalid namespace if the contents of the file are correct.</li> <li>Create a duplicate XSD that doesn't have a namespace, however if they just supply the wrong namespace, or a different namespace, then it will still pass.</li> </ol> <p><strong>Example Xml:</strong></p> <pre><code>&lt;?xml version="1.0"?&gt; &lt;xsd:schema version='3.09' elementFormDefault='qualified' attributeFormDefault='unqualified' id='blah' targetNamespace='urn:schemas-blah.com:blahExample' xmlns='urn:blah:blahExample' xmlns:xsd='http://www.w3.org/2001/XMLSchema'&gt; ... &lt;/xsd:schema&gt; </code></pre> <p>with namespace that is different</p> <pre><code> &lt;?xml version="1.0" encoding="UTF-8" ?&gt; &lt;root xmlns="urn:myCompany.com:blahExample1" attr1="2001-03-03" attr2="google" &gt; ... &lt;/root&gt; </code></pre> <p>without namespace at all.</p> <pre><code> &lt;?xml version="1.0" encoding="UTF-8" ?&gt; &lt;root attr1="2001-03-03" attr2="google" &gt; ... &lt;/root&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMartin
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIgnoring supplied namespaces when validating XML with XSD
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIgnoring supplied namespaces when validating XML with XSD
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIgnoring supplied namespaces when validating XML with XSD
      1. This table or related slice is empty.
      1. VTUpMod
    1. COXML namespaces are a good thing, why fight it?
      singulars
      1. POIgnoring supplied namespaces when validating XML with XSD
      1. USM.Babcock
    2. COit's something that we can't control, I want to make sure that customers are sending the correct XML, however, if a customer misses out the namespace declaration in their submitted XML then I would like to say that we can still validate it. I don't want to just say "You messed up, now fix it!" (and yes I would use better words, but you get the idea).
      singulars
      1. POIgnoring supplied namespaces when validating XML with XSD
      1. USMartin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload