- From: james anderson <james.anderson@setf.de>
- Date: Wed, 13 Jun 2001 17:54:23 +0200
- To: www-ql@w3.org, www-xml-query-comments@w3.org
The draft notes the need to recognize namespace prefix bindings in
element constructors.
Ed. Note: MF: (08-May-2001) The above rules do not handle namespace
attributes in element constructors, e.g.,
<foo:bar xmlns:foo="http://www.foo.com/foo.xsd">.
These need to be added. In mapping from XQuery to core, all namespace
attributes should occur before other attributes.
Whereas prefix bindings also affect the resolution of the element tag
name, there's no reason to restrict the order of the attributes
themselves. Since the environment has to be extended before the element
name itself can be resolved, all attributes could well be examined. The
case might be made for an artificial stop at the point where the first
non-namespace attribute occurs, but it would entail a loss of xml-names compatibility.
Beyond this fine point, I ask whether this issue arises as a consequence
of a goal of compatibility with XML+names encoding, or because there is
some need for name resolution in the constructor?
What approach is being considered to the issue of drawing namespace
bindings from default attribute declarations?
...
Received on Wednesday, 13 June 2001 11:50:46 UTC