W3C home > Mailing lists > Public > public-sml@w3.org > October 2007

[Bug 5040] Hanlding of reference constraints on different kinds of elements

From: <bugzilla@wiggum.w3.org>
Date: Mon, 29 Oct 2007 18:43:23 +0000
CC:
To: public-sml@w3.org
Message-Id: <E1ImZa7-0002MA-OB@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5040





------- Comment #3 from kumarp@microsoft.com  2007-10-29 18:43 -------
Proposal:
Both '?' values in the table should be 'Violated'.

                Acyclic         targetRequired  targetElement   targetType
Unresolved      Satisfied       Violated        ?               ?

The targetElement/Type constraint says that the target element/type must be as
specified. We cannot evaluate targetElement/Type constraint for unresolved
references. We cannot obviously declare the model to be valid when we are not
able to check some constraints. Thus, the most logical choice is 'Violated'.

Note that we have already used this reasoning for targetRequired constraint
where we define the constraint to be violated for unresolved refs. 
Received on Monday, 29 October 2007 18:43:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:56:07 UTC