Customizing Definition tab in Ontology

[Adam Kimball]

Hi all,

I'm trying to publish an ontology in EDG but can't quite figure out how to get the UI to show the class annotations.  We use skos:prefLabel for everything, including class names.  Likewise, skos:note and skos:definition in their own manner.  I also have rdfs:isDefinedBy and a handful of other properties.  All of this data is shown in the source code view, but I need it in the UI.  I assume I am missing something right in front of my face, but..

Adam

[Irene Polikoff]

The forms are driven by SHACL definitions, they do not simply display all available triples.

You need to add shapes for the properties you would like to use with classes. 

You can do the following:

Create a Node Shape and add properties you want. Make owl:Class its applicable class - as shown below.

Now, when looking at a class, you will have 2 views - see the drop down to switch views

In 6.4, you can select in the form’s Settings menu “Merge properties from all suitable view shapes”, then you will see everything together

This approach lets you define any views you want to target them to roles.

Another option is to directly modify the file that contains shape definitions for the ontology resources. It is in the workspace under SHACL and is called metash.ttl

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/85464dc6-3fe0-4ad0-818b-18d40287a91bn%40googlegroups.com.

[Adam Kimball]

Thanks, Irene!  The screenshots really helped, too.  One of the missing links was the "applicable to class" property - I never knew about that.

Is there any way to enable "Merge properties from all suitable view shapes" per project or in some more global way?  Also, is editing metash.ttl something that other EDG customers are doing and therefore something that isn't likely to come back and haunt me? 

Adam

[Irene Polikoff]

On Aug 19, 2020, at 4:29 PM, Adam Kimball <adamfk...@gmail.com> wrote:

Thanks, Irene!  The screenshots really helped, too.  One of the missing links was the "applicable to class" property - I never knew about that.

Is there any way to enable "Merge properties from all suitable view shapes" per project or in some more global way? 

Not that I know of. You could log a request for this.

Also, is editing metash.ttl something that other EDG customers are doing and therefore something that isn't likely to come back and haunt me? 

The only implications I can think of is upgrade to the next releases. After an upgrade, you will need to make sure that the file contains what you need.

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/7a328cd4-005c-4c17-8c07-f2b0928b9fdfn%40googlegroups.com.

[Holger Knublauch]

On 20/08/2020 06:52, Irene Polikoff wrote:

On Aug 19, 2020, at 4:29 PM, Adam Kimball <adamfk...@gmail.com> wrote:

Thanks, Irene!  The screenshots really helped, too.  One of the missing links was the "applicable to class" property - I never knew about that.

Is there any way to enable "Merge properties from all suitable view shapes" per project or in some more global way? 

Not that I know of. You could log a request for this.

Also, is editing metash.ttl something that other EDG customers are doing and therefore something that isn't likely to come back and haunt me? 

The only implications I can think of is upgrade to the next releases. After an upgrade, you will need to make sure that the file contains what you need.

As an alternative to editing metash.ttl itself, create and upload a new file metashx.ttl that owl:imports metash.ttl and has the base URI http://datashapes.org/metashx

This will then be used instead of metash. This approach can be used to *add* triples to metash without having to worry too much about upgrading your workspace.

Moving forward with 7.0 we will probably have this situation cleaned up and will have a metash-like graph as a regular owl:import, and not some hidden magic. Too many people stumble across this current solution.

Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/4C78A01B-15EA-49D3-A6B8-0D551396CBAA%40topquadrant.com.

[Luis Enrique Ramos García]

Hi, I am trying to follow this procedure to include the property skos:definition and skos:preferLabel to an ontology concept.

But, when I search for clasMetadata in nodeshapes, I do not find it.

then, I wonder where should I create the shape to get the effect of viewing the attributes in UI?.

I added them in Class shape, but did not work.

Best regards

Luis Ramos

[Holger Knublauch]

The email you have responded to is from 2020 and as I indicated there we were planning to simplify this for 7.0

In fact you can now simply attach any extra property (such as skos:altLabel) to the owl:Class metaclass.

So just make owl:Class visible in the class tree by using the "Up" button and find it under rdfs:Class, then add properties there, in some Ontology.

Holger

--
The topics of this mailing list include TopBraid EDG and related technologies such as SHACL.
To post to this group, send email to topbrai...@googlegroups.com
---

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/43ab0232-9c6e-4732-b366-55f9e92411a4n%40googlegroups.com.