[Oslc-Automation] Keeping low barriers of entry - defining implementation archetypes?

[John Arwe]

My gut reaction is: sounds complicated.  One of OSLC's features is 
simplicity (relative, no arguments here that today constitutes Simple).
If this is about which specific combinations of [spec] features are 
implemented, maybe it's a companion document rather than something Every 
Reader Must Wrap Their Head Around.

Remember that we also have people using Automation in specific areas, and 
some are openly talking about domains "based on" Automation in some way, 
so any complication we introduce at this level potentially hits them as 
well.  It may well also signal that they have the same need, so a common 
solution would be "useful".

I *like* the idea of carving things into smaller chunks, mind you.  I just 
want to pay attention to the global picture as well.

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/20130517/7279416c/attachment-0003.html>