- From: Markus Gamperl <markus.gamperl@gmx.at>
- Date: Thu, 15 Feb 2007 10:53:38 +0100
- To: "Michael Kay" <mike@saxonica.com>, xmlschema-dev@w3.org
Hi Michael! You are totally right! After defining a xmlns:x prefix in my schema (analog to my default namespace) and adding the prefix in my constraint defintion, validation works well! <xs:unique name="uniquepreis"> <xs:selector xpath="x:preiszeile"/> <xs:field xpath="x:zweig"/> <xs:field xpath="x:herkunft"/> </xs:unique> But why isn't the default namespace enough within xs:unique? Is this the definition of xs:unique? What's the sense of the default namespace... Thanks a lot! Markus -------- Original-Nachricht -------- Datum: Thu, 15 Feb 2007 09:30:18 -0000 Von: "Michael Kay" <mike@saxonica.com> An: "\'Markus Gamperl\'" <markus.gamperl@gmx.at>, xmlschema-dev@w3.org CC: Betreff: RE: RE: RE: unique question > > > Now validate it again and your bad file will be shown as > > valid file. This must be namespace problem - do you have an idea? > > If your elements are in a namespace, then the path expressions used in > defining the constraint need to use prefixed element names. > > Michael Kay > http://www.saxonica.com/ > -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out
Received on Thursday, 15 February 2007 09:53:47 UTC