Hi Joseph, Actually, no. We do not have to go back to clean-URIs. If the XPtr barename meaning does not change, then we only need to tweak our definition of what we intend to do with the result of the barename. The current dsig spec says that the text we generate for URI="#E" is equivalent to what the XPath transform would produce as the result of id("E"). This was under the incorrect assumption that id("E") meant the whole subtree rooted at E (i.e. the whole SignedInfo). The addition of a subtree function means that you can say that URI="#E" is equivalent to what the XPath transform would produce as the result of subtree(id("E")). Alternately, we could simply say that the result of the Xptr barename is an XPath node-set equivalent to calling id("E"). We then use this node-set as an initial evaluation context to an implicit XPath transform with the expression "subtree()". John Boyer Software Development Manager PureEdge Solutions Inc. (formerly UWI.Com) Creating Binding E-Commerce jboyer@PureEdge.comReceived on Wednesday, 7 June 2000 16:57:43 GMT
This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:09 GMT