6648 2009-03-03 21:38:54 +0000 Eventing: define extensibility model for WS-Eventing 2009-04-21 21:26:18 +0000 1 1 1 Unclassified WS-Resource Access Eventing FPWD All All CLOSED REMIND hasProposal, migrationPathNeeded P2 normal --- 1 gilbert.pilz gilbert.pilz bob dug public-ws-resource-access-notifications oldest_to_newest 24034 0 gilbert.pilz 2009-03-03 21:38:54 +0000 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. 24325 1 bob 2009-03-19 09:52:25 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0076.html 24396 2 bob 2009-03-24 20:14:31 +0000 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