Skip to content

Unify INFO and WARNING constraints on target classes

Nicola Stoira requested to merge task-409-info into master

See comments here: https://git.dcc.sib.swiss/sphn-semantic-framework/workingfair/-/issues/409#note_71849

Maybe to revisit are the elements returned by the SELECT statements that then appears in the validation report.

Latest changes:

  • Add path to the message for INFO and code WARNING constraints
  • Add prefixes for the root concepts into the SPARQL queries, therefore remove the full paths and report the properties with the root node IRIs replaces by the prefixes
  • In case the project schema does not define the root project concept as child of SPHNConcept (I suppose it should not happen, I had a lucid schema that was not doing it), then when replacing the properties check check if any root IRI is in the property string. If not we return the property as <property>. So the full IRI with <> signs.
  • Full IRIs replaces all over the SHACL. If you compare the SHACL files, except from the shifting of the constraints, you should be able to get an overview of the differences.

@philip.krauss

Edited by Nicola Stoira

Merge request reports