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 10376 - Eventing: misplaced reference to EVD @Identifier
Summary: Eventing: misplaced reference to EVD @Identifier
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: externalComments
Depends on:
Blocks:
 
Reported: 2010-08-16 11:29 UTC by Doug Davis
Modified: 2011-02-01 18:27 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2010-08-16 11:29:45 UTC 
See: http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/2010Aug/0007.html

From Stephan Poehlsen:
in the current ws-eventing draft in section A.1.1, the second paragraph 
mentions the MetadataSection. As far as I discovered this is obsolete 
since the current draft (5 August 2010). It is a relict of the previous 
draft (30 March 2010).

Am I right, that after this modification the only way to embed 
ws-eventing information is to use ws-policy with EventSource?
Comment 1 Doug Davis 2010-08-16 11:38:06 UTC 
The paragraph in question is this:
- - - - - - -
The value of the @Identifier attribute, if present, for this MetadataSection MUST be equal to the value of its wsevd:EventDescriptions/@targetNamespace. An event source MUST NOT have more than one EventDescriptions document. 
- - - - - - -

Note - this appears in both ws-eventing and ws-evd specs.

While the information in this paragraph is correct, I believe its misplaced and
should be reworked to be more readable.

Proposal:

1 - where this paragraph appears in WS-Eventing and WS-EVD, remove the first
    sentence so that all that's left is: 
    An event source MUST NOT have more than one EventDescriptions document.

2 - in ws-evd, after the examples (so right before 4.1.2), put the first 
    sentence of the above paragraph with a little intro:

    If an EventDescription document appears within a WS-MetadataExchange
    MetadataSection, then the value of the @Identifier attribute, if present,
    MUST be equal to the value of its wsevd:EventDescription/@targetNamespace.

WS-Eventing doesn't need #2 since its EVD's job to define the value of the
@Identifier attribute, not Eventing's.
Comment 2 Doug Davis 2010-08-17 17:20:03 UTC 
additions to the proposal:
add two more examples (one in evd and one in ws-eventing), per:
http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Aug/0012.html
that show what a getMetadataResponse looks like - to remind people
that this metadata can appear within a MetadataSection.
Comment 3 Robert Freund 2010-08-17 19:42:57 UTC 
resolved as proposed