Menu ▾ ▴

#13 Confine options for WSDL retrieval

Amendments
open
nobody
None
2020-05-19
2020-05-19
David
No

DPWS normatively references WS-MetadataExchange which enables up to 4 different ways of retrieving WSDL(s) from a hosted service. In order to reduce verification efforts, we should pick only one or two means to be mandatory.

  1. Location element in metadata section
  2. WSDL inline in metadata section
  3. EPR where to send a WS-TransferGet to
  4. EPR that includes another metadata node where to obtain WSDLs

I propose to only support 1 and 2 as those allow service providers to either refer to a URL with precompiled WSDLs or including a runtime-generated WSDL as inline. 3 and 4 are alternative ways that allow recursive definitions of metadata which appears to be over the top for constrained device integration.

Discussion

  • David

    David - 2020-05-19
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -3,6 +3,6 @@

 1. Location element in metadata section
 2. WSDL inline in metadata section
 3. EPR where to send a WS-TransferGet to
-4. EPR with included reference parameter to request a WSDL
+4. EPR that includes another metadata node where to obtain WSDLs

-I propose to only support 1 and 2 as those allow service providers to either refer to a URL with precompiled WSDLs or including a runtime-generated WSDL as inline. 3 and 4 are only alternative ways that aren't more or less powerful than 1 and 2.
+I propose to only support 1 and 2 as those allow service providers to either refer to a URL with precompiled WSDLs or including a runtime-generated WSDL as inline. 3 is only alternative way isn't more or less powerful than 1 and 4 is a recursive definition which appears to be over the top for constrained device integration.
     

  • David

    David - 2020-05-19
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -5,4 +5,4 @@

 3. EPR where to send a WS-TransferGet to
 4. EPR that includes another metadata node where to obtain WSDLs

-I propose to only support 1 and 2 as those allow service providers to either refer to a URL with precompiled WSDLs or including a runtime-generated WSDL as inline. 3 is only alternative way isn't more or less powerful than 1 and 4 is a recursive definition which appears to be over the top for constrained device integration.
+I propose to only support 1 and 2 as those allow service providers to either refer to a URL with precompiled WSDLs or including a runtime-generated WSDL as inline. 3 and 4 are alternative ways that allow recursive definitions of metadata which appears to be over the top for constrained device integration.
     

Log in to post a comment.

MongoDB Logo MongoDB