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

[John Arwe]

OK.  I could quibble on the particulars, but it would be a case of violent 
agreement now that I understand the sense in which you used 'template'.
Bottom line, I understand the/some reasons for defining ContentAsRDF, it 
is a RDF "version" of the Atom problem where XML-based members were 
"handled differently" than others.  If I try to omit ContentAsRDF, I 
cannot craft rules that both work and are consistent with the Open World 
Assumption that RDF is based on.  In order to avoid the "extra" level of 
indirection I'd have to do weird things like inventing a "http:rdfBody" 
predicate, which is just doing the same thing in a different (worse, 
because of the extra coupling it implies) way.
"next"

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/4f1e2262/attachment-0003.html>