[Bug 4995] Scoping of sml identity constraints (key, keyref, unique)


------- Comment #6 from virginia.smith@hp.com  2007-11-07 22:59 -------
Per our discussion on Nov 1, I think that SML should accommodate 2 scenarios:
1 - the desired sml:key is already available. Scoping reduces the proliferation
of the same sml:key and achieves other benefits as in comment #4.
2 - the desired sml:key is not available. In this case, the sml:key can reside
with the sml:keyref element as in comment #2, 2nd example.

Received on Wednesday, 7 November 2007 22:59:20 UTC