ref and type qname values
- Raised by:
- Paul Downey
- Opened on:
It has been my experience that some clunkier tools failed to resolve qname references, in particlar for element/@ref and element/@type values when the prefix is missing and the element default namespace is expected to be used. i.e. xmlns:tns="http://.." <xs:element ref="tns:foo"/> is better supported than: xmlns="http://..." <xs:element ref="foo"/> I note that several vertical schemas use the default namespace for qnames and my experiences are not very recent. Proposal: allow both ncnames and qnames for element references and type references, but offer a Design Consideration that explicitly supplying the namespace prefix in qnames provides improved interoperability with databinding tools. We may later prohibit ncnames based upon CR or other practical testing with tools.
- Related emails:
- ISSUE-43: ref and type qname values (from firstname.lastname@example.org on 2006-05-04)
- Agenda: XML Schema Patterns for Databinding Telcon 9 May 2006 (from email@example.com on 2006-05-05)
- Minutes: XML Schema Patterns for Databinding F2F 31st July - 1st August 2006 (from firstname.lastname@example.org on 2006-08-01)
- ACTION-80: review ISSUES list against the edtodo list (from email@example.com on 2006-10-12)
2006-08-01: Issue closed, experience of tools shows that non qualified type references cause problems. Use of none qname types moved to advanced patterns. Editorial text will be aqdded to basic patterns to describe that schemas must use qname values.