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

[Martin P Pain]

> I am definitely being confused by the use of the word 'template' in 
> what seems like two distinct senses. 
In the first sense, you say "any http:body". I'm only using it to refer to 
an RDF http:body (originally to the resource described, now to the 
representation/description itself) not, for example, ContentAsText. 
(However, I appreciate that it could be used to refer to any description 
of a body, especially if there's no behaviour specific to the RDF 
representations, but that's not how I've been using the term).

I see this as almost identical to the second sense, with two differences:
A. Where they came from. The first sense was made available by the 
provider as part of the binding, the second sense was made available by 
the provider as the result of a template dialog.
B. How long they last. The templates in the first sense have a long 
lifetime - as long as the binding is valid. The ones from the second sense 
MAY be deleted almost immediately.

Other than that they are both representations that are intended to be 
submitted as an HTTP body.


Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
Open Services for Lifecycle Collaboration - Automation WG joint chair

E-mail: martinpain at uk.ibm.com
Find me on:  and within IBM on:  




IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

"Oslc-Automation" <oslc-automation-bounces at open-services.net> wrote on 
14/01/2014 15:02:25:

> From: John Arwe <johnarwe at us.ibm.com>
> To: oslc-automation at open-services.net, 
> Date: 14/01/2014 15:02
> Subject: Re: [Oslc-Automation] HTTP req impl pattern: template 
indirection
> Sent by: "Oslc-Automation" <oslc-automation-bounces at open-services.net>
> 
> 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
> _______________________________________________
> Oslc-Automation mailing list
> Oslc-Automation at open-services.net
> 
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140114/213a3594/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 518 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140114/213a3594/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1208 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140114/213a3594/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 360 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140114/213a3594/attachment.gif>