Using the following simple XML and XSD, the Stylus studio does not recognize a legal XSD type ("date or dateTime"). It gives me the following error: "Type not found in http://www.w3.org/2001/XMLSchema:date"
This works fine when I run it through the Xerces SAXWriter sample parser using Xerces 1.4.2
At 07.29 11/09/2001 -0400, you wrote:
>From: "Bart Jenkins"
>
>Using the following simple XML and XSD, the Stylus studio does not
>recognize a legal XSD type ("date or dateTime"). It gives me the
>following error: "Type not found in http://www.w3.org/2001/XMLSchema:date"
This is the expected behavior; Xerces 1.5.1 (that we are using to perform
XMLSchema validation) currently supports only a subset of the XMLSchema
specs (see the document at http://xml.apache.org/xerces-c/schema.html).
What you are hitting is explained in this paragraph:
>This works fine when I run it through the Xerces SAXWriter sample parser
>using Xerces 1.4.2
You can parse it fine using Xerces 1.4.2 (and 1.5.1 too) but simply because=
SAXWriter is not enabling XMLSchema validation (so, you are not validating=
your file at all) and the error comes up only when you follow the
xsi:namespaceLocation directive and load the BookStore.xsd file
Alberto
--=====================_15209169==_.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
At 07.29 11/09/2001 -0400, you wrote:
From: "Bart Jenkins"
<bjenkins@globeflow.com>
Using the following simple XML and XSD, the Stylus studio does not
recognize a legal XSD type ("date or dateTime"). It gives
me the following error: "Type not found in http://www.w3.org/2001/XMLSchema:date"
This is the expected behavior; Xerces 1.5.1 (that we are using to perform
XMLSchema validation) currently supports only a subset of the XMLSchema
specs (see the document at http://xml.apache.org/xerces-c/schema.html).
What you are hitting is explained in this paragraph:
Features/Datatypes Supported
...
Subset of Built-in Datatypes
· =x-tab>Primitive
Datatypes
string
boolean
decimal
hexbinary
base64binary
· &nb=sp;Derived
Datatypes
integer
So, no support for xsd:date and xsd:dateTime yet
This works fine when I run it
through the Xerces SAXWriter sample parser using Xerces
1.4.2
You can parse it fine using Xerces 1.4.2 (and 1.5.1 too) but simply
because SAXWriter is not enabling XMLSchema validation (so, you are not
validating your file at all) and the error comes up only when you follow
the xsi:namespaceLocation directive and load the BookStore.xsd
file
NO. An important point is I was using the JAVA version of the Xerces parser which must be further along in terms of compliance than the C or C++ version. I EXPLICITLY enabled validation with the Xerces 1.4.2 parser (and in fact tested validation of date by putting in a 13th month and it correctly flagged it as an error).
Since you provide a mechanism for using an external parser (which we use instead of the built-in), have you thought of extending that external usage to Schema validation?
At 07.00 14/09/2001 -0400, you wrote:
>From: "Bart Jenkins"
>
>NO. An important point is I was using the JAVA version of the Xerces
>parser which must be further along in terms of compliance than the C or
>C++ version. I EXPLICITLY enabled validation with the Xerces 1.4.2 parser
>(and in fact tested validation of date by putting in a 13th month and it
>correctly flagged it as an error).
Sorry, I didn't get that you were referring to Xerces-J. Yes, the Java
version is already providing a pretty much complete support of XMLSchema,
while the C++ version is scheduled to be complete by the end of the year.
>Since you provide a mechanism for using an external parser (which we use
>instead of the built-in), have you thought of extending that external
>usage to Schema validation?
Subject:Re: Stylus doesn't know XSD types. Author:Minollo I. Date:14 Sep 2001 09:29 AM
>...
>Since you provide a mechanism for using an external parser (which we use
>instead of the built-in), have you thought of extending that external
>usage to Schema validation?
Stylus Studio has a mechanism for external XSLT processing, not XML parsing.
Minollo