Fighting with EDG

48 views

Skip to first unread message

Steve Ray

unread,

Sep 16, 2020, 7:58:04 PM9/16/20

to TopBraid Suite Users

Hi,

I'm ramping up on using SHACL for some new modeling I'm doing, and decided to try it using EDG (6.4.0). I defined a simple schema, and then went to create a data graph that includes that schema. Try as I might, I could not convince EDG to let me press the "New" button in the classes and instances Layout, to make some instances. It is constantly greyed out.

In the end, I bludgeoned it into having instances by defining them in Visual Studio Code, and importing the file, but obviously that is not a good way to proceed. What am I doing wrong?

One more piece of information: The "New" button is not greyed out when I am in the ontology graph, but then it warns me that if I create instances there, the properties will be read-only.

I'm attaching the two test files in case that helps. They are short.

Steve

shacl_Room2_temperature_measurement.ttl

room_2_measurement_data.ttl

Holger Knublauch

unread,

Sep 16, 2020, 8:09:42 PM9/16/20

to topbrai...@googlegroups.com

Hi Steve,

the Data Graph collection type is designed for editing arbitrary instances, yet you first need to tell the system which instances you want to allow the users to create. To do that, go to your Ontology's "Home" resource and switch the form from Metadata to GraphQL Schema. There you can select the *public classes* - add all classes that you want to allow editing for. It's sufficient to declare the superclasses there if you have subclasses too.

FWIW this is mentioned in the page where you create new Data Graphs. Obviously this wasn't clear enough so do you have suggestions on how to make it clearer?

HTH
Holger

--
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/CAGUep85WKJ%2B5CrFT0dmEnQMSTxrMhVud9CebzGVAJRXApLjrHQ%40mail.gmail.com.

Steve Ray

unread,

Sep 16, 2020, 8:19:49 PM9/16/20

to TopBraid Suite Users

