Commit ba7718f1 authored by Lynn Foster's avatar Lynn Foster

fixed some github refs; revisited term status

parent 6ed7398d
......@@ -27,7 +27,7 @@ An issue can be created for each use case, and people can discuss. People can p
Based on the models, we can start to refine the vocabulary. When it is getting solid, we can write up the .md doc for that subject area so it will get pulled into the main website. Then continue to refine as needed.
For new people, reading the [existing use cases](https://github.com/valueflows/valueflows/tree/master/use-cases) could be a good way to see how they might plug in to this workflow.
For new people, looking through the formal gitbook documentation here https://valueflo.ws might be the best way to become familiar with the work done to date. It also might be useful to look through the [existing use cases](https://lab.allmende.io/valueflows/valueflows/-/tree/master/use-cases).
We use [Term-centric Semantic Web Vocabulary Annotations](https://www.w3.org/2003/06/sw-vocab-status/note) in following way:
* unstable - included in the vocabulary based on discussions and couple of examples
......@@ -36,12 +36,14 @@ We use [Term-centric Semantic Web Vocabulary Annotations](https://www.w3.org/200
### Examples
We write example snippets using [JSON-LD](https://json-ld.org/) compatible subset of YAML. Later any implementation of YAML to JSON should be able to convert them and any implementation of JSON-LD parse them.
Examples should include common JSON-LD `@context` we use in examples: `https://git.io/vf-examples-jsonld-context` which we maintain in https://github.com/valueflows/vf-examples-jsonld-context
Helpful examples are published here: https://valueflo.ws/examples/ex-agent.html.
## Github process
In terms of our process, we also write example snippets using [JSON-LD](https://json-ld.org/) compatible subset of YAML. Later any implementation of YAML to JSON should be able to convert them and any implementation of JSON-LD parse them.
Examples should include common JSON-LD `@context` we use in examples: `https://git.io/vf-examples-jsonld-context` which we maintain in https://lab.allmende.io/valueflows/support-tools/vf-examples-jsonld-context.
Value Flows follows the ["GitHub Flow"](http://scottchacon.com/2011/08/31/github-flow.html) workflow for using [our GitHub repos](https://github.com/valueflows):
## Git process
Value Flows follows the ["GitHub Flow"](http://scottchacon.com/2011/08/31/github-flow.html) workflow for using [our GitLab repos](https://lab.allmende.io/valueflows):
* Anything in the master branch is deployable
* To work on something new, create a descriptively named branch off of master (i.e. fairy-princess-use-case)
......
......@@ -50,7 +50,7 @@ vf:ResourceEffect a owl:Class ;
vf:AgentRelationshipRole a owl:Class ;
rdfs:label "vf:AgentRelationshipRole" ;
vs:term_status "unstable" ;
vs:term_status "testing" ;
rdfs:comment "A relationship role defining the kind of association one agent can have with another." .
vf:RoleBehavior a owl:Class ;
......@@ -65,7 +65,7 @@ vf:RecipeResource a owl:Class ;
vf:ResourceSpecification a owl:Class ;
rdfs:label "vf:ResourceSpecification" ;
vs:term_status "unstable" ;
vs:term_status "testing" ;
rdfs:comment "Specification of a kind of resource. Could define a material item, service, digital item, currency account, etc." .
vf:RecipeProcess a owl:Class ;
......@@ -80,7 +80,7 @@ vf:ProcessSpecification a owl:Class ;
vf:RecipeFlow a owl:Class ;
rdfs:label "vf:RecipeFlow" ;
vs:term_status "unstable" ;
vs:term_status "testing" ;
rdfs:comment "The specification of a resource inflow to, or outflow from, a recipe process." .
vf:RecipeExchange a owl:Class ;
......@@ -123,7 +123,7 @@ vf:ProposedTo a owl:Class ;
vf:Commitment a owl:Class ;
rdfs:label "vf:Commitment" ;
vs:term_status "testing" ;
vs:term_status "stable" ;
rdfs:comment "A planned economic flow that has been promised by an agent to another agent." .
vf:Satisfaction a owl:Class ;
......@@ -141,32 +141,32 @@ vf:Scenario a owl:Class ;
vs:term_status "unstable" ;
rdfs:comment "An estimated or analytical logical collection of higher level processes used for budgeting, analysis, plan refinement, etc." .
# OBSERVATION CLASSES
vf:EconomicResource a owl:Class ;
rdfs:label "vf:EconomicResource" ;
vs:term_status "testing" ;
vs:term_status "stable" ;
rdfs:comment "A resource which is useful to people or the ecosystem." .
vf:Process a owl:Class ;
rdfs:label "vf:Process" ;
vs:term_status "testing" ;
vs:term_status "stable" ;
rdfs:comment "An activity that changes inputs into outputs. It could transform or transport economic resource(s)." .
vf:EconomicEvent a owl:Class ;
rdfs:label "vf:EconomicEvent" ;
vs:term_status "testing" ;
vs:term_status "stable" ;
rdfs:comment "An observed economic flow, as opposed to a flow planned to happen in the future. This could reflect a change in the quantity of an economic resource. It is also defined by its behavior in relation to the economic resource (see vf:action)" .
vf:AgentRelationship a owl:Class ;
rdfs:label "vf:AgentRelationship" ;
vs:term_status "testing" ;
vs:term_status "stable" ;
rdfs:comment "An ongoing voluntary association between 2 agents of any kind." .
vf:Fulfillment a owl:Class ;
rdfs:label "vf:Fulfillment" ;
vs:term_status "unstable" ;
vs:term_status "testing" ;
rdfs:comment "Represents many-to-many relationships between commitments and economic events that fully or partially satisfy one or more commitments." .
vf:Claim a owl:Class ;
......@@ -545,7 +545,7 @@ vf:name a owl:DatatypeProperty ;
vf:RoleBehavior
vf:Scenario
vf:ScenarioDefinition) ] ;
vs:term_status "unstable" ;
vs:term_status "testing" ;
rdfs:comment "An informal or formal textual identifier for an object. Does not imply uniqueness." .
skos:note
......@@ -893,7 +893,7 @@ vf:accept a owl:NamedIndividual ,
vf:onhandEffect vf:decrement ;
rdfs:comment "In processes like repair or modification or testing, the same resource will appear in the output." ;
rdfs:label "accept" ;
vs:term_status "unstable" .
vs:term_status "testing" .
vf:consume a owl:NamedIndividual ,
vf:Action ;
......@@ -903,7 +903,7 @@ vf:consume a owl:NamedIndividual ,
vf:onhandEffect vf:decrement ;
rdfs:comment "For example an ingredient or component composed into the output, after the process the ingredient is gone." ;
rdfs:label "consume" ;
vs:term_status "unstable" .
vs:term_status "testing" .
vf:cite a owl:NamedIndividual ,
vf:Action ;
......@@ -913,7 +913,7 @@ vf:cite a owl:NamedIndividual ,
vf:onhandEffect vf:noEffect ;
rdfs:comment "For example a design file, neither used nor consumed, the file remains available at all times." ;
rdfs:label "cite" ;
vs:term_status "unstable" .
vs:term_status "testing" .
vf:deliver-service a owl:NamedIndividual ,
vf:Action ;
......@@ -955,7 +955,7 @@ vf:modify a owl:NamedIndividual ,
vf:onhandEffect vf:increment ;
rdfs:comment "In processes like repair or modification, the same resource will appear in the input." ;
rdfs:label "modify" ;
vs:term_status "unstable" .
vs:term_status "testing" .
vf:move a owl:NamedIndividual ,
vf:Action ;
......@@ -986,7 +986,7 @@ vf:produce a owl:NamedIndividual ,
vf:onhandEffect vf:increment ;
rdfs:comment "New resource was created in that process or an existing stock resource was added to." ;
rdfs:label "produce" ;
vs:term_status "unstable" .
vs:term_status "testing" .
vf:raise a owl:NamedIndividual ,
vf:Action ;
......@@ -1036,7 +1036,7 @@ vf:use a owl:NamedIndividual ,
vf:onhandEffect vf:noEffect ;
rdfs:comment "For example a tool used in process; after the process, the tool still exists." ;
rdfs:label "use" ;
vs:term_status "unstable" .
vs:term_status "testing" .
vf:work a owl:NamedIndividual ,
vf:Action ;
......@@ -1046,7 +1046,7 @@ vf:work a owl:NamedIndividual ,
vf:onhandEffect vf:noEffect ;
rdfs:comment "Labor power applied to a process." ;
rdfs:label "work" ;
vs:term_status "unstable" .
vs:term_status "testing" .
# Resource effects
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment