This question is directed at anyone in this group who is fluent in SHACL. I'm looking for guidance on best practices for modeling the following kind of pattern:
A PowerMeasurementDevice takes measurements of Power. Is it better practice to put a SHACL constraint on the instances of a class called PowerMeasurement (that they should be measurements of Power), where: PowerMeasurementDevice producesMeasurements PowerMeasurement . or, should I just define a property shape for PowerMeasurementDevice such that the property producesMeasurements has the appropriate constraints? In this case, I don't need to create a special class called PowerMeasurement. Any thoughts one way or the other? I'm leaning toward the explicit definition of a PowerMeasurement class, but it's more intuition than principle. Steve -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAGUep87ZvBUe0urm5V6rxFPJOVpYCzG3Aa0qz7DxFBH-9TR9Wg%40mail.gmail.com.
