I took the action to do a quick review for CM needs and look how it may be spec'd for CM [1]
Comment on section [2] I'm not sure why the domain specific types are here. Seems like something that would be in CM spec. In fact, we probably wouldn't define a oslc:StateTransitionAction but instead just call it oslc:Action. Seems like the parent class is extraneous. Clients will be looking for oslc_cm:targetState to determine which action to pick. What value is there in having this separate type? CM would simply use profile "POST RDF described by OSLC shapes" [3] Figured I will just sketch out how it will be used below, which seems to be a slight modification of what we already had spec'd. @prefix oslc: <http://open-services.net/ns/core#>. @prefix oslc_cm: <http://open-services.net/ns/cm#>. @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. @prefix dc: <http://purl.org/dc/terms/>. <http://example.com/bugs/2314> a oslc_cm:ChangeRequest; oslc_cm:state <http://open-services.net/ns/cm#Open-state>; dc:identifier "2314"; dc:title "Provide import"; oslc:action <http://example.com/bugs/2314?_action=resolve>, <http://example.com/bugs/2314?_action=start>. <http://example.com/bugs/2314?_action=resolve> a oslc:Action; dc:description "Indicates work is complete on the change request."; dc:identifier "23"; dc:title "Resolve"; oslc:request <#req1>; oslc_cm:targetState <http://open-services.net/ns/cm#Resolved-state>. <http://example.com/bugs/2314?_action=start> a oslc:Action; dc:description "Indicates work is beginning on the change request."; dc:identifier "24"; dc:title "Start Working"; oslc:request <#req2>; oslc_cm:targetState <http://open-services.net/ns/cm#In-progress-state>. <#req1> a http:Request; http:requestURI <>; http:mthd http-methods:POST oslc:resourceShape <http://example.com/bugs/action/resolve/shape>. <#req2> a http:Request; http:requestURI <>; http:mthd http-methods:POST oslc:resourceShape <http://example.com/bugs/action/start/shape>. [1] - http://open-services.net/wiki/automation/AutomationMeetings20140123/#Minutes [2] - http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/#Resources.3A-Action-types [3] - http://open-services.net/wiki/core/Exposing-arbitrary-actions-on-RDF-resources/#profile_POST_resource_shape Thanks, Steve Speicher IBM Rational Software OSLC - Lifecycle integration inspired by the web -> http://open-services.net
