- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 16 Dec 2008 20:38:39 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6255
--- Comment #4 from Jonathan Robie <jonathan.robie@redhat.com> 2008-12-16 20:38:38 ---
In XQuery, this is quite possibly not broken. I started here:
http://www.w3.org/TR/xquery-11/#id-validate
The first step is to convert the operand node to an Information Set using the
rules found in the Data Model. For elements, this rule preserves the Base URI:
<snip from="http://www.w3.org/TR/xpath-datamodel/#const-infoset-element">
Element Node properties are derived from the infoset as follows:
base-uri
The value of the [base URI] property. Note that the base URI property is
always an absolute URI (if an absolute URI can be computed) though it may
contain Unicode characters that are not allowed in URIs. These characters, if
they occur, are present in the base-uri property and will have to be encoded
and escaped by the application to obtain a URI suitable for retrieval, if
retrieval is required.
</snip>
After that, the resulting Infoset is validated as per XML Schema. This does not
lose the Base URIs from the Infoset.
So I don't think there is a real problem here. Did I get that wrong?
Jonathan
--
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 Tuesday, 16 December 2008 20:38:49 UTC