Lists Home |
Date Index |
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
Is there any way around this, or a best practice approach to addressing