Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

XML validation error: Description: TargetNamespace.2: Expecting no namespace, but the schema document has a target namespace of ...

Posted on 2009-05-19
3
Medium Priority
?
2,201 Views
Last Modified: 2012-05-07
Hello,

The following error is reported in Oxygen XML but the parser does successfully validate my XML document against the given XSD:  "Description: TargetNamespace.2: Expecting no namespace, but the schema document has a target namespace of 'http://schemas/jupiter'."

Otherwise it appears to work. If I change noNamespaceSchemaLocation to schemaLocation the error changes to "There is no schema or DTD associated with the document" and the validation stops working. It appears that not using a namespace is not an option because the type used to validate the currency-short-name must be qualified with a namespace.

I would like this error to go away and ultimately have this properly defined.

Thank you,
Peter
Jupiter.xsd
 
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:jupiter="http://schemas/jupiter"
   targetNamespace="http://schemas/jupiter"
   elementFormDefault="unqualified" attributeFormDefault="unqualified">
   <simpleType name="currency-short-name-type">
      <restriction base="string">
         <enumeration value="EUR"/>
         <enumeration value="USD"/>
         <enumeration value="GBP"/>
         <enumeration value="CHF"/>
         <enumeration value="ON_EUR"/>
         <enumeration value="ON_GBP"/>
      </restriction>
   </simpleType>
   . . .
   <element name="estimate">
      <complexType>
         <sequence>
            <element name="estimate-currency" maxOccurs="unbounded">
               <complexType>
                  <sequence/>
                  <attribute name="name" type="string"/>
                  <attribute name="short-name" type="jupiter:currency-short-name-type"/>
                  <attribute name="exchange-rate" type="float"/>
               </complexType>
            </element>
    . . .
 
Sample.xml
 
<?xml version="1.0" encoding="ISO-8859-1"?>
<jupiter:estimate name="XXX" description="X" rev-number="X"
    notice-to-proceed="2009-09-30" status="In Process" base-currency="EUR"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xmlns:jupiter="http://schemas/jupiter" xsi:noNamespaceSchemaLocation="Jupiter.xsd"
    >
    <estimate-currency name="US Dollar" short-name="USD" exchange-rate="0.800000"/>
    <estimate-currency name="Euro" short-name="EURx" exchange-rate="1.000000"/>
 
Note: The above line correctly fails validation because EURx is not a valid currency-short-name-type

Open in new window

0
Comment
Question by:pdegregorio
  • 2
3 Comments
 
LVL 60

Accepted Solution

by:
Geert Bormans earned 2000 total points
ID: 24423614
xsi:noNamespaceSchemaLocation="Jupiter.xsd"

needs to become

xsi:schemaLocation="http://schemas/jupiter Jupiter.xsd"

if there is a targetNamespace, you need to point to it
before the space is the namespace, after the space is the location of the schema
0
 

Author Comment

by:pdegregorio
ID: 24423821
Thank you, that worked! Does anything appear embarrassingly out of kilter that I should look at?
0
 
LVL 60

Expert Comment

by:Geert Bormans
ID: 24424251
Welcome
Nothing embarrassing in this, it is a bit tricky anyway
It is the schema that decides whether you have a namespace or not in your XML
so if there is no targetnamespace in the schema use the reference as you did
if there is a target namespace, you need to reference that as well,
a bit perculiar, don't worry, now you know
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The Confluence of Individual Knowledge and the Collective Intelligence At this writing (summer 2013) the term API (http://dictionary.reference.com/browse/API?s=t) has made its way into the popular lexicon of the English language.  A few years ago, …
Many times as a report developer I've been asked to display normalized data such as three rows with values Jack, Joe, and Bob as a single comma-separated string such as 'Jack, Joe, Bob', and vice versa.  Here's how to do it. 
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
Loops Section Overview

926 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question