[oslc-ArchMgmt] OSC AM Meeting Minutes for Nov 10, 2011

[James Conallen]

We had a great conversation today regarding long running services/processes
and transformations in particular.  See the wiki
(http://open-services.net/bin/view/Main/AMScenariosV3MDD) for the latest
working documentation.  I feel we have only begun to feel out some of the
issues involved.

In summary we looked at a OSLC AM usage scenario where the service
provider, that manages model resources (in our example simple Entity
resources), can also transform these model resources into source code
and/or configuration artifacts.  The artifacts are not necessarily managed
by the server.  In fact they can be generated into an SCM.  The
transformation, does however modify some of the resources is works on.

In keeping with the linked data architecture, and use of REST services,
this scenario is begun with a POST of a TransformationResource to the
server.  This resource, of a specific type, has properties that act as the
parameters of a transform.  The service provider creates an instance of
this resource (thereby giving it a URI), and makes it available to the
client for future GETs.  The creation of this resource triggers the
transformation process which is run asynchronously.


Thanks,

jim conallen
Rational Design Management (DM) Lead Architect, OSLC AM Lead
jconallen at us.ibm.com
Rational Software, IBM Software Group