4834 2007-07-05 02:28:59 +0000 targetXXX attributes and sml:refType 2007-09-05 18:20:30 +0000 1 1 1 Unclassified SML Core unspecified PC Windows XP RESOLVED FIXED SML references editorial P1 normal Second draft 4673 1 sandygao popescu public-sml oldest_to_newest 15735 0 sandygao 2007-07-05 02:28:59 +0000 What happens if targetXXX attributes are used with element declarations whose type is not derived from sml:refType? One answer is to say it's an error, because targetXXX can only be used on references, and sml:refType is used to indicate whether a type is a reference. Then using targetXXX on other types would have no meaning. Another answer is to allow such usage. Whether an element instance is a reference or not depends solely on whether it has sml:ref="true" attribute, which is independent of the schema type. (If the schema type has a reference to sml:ref, or has an attribute wildcard, then the instance can always have such an attribute.) Then a schema author may want to impose targetXXX constraints on such elements even when their types are not derived from refType. This question arises because of the asymmetry between how instances identify references and how schema identifies them (i.e. sml:ref attribute vs. sml:refType complex type). So another possible to the above question may be to harmonize these 2. 16360 1 pratul.dublish 2007-09-05 04:58:59 +0000 We have decided to remove sml:refType and taregtXXX constrainst can be defined on any element declarations. 16385 2 popescu 2007-09-05 18:20:30 +0000 Files changed : sample-model-source.xsd sml-source.xsd sml-source.xml Changes : 1. Removed sml:refType definition and documentation from schema and spec 2. Updated all samples referring to sml:refType by adding a new type that mirrors the sml:refType definition 3. Replaced all occurences of : 'aa must be supported on sml:refType and its derived types' with 'aa must be supported on all element declarations'