Hi Roberto,
Thanks for the useful info. I come to the conclusion that the uncertainty of
how each tool processes an XML catalog in detail (or my incomplete
understanding of it anyway) does place some question marks around the
interoperable use of XML Catalogs, unless the tool set to use is mandated
amongst the data exchange parties, making the resolution results predictable.
For example, I would have thought a local XML Catalog should really override
the schemaLocation (specified by the sender of the message, referring to a
remote absolute or relative storage location.)
Thank you once again.
Juerg
-----Original Message-----
From: roberto@javest.com [mailto:roberto@javest.com]
Sent: Thursday, 28 September 2006 10:40 p.m.
To: Juerg Tschumperlin
Subject: Re: [ubl] Validating UBL 2.0 genericode files with Altova XMLSpy
I am sorry I use a personal xml/ubl editor based on JAXP thus XERCES/XALAN
by default.
I think the right steps to successfully open an xml file are:
1) Check if there is a schemaLocation
2) Test if the schemaLocation URI is reachable and exists (e.g. is local
or internet is available)
3) if the schemaLocation URI doesn't exists lookup the xml catalog.
But someone could start 1st with the catalog and then if URI is not
available switch to the schemaLocation check.
Personally I prefere the 1st case, expecially when the xml catalog is
handled by a third party API (e.g. common-catalog by Apache)
This way 1st I try to handle the xml file by myself and than if I am not
successfull I try to resolve it on a catalog.
I really think the XMLSpy has a "bug" or just a limit.
I personally prefere other tools.
Have you got the latest versione of XMLSpy ?
Roberto Cisternino
> Hi Roberto,
>
> Thank you for your reply. Yes, that makes it clear, and I can follow your
> instructions. (btw English is not my first language either)
>
> Obviously, what you say applies to the XML editor your are using (which
> one is it?), as well as oXygen (according to Ken).
> However, it does not work for XMLSpy, which requires the schemaLocation
> attribute before it is searching the XML Catalog for a matching entry.
>
> So it seems that with XMLSpy, in order to validate a UBL gc file, one has
> to add manually the schemaLocation attribute (with the correct urn and a
> (possibly bogus) storage location).
>
> That also means that XMLSpy does not need the