[
Lists Home |
Date Index |
Thread Index
]
The only way around this that comes to my mind is to add unique/key
constraints for every element that is of the pertinent datatypes (which
I'm sure you've already thought of). This is one downside of using
global datatypes.
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
Christian Nentwich wrote:
>
> All,
>
> we are currently looking at where uniqueness and key constraints can
> be applied to our schema.
>
> The problem is, the schema is semantically very rich, big on element
> reuse, and huge. As a consequence, most of the schema is expressed in
> terms of data types.
>
> There are a few constraints that have to hold for all instances of those
> data types, for example, "elements of type A must reference existing elements
> of type B", but schema lets you express key/uniqueness only *per-element*,
> not *per-datatype*. This is probably prohibitive from a schema management
> perspective.
>
> Is there any way around this, or a best practice approach to addressing
> this?
>
> Christian
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
begin:vcard
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard
|
