W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2009

[Bug 7913] Strange result from definition of governing element declaration

From: <bugzilla@wiggum.w3.org>
Date: Thu, 29 Oct 2009 21:39:32 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1N3ciS-0003j3-0n@wiggum.w3.org>

C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed:

           What    |Removed                     |Added
           Keywords|needsPublication            |needsReview

--- Comment #3 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>  2009-10-29 21:39:31 ---
A wording proposal intended to resolve this issue is now on the server at

  (member-only link)

The proposal does two things.  First, as requested by the WG it introduces the
variable E to provide a name for the element instance whose governing element
declaration is being defined, similar in effect to the E used by the definition
of governing type definition immediately following.

Second, it inserts a new rule three in front of the old one (which now becomes
rule 4):

  3 A declaration ·resolved· to by E's [local name] and [namespace name],
    that E is ·attributed· either to a strict ·wildcard particle· or to a lax

This has the effect that when an element instance is attributed to a wildcard,
it gets the appropriate global element declaration.  And the effect originally
aimed at by clause 3.3 (now 4.3) is retained:  when the element is not
attributed to a wildcard at all (because its parent is invalid and we are in a
fallback mode, trying to get what information we can out of things), it uses a
locally declared type if there is one.

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 Thursday, 29 October 2009 21:39:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:10 UTC