Cookbook: section on SHACL

[kcoyle]

The Cookbook needs a section filled in on converting a DCTAP to SHACL.

[sfolsom]

Will this section of the Cookbook provide guidance on sh:message for providing more context on sh:severity violations and warnings? Or is there somewhere else where this information is available? I've seen open related issues/comments, so maybe this hasn't been decided.

[philbarker]

@sfolsom we might cover how to define severity and a message in extensions to DCTAP (e.g. as extra columns in the table) so that they can be encoded SHACL; but they will be suggestions only, nothing about converting to SHACL will be normative.

[kcoyle]

@sfolsom We are always looking for examples that folks can relate to. "Real" examples tend to be too complex, but if you can tell/send a reduced example from your work that however "looks real" that would be appreciated. It doesn't have to be in code - a use case would be great. Thanks.

[sfolsom]

Thanks for the response. The idea of keeping SHACL-specific work non-normative makes sense.

To provide context to the question, I'm part of a PCC group thinking about interoperability of BIBFRAME data, and we're starting to define shapes, and thinking about how to have meaningful validation reports that include more than pass/fail violations. There's a number of properties that we have designated as "required if applicable" where a sh:Violation or sh:Warning with a sh:resultMessage would be useful.