This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9320 - Eventing: we never really define "format"
Summary: Eventing: we never really define "format"
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 trivial
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2010-03-25 15:56 UTC by Doug Davis
Modified: 2010-07-27 20:29 UTC (History)
0 users

See Also:


Description Doug Davis 2010-03-25 15:56:43 UTC
Section 2.3 of eventing starts with:
2.3 Notification Formats

This specification specifies two delivery formats: wrapped and unwrapped. Use of wrapped format indicates that notification messages MUST be contained in a wrapper element defined by this specification. Use of unwrapped format indicates that notification messages are not contained in a wrapper element. 

We never really define what "format" means.  Sometimes formatting implies
things like encoding and that's not really what we're talking about here.

add an intro sentence that says something like:
This specification does not mandate how events are serialized into
notification messages. Rather, within the Subscribe request message
a subscriber can specify a "Format" that indicates the set of rules
that MUST be followed when constructing notification messages.
Comment 1 Robert Freund 2010-03-30 19:46:01 UTC
Resolved as proposed