- From: <bugzilla@jessica.w3.org>
- Date: Sat, 16 Oct 2010 14:12:19 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11061 --- Comment #1 from Michael Kay <mike@saxonica.com> 2010-10-16 14:12:19 UTC --- (See also bug #11062 on XSD). On reflection, making inherited attributes available in the same way as ordinary attributes creates considerable problems for static type checking. It's not possible to examine an element declaration or its type and to work out statically from that that the element in question might inherit attributes from an ancestor; it's also possible for any inherited attributes to have a different type from like-named attributes declared locally on the element. So if XDM does make inherited attributes available, perhaps they should not be presented (as they are in XSD Conditional Type Assignment XPath expressions) in the same way as local attributes. And if they are going to be treated differently, then perhaps the current way of accessing them - (ancestor::*/@x)[last()] - is good enough? -- 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 Saturday, 16 October 2010 14:12:20 UTC