Bug 8275 – Eventing: editorial: description of wse:Filter/@Dialect verbose and unclear

Bug 8275 - Eventing: editorial: description of wse:Filter/@Dialect verbose and unclear

Summary:

Eventing: editorial: description of wse:Filter/@Dialect verbose and unclear

Status:	CLOSED REMIND

Product:	WS-Resource Access
Component:	Eventing
Version:	FPWD
Platform:	All All

Importance:	P2 trivial
Target Milestone:	---
Assigned To:	Gilbert Pilz
QA Contact:	notifications mailing list for WS Resource Access

URL:
Whiteboard:
Keywords:	hasProposal

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-11-13 06:37 UTC by Gilbert Pilz
Modified:	2010-03-17 11:22 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Gilbert Pilz 2009-11-13 06:37:32 UTC

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."

Comment 1 Robert Freund 2010-01-26 19:24:44 UTC

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.

Comment 2 Robert Freund 2010-01-26 19:27:38 UTC

also apply to enumeration

Comment 3 Robert Freund 2010-03-17 11:22:05 UTC

resolved on 2010-01-27 with comment #1 and #2