commit b3069c1e76ad1349aa444f5a40dff9a521a3052d parent 98ee4e5181ef5c963bd97d37cbfce79d4ab672d9 Author: Lynn Foster <foster.j.lynn@gmail.com> Date: Thu, 16 Mar 2017 15:14:14 -0500 Merge pull request #201 from valueflows/lynn-ttl Working on ttl file, moved around text Diffstat:
41 files changed, 340 insertions(+), 556 deletions(-)
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md @@ -2,7 +2,7 @@ ## Introduction * [Introduction](README.md) -* [Flows of Resources](introduction/concepts.md) +* [Flows of Value](introduction/concepts.md) * [Core](introduction/core.md) * [Principles](introduction/principles.md) * [Status](introduction/status.md) @@ -20,37 +20,8 @@ * [Conversation for Action](introduction/cfa.md) * [Accounting](introduction/accounting.md) -## Classes -* [Agent](specification/classes/agent.md) -* [EconomicEvent](specification/classes/event.md) -* [Group](specification/classes/group.md) -* [Person](specification/classes/person.md) -* [Process](specification/classes/process.md) -* [Relationship](specification/classes/relationship.md) -* [EconomicResource](specification/classes/resource.md) -* [Transformation](specification/classes/transformation.md) -* [Transportation](specification/classes/transportation.md) - -## Properties -* [action](specification/properties/action.md) -* [affectedQuantity](specification/properties/affectedquantity.md) -* [category](specification/properties/category.md) -* [context](specification/properties/context.md) -* [currentLocation](specification/properties/currentlocation.md) -* [eventStart](specification/properties/eventstart.md) -* [image](specification/properties/image.md) -* [input](specification/properties/input.md) -* [name](specification/properties/name.md) -* [note](specification/properties/note.md) -* [object](specification/properties/object.md) -* [output](specification/properties/output.md) -* [primaryLocation](specification/properties/primarylocation.md) -* [quantity](specification/properties/quantity.md) -* [relationship](specification/properties/relationship.md) -* [resource](specification/properties/resource.md) -* [subject](specification/properties/subject.md) -* [trackingIdentifier](specification/properties/trackingidentifier.md) -* [underlyingResource](specification/properties/underlyingresource.md) +## Specification +* [Classes and Properties](http://www.essepuntato.it/lode/owlapi/https://raw.githubusercontent.com/valueflows/valueflows/master/release-doc-in-process/all_vf.TTL) ## Appendices * [REA References](appendix/rea.md) diff --git a/docs/introduction/agents.md b/docs/introduction/agents.md @@ -4,5 +4,21 @@ The agent vocabulary describes networks of people and groups, using agents and t In ValueFlows, we are talking about economic agents, agents who can create or exchange value, make agreements, etc. But we want to re-use existing vocabularies for commonly defined things, so we have elected to use those as much as possible here. +#### Relationships + +A relationship can be direct, like "steward" or "like", or more like a role. +Role types of relationships are often used for a person's role in an organization or group, +for example "grower" or "harvester" for a food network. + +There are a number of useful Properties in existing vocabularies that can be used. +Or people can create their own as needed. + +Although it usually is, the relationship of a particular type does not have to be agreed to from both sides, for example "follow". + +Direction: For example, in "Michael is a member of Enspiral", Michael is the subject and Enspiral is the object. + + +Context: This allows grouping of economic relationships and economic activity (future releases) into a context for coordination and accounting purposes. For agent relationships, it is needed for cases like "Kathy is mentor of Sam, in the context of Enspiral." + diff --git a/docs/introduction/core.md b/docs/introduction/core.md @@ -1,6 +1,6 @@ # Core -The vocabulary has a core that would fit many different kinds of economic - value networks, supply chains, joint ventures, business collaboration network.... +The vocabulary has a core that would fit many different kinds of economic formations - value networks, supply chains, joint ventures, business collaboration network.... The core is based on the REA (Resource, Event, Agent) ontology. You can find all the details by following the [links here](appendix/rea.md). @@ -8,6 +8,8 @@ These are the main concepts in the REA ontology, as pictured in this [document](  +Economic events are the movers and shakers. They say what is happening to economic resources, and what economic agents are involved along the way. They create the "value flows". + A key concept in REA is Duality, which means that each event wants one or more balancing events: in other words, some kind of reciprocity. REA uses an abstract word for this relationship in order to make the meaning configurable. The reciprocity does not need to happen at the same time, or in the same transaction. And it can have any logic that a network wants: payment in money, swap, earn credits, earn reputation points, share with the commons, from each according to ability and to each according to need, etc. All the levels of the REA ontology are similarly flexible and configurable: @@ -15,3 +17,21 @@ All the levels of the REA ontology are similarly flexible and configurable: * The Abstract level represents 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. * The Observation level represents what really happened. + + + +##### 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 + +###### 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+ \ No newline at end of file diff --git a/docs/introduction/resources.md b/docs/introduction/resources.md @@ -10,7 +10,7 @@ And we want knowledge to be freely available. Also, we prefer to think of use value, but economic resources also often have exchange value. -#### The difference between a resource and its category or model* +#### The difference between a resource and its category or model (names TBD) An economic resource is observable. Its category or model defines what type of thing the vf:Resource is. @@ -20,7 +20,13 @@ The one in a box delivered to your door is a resource. Or the description of the book entitled "The Power of Babel: A Natural History of Language", ISBN ISBN-13: 978-0060520854, is a model. Your library may have two copies that you can check out. Those are resources. -*Names TBD. +Resource categories are a Taxonomy. That means they can be defined very broadly and generally and maybe vaguely, or they can be defined very narrowly, but fit into broader categories. + +So, for example, you may want an apple. Or you may want a green apple. Or you may want a Granny Smith apple. + +Or, Herb is the parent category of Anise Hyssop, Goldenrod, Nettles, Red Clover, etc. Besides its usefulness in understanding taxonomies of resource types, this can be useful when one can define a general recipe that will work for many more specific types of resources. + +People can use the multitude of existing taxonomies for resources, or can also create their own as needed. #### Identification and Behaviors of Resources @@ -35,6 +41,8 @@ Moreover, identification of resources will depend on context and purpose. We wan And then in the "independent view", for larger-scale analysis of resource flows, or for example for lot tracking for public health issues like mad cow disease, different combinations of properties might be needed. +Substitutability: This defines if any resources of that type can be freely substituted for any other resource of that type when used, consumed, traded, etc. For example, "B9R-1-red DLP resin photopolymer" is probably a substitutable resource type. While each resource for a resource type called "English-Spanish translation" is probably not substitutable because each will be a different document. + #### Inventory Economic Resources can be inventoried, not inventoried but could be, or it doesn't make sense to think about inventory. @@ -62,4 +70,19 @@ Some people use the terms "stock" and "stock flow". A stock is a resource; a st An event can trigger incrementing or decrementing a resource. Sometimes it does neither, as in the case of using a piece of equipment or citing a document. But in any case, the quantity of a resource related to the event is not a resource itself, it is just a property of the event. For example a resource could be 100 widgets on a pallet, lot number 1234. If 10 of those widgets are consumed in a process that makes something out of them, that is an event: consumption of 10 widgets of lot number 1234. The 10 widgets are not a resource in their own right. The event triggers the decrement of the original resource of 100 widgets, which now has quantity of 90. -For serialized or uniquely identified resources, if the logical and technical unique identifiers are not changed by an event, such as moving a vehicle to another location without any changes to its custody (and assuming location is not part of the logical identifier), the resource does not behave like a stock and is not decremented or incremented.- \ No newline at end of file +For serialized or uniquely identified resources, if the logical and technical unique identifiers are not changed by an event, such as moving a vehicle to another location without any changes to its custody (and assuming location is not part of the logical identifier), the resource does not behave like a stock and is not decremented or incremented. + +#### How resources related to each other + +##### Underlying resource + +This occurs when a resource is basically certain defined rights to another resource. It is often useful to define the rights as a different resource for purposes of processes or exchanges. + +One example: a resource which defines the rental of an apartment has the apartment itself as its underlying resource. Another example: a virtual account resource can have an actual bank account as its underlying resource. + +##### Contains resource + +Unlike underlying resource, if one resource contains other resources, the contained resources are part of, or make up the larger resource. + +For example, a bank account might contain a number of "virtual accounts" that a group manages itself, outside the bank's knowledge. Or, a bike shed might contain 10 bikes, which are identified and tracked by their serial numbers as individual resources. + diff --git a/docs/specification/classes/agent.md b/docs/specification/classes/agent.md @@ -1,13 +0,0 @@ -### vf:Agent - -<table> -<tr><td>rdf:type</td><td>owl:Class</td></tr> -<tr><td>rdfs:label</td><td>Agent</td></tr> -<tr><td>rdfs:comment</td><td>A vf:Agent is an entity that has agency in the social or economic realm. This could be a person, group, organization, network, ongoing project team, etc.</td></tr> -<tr><td>owl:equivalentClass</td><td>foaf:Agent</td></tr> -<tr><td>Properties</td><td>vf:name, vf:url, vf:image, vf:note, vf:primaryLocation</td></tr> -</table> - -(Question: can/should this also have properties for its relationships (where it is an object or subject)?) - -A vf:Agent is empowered to control or affect the flow of economic resources (including his or her own labor) by engaging in economic events. vf:Agents are also empowered to make commitments or promises to affect resource flows in the future. Or putting it another way, a vf:Agent can participate in economic events.- \ No newline at end of file diff --git a/docs/specification/classes/classes.md b/docs/specification/classes/classes.md @@ -1,12 +0,0 @@ -# Classes - -* [Agent](agent.md) -* [EconomicEvent](event.md) -* [Group](group.md) -* [Person](person.md) -* [Process](process.md) -* [Relationship](relationship.md) -* [EconomicResource](resource.md) -* [Transformation](transformation.md) -* [Transportation](transportation.md) - diff --git a/docs/specification/classes/event.md b/docs/specification/classes/event.md @@ -1,8 +0,0 @@ -### vf:EconomicEvent - -<table> -<tr><td>rdf:type</td><td> owl:Class </td></tr> -<tr><td>rdfs:label</td><td>EconomicEvent</td></tr> -<tr><td>rdfs:comment</td><td>An EconomicEvent is an inflow or outflow of an economic resource in relation to a process. This could reflect a change in the quantity of a vf:Resource. It is also defined by its behavior in relation to the vf:Resource and a vf:Process (consume, use, produce, etc.)</td></tr> -<tr><td>Properties</td><td>vf:action, vf:resource, vf:affectedQuantity, vf:eventStart, vf:note</td></tr> -</table> diff --git a/docs/specification/classes/group.md b/docs/specification/classes/group.md @@ -1,10 +0,0 @@ -### vf:Group - -<table> -<tr><td>rdf:type</td><td> owl:Class </td></tr> -<tr><td>rdfs:label</td><td>Group</td></tr> -<tr><td>rdfs:comment</td><td>A vf:Group is any kind of association of more than one person, which can be loosely or formally organized, but has economic agency as a group beyond any person.</td></tr> -<tr><td>rdfs:subClassOf</td><td>vf:Agent</td></tr> -<tr><td>owl:equivalentClass</td><td>foaf:Group</td></tr> -<tr><td>Properties</td><td></td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/classes/person.md b/docs/specification/classes/person.md @@ -1,10 +0,0 @@ -### vf:Person - -<table> -<tr><td>rdf:type</td><td> owl:Class </td></tr> -<tr><td>rdfs:label</td><td>Person</td></tr> -<tr><td>rdfs:comment</td><td>A natural person.</td></tr> -<tr><td>rdfs:subClassOf</td><td>vf:Agent</td></tr> -<tr><td>owl:equivalentClass</td><td>foaf:Person, schema:Person</td></tr> -<tr><td>Properties</td><td></td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/classes/process.md b/docs/specification/classes/process.md @@ -1,8 +0,0 @@ -### vf:Process - -<table> -<tr><td>rdf:type</td><td> owl:Class </td></tr> -<tr><td>rdfs:label</td><td>Process</td></tr> -<tr><td>rdfs:comment</td><td>A vf:Process is an activity that changes inputs into outputs. It could transform or transport vf:EconomicResource(s).</td></tr> -<tr><td>Properties</td><td>vf:name, vf:plannedStart, vf:plannedDuration, vf:input, vf:output, vf:note</td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/classes/relationship.md b/docs/specification/classes/relationship.md @@ -1,10 +0,0 @@ -### vf:Relationship - -<table> -<tr><td>rdf:type</td><td> owl:Class </td></tr> -<tr><td>rdfs:label</td><td>Relationship</td></tr> -<tr><td>rdfs:comment</td><td>A vf:Relationship denotes a relationship between 2 Agents of any type. -The relationship can be in the context of another Agent. -For example, Jane is a mentor of John in the context of the group Enspiral.</td></tr> -<tr><td>Properties</td><td>vf:subject, vf:relationship, vf:object, vf:context</td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/classes/resource.md b/docs/specification/classes/resource.md @@ -1,8 +0,0 @@ -### vf:EconomicResource - -<table> -<tr><td>rdf:type</td><td> owl:Class </td></tr> -<tr><td>rdfs:label</td><td>EconomicResource</td></tr> -<tr><td>rdfs:comment</td><td>An EconomicResource is a resource which is useful to people or the ecosystem.</td></tr> -<tr><td>Properties</td><td>vf:name, vf:trackingIdentity, vf:quantity, vf:category, vf:contains, vf:underlyingResource, vf:note</td></tr> -</table> diff --git a/docs/specification/classes/transformation.md b/docs/specification/classes/transformation.md @@ -1,9 +0,0 @@ -### vf:Transformation - -<table> -<tr><td>rdf:type</td><td> owl:Class </td></tr> -<tr><td>rdfs:label</td><td>Transformation</td></tr> -<tr><td>rdfs:comment</td><td>A vf:Transformation is an activity that transforms inputs into outputs. It causes a change in the composition of the vf:EconomicResource(s).</td></tr> -<tr><td>rdfs:subClassOf</td><td>vf:Process</td></tr> -<tr><td>Properties</td><td></td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/classes/transportation.md b/docs/specification/classes/transportation.md @@ -1,9 +0,0 @@ -### vf:Transportation - -<table> -<tr><td>rdf:type</td><td> owl:Class </td></tr> -<tr><td>rdfs:label</td><td>Transportation</td></tr> -<tr><td>rdfs:comment</td><td>A vf:Transportation is a change in location of vf:EconomicResource(s).</td></tr> -<tr><td>rdfs:subClassOf</td><td>vf:Process</td></tr> -<tr><td>Properties</td><td></td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/diagrams/uml.md b/docs/specification/diagrams/uml.md @@ -2,4 +2,6 @@  -Note: There are some differences in this representation and the RDF based representation. This is to support OO and relational implementations, as well as open vocabularies that are not RDF based. - \ No newline at end of file +Note: There are some differences in this representation and the RDF based representation. This is to support OO 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. + +Credit: https://support.draw.io/+ \ No newline at end of file diff --git a/docs/specification/diagrams/vowl.md b/docs/specification/diagrams/vowl.md @@ -1,3 +1,5 @@ ### RDF-based Representation  + +Credit: http://visualdataweb.de/+ \ No newline at end of file diff --git a/docs/specification/properties/action.md b/docs/specification/properties/action.md @@ -1,25 +0,0 @@ -### vf:action - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>action</td></tr> -<tr><td>rdfs:comment</td><td>A vf:action relates a process input or output (or other vf:IPOEVent) to a verb.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:EconomicEvent</td></tr> -<tr><td>rdfs:range (allowed values)</td><td></td></tr> -</table> - -##### Verbs associated with vf:action - -###### 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 - -###### Output - -* vf:create - 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- \ No newline at end of file diff --git a/docs/specification/properties/affectedquantity.md b/docs/specification/properties/affectedquantity.md @@ -1,11 +0,0 @@ -### vf:affectedQuantity - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>affectedQuantity</td></tr> -<tr><td>rdfs:comment</td><td>The quantity and unit of the event. This is the quantity that could be used to increment or decrement a resource, depending on the type of resource and type of event.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:EconomicEvent</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>qudt:QuantityValue</td></tr> -</table> - -(Need discussion: is this the same as duration, in case of work for example?)- \ No newline at end of file diff --git a/docs/specification/properties/category.md b/docs/specification/properties/category.md @@ -1,17 +0,0 @@ -### vf:category - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>category</td></tr> -<tr><td>rdfs:comment</td><td>A type or categorization that describes a resource.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:ResourceModel, vf:EconomicResource</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>an IRI??</td></tr> -</table> - -Resource categories are a Taxonomy. That means they can be defined very broadly and generally and maybe vaguely, or they can be defined very narrowly, -but fit into broader categories. - -So, for example, you may want an apple. Or you may want a green apple. Or you may want a Granny Smith apple. -Or you may want a Granny Smith apple from your neighboring farm. - -People can use the multitude of existing taxonomies for resources, or can also create their own as needed.- \ No newline at end of file diff --git a/docs/specification/properties/context.md b/docs/specification/properties/context.md @@ -1,11 +0,0 @@ -### vf:context - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>context</td></tr> -<tr><td>rdfs:comment</td><td>The larger context in which something occurs.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:Relationship, </td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:Agent</td></tr> -</table> - -This allows grouping of economic relationships and economic activity (future releases) into a context for coordination and accounting purposes.- \ No newline at end of file diff --git a/docs/specification/properties/currentlocation.md b/docs/specification/properties/currentlocation.md @@ -1,13 +0,0 @@ -### vf:currentLocation - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>currentLocation</td></tr> -<tr><td>rdfs:comment</td><td>The current place an item is, so that it can be found.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:EconomicResource</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>IRI?</td></tr> -</table> - -Location is a complex ontology of its own, from a mappable point of interest to a warehouse:room:aisle:row:tier. We will not repeat existing location ontologies. - -We simply require that any location referenced here has an IRI so it can be identified directly. - \ No newline at end of file diff --git a/docs/specification/properties/eventstart.md b/docs/specification/properties/eventstart.md @@ -1,9 +0,0 @@ -### vf:eventStart - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>eventStart</td></tr> -<tr><td>rdfs:comment</td><td>The starting date and optionally time of the event.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:EconomicEvent</td></tr> -<tr><td>rdfs:range (allowed values)</td><td></td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/properties/image.md b/docs/specification/properties/image.md @@ -1,9 +0,0 @@ -### vf:image - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>image</td></tr> -<tr><td>rdfs:comment</td><td>An image associated with an object, to help clarify it.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:Agent, vf:EconomicResource</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>???</td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/properties/input.md b/docs/specification/properties/input.md @@ -1,9 +0,0 @@ -### vf:input - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>input</td></tr> -<tr><td>rdfs:comment</td><td>Relates a process to its inputs.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:Process</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:EconomicEvent, vf:Commitment</td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/properties/issubstitutable.md b/docs/specification/properties/issubstitutable.md @@ -1,11 +0,0 @@ -### vf:isSubstitutable - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>isSubstitutable</td></tr> -<tr><td>rdfs:comment</td><td>Defines if any resources of that type can be freely substituted for any other resource of that type when used, consumed, traded, etc. </td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:ResourceModel, vf:EconomicResource</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:ResourceModel, vf:EconomicResource</td></tr> -</table> - -For example, "B9R-1-red DLP resin photopolymer" is probably a substitutable resource type. While each resource for a resource type called "English-Spanish translation" is probably not substitutable because each will be a different document.- \ No newline at end of file diff --git a/docs/specification/properties/name.md b/docs/specification/properties/name.md @@ -1,9 +0,0 @@ -### vf:name - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>name</td></tr> -<tr><td>rdfs:comment</td><td>An informal or formal textual identifier for an object. Does not imply uniqueness.</td></tr> -<tr><td>rdfs:domain (property of)</td><td></td></tr> -<tr><td>rdfs:range (allowed values)</td><td>skos:prefLabel</td></tr> -</table> - \ No newline at end of file diff --git a/docs/specification/properties/note.md b/docs/specification/properties/note.md @@ -1,9 +0,0 @@ -### vf:note - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>note</td></tr> -<tr><td>rdfs:comment</td><td>A freeform note or description of an object or item.</td></tr> -<tr><td>rdfs:domain (property of)</td><td></td></tr> -<tr><td>rdfs:range (allowed values)</td><td>skos:note</td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/properties/object.md b/docs/specification/properties/object.md @@ -1,11 +0,0 @@ -### vf:object - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>object</td></tr> -<tr><td>rdfs:comment</td><td>The object of the relationship.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:Relationship</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:Agent</td></tr> -</table> - -For example, in "Michael is a member of Enspiral", Enspiral is the object.- \ No newline at end of file diff --git a/docs/specification/properties/output.md b/docs/specification/properties/output.md @@ -1,9 +0,0 @@ -### vf:output - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>output</td></tr> -<tr><td>rdfs:comment</td><td>Relates a process to its outputs.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:Process</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:EconomicEvent, vf:Commitment</td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/properties/parent.md b/docs/specification/properties/parent.md @@ -1,11 +0,0 @@ -### vf:parent - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>parent</td></tr> -<tr><td>rdfs:comment</td><td>A more general type of resource.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:ResourceModel</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:ResourceModel</td></tr> -</table> - -For example, Herb is the parent resource type of Anise Hyssop, Goldenrod, Nettles, Red Clover, etc. Besides its usefulness in understanding taxonomies of resource types, this can be useful when one can define a general recipe that will work for many more specific types of resources.- \ No newline at end of file diff --git a/docs/specification/properties/primarylocation.md b/docs/specification/properties/primarylocation.md @@ -1,13 +0,0 @@ -### vf:primaryLocation - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>primaryLocation</td></tr> -<tr><td>rdfs:comment</td><td>The main place an agent is, often an address where activities occur and mail can be sent.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:Agent (and subclasses)</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>?</td></tr> -</table> - -Location is a complex ontology of its own, and we will not repeat existing location ontologies. - -In the case of primaryLocation, this is usually a mappable geographic location. It also could be a website address, as in the case of agents who have no physical location.- \ No newline at end of file diff --git a/docs/specification/properties/properties.md b/docs/specification/properties/properties.md @@ -1,21 +0,0 @@ -# Properties - -* [action](action.md) -* [affectedQuantity](affectedquantity.md) -* [category](category.md) -* [context](context.md) -* [currentLocation](currentlocation.md) -* [eventStart](eventstart.md) -* [image](image.md) -* [input](input.md) -* [name](name.md) -* [note](note.md) -* [object](object.md) -* [output](output.md) -* [primaryLocation](primarylocation.md) -* [quantity](quantity.md) -* [relationship](relationship.md) -* [resource](resource.md) -* [subject](subject.md) -* [trackingIdentifier](trackingidentifier.md) -* [underlyingResource](underlyingresource.md) diff --git a/docs/specification/properties/quantity.md b/docs/specification/properties/quantity.md @@ -1,11 +0,0 @@ -### vf:quantity - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>quantity</td></tr> -<tr><td>rdfs:comment</td><td>The current quantity and unit of the resource.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:EconomicResource</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>qudt:QuantityValue</td></tr> -</table> - -NOTE: a resource can have 0 quantity, one can use it for historical resources which some process consumed as well as for planned resources which a planned process will create.- \ No newline at end of file diff --git a/docs/specification/properties/relationship.md b/docs/specification/properties/relationship.md @@ -1,18 +0,0 @@ -### vf:relationship - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>relationship</td></tr> -<tr><td>rdfs:comment</td><td>A verb that describes a generic defined relationship that can be had between 2 Agents (or subclasses of). -Although it usually is, the relationship of a particular type does not have to be agreed to from both sides, for example "follow". -</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:Relationship</td></tr> -<tr><td>rdfs:range (allowed values)</td><td></td></tr> -</table> - -A relationship can be direct, like "steward" or "like", or more like a role. -Role types of relationships are often used for a person's role in an organization or group, -for example "grower" or "harvester" for a food network. - -There are a number of useful Properties in existing vocabularies that can be used. -Or people can create their own as needed.- \ No newline at end of file diff --git a/docs/specification/properties/resource.md b/docs/specification/properties/resource.md @@ -1,9 +0,0 @@ -### vf:resource - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>resource</td></tr> -<tr><td>rdfs:comment</td><td>Relates process input/output to a resource.</td></tr> -<tr><td>rdfs:domain (property of)</td>vf:EconomicEvent<td></td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:EconomicResource</td></tr> -</table>- \ No newline at end of file diff --git a/docs/specification/properties/subject.md b/docs/specification/properties/subject.md @@ -1,11 +0,0 @@ -### vf:subject - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>subject</td></tr> -<tr><td>rdfs:comment</td><td>The subject of a relationship.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:Relationship</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:Agent</td></tr> -</table> - -For example, in "Michael is a member of Enspiral", Michael is the subject.- \ No newline at end of file diff --git a/docs/specification/properties/trackingidentifier.md b/docs/specification/properties/trackingidentifier.md @@ -1,11 +0,0 @@ -### vf:trackingIdentifier - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>trackingIdentifier</td></tr> -<tr><td>rdfs:comment</td><td>Sometimes called "lot number", used for trackable batched resources. Sometimes called "serial number", used when each item must have a trackable identifier (like a computer). Could be used for other unique tracking identifiers.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:EconomicResource</td></tr> -<tr><td>rdfs:range (allowed values)</td><td></td></tr> -</table> - -Example: a lot of asparagus that will be distributed in smaller quantities but may need to be tracked to its source in case of an e-coli outbreak. diff --git a/docs/specification/properties/underlyingresource.md b/docs/specification/properties/underlyingresource.md @@ -1,11 +0,0 @@ -### vf:underlyingResource - -<table> -<tr><td>rdf:type</td><td>owl:ObjectProperty</td></tr> -<tr><td>rdfs:label</td><td>underlyingResource</td></tr> -<tr><td>rdfs:comment</td><td>A more concrete resource upon which a resource is based.</td></tr> -<tr><td>rdfs:domain (property of)</td><td>vf:EconomicResource</td></tr> -<tr><td>rdfs:range (allowed values)</td><td>vf:EconomicResource</td></tr> -</table> - -One example: a resource which defines the rental of an apartment has the apartment itself as its underlying resource. Another example: a virtual account resource can have an actual bank account as its underlying resource. - \ No newline at end of file diff --git a/docs/specification/properties/url.md b/docs/specification/properties/url.md @@ -1,9 +0,0 @@ -### vf:url - -<table> -<tr><td>rdf:type</td><td>owl:DatatypeProperty</td></tr> -<tr><td>rdfs:label</td><td>url</td></tr> -<tr><td>rdfs:comment</td><td>An internet address (we may need to be more exact? IRI?)</td></tr> -<tr><td>rdfs:domain (property of)</td><td></td></tr> -<tr><td>rdfs:range (allowed values)</td><td>?</td></tr> -</table> - \ No newline at end of file diff --git a/release-doc-in-process/ValueFlowsUML.png b/release-doc-in-process/ValueFlowsUML.png Binary files differ. diff --git a/release-doc-in-process/all_vf.TTL b/release-doc-in-process/all_vf.TTL @@ -6,6 +6,7 @@ @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix foaf: <http://xmlns.com/foaf/0.1/#> . @prefix dcterms: <http://purl.org/dc/terms/> . +@prefix qudt: <http://qudt.org/schema/qudt/> . <https://w3id.org/valueflows/> a owl:Ontology; @@ -13,108 +14,125 @@ dcterms:type <http://purl.org/adms/assettype/Ontology>; dcterms:status <http://purl.org/adms/status/UnderDevelopment>. + +# ABSTRACT CLASSES vf:Action a owl:Class ; rdfs:label "vf:Action" ; - rdfs:subClassOf rdf:Property . + rdfs:subClassOf rdf:Property ; + rdfs:comment "An action verb defining the kind of event, commitment, or intent." . -# TAXONOMY CLASSES -vf:TaxonomyItem a owl:Class ; - rdfs:label "vf:TaxonomyItem" . +#vf:TaxonomyItem a owl:Class ; +# rdfs:label "vf:TaxonomyItem" . -vf:ResourceTaxonomyItem a owl:Class ; +vf:ResourceTaxonomyItem a owl:Class ; rdfs:label "vf:ResourceTaxonomyItem" ; - rdfs:subClassOf vf:TaxonomyItem . + #rdfs:subClassOf vf:TaxonomyItem ; + rdfs:comment "A resource category, part of a resource taxonomy." . -vf:ProcessTaxonomyItem a owl:Class ; - rdfs:label "vf:ProcessTaxonomyItem" ; - rdfs:subClassOf vf:TaxonomyItem . +#vf:ProcessTaxonomyItem a owl:Class ; +# rdfs:label "vf:ProcessTaxonomyItem" ; +# rdfs:subClassOf vf:TaxonomyItem . -vf:ExchangeTaxonomyItem a owl:Class ; - rdfs:label "vf:ExchangeTaxonomyItem" ; - rdfs:subClassOf vf:TaxonomyItem . +#vf:ExchangeTaxonomyItem a owl:Class ; +# rdfs:label "vf:ExchangeTaxonomyItem" ; +# rdfs:subClassOf vf:TaxonomyItem . # PLAN CLASSES -vf:Intent a owl:Class ; - rdfs:label "vf:Intent" . +#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:Commitment a owl:Class ; - rdfs:label "vf:Commitment" . + rdfs:label "vf:Commitment" ; + rdfs:comment "A planned economic event or transfer that has been promised by an agent to another agent." . vf:Agreement a owl:Class ; - rdfs:label "vf:Agreement" . + rdfs:label "vf:Agreement" ; + rdfs:comment "Any type of agreement among economic agents, that can be referenced in VF to clarify the economic activity." . vf:ExchangeAgreement a owl:Class ; rdfs:label "vf:ExchangeAgreement" ; - rdfs:subClassOf vf:Agreement . + rdfs:subClassOf vf:Agreement ; + rdfs:comment "An agreement to exchange something with another agent(s), containing vf:Commitments towards that end." . # OBSERVATION CLASSES -vf:Resource a owl:Class ; - rdfs:label "vf:Resource" . +vf:EconomicResource a owl:Class ; + rdfs:label "vf:EconomicResource" ; + rdfs:comment "A resource which is useful to people or the ecosystem." . vf:Process a owl:Class ; - rdfs:label "vf:Process" . + rdfs:label "vf:Process" ; + rdfs:comment "An activity that changes inputs into outputs. It could transform or transport vf:EconomicResource(s), as well as simply issuing a resource so that it is available." . -vf:Fulfillment a owl:Class ; - rdfs:label "vf:Fulfillment" . - -vf:Event a owl:Class ; - rdfs:label "vf:Event" . +vf:Transportation a owl:Class ; + rdfs:label "vf:Transportation" ; + rdfs:subClassOf vf:Process ; + rdfs:comment "A process that changes the location of a resource(s) without changing the resource(s) itself." . -vf:Appreciation a owl:Class ; - rdfs:label "vf:Appreciation" . +vf:Transformation a owl:Class ; + rdfs:label "vf:Transformation" ; + 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 ; + 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.)" . vf:Agent a owl:Class ; rdfs:label "vf:Agent" ; - owl:equivalentClass foaf:Agent . + owl:equivalentClass foaf:Agent ; + rdfs:comment "A person or group with economic agency." . vf:Person a owl:Class ; rdfs:label "vf:Person" ; rdfs:subClassOf vf:Agent ; - owl:equivalentClass schema:Person , foaf:Person . - + owl:equivalentClass schema:Person , foaf:Person ; + rdfs:comment "A natural person." . + vf:Group a owl:Class ; rdfs:label "vf:Group" ; rdfs:subClassOf vf:Agent ; - owl:equivalentClass foaf:Group . - - -# TODO CLASSES + owl:equivalentClass foaf:Group ; + rdfs:comment "Any kind of association of more than one person, which can be loosely or formally organized, but has economic agency as a group beyond any person." . vf:Relationship a owl:Class ; - rdfs:label "vf:Relationship" . + rdfs:label "vf:Relationship" ; + rdfs:comment "An ongoing association between 2 Agents of any type." . + +vf:Fulfillment a owl:Class ; + rdfs:label "vf:Fulfillment" ; + rdfs:comment "The quantity that the vf:EconomicEvent fulfilled towards the vf:Commitment." . + +vf:Appreciation a owl:Class ; + rdfs:label "vf:Appreciation" ; + rdfs:comment "A way to tie an economic event that is given in loose fulfilment for another economic event, without commitments or expectations. Supports the gift economy." . vf:Location a owl:Class ; rdfs:label "vf:Location" . + + +# not sure about these -vf:Transportation a owl:Class ; - rdfs:label "vf:Transportation" ; - rdfs:subClassOf vf:Process . -vf:Transformation a owl:Class ; - rdfs:label "vf:Transformation" ; - rdfs:subClassOf vf:Process . +#vf:MaterialItem a owl:Class ; +# rdfs:label "vf:MaterialItem" ; +# rdfs:subClassOf vf:Resource . -vf:MaterialItem a owl:Class ; - rdfs:label "vf:MaterialItem" ; - rdfs:subClassOf vf:Resource . - -vf:Work a owl:Class ; - rdfs:label "vf:Work" ; - rdfs:subClassOf vf:Resource . - -vf:Service a owl:Class ; - rdfs:label "vf:Service" ; - rdfs:subClassOf vf:Resource . - -vf:Currency a owl:Class ; - rdfs:label "vf:Currency" ; - rdfs:subClassOf vf:Resource . +#vf:Work a owl:Class ; +# rdfs:label "vf:Work" ; +# rdfs:subClassOf vf:Resource . +#vf:Service a owl:Class ; +# rdfs:label "vf:Service" ; +# rdfs:subClassOf vf:Resource . +#vf:Currency a owl:Class ; +# rdfs:label "vf:Currency" ; +# rdfs:subClassOf vf:Resource . # #################################################################### @@ -122,139 +140,273 @@ vf:Currency a owl:Class ; vf:action a owl:ObjectProperty ; - rdfs:domain vf:Intent , vf:Commitment , vf:Event ; - rdfs:range vf:Action . + rdfs:label "action" ; + rdfs:domain vf:EconomicEvent ; + rdfs:range vf:Action ; + rdfs:comment "Relates a process input or output (or other vf:EconomicEVent) to a verb, such as consume, produce, work, improve, etc." . + +vf:committedAction + a owl:ObjectProperty ; + rdfs:label "committed action" ; + rdfs:domain vf:Commitment ; + rdfs:range vf:Action ; + rdfs:comment "Relates a process input or output (or other vf:EconomicEVent) to a verb, such as consume, produce, work, improve, etc." . + +# need one for Intent too + +# Do we want to have the direction this way, to the process? or containers from the process? or both? vf:inputOf a owl:ObjectProperty ; - rdfs:domain vf:Event ; + rdfs:label "input of" ; + rdfs:domain vf:EconomicEvent ; rdfs:range vf:Process . vf:outputOf a owl:ObjectProperty ; - rdfs:domain vf:Event ; + rdfs:label "output of" ; + rdfs:domain vf:EconomicEvent ; rdfs:range vf:Process . -vf:commitedInputOf +vf:committedInputOf a owl:ObjectProperty ; + rdfs:label "committed input of" ; rdfs:domain vf:Commitment ; rdfs:range vf:Process . -vf:commitedOutputOf +vf:committedOutputOf a owl:ObjectProperty ; + rdfs:label "committed output of" ; rdfs:domain vf:Commitment ; rdfs:range vf:Process . -vf:intendedInputOf - a owl:ObjectProperty ; - rdfs:domain vf:Intent ; - rdfs:range vf:Process . +#vf:intendedInputOf +# a owl:ObjectProperty ; +# rdfs:domain vf:Intent ; +# rdfs:range vf:Process . -vf:intendedOutputOf - a owl:ObjectProperty ; - rdfs:domain vf:Intent ; - rdfs:range vf:Process . +#vf:intendedOutputOf +# a owl:ObjectProperty ; +# rdfs:domain vf:Intent ; +# rdfs:range vf:Process . vf:resourceCategory a owl:ObjectProperty ; rdfs:label "category" ; - rdfs:domain vf:Resource , vf:Intent , vf:Commitment ; - rdfs:range vf:ResourceTaxonomyItem . + rdfs:domain vf:EconomicResource ; + rdfs:range vf:ResourceTaxonomyItem ; + rdfs:comment "A type or categorization that describes a resource, at any level of granularity." . -vf:processCategory +vf:committedCategory a owl:ObjectProperty ; - rdfs:domain vf:Process ; - rdfs:range vf:ProcessTaxonomyItem . + rdfs:label "committed category" ; + rdfs:domain vf:Commitment ; + rdfs:range vf:ResourceTaxonomyItem ; + rdfs:comment "A type or categorization that describes a resource committed, at any level of granularity." . -vf:exchangeCategory - a owl:ObjectProperty ; - rdfs:domain vf:ExchangeAgreement ; - rdfs:range vf:ExchangeTaxonomyItem . +# will need one for Intent too + +# waiting to do the recipe model + +#vf:processCategory +# a owl:ObjectProperty ; +# rdfs:domain vf:Process ; +# rdfs:range vf:ProcessTaxonomyItem . + +#vf:exchangeCategory +# a owl:ObjectProperty ; +# rdfs:domain vf:ExchangeAgreement ; +# rdfs:range vf:ExchangeTaxonomyItem . vf:parent + a owl:ObjectProperty ; rdfs:label "parent" ; - a owl:ObjectProperty . + rdfs:domain vf:ResourceTaxonomyItem ; + rdfs:range vf:ResourcetaxonomyItem ; + rdfs:comment "A more general or broader category of resource." . -vf:involveResource +vf:involvesResource a owl:ObjectProperty ; - rdfs:domain vf:Intent , vf:Commitment ; - rdfs:range vf:Resource . + rdfs:label "involves resource" ; + rdfs:domain vf:Commitment ; # create one of these for intents + rdfs:range vf:EconomicResource ; + rdfs:comment "EconomicResource the Commitment intends or commits to affect. Could be an actual resource or a category or type of resource." . vf:underlyingResource a owl:ObjectProperty ; + rdfs:label "underlying resource" ; rdfs:domain vf:Resource ; - rdfs:range vf:Resource . + rdfs:range vf:Resource ; + rdfs:comment "A more concrete resource upon which a resource is based." . vf:relationship a owl:ObjectProperty ; + rdfs:label "relationship" ; rdfs:domain vf:Relationship ; rdfs:label "vf:relationship" ; - rdfs:range rdf:Property . - -vf:commitsTo - a owl:ObjectProperty ; - rdfs:domain vf:Commitment ; - rdfs:range vf:Intent . - + rdfs:range rdf:Property ; # think about creating a subproperty for these + rdfs:comment "A verb that describes a generic defined relationship that exists between 2 agents." . -vf:fulfills - a owl:ObjectProperty ; - rdfs:domain vf:Event; - rdfs:range vf:Fulfillment , vf:Intent , vf:Commitment . +#vf:commitsTo +# a owl:ObjectProperty ; +# rdfs:domain vf:Commitment ; +# rdfs:range vf:Intent ; +# rdfs:comment "The Intent that an economic agent promises to fulfill." . vf:affects a owl:ObjectProperty ; - rdfs:domain vf:Event ; - rdfs:range vf:Resource . + rdfs:label "affects" ; + rdfs:domain vf:EconomicEvent ; + rdfs:range vf:EconomicResource ; + rdfs:comment "The economic resource that is decremented or incremented by the economic event, or just what the economic event is about." . vf:appreciationOf a owl:ObjectProperty ; + rdfs:label "appreciation of" ; rdfs:domain vf:Appreciation ; - rdfs:range vf:Event . + rdfs:range vf:EconomicEvent ; + rdfs:comment "The economic event being appreciated (gift economy)." . vf:appreciationWith a owl:ObjectProperty ; + rdfs:label "appreciation with" ; rdfs:domain vf:Appreciation ; - rdfs:range vf:Event . + rdfs:range vf:EconomicEvent ; + rdfs:comment "The economic event implemented in appreciation (gift economy)." . vf:provider a owl:ObjectProperty ; - rdfs:domain vf:Event, vf:Intent, vf:Commitment ; + rdfs:domain vf:EconomicEvent ; rdfs:label "provider" ; - rdfs:range vf:Agent . + rdfs:range vf:Agent ; + rdfs:comment "The economic agent from whom the economic event is initiated." . vf:receiver a owl:ObjectProperty ; - rdfs:domain vf:Event , vf:Intent, vf:Commitment ; + rdfs:domain vf:EconomicEvent ; rdfs:label "receiver" ; - rdfs:range vf:Agent . + rdfs:range vf:Agent ; + rdfs:comment "The economic agent whom the economic event is for." . + +vf:committedProvider a owl:ObjectProperty ; + rdfs:domain vf:Commitment ; + rdfs:label "committed provider" ; + rdfs:range vf:Agent ; + rdfs:comment "The economic agent who commits to a future economic event." . +vf:committedReceiver a owl:ObjectProperty ; + rdfs:domain vf:Commitment ; + rdfs:label "committed receiver" ; + rdfs:range vf:Agent ; + rdfs:comment "The economic agent whom a future economic event is committed to." . + +#vf:intendedProvider a owl:ObjectProperty ; +# rdfs:domain vf:Intent ; +# rdfs:label "provider" ; +# rdfs:range vf:Agent ; +# rdfs:comment "The economic agent who would like to provide a future economic event." . + +#vf:intendedReceiver a owl:ObjectProperty ; +# rdfs:domain vf:Intent ; +# rdfs:label "receiver" ; +# rdfs:range vf:Agent ; +# rdfs:comment "The economic agent who would like to receive a future economic event." . + vf:subject a owl:ObjectProperty ; rdfs:domain vf:Relationship ; rdfs:label "vf:subject" ; - rdfs:range vf:Agent . + rdfs:range vf:Agent ; + rdfs:comment "The subject of a relationship between 2 agents." . vf:context a owl:ObjectProperty ; rdfs:domain vf:Relationship ; rdfs:label "context" ; - rdfs:range vf:Agent . + rdfs:range vf:Agent ; + rdfs:comment "The larger context of a relationship between 2 agents, used where the relationship is not relevant outside of that context." . vf:object a owl:ObjectProperty ; rdfs:domain vf:Relationship ; rdfs:label "object" ; - rdfs:range vf:Agent . + rdfs:range vf:Agent ; + rdfs:comment "The object of a relationship between 2 agents." . + +vf:under a owl:ObjectProperty ; + rdfs:domain vf:EconomicEvent ; + rdfs:label "under" ; + rdfs:range vf:Agreement ; + rdfs:comment "Reference an agreement between agents which specifies the rules or policies which govern this event." . -vf:underAgreement a owl:ObjectProperty ; - rdfs:domain vf:Event , vf:Intent, vf:Commitment ; - rdfs:label "underAgreement" ; - rdfs:range vf:Agreement . +vf:committedUnder a owl:ObjectProperty ; + rdfs:domain vf:Commitment ; + rdfs:label "committed under" ; + rdfs:range vf:Agreement ; + rdfs:comment "Reference an agreement between agents which specifies the rules or policies which govern this commitment." . vf:inExchangeFor a owl:ObjectProperty ; - rdfs:label "inExchangeFor" ; + rdfs:label "in exchange for" ; rdfs:domain vf:Commitment ; - rdfs:range vf:Event . + rdfs:range vf:EconomicEvent ; + rdfs:comment "References the economic event that generated the commitment, in cases where based on an agreement, an agent commits to some reciprocity if an event occurs." . vf:contains a owl:ObjectProperty ; - rdfs:domain vf:Resource ; rdfs:label "contains" ; - rdfs:range vf:Resource . + rdfs:domain vf:EconomicResource ; + rdfs:range vf:EconomicResource ; + rdfs:comment "Used when a stock economic resource contains units also defined as economic resources." . + + +vf:quantity a owl:ObjectProperty ; + rdfs:label "quantity" ; + rdfs:domain vf:EconomicResource ; + rdfs:range qudt:QuantityValue ; + rdfs:comment "The current amount and unit of the economic resource." . + +vf:affectedQuantity a owl:ObjectProperty ; + rdfs:label "affected quantity" ; + rdfs:domain vf:EconomicEvent ; + rdfs:range qudt:QuantityValue ; + rdfs:comment "The quantity and unit of the event. This is the quantity that could be used to increment or decrement a resource, depending on the type of resource and type of event." . + +vf:currentLocation a owl:ObjectProperty ; + rdfs:label "current location" ; + rdfs:domain vf:EconomicResource ; + rdfs:range vf:Location ; + rdfs:comment "The current place an economic resource is located. Could be at any level of granularity, from a town to an address to a warehouse location. Should be mappable." . + +vf:primaryLocation a owl:ObjectProperty ; + rdfs:label "primary location" ; + rdfs:domain vf:Agent ; + rdfs:range vf:Location ; + rdfs:comment "The main place an agent is located, often an address where activities occur and mail can be sent. This is usually a mappable geographic location. It also could be a website address, as in the case of agents who have no physical location." . + +vf:start a owl:ObjectProperty ; + rdfs:label "start" ; + rdfs:domain vf:EconomicEvent ; + rdfs:comment "The starting date and optionally time of the economic event." . + +vf:duration a owl:ObjectProperty ; + rdfs:label "duration" ; + rdfs:domain vf:EconomicEvent ; + rdfs:comment "The observed duration of the economic event." . + +vf:image a owl:DatatypeProperty ; + rdfs:label "image" . + +vf:url a owl:DatatypeProperty ; + rdfs:label "url" . + +vf:name a owl:DatatypeProperty ; + rdfs:label "name" ; + rdfs:comment "An informal or formal textual identifier for an object. Does not imply uniqueness." . + +vf:note a owl:ObjectProperty ; + rdfs:label "note" ; + rdfs:range skos:note ; + rdfs:comment "A textual comment or description." . + +vf:trackingIdentifier a owl:DatatypeProperty ; + rdfs:label "tracking identifier" ; + rdfs:domain vf:EconomicResource ; + rdfs:comment "Sometimes called lot number, used for trackable batched resources. Sometimes called serial number, used when each item must have a trackable identifier (like a computer). Could also be used for other unique tracking identifiers." . + +# isSubstitutable "Defines if any resources of that type can be freely substituted for any other resource of that type when used, consumed, traded, etc." # ################################ action verbs
