This is an example of how SHACL shapes can be modularized, using title form shapes as illustration. There are a number of open questions, repeated below from the top of bibliotek-o_shapes_form_title.ttl. If we like this approach we can follow through with the implementation throughout.
Import of non-versioned ontologies (BF) - can we import from file system?
Do we give these terms a different namespace from the main file, and do imports, or does it work
to just put them in the same namespace? (latter preferred if it works).
Change all blank nodes to URI resources
Make sure use of HasTitlePropertyShape to define the title property shape on a work form works
Directory structure and naming conventions
Should implementations import these files or copy them into a "target-shapes" directory?
Should each file be a separate shapes module with a different namespace? Then need to use imports between files.
Conventions for form shapes vs validation shapes. Using form-shapes directory for now, later if we do validation can have sibling validation-shapes directory. But will it be possible to maintain complete bifurcation? (Doesn't need to be addressed if/until we start working on validation shapes.
This is an example of how SHACL shapes can be modularized, using title form shapes as illustration. There are a number of open questions, repeated below from the top of bibliotek-o_shapes_form_title.ttl. If we like this approach we can follow through with the implementation throughout.