XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » SS4.5 103k Bug: DTD to XSD wizard makes bad schema
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + element type must not contain ... (3)
-> + XML to .txt file (7)
-> + Modifying a XSL-FO report (5)
-> + Retrievning multiple values...... (2)
-> + does Stylus Enterprise work wi... (2)
-> + MSSQL to 837P conversion (4)
-> + Generating XML files accesing ... (6)
-> + How to bold text using XSL (6)
-> + Different heading based on pag... (3)
-> + Code folding (2)
-> + Bad param=value pair on comman... (2)
-> + Saving an XML file (2)
-> + stylus adding random non print... (2)
-> + Displaying Base64Binary as Ima... (6)
-> - probleme de representation d'i... (1)
-> + SS 2008 error message not disp... (8)
-> + XQuery external variable conve... (4)
-> + encodings available (3)
-> + stand-alone application file n... (4)
-> + Windows Installer Dialog Box a... (4)
-> + Block search and replace (2)
-> + Problem with validation (3)
-> + ISA12 vs GS08 (5)
-> + Web Service Call failure... an... (11)
-> + Quotes in xpath query (3)
-> + Java Built-in processor no lon... (6)
-> + Dynamic input and output names (8)
-> + Java built-in parser (3)
-> + Contains an invalid path (2)
-> + Wizard XML Schema to XML (2)
-> + XML to EDI (14)
-> + Computer with original install... (2)
-> + using Custom Tool - passing ar... (3)
-> + Non-printable special characte... (3)
-> + Transfer Options (Settings, Pr... (2)
-> + Enterprise Edition, Rel. 3, Bu... (9)
-> + Need help with xsl file and xm... (2)
-> + Upgrading and retaining settin... (4)
-> + saxon9.dll etc. missing (2)
-> - Error on using XQuery File in ... (1)
-> - Strange Dialog Box (1)
-> + Studio Crashes in schema edito... (3)
-> + Xml to XMl Conversion (2)
-> + Unable to create a complex typ... (2)
-> + Error message wen trying run j... (2)
-> - XSLT Mapper question... (1)
-> + Dcument Wizard XSLT Editor Tab... (2)
-> + Beginner Question - XPath with... (2)
-> + Trying to generate .net code w... (2)
-> + duplicate values in variable w... (5)
-> + Java Runtime Environment libra... (4)
-> + programmatically generate XML ... (4)
-> + Help Loading Oracle BI Publish... (4)
-> + [French] xsl <=> report (3)
-> + XML Diff (3)
-> + StylusStudio 2008, saxon saxon... (6)
-> + Msql Table err:FODC0004 Table ... (2)
-> + The evaluation period for Data... (2)
-> + Mysql to XML (2)
-> + Is there a Collapse All nodes ... (2)
-> + flat file conversion with CDAT... (4)
-> + Struzzo.exe eats up %40 CPU ba... (2)
-> + schematron support? (11)
-> + XML Generator did not generate... (2)
-> + Nesting XML files (2)
-> + Web Service Call fails - targe... (5)
-> + getting not valid for content ... (2)
-> - element modem was referenced i... (1)
-> + xerces-c++ xml parser (2)
-> + movie.dtd (2)
-> + HELP! Stylus Studio 2008 Enter... (3)
-> + Xalan problem with xsl:attribu... (2)
-> + Breakpoints being ignored (12)
-> + Need a new key for Stylus Stud... (2)
-> + Global parameters are not reco... (4)
-> + mySQL DB Connection 2 (10)
-> + Using Data Direct xQuery to ag... (4)
-> + stylusXslt command line -- XSL... (15)
-> + XSLT processor using EXSLT fun... (2)
-> + Integrating Omni Mark (2)
-> + EDI Standards to gXML (2)
-> + flat file conversion (3)
-> + EDI to XML: Invalid URI error (3)
-> + Validating and XML Schema (6)
-> + XSD to DDL (MS-SQL/2005) (6)
-> + xml converter cant encode 0x19 (4)
-> + XSD Help Needed (2)
-> + How do you delete a field in a... (2)
-> + Disable page breaks (3)
-> + XSD semantic structure compari... (3)
-> + Studio Crashes On File Open (7)
-> + Which parser is used by Stylus... (2)
-> + How to DIFF XML windows with d... (3)
-> + Automation using Visual Studio (7)
-> + CSV to XML conversion help (2)
-> + XML tree help (3)
-> + java.lang.NullPointerException... (2)
-> + Creating schema from xml - how... (3)
-> + Mismatch between intellisense ... (4)
-> + Using FOP 0.94 in XML Pipeline (2)
-- Previous [1081-1100] [1101-1120] [1121-1140] 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
Lee HumphriesSubject: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
Author: Lee Humphries
Date: 24 Nov 2002 09:59 PM
The attached DTD when run through the DTD to XSD wizard generates an XSD schema that fails validation - specifically the Unique Particle Attribution rule.


DocumentTree(1).dtd


DocumentTree(1).xsd
The resultant XSD that fails validation
Postnext
Ivan PedruzziSubject: RE: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
Author: Ivan Pedruzzi
Date: 24 Nov 2002 11:29 PM
Lee,
My understanding is that your DTD can't be mapped to xsd (1:1)
The following should be a reasonable solution

{?xml version="1.0"?}
{xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"}
{xsd:element name="Leaf" type="xsd:string"/}
{xsd:element name="Flower" type="xsd:string"/}
{xsd:element name="Branch"}
{xsd:complexType}
{xsd:sequence}
{xsd:choice}
{xsd:element ref="Leaf"/}
{xsd:element ref="Flower"/}
{/xsd:choice}
{xsd:sequence}
{xsd:element ref="Leaf"/}
{xsd:element ref="Flower"/}
{/xsd:sequence}
{/xsd:sequence}
{/xsd:complexType}
{/xsd:element}
{xsd:element name="Root"}
{xsd:complexType}
{xsd:sequence maxOccurs="unbounded"}
{xsd:element ref="Branch"/}
{/xsd:sequence}
{/xsd:complexType}
{/xsd:element}
{/xsd:schema}

Ivan

> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager]
> Sent: Sunday, November 24, 2002 10:16 PM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
>
>
> From: "Lee Humphries"
>
> The attached DTD when run through the DTD to XSD wizard
> generates an XSD schema that fails validation - specifically
> the Unique Particle Attribution rule.
>
>
>
> To reply: mailto:stylus-studio-tech.6051@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>
>

Postnext
Lee HumphriesSubject: RE: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
Author: Lee Humphries
Date: 25 Nov 2002 12:42 AM
Sorry Ivan, not even close.
What you've written is effectively:
((Leaf | Flower), Leaf, Flower)
Whereas I'm wanting:
(Leaf | Flower | (Leaf, Flower))
i.e. Leaf or Flower or both

Peculiarly this seems to be something very difficult to do with XML schemas, even though it's dead easy with DTDs. That was why I was trying your DTD to XSD wizard.

I've checked the standard and the construct the Wizard generated very definitely violates the Unique Particle Attribution rule. But what I find odd is that it's the rule itself that seems to have the bug. http://www.w3.org/TR/xmlschema-1/#non-ambig
"A content model will violate the unique attribution constraint if it contains two particles which ˇoverlapˇ and which either
are both in the {particles} of a choice or all group "
Postnext
Ivan PedruzziSubject: RE: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
Author: Ivan Pedruzzi
Date: 25 Nov 2002 01:59 AM

Yes you are absolutely right.
This one is the closest definition I can think.

{xsd:element name="Branch"}
{xsd:complexType}>
{xsd:sequence}
{xsd:element ref="Leaf" minOccurs="0"/}
{xsd:element ref="Flower" minOccurs="0"/}
{/xsd:sequence}
{/xsd:complexType}
{/xsd:element}

It validates Leaf or Flower or both but also an empty content.
May be someone will come out with a better idea.

Ivan


> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager]
> Sent: Monday, November 25, 2002 12:59 AM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: RE: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
>
>
> From: "Lee Humphries"
>
> Sorry Ivan, not even close.
> What you've written is effectively:
> ((Leaf | Flower), Leaf, Flower)
> Whereas I'm wanting:
> (Leaf | Flower | (Leaf, Flower))
> i.e. Leaf or Flower or both
>
> Peculiarly this seems to be something very difficult to do
> with XML schemas, even though it's dead easy with DTDs. That
> was why I was trying your DTD to XSD wizard.
>
> I've checked the standard and the construct the Wizard
> generated very definitely violates the Unique Particle
> Attribution rule. But what I find odd is that it's the rule
> itself that seems to have the bug.
> http://www.w3.org/TR/xmlschema-1/#non-ambig
> "A content model
> will violate the unique attribution constraint if it contains
> two particles which .overlap. and which either
> are both in the {particles} of a choice or all group "
>
>
>
> To reply: mailto:stylus-studio-tech.6053@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>
>