Thanks for the quick response, Holger. I tried going to the Ontology graph, clicked the little House icon (that's the Home button, right?), but the "Merged View" pull-down shows a No-Entry icon when I hover over it.

You did mean the Ontology graph and not the Data Graph, correct?

Steve

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/ea2c3f33-1f26-16e1-ade4-f7f735b7952e%40topquadrant.com.

Holger Knublauch

unread,

Sep 16, 2020, 8:28:56 PM9/16/20

to topbrai...@googlegroups.com

In the upper right corner of that form you see the Settings (cog) button. Probably you have Merged View on, which you could deactivate. In any case, there is also a * option "Also show properties that have no values" which should make these missing fields visible.

Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAGUep87RKqw8i5vT_x6woduMs-JH_tzLSonrMxtSBmqx1tBo%3Dw%40mail.gmail.com.

Irene Polikoff

unread,

Sep 16, 2020, 8:29:52 PM9/16/20

to topbrai...@googlegroups.com

It is also described in documentation https://doc.topquadrant.com/6.4/ontologies/#SHACL_requirements_for_working_with_Reference_Datasets_and_Data_Graphs and demonstrated in a video about Data Graphs:

https://www.topquadrant.com/project/data-graphs/

On Sep 16, 2020, at 8:09 PM, Holger Knublauch <hol...@topquadrant.com> wrote:

Hi Steve,
the Data Graph collection type is designed for editing arbitrary instances, yet you first need to tell the system which instances you want to allow the users to create. To do that, go to your Ontology's "Home" resource and switch the form from Metadata to GraphQL Schema. There you can select the *public classes* - add all classes that you want to allow editing for. It's sufficient to declare the superclasses there if you have subclasses too.
FWIW this is mentioned in the page where you create new Data Graphs. Obviously this wasn't clear enough so do you have suggestions on how to make it clearer?

<pnhfgebmcbddadbj.png>

HTH
Holger

On 17/09/2020 09:57, Steve Ray wrote:

Hi,
I'm ramping up on using SHACL for some new modeling I'm doing, and decided to try it using EDG (6.4.0). I defined a simple schema, and then went to create a data graph that includes that schema. Try as I might, I could not convince EDG to let me press the "New" button in the classes and instances Layout, to make some instances. It is constantly greyed out.

<image.png>

In the end, I bludgeoned it into having instances by defining them in Visual Studio Code, and importing the file, but obviously that is not a good way to proceed. What am I doing wrong?

One more piece of information: The "New" button is not greyed out when I am in the ontology graph, but then it warns me that if I create instances there, the properties will be read-only.

I'm attaching the two test files in case that helps. They are short.

Steve

--
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/CAGUep85WKJ%2B5CrFT0dmEnQMSTxrMhVud9CebzGVAJRXApLjrHQ%40mail.gmail.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/ea2c3f33-1f26-16e1-ade4-f7f735b7952e%40topquadrant.com.

Irene Polikoff

unread,

Sep 16, 2020, 8:38:43 PM9/16/20

to topbrai...@googlegroups.com

This is true throughout - if you do not see a property displayed on a form, see if "Also show properties that have no values” is checked. If you only see a handful of properties on a form and they all have some values, chances are this setting is off and the form only shows populated properties.

This is the case for ontologies, data graphs and/or anything else.

If you do not see a property displayed on a form and you know that it has a value e.g., you looked at the source code and you see value there, then there are two possible explanations:

1. No shape have been defined for a property - the form will only show properties for which a shape exist

2. A resource is a member of more than one class (or have multiple views defined via node shapes) and you are currently looking at a view that does not include this property. Of course, if you are using “Merged View”, then this can’t be the case.

On Sep 16, 2020, at 8:28 PM, Holger Knublauch <hol...@topquadrant.com> wrote:

In the upper right corner of that form you see the Settings (cog) button. Probably you have Merged View on, which you could deactivate. In any case, there is also a * option "Also show properties that have no values" which should make these missing fields visible.
Holger

On 17/09/2020 10:19, Steve Ray wrote:

Thanks for the quick response, Holger. I tried going to the Ontology graph, clicked the little House icon (that's the Home button, right?), but the "Merged View" pull-down shows a No-Entry icon when I hover over it.

<image.png>

You did mean the Ontology graph and not the Data Graph, correct?

Steve

On Wed, Sep 16, 2020 at 5:09 PM Holger Knublauch <hol...@topquadrant.com> wrote:

Hi Steve,
the Data Graph collection type is designed for editing arbitrary instances, yet you first need to tell the system which instances you want to allow the users to create. To do that, go to your Ontology's "Home" resource and switch the form from Metadata to GraphQL Schema. There you can select the *public classes* - add all classes that you want to allow editing for. It's sufficient to declare the superclasses there if you have subclasses too.
FWIW this is mentioned in the page where you create new Data Graphs. Obviously this wasn't clear enough so do you have suggestions on how to make it clearer?

<pnhfgebmcbddadbj.png>

HTH
Holger

On 17/09/2020 09:57, Steve Ray wrote:

Hi,
I'm ramping up on using SHACL for some new modeling I'm doing, and decided to try it using EDG (6.4.0). I defined a simple schema, and then went to create a data graph that includes that schema. Try as I might, I could not convince EDG to let me press the "New" button in the classes and instances Layout, to make some instances. It is constantly greyed out.

<image.png>

In the end, I bludgeoned it into having instances by defining them in Visual Studio Code, and importing the file, but obviously that is not a good way to proceed. What am I doing wrong?

One more piece of information: The "New" button is not greyed out when I am in the ontology graph, but then it warns me that if I create instances there, the properties will be read-only.

I'm attaching the two test files in case that helps. They are short.

Steve

--
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/CAGUep85WKJ%2B5CrFT0dmEnQMSTxrMhVud9CebzGVAJRXApLjrHQ%40mail.gmail.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/ea2c3f33-1f26-16e1-ade4-f7f735b7952e%40topquadrant.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/CAGUep87RKqw8i5vT_x6woduMs-JH_tzLSonrMxtSBmqx1tBo%3Dw%40mail.gmail.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/7b662f45-3c98-5509-e81a-6b9488f4c1c4%40topquadrant.com.

Steve Ray

unread,

Sep 16, 2020, 8:54:13 PM9/16/20

to TopBraid Suite Users

Magic! That did the trick.

So, as to how to make that clearer, how about something like:

they must be defined as SHACL node shapes
they must be declared public in the GraphQL Schema (in the new editor use the 'Home' button, ensure the cog wheel pull-down has "Merge properties from all suitable view shapes" unselected, and then switch the form to GraphQL Schema view. Then you can proceed to identify which classes you want to be able to instantiate.)

A bit wordy, I know. Little pictures of the icons would help if that's possible.

Steve

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/7b662f45-3c98-5509-e81a-6b9488f4c1c4%40topquadrant.com.

Steve Ray

unread,

Sep 16, 2020, 9:07:03 PM9/16/20

to TopBraid Suite Users

Thanks. Yes, the merged view was throwing me off. I hadn't fully appreciated the implications of leaving that on.

Steve

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/9E7151C0-9C3A-426A-8238-7D8ED4C4A4CE%40topquadrant.com.

Reply all

Reply to author

Forward

0 new messages