The actions createThing, retrieveThing, updateThing as defined in the TM do not specify 'id' as an input parameter in the affordance input datascheme. Instead it relies on the forms to provide this using uriVariables. As a result a directory can only be implemented using the http protocol binding as there is no specification on how to pass the 'id' input parameter using protocols that do not use uriVariables. (websockets for example).
From my perspective this is a bug in the specification. My understanding is that if an action requires an input there must be an input datascheme in the action affordance. This is missing in the TM.
A second issue is that IMHO URI variables should not take the place of input parameters as they are protocol specific, while the TM should be usable with any protocol.
However, there is a good case to make for simply being able to retrieve a TD using "GET /things/{id}". Not sure what the best approach is. One option that comes to mind is to define 'id' as an input parameter and somehow link the URI variable to that input in the form for http-basic. Your thoughts?
The actions createThing, retrieveThing, updateThing as defined in the TM do not specify 'id' as an input parameter in the affordance input datascheme. Instead it relies on the forms to provide this using uriVariables. As a result a directory can only be implemented using the http protocol binding as there is no specification on how to pass the 'id' input parameter using protocols that do not use uriVariables. (websockets for example).
From my perspective this is a bug in the specification. My understanding is that if an action requires an input there must be an input datascheme in the action affordance. This is missing in the TM.
A second issue is that IMHO URI variables should not take the place of input parameters as they are protocol specific, while the TM should be usable with any protocol.
However, there is a good case to make for simply being able to retrieve a TD using "GET /things/{id}". Not sure what the best approach is. One option that comes to mind is to define 'id' as an input parameter and somehow link the URI variable to that input in the form for http-basic. Your thoughts?