Aida 674

[sharknc]

• Created hypothesis restriction to enforce all clusters must be homogeneous by base class (Entity, Event, or Relation)
• Created valid and invalid test cases to validate the new aforementioned hypothesis restriction
• Updated all other hypothesis test cases that were impacted by the required importance value
• Updated all Hypothesis examples to include more detailed notification strings to help disambiguate output for https://nextcentury.atlassian.net/wiki/spaces/AIDAC/pages/507347434/Example+AIF+that+pass+and+fail+NIST+validations

[eaciv]

Requesting a change to the SHACL to get a better violation report

[eaciv]

Can't tell from the return value which cluster or Entity/Event/Relation violates this. Rather than a count, this should probably indicate which Entity/Event/Relation doesn't match which cluster.

[sharknc]

Updated.

[eaciv]

Your shacl works, but having the values in the message is a little different than what I've seen. If you want to put the violation into report parameters, take a look at this:
674Suggestion.patch.txt

I tried to add this to our conversation, but it wouldn't let me attach files there.

[sharknc]

Your shacl works, but having the values in the message is a little different than what I've seen. If you want to put the violation into report parameters, take a look at this:
674Suggestion.patch.txt

I tried to add this to our conversation, but it wouldn't let me attach files there.

I see. I thought the goal was to get the error in the resultMessage, but after seeing it in the report seems like a much better solution. Also, I didn't realize there were other pre-bound variables like $value that we can attach to, very cool, thanks for the heads up on that. I have made your suggested updates so the report now shows the erroneous cluster and cluster member in the report.