commit 41da29ee1abf6a6f2f50b83171a4b669734c335e
parent 33169d5af7e63d7f178e0426e689beb962f18ab5
Author: Lynn Foster <foster.j.lynn@gmail.com>
Date: Sun, 27 Jan 2019 19:44:24 -0600
Define actions. (#389)
Diffstat:
3 files changed, 52 insertions(+), 23 deletions(-)
diff --git a/docs/introduction/core.md b/docs/introduction/core.md
@@ -19,20 +19,3 @@ All the levels of the REA ontology are similarly flexible and configurable:
* The Observation level represents what really happened.
The core VF vocabulary includes some concepts for which we suggest using other vocabularies. There will also be terms that applications will need that are not part of the VF economic model. This means that it expects people developing those applications to use VF together with other vocabularies / web ontologies. This documentation will suggest other vocabularies and specific terms from them that will come useful in common scenarios that VF aims to address.
-
-
-##### Verbs associated with economic events
-
-###### Input
-* vf:use - for example a tool used in process, after the process, the tool still exists
-* vf:consume - for example an ingredient composed into the output, after the process the ingredient is gone
-* vf:cite - for example a design file, neither used nor consumed, the file remains available at all times
-* vf:work - labor power towards a process
-* vf:accept - in processes like repair or maintentance, same resource will appear in output with *vf:improve* verb
-* vf:load - transported resource enters the process, same resource will appear in output with *vf:unload* verb
-
-###### Output
-
-* vf:produce - new resource created in that process
-* vf:improve - in processes like repair or maintentance, same resource will appear in input with *vf:accept* verb
-* vf:unload - transported resource leaves the process, same resource will appear in input with *vf:load* verb-
\ No newline at end of file
diff --git a/docs/introduction/flows.md b/docs/introduction/flows.md
@@ -7,17 +7,17 @@ Flows come as fundamental construct in ValueFlows ontology. When put in chronolo
## Intent
-On the process side, for example, a work plan could be an Intent, but a work plan that some agent committed to is a Commitment.
-Intent describes some potential future event which might require prior Commitment.
+Intents describe potential future events which have not been agreed to by other agents. Intents are often used for discovering another agent to participate in a desired event. On the process side, for example, planned work could be an Intent, but planned work that some agent committed to is a Commitment.
+
## Commitment
-Commitments are "mirrors" of economic events, and economic events can fulfull commitments. Commitments can be considered contractual promises from one agent to another.
-Commitments describe potential future event which involved agents already agreed to pursuit.
+Commitments describe potential future events which the involved agents already agreed to pursuit. Commitments can be considered contractual promises from one agent to another. Commitments are "mirrors" of economic events, and Economic Events can fulfull Commitments. Commitments can satisfy Intents.
+
## Economic Events
-Economic event describes past event, something already observed, never some potential future event.
+Economic Events describes past events, something observed, never some potential future event. They can fulfill Commitments or satisfy Intents (when there is no Commitment).
## Timeline, plans and observations
@@ -37,3 +37,42 @@ Often agents will start their plans independently and record their initial inten
Intents, Commitments, and Economic Events can occur at any granularity that is needed or for which data can be obtained. So they primarily are used for all operational needs, but can also be used at higher levels for analytical and high level planning needs for communities or regions, for example.
+
+
+## Actions
+
+All flows use an action property to designate what the flow is doing and how it will affect an economic resource (or not). Actions are defined as follows.
+
+* vf:produce - new resource created in that process or an existing stock resource added to
+* vf:use - for example a tool used in process, after the process, the tool still exists
+* vf:consume - for example an ingredient composed into the output, after the process the ingredient is gone
+* vf:cite - for example a design file, neither used nor consumed, the file remains available at all times
+* vf:work - labor power towards a process
+* vf:load - transported resource enters the process, the same resource will appear in output with *vf:unload* verb
+* vf:unload - transported resource leaves the process, the same resource will appear in input with *vf:load* verb
+* vf:accept - in processes like repair or maintentance, the same resource will appear in output with *vf:improve* verb
+* vf:improve - in processes like repair or maintentance, the same resource will appear in input with *vf:accept* verb
+* vf:give - give rights and responsibilities for the resource
+* vf:receive - receive rights and responsibilites for the resource
+* vf:raise - adjusts a quantity up based on a beginning balance or inventory count
+* vf:lower - adjusts a quantity down based on a beginning balance or inventory count
+
+Action | Affect | I/O | Changes existence | Pairs with |
+------ | ------ | --- | ----------------- | ---------- |
+produce | Increment | Output | Yes | N/A |
+consume | Decrement | Input | Yes | N/A |
+use | No effect | Input | No |N/A |
+work | No effect | Input | N/A | N/A |
+cite | No effect | Input | No | N/A |
+load | Decrement | Input | No | unload |
+unload | Increment | Output | No | load |
+accept | No effect | Input | No | improve |
+improve | No effect | Output | No | accept |
+give | Decrement | Input | No | receive |
+receive | Increment | Output | No | give |
+raise | Increment | N/A | N/A | N/A |
+lower | Decrement | N/A | N/A | N/A |
+
+We have defined a core set of actions, but expect that this will be extended with others. If extended, they should be defined as part of this or another formal vocabulary so that all can use them and assume the same meaning.
+
+Temporary note: The actions `use` and `work` are time-based actions, either with or without an explicit schedule. How to handle time-based resources is still under discussion.
diff --git a/release-doc-in-process/all_vf.TTL b/release-doc-in-process/all_vf.TTL
@@ -590,3 +590,11 @@ vf:receive a vf:Action ;
rdfs:label "receive" ;
vs:term_status "unstable" ;
rdfs:subPropertyOf vf:increment .
+
+vf:raise a vf:Action ;
+ rdfs:label "raise" ;
+ rdfs:subPropertyOf vf:increment .
+
+vf:lower a vf:Action ;
+ rdfs:label "lower" ;
+ rdfs:subPropertyOf vf:decrement .
