5064 2007-09-20 20:29:25 +0000 On which component(s) are SML reference constraints specified? 2008-02-20 02:56:23 +0000 1 1 1 Unclassified SML Core FPWD PC Windows XP RESOLVED FIXED resolved P2 normal LC 5063 1 sandygao kumarp public-sml oldest_to_newest 16733 0 sandygao 2007-09-20 20:29:25 +0000 This involves sml:target* and SML identity constraints. There are 3 kinds of <xs:element> elements in schema documents: 1 For global element declaration 2 For local element declaration 3 For reference to global element declaration On which of the above cases are sml:target* and sml:key/keyref/unique allowed to be specified? And to which schema component(s) (element declaration or particle) are these constraints attached to? If these constraints are attached to element declarations, then they should not be allowed on case #3; if they are attached to particles, then they should not be allowed on case #1. So if we want to allow them being specified in all 3 cases, then the constraints need to be attached to both element declarations and particles, and we need to explain what happens if the same kind of constraint is specified both on a global element declaration G and on a reference to G. For example, <xs:schema> <xs:element name="global" targetType="type1"> <xs:complexType name="someType"> <xs:sequence> <xs:element ref="global" targetType="type2"/> </xs:sequence> </xs:complextype> </xs:schema> 16735 1 pratul.dublish 2007-09-20 21:43:24 +0000 a. These constraints are supported on global and local element declarations (1 and 2 in the bug's description) b. These should be attached to the element declaration schema component 17414 2 pratul.dublish 2007-10-25 18:46:39 +0000 Please fix as per Pratul's comment - decision taken on 10/25 call 17653 3 virginia.smith 2007-11-10 00:58:47 +0000 Can't resolve this independent of bug 5063. Moving back to needsAgreement and setting it dependent on bug 5063. 17960 4 kumarp 2007-12-05 07:02:00 +0000 The proposal added to bug# 5063 comment# 6 also addresses this bug. 18034 5 virginia.smith 2007-12-10 22:15:21 +0000 Reassigning this bug back to default since it might be easier to fix along with 5063. 18267 6 kumarp 2008-01-10 20:32:31 +0000 resolution in conf call on 1/10: proposal accepted as stated in comment# 9 of bug# 5063 18788 7 kumarp 2008-02-06 07:48:19 +0000 The fix applied for bug# 5063 also includes the fix for this bug. Please take a look at sml-diff.html attached to bug# 5063. 19059 8 virginia.smith 2008-02-14 19:52:10 +0000 Fix per comment #17 in Bug #5063 19139 9 kumarp 2008-02-20 02:56:23 +0000 This issue is addressed as a part of the fix to bug# 5063.