New to SHACL and TopBraid Composer questions

[Steven Folsom]

A couple quick questions:

• Does TopBraid Composer support sh:order by default in the GUI? I couldn't find the option to assert sh:order in the Node Shape Form Editor, but I was able to type it directly in the ttl from the source code tab. (After which it displayed in the GUI.) 
  
• Related, is it best practice to begin sh:order with the number 0?
• Similarly, is sh:group supported by default in the Node Shape Form Editor? (E.g. can you select sh:group and create links to instances of sh:PropertyGroup using the UI?
• With respect to cardinality and repeatability, if a shape includes a PropertyShape without a sh:max is the expectation that it is repeatable? Is there a way to say "repeatable" explicitly? Or does OWA not apply in SHACL?

Thanks in advance,
Steven

-- 

Steven Folsom

Metadata Specialist

Cornell University Library

http://orcid.org/0000-0003-3427-5769

http://vivo.cornell.edu/individual/sf433

@sf433

[Holger Knublauch]

On 12/09/2017 11:38, Steven Folsom wrote:

A couple quick questions:

• Does TopBraid Composer support sh:order by default in the GUI? I couldn't find the option to assert sh:order in the Node Shape Form Editor, but I was able to type it directly in the ttl from the source code tab. (After which it displayed in the GUI.)
  

You can add any property that is not already visible to a form using the highlighted button "Add widget for property..."

• Related, is it best practice to begin sh:order with the number 0?

Yes I would say so. BTW the SHACL main document unfortunately does not clarify what the default value of sh:order is, if absent. Elsewhere (in SHACL-AF for rules) we made 0 the default and I believe this makes most sense in general.

• Similarly, is sh:group supported by default in the Node Shape Form Editor? (E.g. can you select sh:group and create links to instances of sh:PropertyGroup using the UI?

See above, you'd first need to add the widget. If this becomes too time consuming, you can select sh:NodeShape in the classes tree and then go to the Form Layout tab where you can define a custom layout for the class, so that it will always be there, e.g.



Make sure the "Show widgets for all matching properties" button is activated in the upper right corner of the form window.

We do not automatically show sh:order and sh:group for node shapes, because arguably these options are more important for property shapes than node shapes. What is your use case for these properties at node shapes? I could certainly add them for everyone if they turn out to be important.

• With respect to cardinality and repeatability, if a shape includes a PropertyShape without a sh:max is the expectation that it is repeatable?

Yes, a sh:maxCount of undefined means that it may have any number of values, including two or more.

• Is there a way to say "repeatable" explicitly? Or does OWA not apply in SHACL?

I don't see the connection between repeatability and the OWA - even closed world models may have multi-valued properties. The only way to say this is by excluding a sh:maxCount. "Repeatable" is not a constraint condition that could be checked, so there is nothing to do for a SHACL engine here.

Regards,
Holger

Thanks in advance,
Steven

-- 

Steven Folsom

Metadata Specialist

Cornell University Library

http://orcid.org/0000-0003-3427-5769

http://vivo.cornell.edu/individual/sf433

@sf433

--
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-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.