This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
WS-Management v1.1 [1] Appendix D.3 defines an dialect/profile of XPath called XPath Level 2 noting: "Level 2 contains everything defined in Level 1, plus general-purpose filtering functionality with the standard set of relational operators and parenthesized sub-expressions (with AND, OR, NOT, and so on). This dialect is suitable for filtering using enumerations and subscription filters. This dialect is a strict superset of Level 1, with the <filter_expression> production being considerably extended to contain a useful subset of the XPath filtering syntax." It is the opinion of the WS-Man WG that this feature is sufficiently general as to warrant inclusion in the base specifications. Note: this issue applies to WS-Enumeration as well. --- Proposal: Add WS-Management's XPath Level 2 to the set of profiles being jointly considered by the WS-RA and XMLSec WGs for a separate XPath Profile document/specification [2]. [1] http://www.dmtf.org/standards/published_documents/DSP0226_1.1.pdf [2] http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Apr/0011.html
resolved, since WG is no longer profiling xpath, it sees no reason to add this one.
The WS-RA WG considered this request during the face to face meeting of May 11th, 2010. The following points were raised: 1.) Over the course of its lifetime the WS-RA WG has received a number of proposals and requests to support various flavors of XPath 1.0 profiles, each one slightly different from the other. 2.) The membership of the WG has expressed very little interest in implementing the XPath Level 1 profile that is in the LC draft of WS-Fragment; so much so that the decision was made to remove it from that specification. 3.) Some members of the WG would like to see XPath 2.0 used as the basis for filtering or selection languages. In the judgement of the WS-RA WG it can't specify any dialects of XPath that will satisfy the needs of more than one particular domain (such as management). Rather than becoming a storehouse for various XPath profiles, the various WS-RA specs should, as they already do, provide a simple and extensible framework that allows these domains to specify their own filtering/selection dialects.
reviewer Satisfied http://lists.w3.org/Archives/Public/public-ws-resource-access/2010May/0056.html