[Bug 12259] Issues with governing declaration and governing type definition

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

--- Comment #1 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> 2011-03-07 19:06:40 UTC ---
<rant>
It seems to me that the clause 3 is clear on the case in question.  If there is
no governing attribute declaration and no stipulation by the caller, then the
there is no {type definition} around, so the attribute can have no governing
type definition.  The only way I can think of to be uncertain about that is to
be afraid to make any inferences on the basis of what the spec says, because
one is not certain that the spec is ever willing to accept the implications of
its statements.  Attempting to state every implication explicitly seems to
encourage that fear.  ("They must not mean that implication, since they didn't
state it explicitly, whereas over there they did ...")

Admittedly, the XSD spec has a history of problems with clarity and with being
willing to accept the implications of its statements.  In the long run, the
solution is to make it safer to reason about the spec by cleaning it up, not to
encourage the habit of fear.
</rant>

On the other points, I'm in agreement.  

And even on clause 3, while I think the change is not necessary I also agree
that it does no direct harm, only the indirect harm of encouraging the view
that it's the spec's job to state every possible implication of its definitions
explicitly.

-- 
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 Monday, 7 March 2011 19:06:42 UTC