To wrap this all around, what is the recommended way to share those shapes i.e. when writing the data, and the shapes are in their own ontology, as pure nodeshape, how do we link to it from the data such that the user can pull them.
I mean in the scenario where, the class is a nodeshape there is no issue, it suffice to dereference the type of the entity or property through linked data principles. But with shapes in their own module i have no idea. On Wednesday, September 6, 2023 at 8:32:18 PM UTC+1 Maatary Okouya wrote: > Cristal Clear. > > Thanks. > > On Wednesday, September 6, 2023 at 12:50:02 PM UTC+1 Holger Knublauch > wrote: > >> I guess the problem with this pattern of mixing sh:node and >> rdfs:subClassOf is that the user interface doesn't expect it. The Node >> Shapes panel will only show as roots those node shapes that are not value >> of sh:node - otherwise they are expected to be part of the tree further >> down and are not roots. But if the root nodes are also classes they are >> hidden too, because they are not considered pure node shapes. The UI needs >> to make such choices and I don't consider this mix of design patterns as >> common enough to support it. >> >> The usual pattern is something like >> >> ex:Person >> a owl:Class, sh:NodeShape ; >> >> That class is then used for the rdf:types. >> >> ex:UKPerson >> a sh:NodeShape ; >> sh:targetClass ex:Person ; >> >> Then, if you want to see the additional properties for UK people, you >> would switch the form to that "perspective". >> >> If UKPerson is also an rdf:type then just make it a class and use >> rdfs:subClassOf Person. No need for node shapes then. >> >> The sh:targetClass relationship will indirectly make sure that all >> constraints from Person will also apply to UKPerson. >> >> Holger >> >> >> On 6 Sep 2023, at 7:13 am, Maatary Okouya <[email protected]> wrote: >> >> More importantly i think is, is there a workaround to make it show up in >> the Shape Panel ? >> >> I have double check in the shacl playground that that modelling pattern >> works. I was able to validate things. >> >> However part of doing this models is to make it easily human readable as >> well, as much as machine processable. Hence would be nice to have it >> showing up in EDG. >> >> >> On Tuesday, September 5, 2023 at 10:31:59 PM UTC+1 Maatary Okouya wrote: >> >>> Is that expected or a bug ? >>> >>> On Tuesday, September 5, 2023 at 8:17:23 PM UTC+1 Maatary Okouya wrote: >>> >>>> >> Sure, the SHACL semantics should inherit constraints both ways. So >>>> all constraints at aShape will also apply to bShape. >>>> I tried it in EDG Studio, and the bShape disapear from the shapePanel. >>>> >>>> On Tuesday, September 5, 2023 at 8:16:06 PM UTC+1 Maatary Okouya wrote: >>>> >>>>> Yes it is, as in i am trying my best to model a situation that is best >>>>> described in >>>>> https://www.linkedin.com/pulse/how-model-shared-local-data-viewpoints-using-shacl-irene-polikoff/ >>>>> >>>>> I would not say that the pattern apply 100 % there are some nuance >>>>> here. >>>>> >>>>> >>>>> >>>>> One particular difference with the example is that >>>>> >>>>> - in the example You clearly have the concept of US Person and UK >>>>> Person and Person. >>>>> >>>>> - In our context we are dealing with the same concept just shaped >>>>> differently according to the local view. The name of the concept does not >>>>> change because it is literally the same thing, however in one context it >>>>> is >>>>> shape in a certain way, and in other it is shape in another way. >>>>> >>>>> So while my first approach would be to follow the recommended appraoch >>>>> to subclass classes that are also nodeshape, it does not fill right. At >>>>> the >>>>> same time i am not confy all the way and fully break my class/nodeshape >>>>> into class and node shape. hence the situation described in the previous >>>>> email where i would have some high level class/nodeshape and then have >>>>> shapes for the local views. >>>>> >>>>> Hope it make somewhat sense. >>>>> >>>>> >>>>> Our domain is Biological network. The thing we are talking about are >>>>> biological interaction e.g. ProteinModification, Regulation, >>>>> GeneticChange >>>>> and what not. >>>>> >>>>> >>>>> On Tuesday, September 5, 2023 at 7:34:49 PM UTC+1 Holger Knublauch >>>>> wrote: >>>>> >>>>>> Sure, the SHACL semantics should inherit constraints both ways. So >>>>>> all constraints at aShape will also apply to bShape. >>>>>> >>>>>> But I have not seen this particular pattern in practice. Is this a >>>>>> real use case? >>>>>> >>>>>> Holger >>>>>> >>>>>> >>>>>> On 5 Sep 2023, at 6:25 pm, Maatary Okouya <[email protected]> >>>>>> wrote: >>>>>> >>>>>> One extra clarification on this. >>>>>> >>>>>> Is it ok to actually mix both approach i.e. >>>>>> >>>>>> :aShape a owl:Class; a sh:NodeShape . >>>>>> >>>>>> :bShape a sh:NodeShape; >>>>>> :bShape sh:node aShape; >>>>>> . >>>>>> >>>>>> On Saturday, September 2, 2023 at 12:33:45 AM UTC+1 Maatary Okouya >>>>>> wrote: >>>>>> >>>>>>> thanks for clarifying. >>>>>>> >>>>>>> On Friday, September 1, 2023 at 2:13:44 PM UTC+1 Holger Knublauch >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> On 1 Sep 2023, at 2:00 pm, Maatary Okouya <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> I have a quick question about the best way to express inheritance >>>>>>>> between pure shapes. >>>>>>>> >>>>>>>> E.g. >>>>>>>> >>>>>>>> :aShape a sh:nodeShape . >>>>>>>> :bshape a sh:nodeShape . >>>>>>>> >>>>>>>> Are the following 2 options equivalent, and which one is the >>>>>>>> reocmmended ? >>>>>>>> >>>>>>>> bShape rdfs:subClassOf aShape; >>>>>>>> or >>>>>>>> bShape sh:node aShape ; >>>>>>>> >>>>>>>> The goal is to have bShape inherit the property of aShape. >>>>>>>> >>>>>>>> >>>>>>>> sh:node is the right solution. subClassOf is only for classes, >>>>>>>> including for classes that are also shapes. >>>>>>>> >>>>>>>> (Typo above - sh:NodeShape must have a big N) >>>>>>>> >>>>>>>> Holger >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> -- >>>>>>>> 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/07c4c762-a4be-4617-9991-647907b3e235n%40googlegroups.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/topbraid-users/07c4c762-a4be-4617-9991-647907b3e235n%40googlegroups.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/995f18bd-3789-491d-bc88-09d06e5050d0n%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/topbraid-users/995f18bd-3789-491d-bc88-09d06e5050d0n%40googlegroups.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/9e9d94c3-ca66-4969-b1d1-ae511d24c46en%40googlegroups.com >> >> <https://groups.google.com/d/msgid/topbraid-users/9e9d94c3-ca66-4969-b1d1-ae511d24c46en%40googlegroups.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/d182e19f-169f-4b63-8ad0-3317483dc365n%40googlegroups.com.
