valueflows / valueflo.ws

The website.

Valueflows vf vocabs

Here is the current release spec, which also includes concepts: https://valueflo.ws/

Some specific links of interest for devs:

• Classes and Properties. This is the standard specification format, which includes the VF namespace only. (We have tried to re-use other vocabularies when we can.) For a view of the whole model with references to the vocabularies used, see this diagram.
• Other Namespaces/Terms. This references the other vocabulary elements that are also necessary for a complete value flows economic model.
• RDF Reference This is the "turtle" file that is the system of record source for the specification. It includes only the VF namespace.
• GraphQL Reference. This is actively used, and maintained mostly by the projects using it. It includes the whole vocabulary.
• JSON-schema Reference. This is out of date, but will be updated upon request if a project wants to use it. It includes the whole vocabulary.
• Procedures for moving changes to the website.

If you would like to be part of the Valueflows conversation, please raise an issue here, or fork this or any of the related repositories and issue pull requests. You can also pop into our welcome matrix chat to make comments, ask questions, or introduce yourself!

Also please visit the matrix chat if you have difficulty accessing the gitlab repositories! There have been closures due to spam that may affect your ability to register.

License

This vocabulary and documentation is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Domain info

The domain name valueflo.ws is registered at gandi.net. The people with access currently are Lynn Foster and elf Pavlik. The registration is paid through 2027-10-01.

valueflo.ws's Issues

URL structure

Currently I see at least two categories of content which we may want host on valueflo.ws

vocab terms

particular terms which https://w3id.org/valueflows/ will redirect to eg. https://w3id.org/valueflows/Transfer

general documentation

wiki style documentation which explains some pattern in more depth, often not specific to a single term eg. 'Multilingual Content'

Options

deep path

• https://valueflo.ws/ns/Transfer
• https://valueflo.ws/docs/multilingual

subdomain

• https://valueflo.ws/Transfer
• https://docs.valueflo.ws/multilingual

path exception - docs

• https://valueflo.ws/Transfer
• https://valueflo.ws/docs/multilingual

this one would have https://valueflo.ws/docs/ which doesn't map to a property or class

Any large version of the UML diagram ?

The image at https://valueflo.ws/specification/diagrams/uml.html is really small, to the point of being useless, and I can't find any pointer to a larger version. It is however a key entry point to anyone wanting to understand the vocabulary.

building examples

how do we want to build our examples into our website?

for me: i'm thinking in the short-term we want to copy the '.jsonld' files to https://valueflo.ws/examples/ simply so they can reference each other without using rawgit. in the long-term, i imagine it'd be really sweet to have our examples standardized into some semantic format (skos documentation?) and integrated with our docs, possibly even automatically viewed with JSON-LD playground.

https vs http

Moving this from agent / #23.

From @almereyda:
Can I assist in setting up TLS for https://valueflo.ws, which doesn't work
yet?
It seems we should make it available right from the start, so no http links
get spawned over the web.

From Lynn:
@almereyda sounds like a good idea. Does the certificate cost much?

serve namespace files

hey @elf-pavlik, can you explain what files (and formats) should be in the ns directory? i'm happy to get continuous deployment setup across all our repos so a push to anywhere deploys the namespace files at https://valueflo.ws (so we can migrate away from using rawgit), but i'm not sure what files should be there.

also, to clarify, this question is not about serving these files, just building (assembling) them, as i want to keep those steps separate.

rename to `openvocab.github.io`

i like this idea of having a website repo for our vocab which includes the context.jsonld. if we rename this repo to openvocab.github.io, then GitHub will host the master branch as a website at that URL (which we can CNAME to a different URL once we decide on valueflows/agent#23).

Website certificate errors

It seems the valueflo.ws website generates expired certificate errors blocking access to the site.

Error code: SEC_ERROR_EXPIRED_CERTIFICATE