(possibly a future VOWEL - web vocabulary language)
This is ongoing work to modify the DC-Description Set Profile, taking into account the vocabularies of ShEx and SHACL.
DSP vocabulary project
- Proposed vocabulary for profiles
- DSP ontology
- Diagram for this vocabulary
- Diagram with rules proposes a possible way to include more complex rules within the profile
- Comparison of the proposed vocabulary with other profile vocabularies, including DSP
Background on project
Basic use cases
- People need a simple way to describe their metadata terms for use and reuse
- People need a simple way to convey their data model to others
- There is a need for a way to define and communicate the "business rules" for their data; an extra plus is if those rules are or can be made actionable
- Define a basic vocabulary (a core) for creating metadata application profiles including some basic constraints
- Extra: make this modular so units can be reused
- Define formal validation rules for basic vocabulary
- Extra: create these as code, or that can be converted to code
- Extra: make these modular and reusable
Requirements is a list of requirements.
Use cases is a gathering of use cases relevant to the task.
Comparison with BIBFRAME profiles, and others
Patterns proposes a basic list of design patterns used for metadata description and validation.
Description Set Profile - 2 is a re-writing of the DSP document.
A directory with some attempts at creating CSV files for a simple profile.
From 2014 to 2016 a Dublin Core task group met to discuss the requirements for an application profile for RDF data. These requirements were input to the W3C RDF validation working group that developed SHACL. RDF validation, however, is not the same as a profile, therefore a suitable "core" of functions for simple application profiles is still needed.
This site is one vision of a simple solution to the needs of metadata developers for a standard application profile definition. It leans toward RDF metadata but could be applied to other solutions. The basic assumption (see the Requirements document) is that there are many people designing and employing metadata who do not have either extensive metadata training nor available tools to aid them. In keeping with its history of providing a core vocabulary for metadata, the documents here attempt to define a very basic core vocabulary for the description of metadata profiles.
Many metadata profiles "in the wild" make use of tables (rows and columns) in their documentation. For this reason, this project includes an alignment with the W3C's tabular metadata work (also known as CSV on the Web, or CSVW). Such a solution would allow developers to create their metadata as a set of tables, which could then be converted to serializations such as RDF or JSON. These profiles would also support instance data in table form. (Support for non-tabular profiles is not ruled out. This can be considered a first, experimental step using tables as a "low hanging fruit.")
Eventually, it is desirable that metadata profiles be actionable. Part of this would be the ability to transform profile descriptions into validation schemas for the instance data that the profile defines. Thus a profile would generate the code needed to validate instance data that professes to follow that profile. Currently, DCMI is working with the ShEx working group to align the metadata profile proposal with ShEx validation rules.