> you mean the property really indicates the Content-Type to represent the resource as ? Have you considered using the an extension in the action such as …/my-action.html ?
I had not. Do you mean an extension to describe both the content type and the field to project? There are two parts to this from the demo (and what I implemented): 1: projecting a field from the JSON object that is the result of the action. 2: how to marshal the projected value So I conflated both: the property name implies also a convention for the marshaling. So using html reads response.html and turns it into the proper format. Your suggestion I think makes it possible to disentangle the desired content-type and the property name to project. It could also then make it possible to do what Nick alluded to: rather than projecting one property, the resource could be specified as a full path (of nested properties). As in: http://openwhisk.host/experimental/web/ns/p/action.html/a/b/c. One issue with using "." as the separator is that it's also a legal character for action names. So a different delimiter would be needed otherwise the path parsing is ambiguous. -r
