XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + XML Publisher Generation of XS... (3)
-> + SS Error: Segment UNB: Segment... (6)
-> + SS Enterprise 2007 R2 does not... (2)
-> + Generating XSD from XML - glob... (3)
-> + SS Enterprise 2007 R2 does not... (2)
-> + SS dies on xsl files loads (7)
-> + EDIFACT UNA section ? (3)
-> + SS closes when I attempt to sa... (2)
-> + Support for SPEC 2000 & genera... (6)
-> + Uninstall failure (10)
-> + WSDL to JAVA code (2)
-> + Can't Connect to DB - SQL 2005... (3)
-> + Java editor (3)
-> + Trouble getting my xsl scenari... (6)
-> + Activation Key Not Compatible.... (2)
-> + Stylus Studio 2007 R2 and Regi... (3)
-> - XSD file displayed in Excel an... (1)
-> + What Is This vmm File? (5)
-> + Another in Release 2 (3)
-> + Error on Release 2 (3)
-> + Query DB and convert output to... (11)
-> + import static HTML into XML Pu... (2)
-> + saxon 8.9 include path resolut... (10)
-> + Can't drag field delimiter (2)
-> + Enterprise Edition Relase 2 up... (4)
-> + Upgrade to Enterprise Release ... (2)
-> + HTML to XSLT wizard missing in... (7)
-> + sqlxml.dll error after update ... (4)
-> + Printing the tree or the grid ... (2)
-> + Sorting problem with xsl[decim... (2)
-> + 2007 R2 Saxon: missing Convert... (4)
-> + EDIFACT D96A INVRPT into a SQL... (2)
-> + any addon Feature or tool that... (2)
-> + Catalog Assistance - (3)
-> + WYSIWYG does not show (3)
-> + HL7 support in Stylus (2)
-> + Xerces parser missing from Sty... (4)
-> - automatic DTD verification bef... (1)
-> + Try this (2)
-> - 2007 R2 java code generation -... (1)
-> + 2007 R2 Java built-in XSLT (4)
-> + 2007 R2 saxon 8.9 debug proble... (2)
-> + Stylus Studio Schema Validatio... (3)
-> + Bug: losing items when editing... (2)
-> + 2007 R2 Java built-in XSLT (2)
-> + XML->EDI: inconsistent treatme... (13)
-> + 2007 R2 global java classpath (2)
-> + New Web Service Call Failing (6)
-> + Grid view for nested tables (2)
-> - Revisit Old Problem from last ... (1)
-> + Install Question (3)
-> + hex value problem (5)
-> + WSDL Overview Diagram? (2)
-> + Outputing HTML from an XSLT 2.... (2)
-> + Stylus Studio Schema Publicati... (2)
-> + Re-usable XML Schema (3)
-> + .net xslt extension objects (6)
-> + InstallShield problem (2)
-> + Changing default XSLT processo... (2)
-> - SS incorrectly handles paramet... (1)
-> + Can't add file to project (7)
-> + Stylus invoking when i login i... (2)
-> + How to utilize Saxon (custom) ... (3)
-> + xsl:decimal-format (5)
-> + Hidden Costs of SS? (2)
-> + Eclipse Plugin available? (4)
-> + Having trouble with xpath quer... (2)
-> + Specifying processor to use wi... (3)
-> + MySQL or Generic JDBC Data Sup... (8)
-> + JAXB java generation doesn't s... (3)
-> - Eclipse (1)
-> + XSTL Debugger not working for ... (6)
-> + SS w/ Visual Studio and VSS (2)
-> + SS crashes on load (2)
-> + Can't find file ... then does,... (2)
-> + Diff folders not working (4)
-> + last node in preceding-sibling (3)
-> + SQLXML and Subquery (2)
-> + Xquery - No ReleationalDB opti... (3)
-> + Is a default adapter - not Tid... (8)
-> + Need actual (18)
-> + include path for external enti... (2)
-> + xpath query in SQL server (4)
-> + XPATH Query that works in 2006... (4)
-> + Need help with XML Assignment (3)
-> + Java Compiler in Windows Vista... (6)
-> + Sense:X Only Shows One Enumera... (3)
-> + adding tables and relationship... (6)
-> + preview automatically starts a... (12)
-> + French date in excel 97 using ... (2)
-> + How to maintain large XSL (2)
-> + French date in excel 97 using ... (2)
-> + How to pass EDIFACT as paramet... (3)
-> + C# Generation from XSD (5)
-> + Oracle RDBMS <-> .XSD (2)
-> + Support for Berkeley DB XML 2.... (2)
-> + conrext lost with xslt 2.0 for... (4)
-> + BizTalk schema problem (4)
-> + MSXML 6 properties resolveExte... (3)
-> + Deployment adapters and lookup... (2)
-- Previous [1621-1640] [1641-1660] [1661-1680] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
(Deleted User) Subject: Stylus doesn't know XSD types.
Author: (Deleted User)
Date: 11 Sep 2001 07:23 AM
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


DocumentBookStore.xsd


Documentbooks(2).xml

Postnext
(Deleted User) Subject: Stylus doesn't know XSD types.
Author: (Deleted User)
Date: 11 Sep 2001 07:32 AM
Sorry, the version info is:
Stylus v 3.1 beta build 59
O/S: Windows 2000 Pro


Bart Jenkins,CTO
Globeflow SA

Postnext
(Deleted User) Subject: Re: Stylus doesn't know XSD types.
Author: (Deleted User)
Date: 11 Sep 2001 09:11 AM
--=====================_15209169==_.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable

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:

Features/Datatypes Supported
....
Subset of Built-in Datatypes
· Primitive Datatypes
string
boolean
decimal
hexbinary
base64binary
· 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

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

·       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


Alberto

--=====================_15209169==_.ALT--

Postnext
(Deleted User) Subject: Stylus doesn't know XSD types.
Author: (Deleted User)
Date: 14 Sep 2001 06:53 AM
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?

Bart Jenkins, CTO
Globeflow SA

Postnext
(Deleted User) Subject: Re: Stylus doesn't know XSD types.
Author: (Deleted User)
Date: 14 Sep 2001 07:29 AM
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?

Not yet; we will think about it...

Alberto

Posttop
Minollo I.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

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.