[Bug 8262] New: Naming in Override Constraints and Semantics

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

           Summary: Naming in Override Constraints and Semantics
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: David_E3@VERIFONE.com
        ReportedBy: petexmldev@codalogic.com
         QAContact: www-xml-schema-comments@w3.org
                CC: cmsmcq@blackmesatech.com


In "Schema Representation Constraint: Override Constraints and Semantics", 
is there any chance that:

- D1 could be changed to Doverridden and
- D2 could be changed to Doverriding?

Then:

2 One of the following must be true:
2.1 D2 has a targetNamespace [attribute], and its ·actual value· is 
identical to the ·actual value· of the targetNamespace [attribute] of D1 
(which must have such an [attribute]).
2.2 Neither D2 nor D1 have a targetNamespace [attribute].
2.3 D2 has no targetNamespace [attribute] (but D1 does).

becomes:

2 One of the following must be true:
2.1 Doverriding has a targetNamespace [attribute], and its ·actual value· is 
identical to the ·actual value· of the targetNamespace [attribute] of 
Doverridden (which must have such an [attribute]).
2.2 Neither Doverriding nor Doverridden have a targetNamespace [attribute].
2.3 Doverriding has no targetNamespace [attribute] (but Doverridden does).

This is a lot easier on the old brain!

Henry (Thompson) has suggested using Dold and Dnew for the names as they are
shorter.  (http://lists.w3.org/Archives/Public/xmlschema-dev/2009Nov/0007.html
)  I think there are pros and cons to both approaches and I'm happy to accept
what ever the WG thinks is clearest.

There are possibly similar name changes that could be made that would make 
the life of the reader much easier.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 11 November 2009 14:58:14 UTC