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)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] 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
Bruce WallaceSubject: KEYS (and UNIQUE) enforced?
Author: Bruce Wallace
Date: 09 Feb 2002 05:08 PM
build 69k doesnt seem to enforce KEY uniqueness when validating my XML against my Schema.
Doesnt your validator do this yet?
(see attached if it supposedly does).


Applicationexample.xml
XML file

Documentgg_products.xsd
Schema for XML doc

Posttop
(Deleted User) Subject: Re: KEYS (and UNIQUE) enforced?
Author: (Deleted User)
Date: 11 Feb 2002 06:11 AM
Hi Bruce,

At 17.18 09/02/2002 -0500, you wrote:
>From: "Bruce Wallace"
>
>build 69k doesnt seem to enforce KEY uniqueness when validating my XML
>against my Schema.
>Doesnt your validator do this yet?
>(see attached if it supposedly does).

Xerces does support enforcement of the key/keyref/unique definitions (even
if they warn their interpretation of the specs regarding keyref could be
non-standard - see http://xml.apache.org/xerces-c/schema.html for details).
The problem with your schema is that you have:

{xs:element name="products_by_vendor"}
{xs:complexType}
{xs:sequence}
{xs:element ref="vendor" maxOccurs="unbounded" /}
{/xs:sequence}
{/xs:complexType}

{xs:key name="PK"}
{xs:selector xpath="product"/}
{xs:field xpath="gg_sku"/}
{/xs:key}
{/xs:element}

But the XPath expression "product" will never be true, as the only child of
products_by_vendor is "vendor". If you change the xs:selector definition to
use "vendor/product", you will get two uniqueness errors.

However, your schema doesn't store the "product" elements just as direct
child of a "vendor", but also as part of a "suite"; so an xs:key structure
using the XPath expression "vendor/product" will not check for duplicate
products stored inside the suite. So, if what you want is to enforce that
no duplicate product IDs are present in the entire document you should use
".//product".

Hope this helps,

Alberto

   
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.