[Bug 7039] New: wse:Identifier is asking for trouble

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7039

           Summary: wse:Identifier is asking for trouble
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          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


WS-Eventing defines wse:Identifier as a ref-param that can be used.
However, we've already seen hints that some people's implementations,
in the past, were built with the assumption that this ref-param would
be there. This is incorrect.  We should reduce unnecessary interop
problems like this.

Proposal 1:
--------------------------------------------------------------
Remove the wse:Identifier element - people can define any kind of
ref-param they need.

Proposal 2:
--------------------------------------------------------------
Add clarifying text, after each use.  For example, section 4.1 says:

Note, subscribers wishing to correlate SubscriptionEnd messages with the
subscription to which they apply MAY wish to add a distinguishing reference
parameter to the EndTo EPR. For convenience in this common situation, this
specification defines a global element, wse:Identifier of type xs:anyURI, that
MAY be used as a distinguishing reference parameter.  

Add:
Implementations of Event Sources, or Subscription Managers, MUST NOT assume
that this reference parameter will be used.

And do something similar for the SubscriptionMgr epr defn.
--------------------------------------------------------------

I prefer proposal 1 as it doesn't lead some less experienced developers down
the wrong path.


-- 
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 Monday, 22 June 2009 12:32:32 UTC