diff --git a/images/scripting-error-handling.png b/images/scripting-error-handling.png new file mode 100644 index 00000000..88c8158c Binary files /dev/null and b/images/scripting-error-handling.png differ diff --git a/images/scripting-error-handling.svg b/images/scripting-error-handling.svg new file mode 100644 index 00000000..0a9f544c --- /dev/null +++ b/images/scripting-error-handling.svg @@ -0,0 +1,3 @@ + + +
 WoT Interaction
 WoT Interaction
ConsumedThing
ConsumedThing
 Request
 Request
 Promise
 Promise
WoT
implementation
WoT...
WoT handler
WoT handler
 Response (Body or Error) 
 Response (Body or Error) 
WoT
implementation
WoT...
 request + params 
 request + params 
 ExposedThing
 ExposedThing
return
value or error
return...
HAL
(sensors, actuators)
HAL...
Promise
Promise
Error handling
Error handling
Protocol Bindings
Protocol Bi...
Protocol Bindings
Protocol Bi...Viewer does not support full SVG 1.1 \ No newline at end of file diff --git a/index.html b/index.html index 8a994b74..75f3ab6d 100644 --- a/index.html +++ b/index.html @@ -942,6 +942,33 @@

The InteractionOutput interface

{{InteractionInput}} to the implementation.

+ +

Error handling

+

+ The algorithms in this API define the errors to be reported to application + scripts. +

+

+ The errors reported to the other communication end are mapped and + encapsulated by the Protocol Bindings. +

+
+ +
Error handling in WoT interactions
+
+

+ This topic is still being discussed in + Issue #200. + A standardized error mapping would be needed in order to ensure consistency + in mapping script errors to protocol errors and vice versa. In particular, + when algorithms say "error received from the Protocol Bindings", + that will be factored out as an explicit error mapping algorithm. Currently + that is encapsulated by implementations. +

+
+