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]<mailto:[email protected]> Location<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=!3m1!4b1!4m5!3m4!1s0x47c5b58c52869997:0x56681566be3b8c88!8m2!3d52.000788!4d4.376707> [cid:[email protected]]<http://www.tno.nl/> 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]<mailto:[email protected]> Location<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707> [cid:[email protected]]<http://www.tno.nl/> 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]> [mailto:[email protected]] On Behalf Of Holger Knublauch Sent: Tuesday, November 28, 2017 11:42 PM To: [email protected]<mailto:[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]<mailto:[email protected]> Location<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707> [cid:[email protected]]<http://www.tno.nl/> 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]> [mailto:[email protected]] On Behalf Of Bohms, H.M. (Michel) Sent: Tuesday, November 28, 2017 10:34 PM To: [email protected]<mailto:[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<https://www.w3.org/TR/shacl/#dfn-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]> [mailto:[email protected]] On Behalf Of Irene Polikoff Sent: Tuesday, November 28, 2017 10:18 PM To: [email protected]<mailto:[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]<mailto:[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]<mailto:[email protected]> Location<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707> <image001.gif><http://www.tno.nl/> 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]<mailto:[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]<mailto:[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]<mailto:[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]<mailto:[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]<mailto:[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]<mailto:[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]<mailto:[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.
