Thank you. I will consider creating relationship objects instead. From a UI perspective (for the use case I was trying to solve for) I feel it is more straightforward to enter reifiable data over creating a new relationship object --> saving the form --> and then clicking into the new object to add the associated data.
Thanks again. I always appreciate learning best practices and recommendations to improve my modeling. GaBriella Branson Interagency Wildland Fire - Knowledge Manager [cid:[email protected]] From: [email protected] <[email protected]> On Behalf Of Holger Knublauch Sent: Monday, January 29, 2024 12:39 PM To: 'Bohms, H.M. (Michel)' via TopBraid Suite Users <[email protected]> Subject: [EXTERNAL] Re: [topbraid-users] Reifiable by This email has been received from outside of DOI - Use caution before clicking on links, opening attachments, or responding. Yes, only one level is supported. The general alternative to using reification is to introduce relationship objects, lifting the reification info into the main ontology. Some people argue that reification should not be used when it is really the representation of a relationship. Instead, it should only be used for cases like provenance of triples and other true metadata. Holger On 29 Jan 2024, at 8:24 pm, 'GaBriella Branson' via TopBraid Suite Users <[email protected]<mailto:[email protected]>> wrote: Hello, Is there a limit to how "deep" reifiable statements can go? I have a class with a property that has a node shape it is reifiable by. Within the node shape I would like to add another layer making one of my properties reifiable by yet another node shape. It does not appear that the shape within the shape is working. First "layer" on the class: (this one works) <performed by.JPG> And this is the layer (a node shape on a node shape) that is not working: <performed by shape.JPG> Thanks in advance for any clarification you may have to explain what I should be expecting. -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected]<mailto:[email protected]> --- 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 [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/fba32925-ed8a-4ca6-a10b-a45f8dd25ddcn%40googlegroups.com<https://groups.google.com/d/msgid/topbraid-users/fba32925-ed8a-4ca6-a10b-a45f8dd25ddcn%40googlegroups.com?utm_medium=email&utm_source=footer>. <performed by shape.JPG><performed by.JPG> -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected]<mailto:[email protected]> --- 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 [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/0520CECA-9980-4662-93EC-EE9195DF8F39%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/0520CECA-9980-4662-93EC-EE9195DF8F39%40topquadrant.com?utm_medium=email&utm_source=footer>. -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CO6PR09MB7319419874B5AD99951F72EDDA7E2%40CO6PR09MB7319.namprd09.prod.outlook.com.
