BillTr
asked on
XML question
I get the following error when going from my xml doc to the schema in XMLSpy.
XML Schema has to begin with a <schema> element in namespace 'http://www.w3.org/2001/XMLSchema'!
I assume I have something wrong in one of the headers though I used the schema to create the document. Headers are attached.
Any advise is appreciated.
XML Schema has to begin with a <schema> element in namespace 'http://www.w3.org/2001/XMLSchema'!
I assume I have something wrong in one of the headers though I used the schema to create the document. Headers are attached.
Any advise is appreciated.
Doc Header:
<Fund_NAV xmlns="http://MyCompany.com/AMG/Fund_NAV" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://MyCompany.com/AMG/Fund_NAV file:///C:/Users/btraut/Desktop/NAV5.xsd">
Schema Header:
<xs:schema xmlns="http://MyCompany.com/AMG/Fund_NAV" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:altova="http://www.altova.com/xml-schema-extensions" targetNamespace="http://MyCompany.com/AMG/Fund_NAV" elementFormDefault="qualified" attributeFormDefault="unqualified">
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I find it works when I go to the schema via the DTD/Schema option at the top of the screen.
So, I think my xml is probably correct and that there is a nuance to XMLSPY that I'm not aware of.
So, I think my xml is probably correct and that there is a nuance to XMLSPY that I'm not aware of.
@BillTr
Can you post the two files?
Can you post the two files?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The file is definitely there in the desktop. I did use it when I created the XML file.
Could I have something wrong in the .com portion?
Does http://MyCompany.com/AMG/Fund_NAV have to exist somewhere?
Could I have something wrong in the .com portion?
Does http://MyCompany.com/AMG/Fund_NAV have to exist somewhere?
http://MyCompany.com/AMG/Fund_NAV does not need to exist, it is the namespace uri, it is just an unique identifier that has a url form, but is a URI, not a URL
Can you share the two files?
It always help to create a new XML file based on the schema, then XML Spy sets the header correct. After that you can compare. I don't see an issue however, so it must be somewhere in the files
Can you share the two files?
It always help to create a new XML file based on the schema, then XML Spy sets the header correct. After that you can compare. I don't see an issue however, so it must be somewhere in the files
I have two different XML tools I wanted to expose to your files. I'm interested in what those tools think is happening.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am utterly surprised... time seems to have changed.
When I was still a paying (too much definitely) customer of Altova products, I opened God knows how many tickets, never got a decent reply. So I abandonned Spy for other (much better) tools... seems they finally understood support is important... or you just got lucky :-)
When I was still a paying (too much definitely) customer of Altova products, I opened God knows how many tickets, never got a decent reply. So I abandonned Spy for other (much better) tools... seems they finally understood support is important... or you just got lucky :-)
well aikimark,
some assists would be fair no?
http:#a39573834 did after all confirm the headers were OK
just a thought
some assists would be fair no?
http:#a39573834 did after all confirm the headers were OK
just a thought
ASKER
This turned out to be a training issue on my part, but the quick responses provided were very helpful in pointing me to that. I divided the points as best I could. Let me know if there's a problem.
ASKER
My impression is I'm missing something in how XMLSpy works. I had assumed that if I create the document via the schema that I should be able to jump directly from that document to the schema via the schema button at the bottom. But perhaps that is not the case?