I think the problem is how to configure XMLSpy to
associate a schema location with a namespace.
Reviewing the XML Catalog specification, it seems
the catalogue is only useful for mapping URI
references to physical references. Without a
schemaLocation attribute in the genericode
instances there are no URI references with which to map using a catalogue.
I'm still in favour of not having schemaLocation
in the instances because, as discussed in the
teleconference, tying a schema to an instance
harkens back to the SGML days and limits the
flexibility of life-cycle management of the
instance and using different document models at
different times for a given instance.
If there is a problem with a particular tool, in
this case XMLSpy, then the question is what is
available in XMLSpy to map a namespace to a schema location?
In oXygen the menu item is
Options/Preferences/Editor/Default Schema
Association, and with that control I can
determine in my editing environment which schema
to use for which namespace. This allows me to
edit the instance without tying the instance to any particular schema.
So ... I can do what is necessary in oXygen ...
Juerg cannot, apparently, do the same in XMLSpy,
so the question is "is there some configuration
in XMLSpy to map a namespace to a schema?"
. . . . . . . . . . Ken
At 2006-09-25 08:59 +0100, Anthony B. Coates (Miley Watts) wrote:
>Dear Juerg,
>
> What information were you expecting XML
> Spy to use to look up a Schema
>location in the catalog? Were you expecting it to use the namespace URI?
>You seem surprised that it uses the Schema location.
>
> Cheers, Tony.
>
>On Mon, 25 Sep 2006 02:10:09 +0100, <>
>wrote:
>
>>Hi,
>>Is anyone else experiencing this issue:
>>When I edit and validate a UBL 2.0 supplied GC file using XMLSpy 2006
>>SP3, I get this error: "Unable to locate a reference to a supported
>>schema type (DTD, W3C Schema) within this document instance." So far, I
>>understand (well, it is more of a deducting guess really) that XMLSpy is
>>doing this:
>>
>>- if no schemaLocation is present, validation is stopped immediately
>>with the above error message
>>
>>- if the schemaLocation attribute is found (the named file however may
>>be bogus), then the CustomCatalog.xml file (part of XMLSpy installation,
>>and a subset of OASIS XML catalog) is checked:
>>
>> - if an matching uri name= entry is found in the catalog, then the
>>specified uri= file location is used for the validation (and the one
>>specified in schemaLocation is ignored).
>>
>> - if no matching uri name= entry is found, then the file name in the
>>schemaLocation attribute is used to validate, or an error reported if
>>that file cannot be found.
>>
>>It appears to me that XMLSpy requires a schemaLocation attribute even if
>>a XML catalog is used to define the storage location.
>>
>>Or is it something to do with my XMLSpy configuration?
>>Regards
>>Juerg
>
>
>
>--
>Anthony B. Coates
>Senior Partner
>Miley Watts LLP
>Experts In Data
>+44 (79) 0543 9026
>Data standards participant: ISO 20022 (ISO 15022 XML), ISO 19312,
>UN/CEFACT TMG, MDDL, FpML, UBL.
>
>
--
UBL/XML/XSLT/XSL-FO training: Vårø, Denmark 2006-10-02/06,11-20/24
UBL International 2006 2006-11-13/17 http://www.ublconference.com
World-wide corporate, govt. & user group UBL, XSL, & XML training.
G. Ken Holman mailto:
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/
Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05 http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
