valueflows docs
git clone
Log | Files | Refs | README

commit e95bb1597abb2be0ba66f4318071f9d786b59e6b
parent 9c44f4854ecae865bf6cefb090c4d23d58e42a08
Author: Lynn Foster <>
Date:   Sun, 15 May 2016 18:59:35 -0500

Aminutes/ | 23+++++++++++++++++++++++
1 file changed, 23 insertions(+), 0 deletions(-)

diff --git a/minutes/ b/minutes/ @@ -0,0 +1,23 @@ + +* [use YAML for all examples]( &mdash; elf Pavlik + +We will give this a try, we will be able to get to all LOD formats from YAML. Can use JSON-LD instead if easier or generating. + +* What formats of output do we want to support in VF? + +All + +* Definitions and Use Cases (see README of each repo) &mdash; elf Pavlik + +Pavlik is listing use cases and linking to a separate definition page for each repo. + +* OWL/RDFS classes &`rdf:type` (`@type` in JSON-LD) vs. SKOS topics & vf:kind/vf:variant/vf:taxon/vf:classifiedAs/??? + +Discussion of various levels of specificity in resource types and probably other types (process types), referring to existing links vs defining some vf LOD elements + +* JSON-LD context can handle aliases like `"name": "skos:prefLabel"`, so we don't need to redefine common terms in `vf:` namespace &mdash; elf Pavlik + * Library helpful in javascript + + Left for later + + * Not on the agenda: We spent some time discussion Transfer vs Transportation, Conversations for Agreement. Didn't capture the notes.