8275 2009-11-13 06:37:32 +0000 Eventing: editorial: description of wse:Filter/@Dialect verbose and unclear 2010-03-17 11:22:05 +0000 1 1 1 Unclassified WS-Resource Access Eventing FPWD All All CLOSED REMIND hasProposal P2 trivial --- 1 gilbert.pilz gilbert.pilz dug public-ws-resource-access-notifications oldest_to_newest 29539 0 gilbert.pilz 2009-11-13 06:37:32 +0000 The description of [Body]/wse:Subscribe/wse:Filter/@Dialect contains the following paragraph: "While an XPath predicate expression provides great flexibility and power, alternate filter dialects MAY be defined. For instance, a simpler, less powerful dialect might be defined for resource-constrained implementations, or a new dialect might be defined to support filtering based on data not included in the notification message itself. If desired, a filter dialect could allow the definition of a composite filter that contained multiple filters from other dialects. New dialect definitions MUST include sufficient information for proper application. For example, it would need to include the context (which data) over which the filter operates." Most of this material would be more appropriately place in the primer. Proposal: "The XPath 1.0 dialect (described below) MUST be supported. Alternate filter dialects can be defined. Such dialect definitions MUST include sufficient information for proper application." 31244 1 bob 2010-01-26 19:24:44 +0000 If filtering is supported, then support for the XPath 1.0 dialect (described below) is RECOMMENDED. Alternate filter dialects can be defined. Such dialect definitions MUST include sufficient information for proper application. 31245 2 bob 2010-01-26 19:27:38 +0000 also apply to enumeration 33644 3 bob 2010-03-17 11:22:05 +0000 resolved on 2010-01-27 with comment #1 and #2