Postnext
Lee HumphriesSubject: RE: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
Author: Lee Humphries
Date: 25 Nov 2002 06:27 PM
Hi Ivan,

I've received some advice that
(Leaf | Flower (Leaf, Flower))
is actually bad DTD, and
((Leaf, Flower?) | Flower)
is much better. I tried this and it worked after converting to XSD.

However, I also tried
(Leaf | (Leaf? | Flower))
and converted that to an XSD and I still got a Unique Particle Attribution rule failure.

Any ideas why there's a difference?

Regards, Lee
Posttop
Ivan PedruzziSubject: RE: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
Author: Ivan Pedruzzi
Date: 26 Nov 2002 11:36 AM
Lee,

After discussing with Alby, this is what I believe is happening

1) it validates

When the validator encounter "Leaf" it knows that it could find
"Flower" too.
The presence of "Leaf" is not ambiguous






minOccurs="0"/>






2) it doesn't validate

When the validator encounter "Leaf" it can not determine what
branch of choice to pick
The presence of "Leaf" is ambiguous







minOccurs="0"/>





Ivan






> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager]
> Sent: Monday, November 25, 2002 6:44 PM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: RE: SS4.5 103k Bug: DTD to XSD wizard makes bad schema
>
>
> From: "Lee Humphries"
>
> Hi Ivan,
>
> I've received some advice that
> (Leaf | Flower (Leaf, Flower))
> is actually bad DTD, and
> ((Leaf, Flower?) | Flower)
> is much better. I tried this and it worked after converting to XSD.
>
> However, I also tried
> (Leaf | (Leaf? | Flower))
> and converted that to an XSD and I still got a Unique
> Particle Attribution rule failure.
>
> Any ideas why there's a difference?
>
> Regards, Lee
>
>
>
> To reply: mailto:stylus-studio-tech.6057@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>
>

   
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.