4622 2007-06-11 08:39:39 +0000 [XSLT 2.0] unparsed-entity-uri - absolute or relative? 2008-09-16 19:58:50 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Data Model 1.0 Recommendation PC Windows XP CLOSED FIXED P2 normal --- 1 mike alb.w3c public-qt-comments oldest_to_newest 15346 0 mike 2007-06-11 08:39:39 +0000 I am raising this as an XSLT 2.0 issue, though it is really a data model issue in an area of XDM that only affects XSLT. It derives from bug 724 agains the XSLT test suite (member-only), which in turn relates to a thread on the xsl-list at mulberrytech.com entitled "Problems with Entities", started by Jeff Sese, which took place on 31 Jan 2007: http://www.biglist.com/lists/xsl-list/archives/200701/msg00750.html In XSLT 1.0, it was stated in section 3.3: if the system identifier [of an unparsed entity] is a relative URI, it must be resolved into an absolute URI using the URI of the resource containing the entity declaration as the base URI. Thus, the unparsed-entity-uri() function would always return an absolute URI. This provision seems to have been lost in XSLT 2.0. XSLT 2.0 defines unparsed-entity-uri() in terms of the dm:unparsed-entity-system-id accessor in XDM. XDM says of this accessor: "Returns the system identifier of the specified unparsed entity or the empty sequence if no such entity exists." In building from an infoset, this property is derived from the [system identifier] of the [unparsed entities] information item, which is defined in Infoset as "[system identifier] The system identifier of the entity, as it appears in the declaration of the entity, without any additional URI escaping applied by the processor." I think the correct resolution of this is to change XDM to say (a) in defining the property, that it is an absolute URI, and (b) in constructing from an Infoset, that the value of the property is obtained by resolving the [system identifier] of the unparsed entity information item against the [declaration base URI] of the same item. 15502 1 mike 2007-06-21 16:59:56 +0000 The XSL WG discussed this on 21 Jun 2007 and agreed to bring the proposal to the imminent joint F2F meeting under the Data Model agenda. 15841 2 sca.w3c 2007-07-17 16:48:17 +0000 For "housekeeping" the following is the snipped of Joint minutes on 4622: J3.1.2 Bugzilla Bug 4622, [XSLT 2.0] unparsed-entity-uri - absolute or relative? http://www.w3.org/Bugs/Public/show_bug.cgi?id=4622 Suggested resolution has been accepted. Construction from PSVI may be affected. XSLT will be discussing it on Friday and editor to write a proposal. 17129 3 sca.w3c 2007-10-10 20:58:15 +0000 This was discussed at XSLT meeting at Microsoft on 10/10/07. ALB took the action item to draft proposed text for the Data Model errata document based on the approach outlined in comment#0 by Mike Kay. ETA for draft text is 18 October 2007. Will be marked "resolved" when proposed text is finally accepted. 17992 4 alb.w3c 2007-12-06 19:28:21 +0000 The XSL WG approved 2007-12-06 the following text to add in 5.17. The dm:unparsed-entity-system-id accessor returns the system identifier of an unparsed external entity declared in the specified document. (inserted text:) The value is an absolute URI, and is obtained by resolving the [system identifier] of the unparsed entity information item against the [declaration base URI] of the same item. (end of inserted text) If no entity with the name specified in $entityname exists, or if the entity is not an external unparsed entity, the empty sequence is returned.