W3C home > Mailing lists > Public > xmlschema-dev@w3.org > May 2004

RE: Resolving ID usage in schemas

From: Bagepalli, Kiran <kbagepalli@informatica.com>
Date: Wed, 12 May 2004 12:11:11 -0700
Message-ID: <27D936D54B6740439A140C5CA02DFE5254E97D@ps2kex03.informatica.com>
To: "Xan Gregg" <xan.gregg@jmp.com>
Cc: <xmlschema-dev@w3.org>

Does that mean the below set of schemas are valid? Does ID attribute have applicability only with respect with the XML representation and not with the includes?

-----Original Message-----
From: Xan Gregg [mailto:xan.gregg@jmp.com]
Sent: Wednesday, May 12, 2004 11:47 AM
To: Bagepalli, Kiran
Cc: xmlschema-dev@w3.org
Subject: Re: Resolving ID usage in schemas

There's no conflict.  The xsd:include is not the same as an XInclude 
include.  xsd:include 'includes' the schema components that belong to 
the *parsed* included schema document.  It doesn't 'include' the xml 
representation of the included schema document, so the DTD for schemas 
is not applicable.  As far as I can tell, the id attribute doesn't 
constrain the schema components (only their XML representations).


On May 12, 2004, at 2:28 PM, Bagepalli, Kiran wrote:
> I had a question on  id handling in schemas.
> For eg. if I have schema A.xsd
> <xsd:schema id="ABC">
>   <xsd:include schemaLocation="B.xsd">
>   <xsd:element name="x" type="xsd:string">
> </xsd:schema>
> schema B.xsd
> <xsd:schema id="ABC">     //HERE ABC value is repeated as a id
> </xsd:schema>
> If we look at A.xsd as standalone XML having a id attribute it is 
> unique.
> However since it includes B.xsd does the id declared here considered a 
> duplicate.
> The schema spec is silent on this. On one front, the DTD for schemas 
> states that id is unique within the schema instance.
> On the other front it states schema document is a collection of 
> schemas resulting from the includes and imports.
> Is the id in B.xsd considered to have a duplicate value?
> Appreciate your help
> Thanks
> Kiran
Received on Wednesday, 12 May 2004 15:14:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:56:05 UTC