Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Does IDREF require a matching ID?

From: "Karr, David" <david.karr@----.--->
To: "George Cristian Bina" <george@---------.--->
Date: 3/5/2007 5:56:00 PM
Perfect.  Thanks. 

> -----Original Message-----
> From: George Cristian Bina [mailto:george@o...] 
> Sent: Monday, March 05, 2007 9:52 AM
> To: Karr, David
> Cc: xml-dev@l...
> Subject: Re: [xml-dev] Does IDREF require a matching ID?
> 
> Hi,
> 
> If you have an IDREF attribute in the schema it is not 
> required for that schema to define an ID attribute. However, 
> when you validate an instance document the value for the 
> IDREF attribute needs to be specified in a component (element 
> or attribute) that have an ID type or a type derived form ID. 
> The part of the specification related with this is 
> http://www.w3.org/TR/xmlschema-1/#cvc-id
> ***
> 1 There must be no ID/IDREF binding in the item's [ID/IDREF 
> table] whose [binding] is the empty set.
> ***
> 
> Best Regards,
> George
> ---------------------------------------------------------------------
> George Cristian Bina
> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger 
> www.---.com
> 
> Karr, David wrote:
> > This may be a trivial question in this audience, but if you have an 
> > attribute defined in the schema as "xs:IDREF", does there 
> also have to 
> > be at least one attribute defined in the schema as "xs:ID", and a 
> > similar relationship in the XML instance document, with the IDREF 
> > value matching at least one ID attribute?  If this 
> relationship does 
> > not hold true, does this mean that the document is not valid?
> > 
> > If so, can you point me somewhere in the specs that state this?
> > 
> > 
> ______________________________________________________________________
> > _
> > 
> > XML-DEV is a publicly archived, unmoderated list hosted by OASIS to 
> > support XML implementation and development. To minimize spam in the 
> > archives, you must subscribe before posting.
> > 
> > [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> > Or unsubscribe: xml-dev-unsubscribe@l...
> > subscribe: xml-dev-subscribe@l... List archive: 
> > http://lists.xml.org/archives/xml-dev/
> > List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> > 
> 
> ______________________________________________________________
> _________
> 
> XML-DEV is a publicly archived, unmoderated list hosted by 
> OASIS to support XML implementation and development. To 
> minimize spam in the archives, you must subscribe before posting.
> 
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l... List archive: 
> http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> 
>


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent