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 6648 - Eventing: define extensibility model for WS-Eventing
Summary: Eventing: define extensibility model for WS-Eventing
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal, migrationPathNeeded
Depends on:
Blocks:
 
Reported: 2009-03-03 21:38 UTC by Gilbert Pilz
Modified: 2009-04-21 21:26 UTC (History)
2 users (show)

See Also:

Attachments

Description Gilbert Pilz 2009-03-03 21:38:54 UTC 
Currently WS-Eventing says "If a receiver does not recognize an extension, the receiver SHOULD NOT process the message and MAY fault." This contradicts accepted practice in web services standards and is a bad idea in any case. We need to bring this into line with other web services specs (unrecognized extensions ignored) and define a way of overriding this behavior.
Comment 2 Robert Freund 2009-03-24 20:14:31 UTC 
The elements defined in this specification MAY be extended at the points indicated by their outlines and schema. Implementations MAY add child elements and/or attributes at the indicated extension points but MUST NOT contradict the semantics of the parent and/or owner, respectively. If a receiver does not recognize an extension, the receiver SHOULD ignore that extension. Senders MAY indicate the presence of an extension that has to be understood through the use of a corresponding SOAP Header with a soap:mustUnderstand attribute with the value “1”.

resolved to apply to all of the specs