commit eb97111d714d236faa294c039f72cc97869fc71f
parent 0cba1f3a0be34af8120f16939c65ec01ff862d9e
Author: Lynn Foster <foster.j.lynn@gmail.com>
Date: Sun, 12 Mar 2017 14:24:08 -0500
Do first cut intent and exchange subject areas for gitbook.
Diffstat:
3 files changed, 13 insertions(+), 44 deletions(-)
diff --git a/docs/introduction/exchanges.md b/docs/introduction/exchanges.md
@@ -1,33 +1,10 @@
# Exchange
-[This section has not been worked on yet. Just pulled from the repo.]
-
-## Why?
-
-We are seeing several organizations that do exchanges, but not production processes. They also sometimes use several different software apps that might want to know about those exchanges. Some of them even conduct different exchanges in different instances of the same app, or in different apps altogether! As with all of the other Open Vocab projects, its goal is to help different apps talk to each other by means of a common vocabulary and protocols.
-
-## Who uses this?
-
-[NRP](https://github.com/valnet/valuenetwork) is the source of much of the vocabulary, and continues to refine the model, collaborating with user networks like [Sensorica](http://nrp.sensorica.co). [Holodex](https://github.com/open-app/holodex) is using the [organization aspects of the OVN vocab](https://github.com/openvocab/holodex).
-
-But most of the vocabulary comes from the [Resource-Event-Agent (REA) ontology](http://en.wikipedia.org/wiki/Resources,_events,_agents_(accounting_model)) originated by [Professor William McCarthy of Michigan State University](https://www.msu.edu/~mccarth4/) in 1982, used in many places around the world.
-
-## Overview of Exchanges
-
This vocabulary subset looks at exchanges of resources from an independent or neutral viewpoint (not the viewpoint of one of the Agents in the exchange). For example, from one Agent's viewpoint, the exchange may be a Purchase, from the other Agent's viewpoint, it might be a Sale. From the neutral viewpoint, it is an exchange of resources, with usually at least two flows of resources, one from each direction. So for example, the seller might give some goods to the buyer, and the buyer might give some money to the seller. Or in a barter exchange, one agent might give the other some books, and the other agent might compensate with some cookies.
-This differs from (for example) the [Good Relations Conceptual Model](http://wiki.goodrelations-vocabulary.org/Documentation/Conceptual_model), which otherwise we like and want to intertrade with. But Good Relations assumes Compensation in the form of money; the compensation itself is not a separate promise; and the actual flow events are not part of the model. (That's not a criticism. Good Relations has different goals, and a more minimal model makes sense for them.)
+This differs from (for example) the [Good Relations Conceptual Model](http://wiki.goodrelations-vocabulary.org/Documentation/Conceptual_model), which we like and want to intertrade with. But Good Relations assumes Compensation in the form of money; the compensation itself is not a separate promise; and the actual flow events are not part of the model. (That's not a criticism. Good Relations has different goals, and a more minimal model makes sense for them.)
-Other related vocabularies include [this product type ontology based on Wikipedia](http://www.productontology.org/) and the [ISO Accounting and Economic Ontology based on REA](https://webstore.iec.ch/preview/info_isoiec15944-4%7Bed2.0%7Den.pdf).
-
-In the [OVN vocab](https://github.com/openvocab/ovn), we want to track not only the offers and promises, but also the actual flows of resources in networks, in all directions. And we want to support exchanges that don't involve money as well as those that do.
-
-### Definitions
-
-* *[Transfer](https://github.com/valueflows/exchange/blob/master/Transfer.md)*
-
-### Use Cases
-* [Dental Care](https://github.com/valueflows/valueflows/blob/master/use-cases/dental-care.md)
+In ValueFlows, we want to track not only the offers and promises, but also the actual flows of resources in networks, in all directions. And we want to support exchanges that don't involve money as well as those that do.
### Exchange protocols
@@ -45,8 +22,3 @@ Offers and Wants are matched in the Planning and Identification Phases. Conversa
-### Resource flows
-
-One of the purposes of this vocab is to support resource flows connecting many websites. These flows may be oriented around Processes, Exchanges, or combinations of both. We are breaking out the Processes and Exchanges into their own vocab repositories, but here some overview diagrams.
-
-In general, processes and exchanges alternate in a flow. But in some situations, either the processes or the exchanges are more important, and the other is not worth tracking and can be elided. This Exchange vocab is focused on the situations where the processes are not important.-
\ No newline at end of file
diff --git a/docs/introduction/intents.md b/docs/introduction/intents.md
@@ -1,24 +1,20 @@
# Intents and Commitments
-[This section has not been worked on yet, and is pulled from Intent. Needs to be though through, as well as adding commitments.]
-Vocab about Offer, Request, Want, Need, Desire, and other related predecessors to [exchanges](https://github.com/openvocab/exchange) or [processes](https://github.com/valueflows/process). .
+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,
-We see many groups posting intents that are different from commercial advertisements or ecommerce offers.
+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.
+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 an [exchange](https://github.com/valueflows/exchange).
+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 a [process](https://github.com/valueflows/process).
+A proposal to do something might enter into conversation for action which might result in commitments for a process.
-Some of the groups we have seen posting these intents include [Mutual Aid Networks](http://www.mutualaidnetwork.org/), [Mutual Credit Associations](https://www.community-exchange.org/home/), and [Hylo](https://www.hylo.com/c/collaborative-technology-alliance).
-
-See also [intent casting](https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=intent%20casting)
-
-Or [Netention](http://www.slideshare.net/helenefinidori/introduction-to-netention).
+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:
+
diff --git a/docs/introduction/planning.md b/docs/introduction/planning.md
@@ -1,6 +1,8 @@
-# Planning
+# Dependent Demand Logic
-I wrote a much longer version of this called [Dependent Demand](http://hillside.net/plop/plop97/Proceedings/haugen.pdf) for a PLoP conference in 1997. This is the shorter version, but maybe still difficult to read because I am trying to qualify all the vf:Names.
+[Needs to be cleaned up for naming]
+
+I (Bob Haugen) wrote a much longer version of this called [Dependent Demand](http://hillside.net/plop/plop97/Proceedings/haugen.pdf) for a PLoP conference in 1997.
Basically, you traverse a graph of vf:ProcessTypes backwards from the last vf:OutputType, connecting vf:InputTypes with vf:OutputTypes that have matching vf:ResourceTypes. See [Graph search algorithms](http://jasonpark.me/AlgorithmVisualizer/).
