- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 13 Nov 2009 06:37:32 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275 Summary: editorial: description of wse:Filter/@Dialect verbose and unclear Product: WS-Resource Access Version: PR Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Eventing AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: gilbert.pilz@oracle.com QAContact: public-ws-resource-access-notifications@w3.org 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." -- 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. You are the assignee for the bug.
Received on Friday, 13 November 2009 06:37:34 UTC