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

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

           Summary: Hanlding of reference constraints on different kinds of
                    elements
           Product: SML
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
        AssignedTo: cmsmcq@w3.org
        ReportedBy: sandygao@ca.ibm.com
         QAContact: public-sml@w3.org


For the 4 reference constraints:
- acyclic
- targetRequired
- targetElement
- targetType

And for the 4 kinds of elements:
- non-reference
- null-reference
- unresolved reference
- resolved reference

We need to define what to do for all the 16 combinations.

It's easy to answer for the "resolved" kinds of the elements:
- targetRequired: satisfied
- other: check

During the 2007-08 F2F, the WG also agreed on the "non-reference" category:
- all: satisfied

The remaining question is about "null-reference" and "unresolved" categories.
It's obvious that "acyclic" should be "satisfied" for both cases. We also
agreed (bug 4780) that targetRequired should be "violated". How about
targetType and targetElement?

That is, we need to define the following 4 cases:
null + targetType
null + targetElement
unresolved + targetType
unresolved + targetElement

The current draft seems to suggest "violated". But there is desire to change
it, at least partially. See
http://lists.w3.org/Archives/Public/public-sml/2007Sep/0019.html

Received on Wednesday, 12 September 2007 15:39:12 UTC