valueflows

valueflows docs
git clone https://s.sonu.ch/~srfsh/valueflows.git
Log | Files | Refs | README

commit 359bd36f91ec853e93b93d6e52f30af5c4660feb
parent 36aa5dc70faa59879ebcb348e6e0cbd6926cada0
Author: Lynn Foster <foster.j.lynn@gmail.com>
Date:   Tue,  6 Nov 2018 17:18:01 -0600

Merge pull request #288 from elf-pavlik/intent

deconflating intent and proposal
Diffstat:
Mdocs/SUMMARY.md | 3++-
Adocs/introduction/flows.md | 21+++++++++++++++++++++
Ddocs/introduction/intents.md | 20--------------------
Adocs/introduction/proposals.md | 17+++++++++++++++++
Mrelease-doc-in-process/all_vf.TTL | 14+++++++-------
5 files changed, 47 insertions(+), 28 deletions(-)

diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md @@ -14,9 +14,10 @@ ## Concepts * [Agent](introduction/agents.md) * [Resource](introduction/resources.md) +* [Flows](introduction/flows.md) * [Process](introduction/processes.md) * [Exchange](introduction/exchanges.md) -* [Intent and Commitment](introduction/intents.md) +* [Proposals](introduction/proposals.md) * [Scoping](introduction/scope.md) * [Classification](introduction/classification.md) * [Conversation for Action](introduction/cfa.md) diff --git a/docs/introduction/flows.md b/docs/introduction/flows.md @@ -0,0 +1,20 @@ +# Flows + +Flows come as fundamental construct in ValueFlows ontology. When put in chronological order, they form a progression: + +1. Intents which can lead to Commitments +2. Commitments which can lead to Economic Events + +## 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. + +## 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. + +## Economic Events + +Economic event describes past event, something already observed, never some potential future event.+ \ No newline at end of file diff --git a/docs/introduction/intents.md b/docs/introduction/intents.md @@ -1,20 +0,0 @@ -# Intents and Commitments - - -Intents refer to published wants or offers or plans, sometimes with what is expected in return. Commitments can evolve from intents, or be entered into without intents. They are specifically committed to by agents. 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. On the exchange side, - -Intents are everywhere in advertising. But we see many groups posting intents that are different from commercial advertisements or ecommerce offers. - -They are more general, often not commercial at all, expressed not in identified products but in categories, tags, and text. But they want to find each other. The offers want to find the matching wants. The wants want to find the matching offers. - -When they find their match, those with the matching offer and want enter into a conversation for action which might result in a set of commitments for exchange. - -A proposal to do something might enter into conversation for action which might result in commitments for a process. - -Commitments are "mirrors" of economic events, and economic events can fulfull commitments. Some commitments can be considered contractual promises from one agent to another. - -Intents may lead to conversations for action, which may lead to more and better cycles of engagement: - -![funnel](https://cloud.githubusercontent.com/assets/117439/11401215/144641f6-9357-11e5-8ddd-f01f5bcf4012.png) - - diff --git a/docs/introduction/proposals.md b/docs/introduction/proposals.md @@ -0,0 +1,17 @@ +# Proposals + +Proposals refer to published requests or offers, sometimes with what is expected in return. Agreements can evolve from proposals, or be entered into without proposals. They are specifically committed to by agents. + +Proposals are everywhere in advertising. But we see many groups posting proposals that are different from commercial advertisements or e-commerce offers. + +Proposals can stay directed to broad or specific *audience*. In the broadest case, they stay available for anyone (public proposals). In the most narrow case, the stay available only for specific agent. In between those two extremes a whole spectrum exists, for example two distinct proposals can exist on providing particular product or service - one for club members and one for general public etc. + +They are more general, often not commercial at all, expressed not in identified products but in categories, tags, and text. But they want to find each other. The offers want to find the matching requests. The requests want to find the matching offers. + +When they find their match, those with the matching offer and request enter into a [conversation for action](cfa.html) which might result in an agreement, possibly an exchange agreement. + +A proposal to do something might enter into conversation for action which might result in commitments for a process. + +Proposals may lead to conversations for action, which may lead to more and better cycles of engagement: + +![funnel](https://cloud.githubusercontent.com/assets/117439/11401215/144641f6-9357-11e5-8ddd-f01f5bcf4012.png) diff --git a/release-doc-in-process/all_vf.TTL b/release-doc-in-process/all_vf.TTL @@ -47,13 +47,13 @@ vf:TransferClassification a owl:Class ; # PLAN CLASSES -#vf:Intent a owl:Class ; -# rdfs:label "vf:Intent" ; -# rdfs:comment "A published want or offer or plan, sometimes with what is expected or desired in return." . +vf:Intent a owl:Class ; + rdfs:label "vf:Intent" ; + rdfs:comment "A planned economic flow, which can lead to economic events (sometimes through commitments)" . vf:Commitment a owl:Class ; - rdfs:label "vf:Commitment" ; - rdfs:comment "A planned economic event or transfer that has been promised by an agent to another agent." . + rdfs:label "vf:Commitment" ; + rdfs:comment "A planned economic flow that has been promised by an agent to another agent." . vf:Agreement a owl:Class ; rdfs:label "vf:Agreement" ; @@ -94,9 +94,9 @@ vf:Transfer a owl:Class ; # rdfs:subClassOf vf:Process ; # rdfs:comment "A process that produces something new from other resources, or improves an existing resource." . -vf:EconomicEvent a owl:Class ; +vf:EconomicEvent a owl:Class ; rdfs:label "vf:EconomicEvent" ; - rdfs:comment "An inflow or outflow of an economic resource in relation to a process and/or exchange. This could reflect a change in the quantity of a vf:EconomicResource. It is also defined by its behavior in relation to the vf:EconomicResource and a vf:Process (consume, use, produce, etc.)" . + rdfs:comment "Observed economic flow, never flow planned to happen in the future. This could reflect a change in the quantity of a vf:EconomicResource. It is also defined by its behavior in relation to the vf:EconomicResource (see vf:action)" . foaf:Agent a owl:Class ; rdfs:label "foaf:Agent" ;