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

[Bug 5003] Applicability of <alternative> element to xml:lang

From: <bugzilla@wiggum.w3.org>
Date: Mon, 05 Jan 2009 20:44:29 +0000
To: www-xml-schema-comments@w3.org
Message-Id: <E1LJwJJ-0005qG-Ow@farnsworth.w3.org>

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


Sandy Gao <sandygao@ca.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
           Keywords|needsAgreement              |resolved
         Resolution|                            |FIXED




--- Comment #30 from Sandy Gao <sandygao@ca.ibm.com>  2009-01-05 20:44:29 ---
During its 2008-12-12 telecon, the schema WG adopted a proposal to address this
issue.

The proposal can be found at (member-only):
  http://www.w3.org/XML/Group/2004/06/xmlschema-1/structures.b5003c.html

Changes include:
1. Certain attributes can be declared "inheritable"
2. When an inheritable attribute is available (either specified or defaulted)
on an ancestor element, then it's included in the [inherited attributes] PSVI
property of descendant elements.
3. When evaluating type alternative XPaths, [inherited attributes] are
accessible as if they were also specified on the current element.
4. Restriction rules are also updated so that the {inheritable} property of an
attribute in a restriction type has the same value as the same-named attribute
in the base type, if any.

For example, to support the xml:lang scenario raised in this bug, the xml:lang
attribute can be declared "inheritable":

<xs:attribute name="lang" type="xs:language" inheritable="true">
  ...
</xs:attribute>

Then the schema snippet in the original bug report will work.

Note the linked proposal shows "heritable" as the name of the properties. The
WG agreed to use "inheritable" instead.

With these change, the WG believes that the issue raised in this bug report
is fully addressed. I'm marking this RESOLVED accordingly.

Felix and Michael, as the persons who opened and reopened this issue, if you
would indicate your concurrence with or dissent from the WG's disposition of
the comment by closing or reopening the issue, we'll be grateful. If we don't
hear from you in the next two weeks, we'll assume that silence implies consent.


-- 
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, 5 January 2009 20:44:39 UTC

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