Devices Profile for Web Services Version 1.1 OASIS Standard 1 July ...

More documents

Recommendations

Info

803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850Because all components in WSDL are extensible via elements [BP 1.1, Section 4], attachment usingwsp:PolicyReference/@URI is sufficient.Get [WS-Transfer] is the interoperable means for a CLIENT to retrieve attached policy.CORRECT:http://schemas.xmlsoap.org/ws/2004/09/transfer/GetResponseurn:uuid:82204a83-52f6-475c-9708-174fa27659echttp://www.w3.org/2005/08/addressing/anonymouswsdd-dpws-1.1-spec-os 1 July 2009Copyright © OASIS® 2009. All Rights Reserved. Page 24 of 43
8518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928935 EventingThe scope of this section is the following set of Web services specifications. All of the requirements inthese specifications are included by reference except where superseded by normative statements herein:[WS-Eventing]5.1 SubscriptionR3009: A HOSTED SERVICE MUST at least support Push Delivery Mode indicated by"http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryModes/Push".The Push Delivery Mode [WS-Eventing] is the default Delivery Mode and indicates the Event Source(HOSTED SERVICE) will push Notifications to the Event Sink (CLIENT).R3017: If a HOSTED SERVICE does not understand the [address] of the Notify To of a Subscribe SOAPENVELOPE, the HOSTED SERVICE MUST generate a wsa:DestinationUnreachable SOAP Faultin place of a SubscribeResponse message.R3018: If a HOSTED SERVICE does not understand the [address] of the End To of a Subscribe SOAPENVELOPE, the HOSTED SERVICE MUST generate a wsa:DestinationUnreachable SOAP Faultin place of a SubscribeResponse message.R3017 and R3018 do not ensure that a HOSTED SERVICE can contact an event sink, but they doprovide a mechanism for the event source to fault on unsupported URI schemes or addresses it knows itcannot contact.R5003: If a HOSTED SERVICE generates a wsa:DestinationUnreachable SOAP Fault under R3017 orR3018, the SOAP Fault Detail MUST be the EndTo or NotifyTo Endpoint Reference Address thatthe HOSTED SERVICE did not understand.R5003 allows a client to distinguish between a SOAP Fault generated due to an unreachable [destination]information header in the Subscribe message, and a SOAP Fault generated due to an unreachableNotifyTo or EndTo address.R3019: If a HOSTED SERVICE cannot deliver a Notification SOAP ENVELOPE to an Event Sink, theHOSTED SERVICE MAY terminate the corresponding Subscription.R5004: If a HOSTED SERVICE terminates a subscription (per R3019), the HOSTED SERVICE SHOULDsend a Subscription End SOAP ENVELOPE with a Status of"http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryFailure".5.1.1 FilteringTo enable subscribing to one or more Notifications exposed by a HOSTED SERVICE, this profile definesa Filter Dialect designated "http://docs.oasis-open.org/ws-dd/ns/dpws/2009/01/Action".A Filter in this Dialect contains a white space-delimited list of URIs that indicate the [action]property of desired Notifications.The content of a Filter in this Dialect is defined as xs:list/@itemType="xs:anyURI" [XML SchemaPart 2].A Filter in this Dialect evaluates to true for an Output Message of a Notification or Solicit-Response operation if and only if a URI in the Filter matches the [action] property of the Messageusing the "http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01/rfc3986" matching rule [WS-Discovery].A Filter in this Dialect with no URIs specified will always evaluate to false for all messages.The Action Dialect uses the RFC 3986 prefix matching rule so CLIENTs can subscribe to a related set ofNotifications by including the common prefix of the [action] property of those Notifications. Typically, thewsdd-dpws-1.1-spec-os 1 July 2009Copyright © OASIS® 2009. All Rights Reserved. Page 25 of 43
Page 1 and 2: Devices Profile for Web Services Ve
Page 3 and 4: NoticesCopyright © OASIS® 2009. A
Page 5 and 6: 12345678910111213141516171819202122
Page 7 and 8: 6869707172737475767778798081828384A
Page 9 and 10: 14814915015115215315415515615715815
Page 11 and 12: 22322422522622722822923023123223323
Page 13 and 14: 30130230330430530630730830931031131
Page 15 and 16: 35335435535635735835936036136236336
Page 17 and 18: 44444544644744844945045145245345445
Page 19 and 20: 54955055155255355455555655755855956
Page 21 and 22: 65165265365465565665765865966066166
Page 23: 75475575675775875976076176276376476
Page 27 and 28: [Reason][Detail]E.g., “no notific
Page 29 and 30: 10021003100410051006100710081009101
Page 31 and 32: 10801081108210831084108510861087108
Page 33 and 34: 11611162116311641165116611671168116
Page 35 and 36: 11991200120112021203120412051206120
Page 37 and 38: 126312641265Appendix B. ConstantsTh
Page 39 and 40: 130513061307Appendix D. Example x.5
Page 41 and 42: 029: Fix SERVICE/DEVICE for WS-Poli
Page 43: 1312wsdd-dpws-1.1-spec-os 1 July 20

Devices Profile for Web Services Version 1.1 OASIS Standard 1 July ...

Create successful ePaper yourself

Delete template?

Save as template?