commit 0bb9f686c92b7e78afba3d9e7de4bd5885663780
parent addfb7f64a968be37824cab8827a6de410e119ad
Author: Bob Haugen <bob.haugen@gmail.com>
Date: Mon, 23 Sep 2019 09:57:18 -0500
Replace rawgit with raw.githubusercontent everywhere
Diffstat:
22 files changed, 48 insertions(+), 48 deletions(-)
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
# [Value Flows `vf` vocabs](https://github.com/valueflows/valueflows)
-
+
Here is the current release spec: https://www.valueflo.ws/
diff --git a/docs/README.md b/docs/README.md
@@ -1,4 +1,4 @@
-
+
### A vocabulary for the distributed economic networks of the next economy
Value Flows is a set of common vocabularies to describe flows of economic resources of all kinds within distributed economic ecosystems.
diff --git a/docs/appendix/dependent-demand.md b/docs/appendix/dependent-demand.md
@@ -7,7 +7,7 @@ Here is a long description of [Dependent Demand](http://hillside.net/plop/plop97
Basically, you traverse a graph of Recipe Processes backwards from the last Recipe Output, connecting Recipe Inputs with Recipe Outputs that have matching Resource Categories, and backscheduling all the processes and resource requirements based on estimated process durations. See [Graph search algorithms](http://jasonpark.me/AlgorithmVisualizer/).
This description refers to this diagram:
-
+
Take each request for quantities of Recipe Resource as a demand and start the traversal.
**Start:**
diff --git a/docs/appendix/equations.md b/docs/appendix/equations.md
@@ -8,9 +8,9 @@ This is a (simplified) very specific example taken from Sensorica:
Contributing to creating the output:
-
+
Distributing income according to the value equation:
-
+
Here's [a lot more detail about value equations](https://speakerdeck.com/mikorizal/10-nrp-value-equation-concepts-and-tutorial) as implemented in Sensorica's NRP software, one of the precursors to Value Flows.
\ No newline at end of file
diff --git a/docs/examples/ex-agent.md b/docs/examples/ex-agent.md
@@ -2,7 +2,7 @@
This example include agents (people and organizations) and their relationships.
-
+
[import, lang:"yaml"](../../examples/agent.yaml)
diff --git a/docs/examples/ex-complex.md b/docs/examples/ex-complex.md
@@ -7,7 +7,7 @@
Bob purchases 30kg of apples from Alice and Claudia transports them (FOB destination)
-
+
[import, lang:"yaml"](../../examples/transport-with-transfer.yaml)
@@ -19,6 +19,6 @@ The QT needs the stage and state of the input component resource, because QT wou
This example includes recipe, plan, and actuals.
-
+
[import, lang:"yaml"](../../examples/workflow-stage-state.yaml)
diff --git a/docs/examples/ex-exchange.md b/docs/examples/ex-exchange.md
@@ -11,7 +11,7 @@
An exchange agreement with commitments.
-
+
[import, lang:"yaml"](../../examples/exch-agreement.yaml)
@@ -19,7 +19,7 @@ An exchange agreement with commitments.
An exchange without prior commitments. Note we are still using the Agreement to tie together the reciprocal events, even there were no commitments ahead of time.
-
+
[import, lang:"yaml"](../../examples/exch-retail.yaml)
@@ -27,7 +27,7 @@ An exchange without prior commitments. Note we are still using the Agreement to
A simple transfer of a currency from one agent to another.
-
+
[import, lang:"yaml"](../../examples/transfer-crypto.yaml)
@@ -35,7 +35,7 @@ A simple transfer of a currency from one agent to another.
A simple move of a currency from one account to another by one agent.
-
+
[import, lang:"yaml"](../../examples/move-crypto.yaml)
@@ -43,7 +43,7 @@ A simple move of a currency from one account to another by one agent.
Checking out and checking back in a library book (a loan).
-
+
[import, lang:"yaml"](../../examples/checkout-book.yaml)
@@ -51,7 +51,7 @@ Checking out and checking back in a library book (a loan).
Logged work triggers a claim for future income distribution for that work.
-
+
[import, lang:"yaml"](../../examples/claim.yaml)
diff --git a/docs/examples/ex-planning.md b/docs/examples/ex-planning.md
@@ -13,7 +13,7 @@
A plan for creating two different resources needed for one campaign. The first resource requires two chained processes.
-
+
[import, lang:"yaml"](../../examples/simple-plan.yaml)
@@ -21,7 +21,7 @@ A plan for creating two different resources needed for one campaign. The first
A plan generated from a recipe, for making a component.
-
+
[import, lang:"yaml"](../../examples/plan-from-recipe.yaml)
@@ -29,7 +29,7 @@ A plan generated from a recipe, for making a component.
Commitments satisfying intents, and economic events fulfilling commitments.
-
+
[import, lang:"yaml"](../../examples/fulfill-satisfy.yaml)
@@ -37,7 +37,7 @@ Commitments satisfying intents, and economic events fulfilling commitments.
A simple proposal with reciprocity expected, then another one to give the item away.
-
+
[import, lang:"yaml"](../../examples/simple-proposals.yaml)
@@ -45,7 +45,7 @@ A simple proposal with reciprocity expected, then another one to give the item a
A simple proposal for a timebank. The reciprocity is assumed based on the timebank policies.
-
+
[import, lang:"yaml"](../../examples/proposal-timebank.yaml)
@@ -53,7 +53,7 @@ A simple proposal for a timebank. The reciprocity is assumed based on the timeb
A simple proposal for barter.
-
+
[import, lang:"yaml"](../../examples/proposal-barter.yaml)
@@ -61,7 +61,7 @@ A simple proposal for barter.
A simple proposal requesting help for work on a planned production process. The reciprocal intent (payment) is governed by a previous agreement, and based on the actual hours that will be worked.
-
+
[import, lang:"yaml"](../../examples/proposal-plan.yaml)
@@ -69,6 +69,6 @@ A simple proposal requesting help for work on a planned production process. The
A simple set of proposals that make up a price list.
-
+
[import, lang:"yaml"](../../examples/proposal-list.yaml)
diff --git a/docs/examples/ex-production.md b/docs/examples/ex-production.md
@@ -8,7 +8,7 @@
Simple one-process manufacturing with typical inputs and outputs.
-
+
[import, lang:"yaml"](../../examples/process-manufacturing.yaml)
@@ -16,7 +16,7 @@ Simple one-process manufacturing with typical inputs and outputs.
Simple delivery of a service with typical inputs and outputs.
-
+
[import, lang:"yaml"](../../examples/process-service.yaml)
@@ -24,7 +24,7 @@ Simple delivery of a service with typical inputs and outputs.
Simple repair process with typical inputs and outputs. The same economic resource goes into and out of the process(es).
-
+
[import, lang:"yaml"](../../examples/process-workflow.yaml)
diff --git a/docs/examples/ex-resource.md b/docs/examples/ex-resource.md
@@ -2,6 +2,6 @@
This example includes economic resources, with their resource specifications. One resource has a lot identifier.
-
+
[import, lang:"yaml"](../../examples/resource.yaml)
diff --git a/docs/introduction/accounting.md b/docs/introduction/accounting.md
@@ -27,7 +27,7 @@ Accounting isn't always just counting beans. It will be important for community
The standard set of accounting reports are needed by many organizations. A standard General Ledger, Balance Sheet, and Income Statement can be generated automatically from ValueFlows data. No need to create a Chart of Accounts or post double-entries, those can all be created by a computer program on request.
-
+
Moreover, General Ledgers and accounting reports can be created automatically for each agent in an economic network using the VF vocabulary. The accounting views use the Dependent or Individual Agent view of ValueFlows. See also [Independent vs Dependent views](https://valueflo.ws/introduction/core.html#independent-vs-dependent-views).
diff --git a/docs/introduction/cfa.md b/docs/introduction/cfa.md
@@ -12,5 +12,5 @@ ISO lists 5 phases:
Offers and Wants are matched in the Planning and Identification Phases. Conversation for Action covers Negotiation, Actualization and some of Post-Actualization.
-
+
diff --git a/docs/introduction/concepts.md b/docs/introduction/concepts.md
@@ -1,6 +1,6 @@
# Flows of Value
-
+
Networks of value flows are created when processes are linked together through flows of resources.
@@ -19,18 +19,18 @@ Like:
This is a (simplified) very specific example taken from the Open Value Network (OVN) Sensorica, where contributions to processes are rewarded according to agreed upon rules when there is income.
-
-
+
+
### ... another little value flow....
Producing and exchange olive oil and coffee, even more simplified.
-
+
### ... to thinking bigger.
-
+
### Traversing value flows
diff --git a/docs/introduction/core.md b/docs/introduction/core.md
@@ -14,7 +14,7 @@ A key concept in REA is Duality, which means that each event wants one or more b
### Independent vs Dependent views
-
+
Conventional accounting always takes the view of an individual agent: often a company. REA, and ValueFlows, take an independent view, sometimes called a “collaboration space” or economic network or supply chain view. At the same time, derived from the independent view, REA and ValueFlows support each agent's own accounting view.
@@ -29,7 +29,7 @@ While conventional accounting uses the individual agent view, larger-scale econo
All the levels of the REA ontology are similarly flexible and configurable:
-
+
* The Knowledge level represents classification, policies, procedures, rules and patterns. This is where each network or community can configure the core concepts to fit their desires.
* The Plan level represents offers, requests, schedules and promises.
diff --git a/docs/introduction/estimates.md b/docs/introduction/estimates.md
@@ -26,4 +26,4 @@ Scenarios can be refinements of other scenarios. For example, a group might do
If other requirements arise, we are happy to add connections as needed to the vocabulary.
-
+
diff --git a/docs/introduction/flows.md b/docs/introduction/flows.md
@@ -40,7 +40,7 @@ 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 budgeting for organizations, analytical and high level planning needs for communities or regions, etc.
-
+
### Actions
diff --git a/docs/introduction/plan.md b/docs/introduction/plan.md
@@ -22,7 +22,7 @@ Some examples:
When processes are "nested", it is not random, nor based on a taxonomy. It is based on what processes are actually part of the plan. And not all the inputs and outputs of nested processes are considered inputs and outputs of the plan, since some are both produced and consumed within the plan. In the following simplified example, the flows between plant/weed and weed/harvest start and end inside the nest, and so are not inputs to, or outputs of, the plan.
-
+
* There are some common situations for nested processes that will not be as simple as the above diagram. Thes include:
* Action makes a difference. When a piece of equipment or tool is "used", it is not gone at the end of the nesting process. But if it is managed as a time-based resource with a calendar, some calendar duration is in fact consumed. Or if a citable resource is created and then cited inside, it is also still there at the end of the nesting process.
@@ -33,4 +33,4 @@ When processes are "nested", it is not random, nor based on a taxonomy. It is ba
Plans can be generated from a recipe by scaling the recipe according to the demanded quantity of the end outputs. This is called a "demand explosion". The generation might take into account current inventories, batch sizes, etc., so it is not necessarily a "pure" reflection of the recipe. In addition, often plans are tweaked after generation from a recipe, depending on how firm and exact the recipe is. A manufacturing recipe might be more exact than a recipe for a more general business process. For these reasons, a plans is decoupled from the recipe that generated it in the vocabulary. It maintains only the references to the resource and process specifications that were supplied from the recipe.
-
+
diff --git a/docs/introduction/processes.md b/docs/introduction/processes.md
@@ -14,8 +14,8 @@ Connected processes enable us to see cause and effect, if we want.
Below is a view of processes, which occur in resource flow networks, and live in three layers: Knowledge, which describe how processes work. Plans, which describe processes which are intended to happen. And Observation, which is a record of processes that have already happened.
-
+
Here is a specific example:
-
+
diff --git a/docs/specification/diagrams/uml.md b/docs/specification/diagrams/uml.md
@@ -4,6 +4,6 @@ Note: There are some differences in this representation and the RDF based repres
* This is to support object oriented and relational implementations, as well as open vocabularies that are not RDF based. This is mostly where there are rdf properties not associated with classes.
* This includes all elements necessary for the vocabulary, so includes (and denotes) necessary elements that we re-use from other vocabularies.
-
+
Credit: https://support.draw.io/
diff --git a/docs/specification/diagrams/vowl.md b/docs/specification/diagrams/vowl.md
@@ -4,6 +4,6 @@ You can view this in an active environment [here](http://www.visualdataweb.de/we
Note that this diagram includes only the linked open data VF namespace, so does not include important items for which we are re-using other namespaces. See [the UML Diagram](https://valueflo.ws/specification/diagrams/uml.html) for a complete model with the namespaces identified.
-
+
Credit: http://visualdataweb.de/
diff --git a/docs/specification/json-schema-ref.md b/docs/specification/json-schema-ref.md
@@ -37,7 +37,7 @@ The following are the classes needed for a ValueFlows implementation, in json-sc
#### Agent
-[import, lang:"json"](https://rawgit.com/valueflows/vf-json-schema/master/schemas/Agent.json)
+[import, lang:"json"](https://raw.githubusercontent.com/valueflows/vf-json-schema/master/schemas/Agent.json)
#### AgentRelationship
diff --git a/release-doc-in-process/README.md b/release-doc-in-process/README.md
@@ -1,4 +1,4 @@
-
+
# A vocabulary for distributed economic systems
## Table of Contents
@@ -18,7 +18,7 @@ We want to support RDF based and non-RDF based use of the vocabulary, basically
### Concepts
-
+
Networks of value flows are created when processes are linked together through flows of resources.
@@ -68,11 +68,11 @@ Yet to come:
### UML
-
+
### RDF
-
+
### Classes
