9701 2010-05-10 20:31:15 +0000 Eventing: Add a wse:UnsupportedDelivery fault 2010-07-28 09:10:04 +0000 1 1 1 Unclassified WS-Resource Access Eventing LC PC Windows XP CLOSED REMIND externalComments, reviewerSatisfied P2 normal --- 1 antoine.mensch public-ws-resource-access-notifications dug lli5 public-ws-resource-access-notifications oldest_to_newest 35541 0 antoine.mensch 2010-05-10 20:31:15 +0000 The spec does not say what happens when the content of the wse:Delivery is not wse:NotifyTo and is not recognized. Per WS-*, unknown extensions should be ignored. However, this may lead to the wse:Delivery element to be considered empty, which is not allowed by the spec. Either a general wse:InvalidSubscription fault should be returned, or, as specific faults for all child elements (EndTo, Format, NotifyTo, Expires, Filter) are already defined, a new one for Delivery should be added. 35626 1 lli5 2010-05-12 15:18:08 +0000 The spec says <Delivery> must have at least one child but does not say that child has to be recognized. An unrecognized element still exists and cannot be considered empty in XML 1.0. Therefore, no fault is necessary. 35629 2 antoine.mensch 2010-05-12 15:46:40 +0000 OK, maybe my description is not clear. The question should be: what should an event source return in response to a subscribe request containing a wse:Delivery element with unrecognized (and therefore ignored) content? It cannot be a subscription manager endpoint (the subscription is not created), so I guess it should be a fault. Which one? None of the predefined faults seems to apply. 35643 3 bob 2010-05-12 18:19:28 +0000 resolved by agreeing to generate a fault when no delivery mechanism has been established. Editor to supply text 35644 4 dug 2010-05-12 18:24:52 +0000 adding new Fault "NoDeliveryMechanismEstablished" with appropriate explanatory text 35669 5 bob 2010-05-13 12:52:17 +0000 reviewer satisfied http://lists.w3.org/Archives/Public/public-ws-resource-access/2010May/0040.html