- From: Wilson, Kirk D <Kirk.Wilson@ca.com>
- Date: Wed, 7 Nov 2007 18:28:50 -0500
- To: <public-sml@w3.org>
I support this proposal. Hopefully, it can be approved on Thurs conference call. (In absentia, I wish to vote "yes".) Kirk Wilson, Ph.D. Research Staff Member CA Labs 603 823-7146 -----Original Message----- From: public-sml-request@w3.org [mailto:public-sml-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org Sent: Wednesday, November 07, 2007 5:59 PM To: public-sml@w3.org Subject: [Bug 4995] Scoping of sml identity constraints (key, keyref, unique) http://www.w3.org/Bugs/Public/show_bug.cgi?id=4995 ------- 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 23:28:59 UTC