[Oslc-Automation] HTTP req impl pattern: template indirection

[John Arwe]

I see.
I am definitely being confused by the use of the word 'template' in what
seems like two distinct senses.  Or you're using it only one way and I'm
unclear which meaning to use/where.
1: in a very general "any http body in a request binding
is ...definitionally... used as a template" sense
2: in the more specific "an output from an Automation 2.1 template
dialog/factory" sense

Your binding 1 and binding 3 (with alternative ContentAsText response)
would be interpreted identically by clients, in my world.  The only
difference is 1=blank node, 3=<template> URI.

The long nested parenthetical I'm not able to completely follow, but the
example was useful just to help articulate the pieces above.  Could you
clarify which sense(s) I should use to interpret you example, and I can
re-try after the meeting that's about to start for me?



I may be seeing the need for ContentAsRDF ... similar problem as AtomPub
"special casing" XML, pattern I've seen before.  Just needs some time +
answer to question above to gestate.



Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140114/5b26be41/attachment-0003.html>