Currently the only way to see the generated SHACL graphs from the DCTap files is to use the bf-demo-validation-tool to load the DCTap tsv files and then copy and save the resulting SHACL graph as a serialized RDF file. To encourage re-use and allow for other SHACL validation workflows outside of the demo tool, having these SHACL graphs generated as version artifacts would be beneficial.
Currently the only way to see the generated SHACL graphs from the DCTap files is to use the bf-demo-validation-tool to load the DCTap tsv files and then copy and save the resulting SHACL graph as a serialized RDF file. To encourage re-use and allow for other SHACL validation workflows outside of the demo tool, having these SHACL graphs generated as version artifacts would be beneficial.