Check whether the CRS4 validator supports these layers of validation

[elichad]

1. JSON-LD syntax - third-party tools
2. Check that all terms used are in the context
3. Base specification (automated checks for MUST statements) - RDF shapes, LinkML schema, or similar
4. Best practices (automated + human checks) - target more of the SHOULD statements in the base spec
5. One or more user-specified profiles (automated + human checks) - must handle profile inheritance
6. Crate contents match local paths used in metadata

[OliverWoolland]

Linkml has cardinality https://linkml.io/linkml/schemas/slots.html#cardinality

[ianhinder]

This is blocked waiting for evaluation of rocrate-validator.

[ianhinder]

The task now is to check whether the CRS4 validator supports these layers of validation.

[elichad]

CRS4 validator support for the layers listed:

1. Yes
2. No, I've just made Validate that all terms used in the metadata are in the JSON-LD @context crs4/rocrate-validator#67 to request this
3. Yes
4. Yes, where these are machine-testable (using the option --requirement-severity [OPTIONAL|RECOMMENDED|REQUIRED])
5. Yes, where these are machine-testable
   • Profile developers must provide SHACL validation files for the profile
   • Profile inheritance is supported
   • Multiple profiles can be selected in the same test run
   • Attempts to automatically detect which profiles to check; falls back on human input
6. Not as of the most recent tagged version (v0.5.0), but in progress right now (see Check for data entity existence in the RO-Crate payload crs4/rocrate-validator#60 and feat: check data entity existence in RO-Crate payload crs4/rocrate-validator#66

I don't think we need to create any new tools for anything here, just extend the CRS4 validator through the linked issues to cover the missing parts.