Home » Archived » XML Schema Definition (XSD) » Preferences: XML Catalog - problem with relative schemaLocation's
| Preferences: XML Catalog - problem with relative schemaLocation's [message #58481] |
Thu, 10 March 2005 18:54  |
Eclipse User |
|
|
|
Originally posted by: ushakov.int.com.ru
Hi,
I am trying to make the local schema cache work for me, and got a trouble
with resolution of relative references to imported schemas.
Namely, I try to get xhtml-basic10.xsd into the local cache.
I start with making three entries in the "Preferences: XML Catalog" section,
with "External schema sources" being a name of a local project:
1:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd
2:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-model-1.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd
3:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-modules-1.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd
The result is a number of validation errors that originate to the problem
that xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd were not
found.
If I remove the first cache entry (for xhtml-basic10.xsd), then
xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd are resolved ok
(evidently, from the cache), and the errors move to the nested xsd's
referenced from these two files.
All the imported schema references in this W3C schema are relative. So it
looks like some problem in resolving relative references for schemas in the
local XML Catalog.
Is it the real state of the art or am I doing anything wrong?
Regards,
Sergey
|
|
|
| Re: Preferences: XML Catalog - problem with relative schemaLocation's [message #58485 is a reply to message #58481] |
Fri, 11 March 2005 07:02  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------020605050505000506080501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sergey,
I don't know anything about the XML catalog; that must be coming from WTP?
It's important to realize that relative references in a schema are made
absolute relative to their containing resource/document's absolute URI
(just as for hrefs in a .html document). E.g., in schema
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd,
the relative reference
<xs:include schemaLocation="xhtml-basic10-model-1.xsd">
will be resolved to
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd.
This resolution is only done if the containing resource has an absolute
URI, i.e., if the URI starts with file:, http:, platform:, and so on.
Because of this, I generally would not expect a catalog to contain
entries for relative URIs. (But as I said, I don't know the details of
how the XML catalog is designed to work.)
Sergey Ushakov wrote:
>Hi,
>
>I am trying to make the local schema cache work for me, and got a trouble
>with resolution of relative references to imported schemas.
>
>Namely, I try to get xhtml-basic10.xsd into the local cache.
>
>I start with making three entries in the "Preferences: XML Catalog" section,
>with "External schema sources" being a name of a local project:
>
>1:
>External schema
> sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
>ic10.xsd
>Schema Location
> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd
>
>2:
>External schema
> sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
>ic10-model-1.xsd
>Schema Location
> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd
>
>3:
>External schema
> sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
>ic10-modules-1.xsd
>Schema Location
> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd
>
>The result is a number of validation errors that originate to the problem
>that xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd were not
>found.
>
>If I remove the first cache entry (for xhtml-basic10.xsd), then
>xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd are resolved ok
>(evidently, from the cache), and the errors move to the nested xsd's
>referenced from these two files.
>
>All the imported schema references in this W3C schema are relative. So it
>looks like some problem in resolving relative references for schemas in the
>local XML Catalog.
>
>Is it the real state of the art or am I doing anything wrong?
>
>Regards,
>Sergey
>
>
>
>
>
--------------020605050505000506080501
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Sergey,<br>
<br>
I don't know anything about the XML catalog; that must be coming from
WTP? <br>
<br>
It's important to realize that relative references in a schema are made
absolute relative to their containing resource/document's absolute URI
(just as for hrefs in a .html document). E.g., in schema
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd</a>,
the relative reference<br>
<blockquote><xs:include
schemaLocation="xhtml-basic10-model-1.xsd"><br>
</blockquote>
will be resolved to
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd</a>.
This resolution is only done if the containing resource has an absolute
URI, i.e., if the URI starts with file:, http:, platform:, and so on. <br>
<br>
Because of this, I generally would not expect a catalog to contain
entries for relative URIs. (But as I said, I don't know the details of
how the XML catalog is designed to work.)<br>
<br>
<br>
Sergey Ushakov wrote:
<blockquote cite="midd0qmmp$nn6$1@www.eclipse.org" type="cite">
<pre wrap="">Hi,
I am trying to make the local schema cache work for me, and got a trouble
with resolution of relative references to imported schemas.
Namely, I try to get xhtml-basic10.xsd into the local cache.
I start with making three entries in the "Preferences: XML Catalog" section,
with "External schema sources" being a name of a local project:
1:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10.xsd
Schema Location
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd</a>
2:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-model-1.xsd
Schema Location
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd</a>
3:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-modules-1.xsd
Schema Location
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd</a>
The result is a number of validation errors that originate to the problem
that xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd were not
found.
If I remove the first cache entry (for xhtml-basic10.xsd), then
xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd are resolved ok
(evidently, from the cache), and the errors move to the nested xsd's
referenced from these two files.
All the imported schema references in this W3C schema are relative. So it
looks like some problem in resolving relative references for schemas in the
local XML Catalog.
Is it the real state of the art or am I doing anything wrong?
Regards,
Sergey
</pre>
</blockquote>
<br>
</body>
</html>
--------------020605050505000506080501--
|
|
|
| Re: Preferences: XML Catalog - problem with relative schemaLocation's [message #58549 is a reply to message #58485] |
Sat, 12 March 2005 22:29 |
| Eclipse User |
|
|
|
Originally posted by: ushakov.int.com.ru
Yes Ed, thanks. It really comes from WTP/WST - I've got it now :)
Sorry, I'm still not very comfortable with different Eclipse projects and
their functionality, and sometimes believe that bread loafs grow on the
trees... :)
You are absolutely right IMHO about relative references resolution. Hope not
only IMHO :)
Standard W3C schemas seem to have correct references. At least they do
validate if not cached :)
I believe this is some issue in the relative URI resolver for cached schemas
in this WTP/WST schema cache.
I'll try to contact WTP/WST folks...
Regards,
Sergey
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:d0s1df$jiu$1@www.eclipse.org...
Sergey,
I don't know anything about the XML catalog; that must be coming from WTP?
It's important to realize that relative references in a schema are made
absolute relative to their containing resource/document's absolute URI (just
as for hrefs in a .html document). E.g., in schema
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd,
the relative reference
<xs:include schemaLocation="xhtml-basic10-model-1.xsd">
will be resolved to
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd.
This resolution is only done if the containing resource has an absolute URI,
i.e., if the URI starts with file:, http:, platform:, and so on.
Because of this, I generally would not expect a catalog to contain entries
for relative URIs. (But as I said, I don't know the details of how the XML
catalog is designed to work.)
Sergey Ushakov wrote:
Hi,
I am trying to make the local schema cache work for me, and got a trouble
with resolution of relative references to imported schemas.
Namely, I try to get xhtml-basic10.xsd into the local cache.
I start with making three entries in the "Preferences: XML Catalog" section,
with "External schema sources" being a name of a local project:
1:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd
2:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-model-1.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd
3:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-modules-1.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd
The result is a number of validation errors that originate to the problem
that xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd were not
found.
If I remove the first cache entry (for xhtml-basic10.xsd), then
xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd are resolved ok
(evidently, from the cache), and the errors move to the nested xsd's
referenced from these two files.
All the imported schema references in this W3C schema are relative. So it
looks like some problem in resolving relative references for schemas in the
local XML Catalog.
Is it the real state of the art or am I doing anything wrong?
Regards,
Sergey
|
|
|
| Re: Preferences: XML Catalog - problem with relative schemaLocation's [message #594473 is a reply to message #58481] |
Fri, 11 March 2005 07:02 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------020605050505000506080501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sergey,
I don't know anything about the XML catalog; that must be coming from WTP?
It's important to realize that relative references in a schema are made
absolute relative to their containing resource/document's absolute URI
(just as for hrefs in a .html document). E.g., in schema
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd,
the relative reference
<xs:include schemaLocation="xhtml-basic10-model-1.xsd">
will be resolved to
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd
This resolution is only done if the containing resource has an absolute
URI, i.e., if the URI starts with file:, http:, platform:, and so on.
Because of this, I generally would not expect a catalog to contain
entries for relative URIs. (But as I said, I don't know the details of
how the XML catalog is designed to work.)
Sergey Ushakov wrote:
>Hi,
>
>I am trying to make the local schema cache work for me, and got a trouble
>with resolution of relative references to imported schemas.
>
>Namely, I try to get xhtml-basic10.xsd into the local cache.
>
>I start with making three entries in the "Preferences: XML Catalog" section,
>with "External schema sources" being a name of a local project:
>
>1:
>External schema
> sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
>ic10.xsd
>Schema Location
> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd
>
>2:
>External schema
> sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
>ic10-model-1.xsd
>Schema Location
> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd
>
>3:
>External schema
> sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
>ic10-modules-1.xsd
>Schema Location
> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd
>
>The result is a number of validation errors that originate to the problem
>that xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd were not
>found.
>
>If I remove the first cache entry (for xhtml-basic10.xsd), then
>xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd are resolved ok
>(evidently, from the cache), and the errors move to the nested xsd's
>referenced from these two files.
>
>All the imported schema references in this W3C schema are relative. So it
>looks like some problem in resolving relative references for schemas in the
>local XML Catalog.
>
>Is it the real state of the art or am I doing anything wrong?
>
>Regards,
>Sergey
>
>
>
>
>
--------------020605050505000506080501
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Sergey,<br>
<br>
I don't know anything about the XML catalog; that must be coming from
WTP? <br>
<br>
It's important to realize that relative references in a schema are made
absolute relative to their containing resource/document's absolute URI
(just as for hrefs in a .html document). E.g., in schema
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd</a>,
the relative reference<br>
<blockquote><xs:include
schemaLocation="xhtml-basic10-model-1.xsd"><br>
</blockquote>
will be resolved to
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd</a>.
This resolution is only done if the containing resource has an absolute
URI, i.e., if the URI starts with file:, http:, platform:, and so on. <br>
<br>
Because of this, I generally would not expect a catalog to contain
entries for relative URIs. (But as I said, I don't know the details of
how the XML catalog is designed to work.)<br>
<br>
<br>
Sergey Ushakov wrote:
<blockquote cite="midd0qmmp$nn6$1@www.eclipse.org" type="cite">
<pre wrap="">Hi,
I am trying to make the local schema cache work for me, and got a trouble
with resolution of relative references to imported schemas.
Namely, I try to get xhtml-basic10.xsd into the local cache.
I start with making three entries in the "Preferences: XML Catalog" section,
with "External schema sources" being a name of a local project:
1:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10.xsd
Schema Location
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd</a>
2:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-model-1.xsd
Schema Location
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd</a>
3:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-modules-1.xsd
Schema Location
<a class="moz-txt-link-freetext" href=" http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd"> http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd</a>
The result is a number of validation errors that originate to the problem
that xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd were not
found.
If I remove the first cache entry (for xhtml-basic10.xsd), then
xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd are resolved ok
(evidently, from the cache), and the errors move to the nested xsd's
referenced from these two files.
All the imported schema references in this W3C schema are relative. So it
looks like some problem in resolving relative references for schemas in the
local XML Catalog.
Is it the real state of the art or am I doing anything wrong?
Regards,
Sergey
</pre>
</blockquote>
<br>
</body>
</html>
--------------020605050505000506080501--
|
|
|
| Re: Preferences: XML Catalog - problem with relative schemaLocation's [message #594484 is a reply to message #58485] |
Sat, 12 March 2005 22:29 |
| Eclipse User |
|
|
|
Originally posted by: ushakov.int.com.ru
Yes Ed, thanks. It really comes from WTP/WST - I've got it now :)
Sorry, I'm still not very comfortable with different Eclipse projects and
their functionality, and sometimes believe that bread loafs grow on the
trees... :)
You are absolutely right IMHO about relative references resolution. Hope not
only IMHO :)
Standard W3C schemas seem to have correct references. At least they do
validate if not cached :)
I believe this is some issue in the relative URI resolver for cached schemas
in this WTP/WST schema cache.
I'll try to contact WTP/WST folks...
Regards,
Sergey
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:d0s1df$jiu$1@www.eclipse.org...
Sergey,
I don't know anything about the XML catalog; that must be coming from WTP?
It's important to realize that relative references in a schema are made
absolute relative to their containing resource/document's absolute URI (just
as for hrefs in a .html document). E.g., in schema
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd,
the relative reference
<xs:include schemaLocation="xhtml-basic10-model-1.xsd">
will be resolved to
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd
This resolution is only done if the containing resource has an absolute URI,
i.e., if the URI starts with file:, http:, platform:, and so on.
Because of this, I generally would not expect a catalog to contain entries
for relative URIs. (But as I said, I don't know the details of how the XML
catalog is designed to work.)
Sergey Ushakov wrote:
Hi,
I am trying to make the local schema cache work for me, and got a trouble
with resolution of relative references to imported schemas.
Namely, I try to get xhtml-basic10.xsd into the local cache.
I start with making three entries in the "Preferences: XML Catalog" section,
with "External schema sources" being a name of a local project:
1:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10.xsd
2:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-model-1.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-model-1.xsd
3:
External schema
sources/www.w3.org/TR/2004/WD-xhtml-modularization-20040218/ SCHEMA/xhtml-bas
ic10-modules-1.xsd
Schema Location
http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/S CHEMA/xhtml-basic10-modules-1.xsd
The result is a number of validation errors that originate to the problem
that xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd were not
found.
If I remove the first cache entry (for xhtml-basic10.xsd), then
xhtml-basic10-model-1.xsd and xhtml-basic10-modules-1.xsd are resolved ok
(evidently, from the cache), and the errors move to the nested xsd's
referenced from these two files.
All the imported schema references in this W3C schema are relative. So it
looks like some problem in resolving relative references for schemas in the
local XML Catalog.
Is it the real state of the art or am I doing anything wrong?
Regards,
Sergey
|
|
|
Goto Forum:
Current Time: Thu Mar 13 13:55:35 EDT 2025
Powered by FUDForum. Page generated in 0.04300 seconds |
Home