A repo for vocabs built for Solid applications.
Ontology design and development has been done for decades in the conte
The goal of this repo is to provide a straightforward and opinionated means for developers in the Solid ecosystem - especially those with no previous exposure to the Semantic Web stack - to design and publish vocabularies for their applications.
To support this, we will set up light-weight automation for:
- Collaborative development; including enabling developers to take ownership over the vocabularies they create
- Linting and best practises for creating ontologies
- Clear and concise guidance on how to create and publish a new vocabulary
In the future we may also:
- Establish tooling to support automated publishing of vocabs to the repo e.g. if created by WebProtege
The following, whilst important, are not in scope for this repository:
- Be a comprehensive index of all vocabularies that exist. There is a need for tooling targeted at Solid developers to support this discovery, in the meantime use existing resources such as:
- The Linked Open Vocabulary, and
- Schemas with large sets of concepts such as schema.org
- Provide tooling to generate artefacts - such as shapes and schemas - inlcuding the proposed shape repo - for which there are already some actions available
- Provide analytics of which applications are using which vocabularies
- Developing best practises and standards for ensuring that applications that are logically inconsistent are not corrupting each others data
The following are open decisions:
- High priority
- Where do vocabs get published to (w3c.org, w3.id, purl, solidproject.org, theodi.org, ...)
- Medium priority
- How are we going to go about versioning vocabularies
- What best practises do we want to enforce. Do we want to constrain to only enabling particular ontology types (e.g. OWL, RDFS)
- Low priority
- What tooling do we want to create to support developers in creating / editing ontologies (e.g. WebProtege)