If you specify one order at a parent class and another order at a child class, there is no saying which one would apply.
I recommend not specifying anything at the parent class that you do not want inherited. You could create a custom constraint component which would take the order from the class itself, if exists and, if not, take the order from the nearest parent. Sent from my iPhone > On Nov 29, 2017, at 1:34 PM, Bohms, H.M. (Michel) <[email protected]> wrote: > > Thx Irene for the extra info. All clear. > For the moment I used my own group there: > <image001.jpg> > > > The order is working perfectly. > > I just moved a property-shape from a generic class to a lower level because I > did not now how to deal with that in my order-numbering. Would inherited > shapes also come first, the more generic the earlier? > (that would be ok since I do not want a generic shape show as number 6 after > a specific shape for instance….) > > Gr, Michel > > > > > > Dr. ir. H.M. (Michel) Böhms > Senior Data Scientist > > T +31888663107 > M +31630381220 > E [email protected] > Location > > > <image004.gif> > This message may contain information that is not intended for you. If you are > not the addressee or if this message was sent to you by mistake, you are > requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use it > and for damage of any kind resulting from the risks inherent to the > electronic transmission of messages. > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Irene Polikoff > Sent: Wednesday, November 29, 2017 6:07 PM > To: [email protected] > Subject: Re: [topbraid-users] sh:order in evn > > This is really only about our internal development. > > Holger mentioned it in response to your question about certain section > headings that appear on the forms, but you are not finding defined as SHACL > groups. You are not finding them because currently they are not defined using > SHACL. We plan to change this going forward. However, this should not impact > your work. > > Right now, forms for all classes in pre-built EDG models (e.g., glossary > terms, databases, applications, etc.,) are defined in SHACL. For your custom > classes, you can do the same and define forms for their instances using SHACL. > > There is a ‘catch all’ section “Other Properties” that will list all > properties that have not been associated with any group. Understandably, its > presence and what to put there is not defined in SHACL. > > Forms for classes themselves, properties themselves and for SKOS classes > (e.g., skos:Concept) are not yet defined in SHACL. > > On Nov 29, 2017, at 2:49 AM, Bohms, H.M. (Michel) <[email protected]> wrote: > > Ok clear thx > > You say “Once you have fully migrated to SHACL forms, none of these headings > should show up any more.” > > > Was wondering what that actually meant…which things should I stop/start doing > to get to that situation? (or do you refer to future evn sw dev.) > > > > > > Dr. ir. H.M. (Michel) Böhms > Senior Data Scientist > > > T +31888663107 > M +31630381220 > E [email protected] > Location > > > <image001.gif> > This message may contain information that is not intended for you. If you are > not the addressee or if this message was sent to you by mistake, you are > requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use it > and for damage of any kind resulting from the risks inherent to the > electronic transmission of messages. > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Holger Knublauch > Sent: Wednesday, November 29, 2017 1:00 AM > To: [email protected] > Subject: Re: [topbraid-users] sh:order in evn > > > > On 29/11/2017 8:46, Bohms, H.M. (Michel) wrote: > > Ok clear! > > But better define my own group or reuse an existing tosh group? > > The tosh: property groups are really about meta-shapes only, e.g. the > definitions of sh:PropertyShape themselves. These are unlikely to be > useful/suitable for your custom data models. So better create your own URIs. > > > > > I was wondering which group corresponds to the EVN “Properties” heading ….(if > I use that one…) but I see no tosh group with label “Properties” so this > might not be possible…. > > Some of these headings are still "hard-coded" as SWA forms. Once you have > fully migrated to SHACL forms, none of these headings should show up any more. > > Holger > > > > > > > > > Dr. ir. H.M. (Michel) Böhms > Senior Data Scientist > > > > T +31888663107 > M +31630381220 > E [email protected] > Location > > > <image001.gif> > This message may contain information that is not intended for you. If you are > not the addressee or if this message was sent to you by mistake, you are > requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use it > and for damage of any kind resulting from the risks inherent to the > electronic transmission of messages. > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Holger Knublauch > Sent: Tuesday, November 28, 2017 11:42 PM > To: [email protected] > Subject: Re: [topbraid-users] sh:order in evn > > The SHACL spec is intentionally vague about sh:order, because there are > different potential use cases and it doesn't have strict semantics anyway. In > the case of form building, the best practice that seems to establish itself > is to combine sh:order with sh:group. You can either reuse existing property > groups or create new ones. Then, use sh:order to establish the relative > position of a property within its group. > > The example in the spec illustrates all this > > https://www.w3.org/TR/shacl/#defaultValue > > Holger > > > > > On 29/11/2017 7:40, Bohms, H.M. (Michel) wrote: > > Or can I reuse the existing tosh:DisplayPropertyGroup? > > > > > Dr. ir. H.M. (Michel) Böhms > Senior Data Scientist > > > > > T +31888663107 > M +31630381220 > E [email protected] > Location > > > <image001.gif> > This message may contain information that is not intended for you. If you are > not the addressee or if this message was sent to you by mistake, you are > requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use it > and for damage of any kind resulting from the risks inherent to the > electronic transmission of messages. > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Bohms, H.M. (Michel) > Sent: Tuesday, November 28, 2017 10:34 PM > To: [email protected] > Subject: RE: [topbraid-users] sh:order in evn > > Hi Irene > > The spec: > > 2.3.2.2 sh:order > Property shapes may have one value for the property sh:order to indicate the > relative order of the property shape for purposes such as form building. The > values of sh:order are decimals. sh:order is not used for validation purposes > and may be used with any type of subjects. If present at property shapes, the > recommended use of sh:order is to sort the property shapes in an ascending > order, for example so that properties with smaller order are placed above (or > to the left) of properties with larger order. > > > Seems to suggest (by not saying anything about “in context of a group”: > Not always group needed for order of property shapes > > But ok, where do I actually define this one group? > Do I just instantiate it myself next to the tosh groups? > > Thx again! Michel > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Irene Polikoff > Sent: Tuesday, November 28, 2017 10:18 PM > To: [email protected] > Subject: Re: [topbraid-users] sh:order in evn > > The order is within a property group, so you need to create a property group > and add it to each property shape. > > On Nov 28, 2017, at 3:59 PM, Bohms, H.M. (Michel) <[email protected]> wrote: > > I tried: > kebo:TechniqueType > rdf:type owl:Class ; > rdf:type sh:NodeShape ; > rdfs:label "TechniekType"@nl ; > rdfs:label "TechniqueType"@en ; > rdfs:subClassOf kebo:Root ; > sh:property [ > rdf:type sh:PropertyShape ; > sh:path kebo:analysisAndElaboration ; > sh:datatype xsd:string ; > sh:name "analysisAndElaboration" ; > ] ; > sh:property [ > rdf:type sh:PropertyShape ; > sh:path kebo:applicability ; > sh:datatype xsd:string ; > sh:name "applicability" ; > ] ; > sh:property [ > rdf:type sh:PropertyShape ; > sh:path kebo:applicableForRiskType ; > sh:class kebo:RiskType ; > sh:name "applicableForRiskType" ; > sh:nodeKind sh:IRI ; > ] ; > sh:property [ > rdf:type sh:PropertyShape ; > sh:path kebo:background ; > sh:datatype rdf:HTML ; > sh:name "background" ; > sh:order 1 ; > ] ; > sh:property [ > rdf:type sh:PropertyShape ; > sh:path kebo:backgroundImage ; > sh:datatype xsd:anyURI ; > sh:name "backgroundImage" ; > ] ; > sh:property [ > rdf:type sh:PropertyShape ; > sh:path kebo:externalExpertise ; > sh:datatype xsd:string ; > sh:name "externalExpertise" ; > ] ; > sh:property [ > rdf:type sh:PropertyShape ; > sh:path kebo:frequency ; > sh:datatype xsd:string ; > sh:name "frequency" ; > ] ; > sh:property [ > rdf:type sh:PropertyShape ; > sh:path kebo:goal ; > sh:datatype xsd:string ; > sh:name "goal" ; > sh:order 0 ; > ] ; > > But the order in evn of my actual property data stays alphabetical. What am I > doing wrong? > > Thx Michel > > > > > > > Dr. ir. H.M. (Michel) Böhms > Senior Data Scientist > > > > > > T +31888663107 > M +31630381220 > E [email protected] > Location > > > <image001.gif> > This message may contain information that is not intended for you. If you are > not the addressee or if this message was sent to you by mistake, you are > requested to inform the sender and delete the message. TNO accepts no > liability for the content of this e-mail, for the manner in which you use it > and for damage of any kind resulting from the risks inherent to the > electronic transmission of messages. > > > > > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- > 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]. > For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout.
