--- C:/Users/IBM_ADMIN/Documents/core-2.0.rdf Wed Apr 16 12:17:48 2014
+++ C:/Users/IBM_ADMIN/Documents/core.rdf Thu Apr 17 11:14:06 2014
@@ -178,6 +178,14 @@
rdf:resource="http://open-services.net/bin/view/Main/OslcCoreUiPreview#Resource_Compact" />
+
+
+ Action
+ An Action provides a representation of an action, process or operation that can be executed against the subject resource, for example start or stop.
+
+
+
@@ -702,6 +710,49 @@
rdf:resource="http://open-services.net/bin/view/Main/OslcCoreSpecification" />
+
+
+
+
+ action
+ A link from any resource to an action that is currently available to
+ execute on that subject resource. It is expected that the target will be of type
+ oslc:Action, and will contain at least one oslc:binding predicate, but this is
+ not necessarily the case.
+
+
+
+
+
+
+ binding
+ The binding of some abstract action (the semantics of a process or
+ operation) onto a more concrete interaction pattern or endpoint(s). For example,
+ it can link an oslc:Action to a description of the messages (e.g. HTTP) that must
+ be exchanged in order to perform the action. In OSLC Core Actions it is expected
+ that the target will be of type http:Request, oslc:Dialog, or oslc:CreationFactory,
+ but this is not necessarily the case.
+
+
+
+
+
+ finalStatusLocation
+ The location at which the final status of a process, operation or
+ action will be available. The meaning of any particular value of this predicate
+ must be defined by an appropriate specification. For example, the OSLC Core Actions
+ specification defines that if the value of this predicate is the URI http:StatusCode
+ then the final status is to be taken from the HTTP response status code of a
+ request that is described by the subject resource. OSLC Core Actions also defines
+ the meaning of oslc:Dialog, oslc:ActionDialog and oslc-automation:AutomationResult
+ in this context.
+
+
+
@@ -854,4 +905,20 @@
rdf:resource="http://open-services.net/bin/view/Main/OslcCoreSpecification" />
+
+
+ ActionDialog
+ An individual that represents that a dialog is to be used (oslc:usage)
+ as a dialog to execute an oslc:Action. When the dialog is completed, the action's
+ execution has been completed. (This is the added value on top of merely identifying
+ a resource as rdf:type oslc:Dialog. This is in contrast to
+ oslc-automation:DeferredExecution, which can be used as part of executing an
+ action, but after the dialog completes the consumer has more steps to take.) The
+ OSLC Core Actions specification defines additional status information that can be
+ returned by dialogs used in this way.
+
+
+