- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 25 Mar 2010 15:56:44 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9320 Summary: Eventing: we never really define "format" Product: WS-Resource Access Version: LC Platform: PC OS/Version: Windows XP Status: NEW Severity: trivial Priority: P2 Component: Eventing AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: dug@us.ibm.com QAContact: public-ws-resource-access-notifications@w3.org 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. Proposal: 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. --- -- 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 Thursday, 25 March 2010 15:56:45 UTC