rdfs:label "Process specification"@en ; rdfs:label "process specification"@en ; rdfs:label "Process Specification"@en ;
Good question. The only thing we have used the labels for so far is for diagrams.
Without having a strong opinion, I lean towards the third for classes because using in a sentence seems like it might refer to the class, not the concept in general? And for properties, all lower case?
But I'm very open to suggestion on this, I don't feel like I have anywhere close to enough experience to answer. I'd be interested in any info on what people generally do in rdf. @hoijui:fabcity.hamburg @elf-pavlik [Answering inline because it seems I couldn't at-mention in a reply.]
vf:deliver-service, while all the others use camel-casing, like
what is the state of the project?
I see a definition of a common vocabulary
is there an implementation yet?
The first implementation was the graphql API in https://github.com/FreedomCoop/valuenetwork/tree/master/valuenetwork/api
Two new implementations are in progress:
is there something being used by organisations?
Is there a product or something that gathers funding for sustainability of the project?
Each of those software projects has some funding, but none for Valueflows the vocabulary project.
Hi @samrose I'll be in and out here for a few days. The owl spec is the "system of record" for VF. We have said we would maintain RDF feed here https://w3id.org/valueflows#. But nobody has wanted it yet, and we haven't implemented it. Is that what you are looking for? And/or are there other things that would be needed to "publish a working RDF ontology"? Eager to make this happen, and to see an RDF based implementation.
Another thing to keep in mind: The VF namespace covers most of what is needed for a "complete" working ontology for economic activity, but not all. This page https://valueflo.ws/specification/external-terms.html has the other elements, because we decided to re-use where we could. And they are all on the UML model with namespace noted https://raw.githubusercontent.com/valueflows/valueflows/master/release-doc-in-process/ValueFlowsUML.png.
rdfs:range, don't restrict anything only lead to additional statements being inferred. ShEx Triple Constaints provide a clear way to define valid set of values. One could think of it as JSON Schema for RDF.