W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > May 2006

ISSUE-43: ref and type qname values

From: Databinding Issue Tracker <dean+cgi@w3.org>
Date: Thu, 4 May 2006 17:04:06 +0000 (GMT)
To: public-xsd-databinding@w3.org
Message-Id: <20060504170406.0F40733205@kearny.w3.org>


ISSUE-43: ref and type qname values

http://www.w3.org/2005/06/tracker/databinding/issues/43

Raised by: Paul Downey
On product: Basic

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.
Received on Thursday, 4 May 2006 17:04:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:20:37 GMT