[Bug 6159] Wildcard allows element name

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





--- Comment #2 from Michael Kay <mike@saxonica.com>  2009-03-27 17:44:37 ---
I took an action to propose wording for this. After struggling for a bit, I
think the effect can be achieved by moving the relevant rule from 3.10.4.2 to
3.10.4.1.

1. In 3.10.4.2 "Wildcard allows expanded Name", delete rule 4.

This means that the condition depends only on the wildcard and the name, and
not on any context.

2. In 3.10.4.1, "Item valid (wildcard)", change the rules to:

For an element or attribute information item I to be locally ·valid· with
respect to a Wildcard W all the following conditions must be true: 

(1) The expanded name of I must be ·valid· with respect to W.{namespace
constraint}, as defined in Wildcard allows Expanded Name (§3.10.4.2).

(2) If all of the following are true:
4.1 W.{namespace constraint}.{disallowed names} contains the keyword sibling;
4.2 W is an element wildcard
4.3 I is an element information item 
4.4 I has a [parent] P that is also an element information item
4.5 I and P have the same [validation context]
4.6 P has a ·governing type definition· T (which is always a complex type and
contains W in its ·content model·)
then E does not ·match· any element declaration ·contained· in the content
model of T, whether ·directly·, ·indirectly·, or ·implicitly·.

3. The effect of the above changes is to move the effect of "sibling" from
"Wildcard allows expanded name" (WAEN) to "Item valid (Wildcard)" (IVW). So we
need to look at places where WAEN is invoked other than via IVW. There are two
such places. 

- Wildcard subset. I believe here the change proposed above is beneficial.
Wildcard subset needs to look at two wildcards in a context-independent way.
There is no "item having E as its name" in this situation.

- Attribute wildcard union. The same is true, but it doesn't matter anyway,
since we are only concerned here with attribute wildcards.

Michael Kay








-- 
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 Friday, 27 March 2009 17:44:48 UTC