[topbraid-users] add rdfs:seeAlso to class definition

['Luis Enrique Ramos García' via TopBraid Suite Users]

Dear All,

I am tryin to include a uri ref using the rdfs:seeAlso in the definition of
a class.
But, when I try to include it, I do not find it in the list of existing
properties.

Furthermore, if I try to create the shape I get this answer:

[image: image.png]
So, I wonder what I should be doing wrong?, if the property exists.

what should I do then to include the property in the definition of the
class, and add the uri?.

best regards

Luis

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/CABy94X%3DKhGFsko0hLAa8Tk4VnRMK0HMdR7cSoTXoWw2-JYh_vw%40mail.gmail.com.

Re: [topbraid-users] enum creation

['Luis Enrique Ramos García' via TopBraid Suite Users]

When I edit TrafficColor I do not see anything new,

Luis

El jue, 18 abr 2024 a las 15:46, Holger Knublauch ()
escribió:

>
>
> On 18 Apr 2024, at 3:41 PM, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> Holger,
>
> I think I did the recommended change:
>
> tesontologyramosenum:TrafficLight
>   a owl:Class ;
>   a sh:NodeShape ;
>   rdfs:label "TrafficLight" ;
>   rdfs:subClassOf owl:Thing ;
>   sh:property tesontologyramosenum:TrafficLight-color ;
> .
> tesontologyramosenum:TrafficLight-color
>   a sh:PropertyShape ;
>   sh:path tesontologyramosenum:color ;
>   sh:class tesontologyramosenum:Color ;
>   sh:name "color" ;
>   sh:nodeKind sh:IRI ;
>
>
> But, when I create a trafficlight1 instance, I still have the same view,
> the color property is present, however it is blank, no colors:
>
>
> New instances will not have a default value for it, but what happens when
> you switch to edit mode? Don't you see a drop down for colors when you add
> a new value/row?
>
> Holger
>
>
>
> 
> So, I am still not able to find out where the problem is..
>
>
> Luis Ramos
>
>
> El jue, 18 abr 2024 a las 8:22, Holger Knublauch ()
> escribió:
>
>>
>>
>> On 18 Apr 2024, at 7:52 AM, 'Luis Enrique Ramos García' via TopBraid
>> Suite Users  wrote:
>>
>> Hi Holger,
>>
>> good morning,
>>
>> Unfortunately it is not the case, and I can not see the options in the
>> editor.
>>
>> The code of the traffic light class and color property are:
>>
>> tesontologyramosenum:TrafficLight
>>   a owl:Class ;
>>   a sh:NodeShape ;
>>   rdfs:label "TrafficLight" ;
>>   rdfs:subClassOf owl:Thing ;
>>   sh:property tesontologyramosenum:TrafficLight-color ;
>> .
>> tesontologyramosenum:TrafficLight-color
>>   a sh:PropertyShape ;
>>   sh:path tesontologyramosenum:color ;
>>   sh:name "color" ;
>>   sh:node tesontologyramosenum:Color ;
>>   sh:nodeKind sh:IRI ;
>>
>>
>> Replace the sh:node with:
>>
>>sh:class tesontologyramosenum:Color ;
>>
>> as sh:node is not enough to tell the system which values can be selected.
>>
>> Holger
>>
>>
>>
>> .
>> and when I create an instance of traffic light, this is what I see:
>>
>> 
>> Thus, I wonder what I am doing wrong?.
>>
>>
>> best regards
>>
>>
>> Luis Ramos
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> El mié, 17 abr 2024 a las 16:46, Holger Knublauch (<
>> hol...@topquadrant.com>) escribió:
>>
>>>
>>>
>>> On 17 Apr 2024, at 3:55 PM, 'Luis Enrique Ramos García' via TopBraid
>>> Suite Users  wrote:
>>>
>>> it works now in this ontology,
>>>
>>> now, if I want to add a color in any instance (for testing purpose),
>>> it is only by modifying the code?, like this?:
>>>
>>>
>>> If you have properly declared the color property then you should be able
>>> to select values from the form, not just source code.
>>>
>>> Holger
>>>
>>>
>>>
>>> 
>>> That is moreless the expected result on my end.
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Luis
>>>
>>> El mié, 17 abr 2024 a las 15:37, Holger Knublauch (<
>>> hol...@topquadrant.com>) escribió:
>>>
>>>> Yes that looks right. To use it in traffic lights, just declare a color
>>>> property there which has sh:class :Color.
>>>>
>>>> Holger
>>>>
>>>>
>>>> On 17 Apr 2024, at 3:00 PM, 'Luis Enrique Ramos García' via TopBraid
>>>> Suite Users  wrote:
>>>>
>>>> sure,
>>>>
>>>> I created a similar ontology for testing with same results, here is the
>>>> code:
>>>>
>>>> tesontologyramosenum:Color
>>>>   a owl:Class ;
>>>>   a sh:NodeShape ;
>>>>   rdfs:label "Color" ;
>>>>   rdfs:subClassOf owl:Thing ;
>>>>   sh:in (
>>>>   tesontologyramosenum:Green
>>>>   tesontologyramosenum:Yellow
>>>>   tesontologyramosenum:Red
>>>> ) ;
>>>>   sh:property tesontologyramosenum:Color-label ;
>>>> .
>>>>
>>>> the screen shot is this:
>>>>
>>>> 
>>>

Re: [topbraid-users] enum creation

['Luis Enrique Ramos García' via TopBraid Suite Users]

it works now in this ontology,

now, if I want to add a color in any instance (for testing purpose),
it is only by modifying the code?, like this?:

[image: image.png]
That is moreless the expected result on my end.


Thanks,


Luis

El mié, 17 abr 2024 a las 15:37, Holger Knublauch ()
escribió:

> Yes that looks right. To use it in traffic lights, just declare a color
> property there which has sh:class :Color.
>
> Holger
>
>
> On 17 Apr 2024, at 3:00 PM, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> sure,
>
> I created a similar ontology for testing with same results, here is the
> code:
>
> tesontologyramosenum:Color
>   a owl:Class ;
>   a sh:NodeShape ;
>   rdfs:label "Color" ;
>   rdfs:subClassOf owl:Thing ;
>   sh:in (
>   tesontologyramosenum:Green
>   tesontologyramosenum:Yellow
>   tesontologyramosenum:Red
> ) ;
>   sh:property tesontologyramosenum:Color-label ;
> .
>
> the screen shot is this:
>
> 
> 
>
> with similar results, a datatype property without labeling, and a group of
> undeclared properties.
>
> Is this the expected result?
>
> How do I use this in traffic light instances, if that were the case?
>
>
> Luis
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> El mié, 17 abr 2024 a las 14:41, Holger Knublauch ()
> escribió:
>
>> Can you paste us the complete content of the source code panel, e.g. as a
>> screenshot? It's hard to see otherwise and there are syntax errors below.
>>
>> Holger
>>
>>
>> On 17 Apr 2024, at 2:38 PM, 'Luis Enrique Ramos García' via TopBraid
>> Suite Users  wrote:
>>
>> I need only 3 elements in the enum,
>>
>> But, I tried at the first the source code edition, and told you the
>> result I got:
>>
>>
>> **
>>
>> 1. I tried to add the code by myself, but it seems there is something
>> wrong with the code:
>> sh:in (
>>   myontology:value1
>>myontology _:value2
>>   myontology :value3
>> ) ;
>> myontology:property1;
>> myontology:property2;
>> myontology:enumproperty;
>>
>> Please, take in account that I edited the enum property just after the
>> sh:in, but the editor put it at the end
>> of the list of properties.
>>
>> Part of the result was this black datatype property in properties list
>>
>> 
>>
>> and in the undeclared property there is a list with these values:
>>
>> in  [myontology:property1;
>>           myontology:property1;
>>   myontology:enumproperty;]
>>
>> is thát the expected result?
>>
>>
>> **
>>
>>
>> Luis
>>
>> El mié, 17 abr 2024 a las 14:33, Holger Knublauch (<
>> hol...@topquadrant.com>) escribió:
>>
>>>
>>>
>>> On 17 Apr 2024, at 2:30 PM, 'Luis Enrique Ramos García' via TopBraid
>>> Suite Users  wrote:
>>>
>>> Thanks for your quick answer,
>>>
>>> But, dear, where should I add this code?.
>>>
>>> Because I tried to add it in the source code panel, and it didn't work,
>>> same with the script panel,
>>> where I expected it should work, but it did not.
>>>
>>> So, I owner in which panel should I add this code?.
>>>
>>> I do not have any idea how to use it.
>>>
>>>
>>> Yes, it requires JS experience. There is no out-of-the-box solution for
>>> what you are trying to express.
>>>
>>> How many enumerations do you need? If it's just a few, I would suggest
>>> going ahead with manual editing of sh:in lists in the Source Code.
>>>
>>> Holger
>>>
>>>
>>>
>>>
>>> Luis
>>>
>>>
>>>
>>> El mié, 17 abr 2024 a las 13:45, Holger Knublauch (<
>>> hol...@topquadrant.com>) escribió:
>>>
>>>>
>>>>
>>>> On 17 Apr 2024, at 1:38 PM, 'Luis Enrique Ramos García' via TopBraid
>>>> Suite Users  wrote:
>>>>
>>>> I am working with version Version: 7.5.1 (20230316-1531).
>>>>
>>>>
>>>> Ok then the script may not work, assuming the RDFNodeUtil object was
>>>&g

Re: [topbraid-users] enum creation

['Luis Enrique Ramos García' via TopBraid Suite Users]

David,

With your recommendation, now at least I can see the following in the
object property:

[image: image.png]
I created an instance of traffic light, and added the property Color-label
to traffic light as domain,

but when I create the instance of the class traffic light, what I expect is
to have the possibility of

viewing the three possible colors for my traffic light, however I can not
visualize it.

[image: image.png]
previous property name was "label"


Luis


El mié, 17 abr 2024 a las 15:04, David Price ()
escribió:

> Need the sh:in do be defined in PropertyShaps, not NodeShape.
>
> Example from eariler:
>
> example_schema:ThingWithStatus-hasStatus
>   a *sh:PropertyShape ;*
>   sh:path example_schema:hasStatus ;
>   sh:class example_schema:Status ;
>   sh:description "only Active or Retired allowed" ;
>   sh:in (
>   example_schema:Active
>   example_schema:Retired
> ) ;
>   sh:maxCount 1 ;
>   sh:name "has status" ;
> .
>
>
> Cheers,
> David
>
> On 17 Apr 2024, at 14:00, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> sure,
>
> I created a similar ontology for testing with same results, here is the
> code:
>
> tesontologyramosenum:Color
>   a owl:Class ;
>   a sh:NodeShape ;
>   rdfs:label "Color" ;
>   rdfs:subClassOf owl:Thing ;
>   sh:in (
>   tesontologyramosenum:Green
>   tesontologyramosenum:Yellow
>   tesontologyramosenum:Red
> ) ;
>   sh:property tesontologyramosenum:Color-label ;
> .
>
> the screen shot is this:
>
> 
> 
>
> with similar results, a datatype property without labeling, and a group of
> undeclared properties.
>
> Is this the expected result?
>
> How do I use this in traffic light instances, if that were the case?
>
>
> Luis
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> El mié, 17 abr 2024 a las 14:41, Holger Knublauch ()
> escribió:
>
>> Can you paste us the complete content of the source code panel, e.g. as a
>> screenshot? It's hard to see otherwise and there are syntax errors below.
>>
>> Holger
>>
>>
>> On 17 Apr 2024, at 2:38 PM, 'Luis Enrique Ramos García' via TopBraid
>> Suite Users  wrote:
>>
>> I need only 3 elements in the enum,
>>
>> But, I tried at the first the source code edition, and told you the
>> result I got:
>>
>>
>> **
>>
>> 1. I tried to add the code by myself, but it seems there is something
>> wrong with the code:
>> sh:in (
>>   myontology:value1
>>myontology _:value2
>>   myontology :value3
>> ) ;
>> myontology:property1;
>> myontology:property2;
>> myontology:enumproperty;
>>
>> Please, take in account that I edited the enum property just after the
>> sh:in, but the editor put it at the end
>> of the list of properties.
>>
>> Part of the result was this black datatype property in properties list
>>
>> 
>>
>> and in the undeclared property there is a list with these values:
>>
>> in              [myontology:property1;
>>   myontology:property1;
>>   myontology:enumproperty;]
>>
>> is thát the expected result?
>>
>>
>> **
>>
>>
>> Luis
>>
>> El mié, 17 abr 2024 a las 14:33, Holger Knublauch (<
>> hol...@topquadrant.com>) escribió:
>>
>>>
>>>
>>> On 17 Apr 2024, at 2:30 PM, 'Luis Enrique Ramos García' via TopBraid
>>> Suite Users  wrote:
>>>
>>> Thanks for your quick answer,
>>>
>>> But, dear, where should I add this code?.
>>>
>>> Because I tried to add it in the source code panel, and it didn't work,
>>> same with the script panel,
>>> where I expected it should work, but it did not.
>>>
>>> So, I owner in which panel should I add this code?.
>>>
>>> I do not have any idea how to use it.
>>>
>>>
>>> Yes, it requires JS experience. There is no out-of-the-box solution for
>>> what you are trying to express.
>>>
>>> How many enumerations do you need? If it's just a few, I would suggest
>>> going ahead with manual editing of sh:in lists in the Source Code.
>>>
>>> Holge

Re: [topbraid-users] enum creation

['Luis Enrique Ramos García' via TopBraid Suite Users]

Thanks or your answer David,

I did the following, but I do not see any change:

tesontologyramosenum:Color
  a owl:Class ;
  a sh:NodeShape ;
  rdfs:label "Color" ;
  rdfs:subClassOf owl:Thing ;
  sh:property tesontologyramosenum:Color-label ;
.
tesontologyramosenum:Color-label
  a sh:PropertyShape ;
  sh:path tesontologyramosenum:label ;
  sh:class tesontologyramosenum:Color ;
  sh:in (
  tesontologyramosenum:Green
  tesontologyramosenum:Yellow
  tesontologyramosenum:Red
) ;
  sh:name "label" ;
.

What should I be missing?


Luis






El mié, 17 abr 2024 a las 15:04, David Price ()
escribió:

> Need the sh:in do be defined in PropertyShaps, not NodeShape.
>
> Example from eariler:
>
> example_schema:ThingWithStatus-hasStatus
>   a *sh:PropertyShape ;*
>   sh:path example_schema:hasStatus ;
>   sh:class example_schema:Status ;
>   sh:description "only Active or Retired allowed" ;
>   sh:in (
>   example_schema:Active
>   example_schema:Retired
> ) ;
>   sh:maxCount 1 ;
>   sh:name "has status" ;
> .
>
>
> Cheers,
> David
>
> On 17 Apr 2024, at 14:00, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> sure,
>
> I created a similar ontology for testing with same results, here is the
> code:
>
> tesontologyramosenum:Color
>   a owl:Class ;
>   a sh:NodeShape ;
>   rdfs:label "Color" ;
>   rdfs:subClassOf owl:Thing ;
>   sh:in (
>   tesontologyramosenum:Green
>   tesontologyramosenum:Yellow
>   tesontologyramosenum:Red
> ) ;
>   sh:property tesontologyramosenum:Color-label ;
> .
>
> the screen shot is this:
>
> 
> 
>
> with similar results, a datatype property without labeling, and a group of
> undeclared properties.
>
> Is this the expected result?
>
> How do I use this in traffic light instances, if that were the case?
>
>
> Luis
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> El mié, 17 abr 2024 a las 14:41, Holger Knublauch ()
> escribió:
>
>> Can you paste us the complete content of the source code panel, e.g. as a
>> screenshot? It's hard to see otherwise and there are syntax errors below.
>>
>> Holger
>>
>>
>> On 17 Apr 2024, at 2:38 PM, 'Luis Enrique Ramos García' via TopBraid
>> Suite Users  wrote:
>>
>> I need only 3 elements in the enum,
>>
>> But, I tried at the first the source code edition, and told you the
>> result I got:
>>
>>
>> **
>>
>> 1. I tried to add the code by myself, but it seems there is something
>> wrong with the code:
>> sh:in (
>>   myontology:value1
>>myontology _:value2
>>   myontology :value3
>> ) ;
>> myontology:property1;
>> myontology:property2;
>> myontology:enumproperty;
>>
>> Please, take in account that I edited the enum property just after the
>> sh:in, but the editor put it at the end
>> of the list of properties.
>>
>> Part of the result was this black datatype property in properties list
>>
>> 
>>
>> and in the undeclared property there is a list with these values:
>>
>> in                  [myontology:property1;
>>   myontology:property1;
>>   myontology:enumproperty;]
>>
>> is thát the expected result?
>>
>>
>> **
>>
>>
>> Luis
>>
>> El mié, 17 abr 2024 a las 14:33, Holger Knublauch (<
>> hol...@topquadrant.com>) escribió:
>>
>>>
>>>
>>> On 17 Apr 2024, at 2:30 PM, 'Luis Enrique Ramos García' via TopBraid
>>> Suite Users  wrote:
>>>
>>> Thanks for your quick answer,
>>>
>>> But, dear, where should I add this code?.
>>>
>>> Because I tried to add it in the source code panel, and it didn't work,
>>> same with the script panel,
>>> where I expected it should work, but it did not.
>>>
>>> So, I owner in which panel should I add this code?.
>>>
>>> I do not have any idea how to use it.
>>>
>>>
>>> Yes, it requires JS experience. There is no out-of-the-box solution for
>>> what you are trying to express.
>>>
>>> How many enumerations do you need? If it's just a few, I would suggest
>>> 

Re: [topbraid-users] enum creation

['Luis Enrique Ramos García' via TopBraid Suite Users]

I need only 3 elements in the enum,

But, I tried at the first the source code edition, and told you the result
I got:

**

1. I tried to add the code by myself, but it seems there is something wrong
with the code:
sh:in (
  myontology:value1
   myontology _:value2
  myontology :value3
) ;
myontology:property1;
myontology:property2;
myontology:enumproperty;

Please, take in account that I edited the enum property just after the
sh:in, but the editor put it at the end
of the list of properties.

Part of the result was this black datatype property in properties list

[image: image.png]

and in the undeclared property there is a list with these values:

in  [myontology:property1;
  myontology:property1;
  myontology:enumproperty;]

is thát the expected result?

**


Luis

El mié, 17 abr 2024 a las 14:33, Holger Knublauch ()
escribió:

>
>
> On 17 Apr 2024, at 2:30 PM, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> Thanks for your quick answer,
>
> But, dear, where should I add this code?.
>
> Because I tried to add it in the source code panel, and it didn't work,
> same with the script panel,
> where I expected it should work, but it did not.
>
> So, I owner in which panel should I add this code?.
>
> I do not have any idea how to use it.
>
>
> Yes, it requires JS experience. There is no out-of-the-box solution for
> what you are trying to express.
>
> How many enumerations do you need? If it's just a few, I would suggest
> going ahead with manual editing of sh:in lists in the Source Code.
>
> Holger
>
>
>
>
> Luis
>
>
>
> El mié, 17 abr 2024 a las 13:45, Holger Knublauch ()
> escribió:
>
>>
>>
>> On 17 Apr 2024, at 1:38 PM, 'Luis Enrique Ramos García' via TopBraid
>> Suite Users  wrote:
>>
>> I am working with version Version: 7.5.1 (20230316-1531).
>>
>>
>> Ok then the script may not work, assuming the RDFNodeUtil object was
>> introduced later.
>>
>> In that case source code editing may be your best solution, unless you
>> know how to use this
>>
>>
>> createList: (nodes) => {
>> let nil = graph.namedNode(rdf.NS + 'nil');
>> if(nodes.length == 0) {
>> return nil;
>> }
>> let root = graph.blankNode();
>> let current = root;
>> nodes.forEach((node, index) => {
>> current.add(rdf.first, node);
>> let rest = index < nodes.length - 1 ? graph.blankNode() : nil;
>> current.add(rdf.rest, rest);
>> current = rest;
>> })
>> return root;
>> },
>>
>>
>>
>> I included an script panel, refreshed it, and I have this view:
>> 
>> When I run the script I can see my class, the one for which I want to
>> create the enum, is the result of focusNode.
>>
>> But, when I click in "Declare enumerations from instances" I get the same
>> result again:
>>
>> 
>> I have a question:
>>
>> how does my script know from which class I do want to get my instances
>> for the enum list?.
>>
>>
>> The infrastructure around the ModifyAction will make sure that the
>> variable focusNode points at the asset that
>> the action was called from (in the Modify menu).
>>
>>
>>
>> Because I think you are using the same class color?, how do I relate the
>> class traffic light there?
>>
>> What I want to say is something like this:
>>
>> Product hasSize oneof  Size (short, medium, large)
>>
>> And at this moment my focus is in *Product*, not in *Size*.
>>
>>
>> In SHACL you can either add sh:in to a class/node shape or to a property
>> shape. If you just want to add it to a specific property then a different
>> script would be needed.
>>
>> Holger
>>
>>
>>
>>
>> Luis
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> El mié, 17 abr 2024 a las 11:50, Holger Knublauch (<
>> hol...@topquadrant.com>) escribió:
>>
>>>
>>>
>>> On 17 Apr 2024, at 11:29 AM, 'Luis Enrique Ramos García' via TopBraid
>>> Suite Users  wrote:
>>>
>>> I added the code at the end of the code of the target class, and got
>>> this result:
>>>
>>> 
>>> When I click in "Declare e

Re: [topbraid-users] enum creation

['Luis Enrique Ramos García' via TopBraid Suite Users]

Thanks for your quick answer,

But, dear, where should I add this code?.

Because I tried to add it in the source code panel, and it didn't work,
same with the script panel,
where I expected it should work, but it did not.

So, I owner in which panel should I add this code?.

I do not have any idea how to use it.


Luis



El mié, 17 abr 2024 a las 13:45, Holger Knublauch ()
escribió:

>
>
> On 17 Apr 2024, at 1:38 PM, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> I am working with version Version: 7.5.1 (20230316-1531).
>
>
> Ok then the script may not work, assuming the RDFNodeUtil object was
> introduced later.
>
> In that case source code editing may be your best solution, unless you
> know how to use this
>
>
> createList: (nodes) => {
> let nil = graph.namedNode(rdf.NS + 'nil');
> if(nodes.length == 0) {
> return nil;
> }
> let root = graph.blankNode();
> let current = root;
> nodes.forEach((node, index) => {
> current.add(rdf.first, node);
> let rest = index < nodes.length - 1 ? graph.blankNode() : nil;
> current.add(rdf.rest, rest);
> current = rest;
> })
> return root;
> },
>
>
>
> I included an script panel, refreshed it, and I have this view:
> 
> When I run the script I can see my class, the one for which I want to
> create the enum, is the result of focusNode.
>
> But, when I click in "Declare enumerations from instances" I get the same
> result again:
>
> 
> I have a question:
>
> how does my script know from which class I do want to get my instances for
> the enum list?.
>
>
> The infrastructure around the ModifyAction will make sure that the
> variable focusNode points at the asset that
> the action was called from (in the Modify menu).
>
>
>
> Because I think you are using the same class color?, how do I relate the
> class traffic light there?
>
> What I want to say is something like this:
>
> Product hasSize oneof  Size (short, medium, large)
>
> And at this moment my focus is in *Product*, not in *Size*.
>
>
> In SHACL you can either add sh:in to a class/node shape or to a property
> shape. If you just want to add it to a specific property then a different
> script would be needed.
>
> Holger
>
>
>
>
> Luis
>
>
>
>
>
>
>
>
>
>
>
>
>
> El mié, 17 abr 2024 a las 11:50, Holger Knublauch ()
> escribió:
>
>>
>>
>> On 17 Apr 2024, at 11:29 AM, 'Luis Enrique Ramos García' via TopBraid
>> Suite Users  wrote:
>>
>> I added the code at the end of the code of the target class, and got this
>> result:
>>
>> 
>> When I click in "Declare enumeration from instances, I get this view:
>>
>> 
>>
>>
>> This looks unexpected. What version are you on? The RDFNodeUtil object
>> should be there. Maybe try the Refresh button in the Script Editor panel.
>>
>>
>> 
>> Then, I wonder how to make the system know where my list of enum values
>> are?
>>
>>
>> It will simply look at the already-existing instances of the currently
>> selected class, see graph.every(focusNode) where focusNode is the current
>> class.
>>
>> Holger
>>
>>
>>
>>
>>
>> Luis
>>
>>
>>
>> El mié, 17 abr 2024 a las 10:51, Luis Enrique Ramos García (<
>> luisenriqueramos1...@googlemail.com>) escribió:
>>
>>> Hi Holger,
>>> Thanks for your answer, but to be frank I find these procedures very
>>> complicated.
>>> In my opinion the enum is a very common pattern, and I understand when
>>> to use it.
>>>
>>> Anyway, let's try to solve the issue
>>>
>>> 1. I tried to add the code by myself, but it seems there is something
>>> wrong with the code:
>>> sh:in (
>>>   myontology:value1
>>>myontology _:value2
>>>   myontology :value3
>>> ) ;
>>> myontology:property1;
>>> myontology:property2;
>>> myontology:enumproperty;
>>>
>>> Please, take in account that I edited the enum property just after the
>>> sh:in, but the editor put it at the end
>>> of the list of properties.
>>>
>>> Part of the result was this black datatype property in properties list
>>>
>>> 
>>>
>>> and in the undeclared property there is a list with these values:
>>>
>>> in  [myontology:property1;
>>>   myontology:property1;
>>>   

Re: [topbraid-users] enum creation

['Luis Enrique Ramos García' via TopBraid Suite Users]

I am working with version Version: 7.5.1 (20230316-1531).

I included an script panel, refreshed it, and I have this view:
[image: image.png]
When I run the script I can see my class, the one for which I want to
create the enum, is the result of focusNode.

But, when I click in "Declare enumerations from instances" I get the same
result again:

[image: image.png]
I have a question:

how does my script know from which class I do want to get my instances for
the enum list?.

Because I think you are using the same class color?, how do I relate the
class traffic light there?

What I want to say is something like this:

Product hasSize oneof  Size (short, medium, large)

And at this moment my focus is in *Product*, not in *Size*.


Luis













El mié, 17 abr 2024 a las 11:50, Holger Knublauch ()
escribió:

>
>
> On 17 Apr 2024, at 11:29 AM, 'Luis Enrique Ramos García' via TopBraid
> Suite Users  wrote:
>
> I added the code at the end of the code of the target class, and got this
> result:
>
> 
> When I click in "Declare enumeration from instances, I get this view:
>
> 
>
>
> This looks unexpected. What version are you on? The RDFNodeUtil object
> should be there. Maybe try the Refresh button in the Script Editor panel.
>
>
> 
> Then, I wonder how to make the system know where my list of enum values
> are?
>
>
> It will simply look at the already-existing instances of the currently
> selected class, see graph.every(focusNode) where focusNode is the current
> class.
>
> Holger
>
>
>
>
>
> Luis
>
>
>
> El mié, 17 abr 2024 a las 10:51, Luis Enrique Ramos García (<
> luisenriqueramos1...@googlemail.com>) escribió:
>
>> Hi Holger,
>> Thanks for your answer, but to be frank I find these procedures very
>> complicated.
>> In my opinion the enum is a very common pattern, and I understand when to
>> use it.
>>
>> Anyway, let's try to solve the issue
>>
>> 1. I tried to add the code by myself, but it seems there is something
>> wrong with the code:
>> sh:in (
>>   myontology:value1
>>myontology _:value2
>>   myontology :value3
>> ) ;
>> myontology:property1;
>> myontology:property2;
>> myontology:enumproperty;
>>
>> Please, take in account that I edited the enum property just after the
>> sh:in, but the editor put it at the end
>> of the list of properties.
>>
>> Part of the result was this black datatype property in properties list
>>
>> 
>>
>> and in the undeclared property there is a list with these values:
>>
>> in  [myontology:property1;
>>   myontology:property1;
>>   myontology:enumproperty;]
>>
>> is thát the expected result?
>>
>> if not, for the second option,
>>
>> where do I have to insert this code:
>>
>> focusNode.add(sh.in, RDFNodeUtil.createList(graph.every(focusNode)))
>>
>>
>> do I have to add this code at the beginning of the code of my ontology?
>>
>>
>> myontology:ClassActionsGroup
>> a dash:ActionGroup ;
>> rdfs:label "Class actions group" ;
>> .
>> myontology:DeclareEnumerationFromInstances
>> a dash:ModifyAction ;
>> dash:actionGroup myontology:ClassActionsGroup ;
>> dash:js "focusNode.add(sh.in,
>> RDFNodeUtil.createList(graph.every(focusNode)))" ;
>> rdfs:comment "Adds a sh:in declaration that enumerates all (current)
>> instances of the selected class." ;
>> rdfs:label "Declare enumeration from instances" ;
>> .
>> rdfs:Class
>> dash:resourceAction myontology:DeclareEnumerationFromInstances ;
>>
>> I have not done this before, if you have a tutorial or some document I
>> could read, I would really appreciate
>> if you can share it with me.
>>
>>
>>
>>
>> Best regards
>>
>>
>>
>> Luis Ramos
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> El mié, 17 abr 2024 a las 10:00, Holger Knublauch (<
>> hol...@topquadrant.com>) escribió:
>>
>>> Hi Luis,
>>>
>>> declaring an enumerated class is achieved in SHACL via sh:in. There is
>>> no dedicated user interface for creating those quickly, as this isn't
>>> anything that we have seen used much so far. I guess this is because the
>>> user interface for entering instance data is already a drop down box
>>> any

[topbraid-users] enum creation

['Luis Enrique Ramos García' via TopBraid Suite Users]

 

I need to model an enum, 

and found this non uptodate tutorial:

https://topbraidcomposer.org/html/Create_an_enumeration.htm

Thus, I wonder if there is an uptodate procedure to create an enum in EDG?

 

Thanks


Luis 

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/6621d600-2195-4e9c-9b5d-58ce8172722bn%40googlegroups.com.

Re: [topbraid-users] TBC Label Display

['Luis Enrique Ramos García' via TopBraid Suite Users]

Holger,

I checked with the administrator and he helped to solve the issue.

I had to have a label without tag, so the default language (English) could
be rendered,

But, it currently renders the default language only  with the EDGE browser,
not in mozilla.

Luis





El lun, 15 abr 2024 a las 12:03, Holger Knublauch ()
escribió:

>
>
> On 15 Apr 2024, at 11:54 AM, 'Luis Enrique Ramos García' via TopBraid
> Suite Users  wrote:
>
> Holger,
>
> I do not have access to system administrator, thus I can only comment the
> other options:
>
> * 1. The system doesn't know that skos:prefLabel is rdfs:subPropertyOf
> rdfs:label - from your screenshot it seems that skos:prefLabel doesn't even
> have a label of its own *
>
> I only can show you what I see when I edit the class:
>
> 
> There, I see skos:prefLabel, and the label by language, as I see
> skos:prefLabel has labels.
>
> * What are the owl:imports here? *
>
> 
>
> * Are you sure Maschine is used from the "de" label or does it happen to
> be the local name of the URI? The local names are used if no display labels
> are found. *
>
> I hope your first screenshot could answer your question
>
>
> It did not 100% because I didn't see the URI of the resource. But I guess
> when you change the "de" label, then the display shows that changed label
> too?
>
> Anyway, I guess you should check with whoever is the administrator if some
> global language override has been configured. I cannot think of other
> reasons right now.
>
> Holger
>
>
>
> *If none of this works, could you share a screenshot of the language
> settings in Chrome?*
>
> 
> Only English is selected
>
>
> Luis Ramos
>
>
>
> El lun, 15 abr 2024 a las 11:30, Holger Knublauch ()
> escribió:
>
>> This is surprising. Possible explanations may be
>>
>> - System Administration > Server Configuration > Preferred Languages has
>> been set
>>
>> - The system doesn't know that skos:prefLabel is rdfs:subPropertyOf
>> rdfs:label - from your screenshot it seems that skos:prefLabel doesn't even
>> have a label of its own. What are the owl:imports here?
>>
>> - Are you sure Maschine is used from the "de" label or does it happen to
>> be the local name of the URI? The local names are used if no display labels
>> are found.
>>
>> If none of this works, could you share a screenshot of the language
>> settings in Chrome?
>>
>> Holger
>>
>>
>>
>> On 15 Apr 2024, at 9:53 AM, 'Luis Enrique Ramos García' via TopBraid
>> Suite Users  wrote:
>>
>> sure dear,
>>
>> it is about EDG
>>
>> the screenshot:
>>
>> 
>>
>>
>> El lun, 15 abr 2024 a las 9:37, Holger Knublauch ()
>> escribió:
>>
>>> Hi Luis,
>>>
>>> is this about TBC? If yes, then default language of browser is not
>>> relevant.
>>>
>>> If this is about EDG, could you share a screenshot?
>>>
>>> Holger
>>>
>>>
>>> On 15 Apr 2024, at 8:22 AM, 'Luis Enrique Ramos García' via TopBraid
>>> Suite Users  wrote:
>>>
>>> Hi Holger,
>>>
>>> I have a similar use case with the following labels:
>>>
>>>  rdfs:label "Machine"@en ;
>>>  skos:prefLabel "Machine"@en ;
>>>  skos:prefLabel "Maquina"@es ;
>>>  skos:prefLabel "Maschine"@de ;
>>>
>>> I checked that English is my default language in browser,
>>> and also checked that skos:core was imported,
>>> however in this case, still the label in German is still rendered.
>>>
>>>
>>> There should be something that I am not considering?
>>>
>>> Best regards
>>>
>>>
>>> Luis Ramos
>>>
>>>
>>>
>>>
>>> On Thursday, May 27, 2021 at 12:05:02 AM UTC+2 Holger Knublauch wrote:
>>>
>>>> Hi Matt,
>>>>
>>>> TBC will use skos:prefLabel even in preference over rdfs:label for any
>>>> resource, as shown in the attached test. However you need to make sure that
>>>> the triple skos:preflabel rdfs:subPropertyOf rdfs:label exists, which is
>>>> most commonly achieved by owl:importing the SKOS Core namespace.
>>>>
>>>> HTH
>>>> Holger
>>>>
>>>>
>>>> On 2021-05-27 2:39 am, Matt Goldberg wrote:
>>>>
>>>> Hello-
>>>>
>>>> The top toolbar of TBC has the button that toggles between s

Re: [topbraid-users] TBC Label Display

['Luis Enrique Ramos García' via TopBraid Suite Users]

Holger,

I do not have access to system administrator, thus I can only comment the
other options:

* 1. The system doesn't know that skos:prefLabel is rdfs:subPropertyOf
rdfs:label - from your screenshot it seems that skos:prefLabel doesn't even
have a label of its own *

I only can show you what I see when I edit the class:

[image: image.png]
There, I see skos:prefLabel, and the label by language, as I see
skos:prefLabel has labels.

* What are the owl:imports here? *

[image: image.png]

* Are you sure Maschine is used from the "de" label or does it happen to be
the local name of the URI? The local names are used if no display labels
are found. *

I hope your first screenshot could answer your question

*If none of this works, could you share a screenshot of the language
settings in Chrome?*

[image: image.png]
Only English is selected


Luis Ramos



El lun, 15 abr 2024 a las 11:30, Holger Knublauch ()
escribió:

> This is surprising. Possible explanations may be
>
> - System Administration > Server Configuration > Preferred Languages has
> been set
>
> - The system doesn't know that skos:prefLabel is rdfs:subPropertyOf
> rdfs:label - from your screenshot it seems that skos:prefLabel doesn't even
> have a label of its own. What are the owl:imports here?
>
> - Are you sure Maschine is used from the "de" label or does it happen to
> be the local name of the URI? The local names are used if no display labels
> are found.
>
> If none of this works, could you share a screenshot of the language
> settings in Chrome?
>
> Holger
>
>
>
> On 15 Apr 2024, at 9:53 AM, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> sure dear,
>
> it is about EDG
>
> the screenshot:
>
> 
>
>
> El lun, 15 abr 2024 a las 9:37, Holger Knublauch ()
> escribió:
>
>> Hi Luis,
>>
>> is this about TBC? If yes, then default language of browser is not
>> relevant.
>>
>> If this is about EDG, could you share a screenshot?
>>
>> Holger
>>
>>
>> On 15 Apr 2024, at 8:22 AM, 'Luis Enrique Ramos García' via TopBraid
>> Suite Users  wrote:
>>
>> Hi Holger,
>>
>> I have a similar use case with the following labels:
>>
>>  rdfs:label "Machine"@en ;
>>  skos:prefLabel "Machine"@en ;
>>  skos:prefLabel "Maquina"@es ;
>>  skos:prefLabel "Maschine"@de ;
>>
>> I checked that English is my default language in browser,
>> and also checked that skos:core was imported,
>> however in this case, still the label in German is still rendered.
>>
>>
>> There should be something that I am not considering?
>>
>> Best regards
>>
>>
>> Luis Ramos
>>
>>
>>
>>
>> On Thursday, May 27, 2021 at 12:05:02 AM UTC+2 Holger Knublauch wrote:
>>
>>> Hi Matt,
>>>
>>> TBC will use skos:prefLabel even in preference over rdfs:label for any
>>> resource, as shown in the attached test. However you need to make sure that
>>> the triple skos:preflabel rdfs:subPropertyOf rdfs:label exists, which is
>>> most commonly achieved by owl:importing the SKOS Core namespace.
>>>
>>> HTH
>>> Holger
>>>
>>>
>>> On 2021-05-27 2:39 am, Matt Goldberg wrote:
>>>
>>> Hello-
>>>
>>> The top toolbar of TBC has the button that toggles between showing
>>> prefixed qnames and rdfs:labels. I'm working with some files that are using
>>> the SKOS label properties and not rdfs:label directly. Consequently, when
>>> it is toggled to show human readable labels, it still shows qnames because
>>> there are no rdfs:labels. Is there an option somewhere to change the
>>> behavior of that button to show skos:prefLabels instead of rdfs:labels, or
>>> do I have to rely on the RDFS Plus reasoner (at a minimum) to get labels to
>>> show without modifying the file?
>>>
>>> I'm using version TBC 7.0.2.
>>>
>>> Thanks.
>>>
>>> --
>>> 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/d12bb9a9-44c4-4d07-ace2-c96e1e4aae70n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/topbraid-users/d12bb9a9-44c4-4d07-ace2-c96e1e4aae70n%40googlegroups.com?utm_medium=email_source=f

Re: [topbraid-users] TBC Label Display

['Luis Enrique Ramos García' via TopBraid Suite Users]

sure dear,

it is about EDG

the screenshot:

[image: image.png]


El lun, 15 abr 2024 a las 9:37, Holger Knublauch ()
escribió:

> Hi Luis,
>
> is this about TBC? If yes, then default language of browser is not
> relevant.
>
> If this is about EDG, could you share a screenshot?
>
> Holger
>
>
> On 15 Apr 2024, at 8:22 AM, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> Hi Holger,
>
> I have a similar use case with the following labels:
>
>  rdfs:label "Machine"@en ;
>  skos:prefLabel "Machine"@en ;
>  skos:prefLabel "Maquina"@es ;
>  skos:prefLabel "Maschine"@de ;
>
> I checked that English is my default language in browser,
> and also checked that skos:core was imported,
> however in this case, still the label in German is still rendered.
>
>
> There should be something that I am not considering?
>
> Best regards
>
>
> Luis Ramos
>
>
>
>
> On Thursday, May 27, 2021 at 12:05:02 AM UTC+2 Holger Knublauch wrote:
>
>> Hi Matt,
>>
>> TBC will use skos:prefLabel even in preference over rdfs:label for any
>> resource, as shown in the attached test. However you need to make sure that
>> the triple skos:preflabel rdfs:subPropertyOf rdfs:label exists, which is
>> most commonly achieved by owl:importing the SKOS Core namespace.
>>
>> HTH
>> Holger
>>
>>
>> On 2021-05-27 2:39 am, Matt Goldberg wrote:
>>
>> Hello-
>>
>> The top toolbar of TBC has the button that toggles between showing
>> prefixed qnames and rdfs:labels. I'm working with some files that are using
>> the SKOS label properties and not rdfs:label directly. Consequently, when
>> it is toggled to show human readable labels, it still shows qnames because
>> there are no rdfs:labels. Is there an option somewhere to change the
>> behavior of that button to show skos:prefLabels instead of rdfs:labels, or
>> do I have to rely on the RDFS Plus reasoner (at a minimum) to get labels to
>> show without modifying the file?
>>
>> I'm using version TBC 7.0.2.
>>
>> Thanks.
>>
>> --
>> 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/d12bb9a9-44c4-4d07-ace2-c96e1e4aae70n%40googlegroups.com
>> <https://groups.google.com/d/msgid/topbraid-users/d12bb9a9-44c4-4d07-ace2-c96e1e4aae70n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/1a6211f7-7ae2-47da-bd1e-4a168e033987n%40googlegroups.com
> <https://groups.google.com/d/msgid/topbraid-users/1a6211f7-7ae2-47da-bd1e-4a168e033987n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/A2C5F6C0-7E2E-4CE5-BCB1-3A4FFA94CC48%40topquadrant.com
> <https://groups.google.com/d/msgid/topbraid-users/A2C5F6C0-7E2E-4CE5-BCB1-3A4FFA94CC48%40topquadrant.com?utm_medium=email_source=footer>
> .
>

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/CABy94X%3DyNHeFS_n9Eub_bLZ1ucM6-9OCr0podaqRFBksebtbsg%40mail.gmail.com.

Re: [topbraid-users] TBC Label Display

['Luis Enrique Ramos García' via TopBraid Suite Users]

Hi Holger, 

I have a similar use case with the following labels:

 rdfs:label "Machine"@en ;
 skos:prefLabel "Machine"@en ;
 skos:prefLabel "Maquina"@es ;
 skos:prefLabel "Maschine"@de ;

I checked that English is my default language in browser, 
and also checked that skos:core was imported, 
however in this case, still the label in German is still rendered.


There should be something that I am not considering?

Best regards


Luis Ramos




On Thursday, May 27, 2021 at 12:05:02 AM UTC+2 Holger Knublauch wrote:

> Hi Matt,
>
> TBC will use skos:prefLabel even in preference over rdfs:label for any 
> resource, as shown in the attached test. However you need to make sure that 
> the triple skos:preflabel rdfs:subPropertyOf rdfs:label exists, which is 
> most commonly achieved by owl:importing the SKOS Core namespace.
>
> HTH
> Holger
>
>
> On 2021-05-27 2:39 am, Matt Goldberg wrote:
>
> Hello- 
>
> The top toolbar of TBC has the button that toggles between showing 
> prefixed qnames and rdfs:labels. I'm working with some files that are using 
> the SKOS label properties and not rdfs:label directly. Consequently, when 
> it is toggled to show human readable labels, it still shows qnames because 
> there are no rdfs:labels. Is there an option somewhere to change the 
> behavior of that button to show skos:prefLabels instead of rdfs:labels, or 
> do I have to rely on the RDFS Plus reasoner (at a minimum) to get labels to 
> show without modifying the file?
>
> I'm using version TBC 7.0.2.
>
> Thanks.
>
> -- 
> 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/d12bb9a9-44c4-4d07-ace2-c96e1e4aae70n%40googlegroups.com
>  
> 
> .
>
>

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/1a6211f7-7ae2-47da-bd1e-4a168e033987n%40googlegroups.com.

Re: [topbraid-users] Customizing Definition tab in Ontology

['Luis Enrique Ramos García' via TopBraid Suite Users]

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

On Thursday, August 20, 2020 at 12:59:08 AM UTC+2 Holger Knublauch wrote:

>
> On 20/08/2020 06:52, Irene Polikoff wrote:
>
>
>
> On Aug 19, 2020, at 4:29 PM, Adam Kimball  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
>
>
>
>
> Adam
>
>
>
> On Wednesday, August 12, 2020 at 11:50:02 AM UTC-6 Irene Polikoff wrote:
>
>> 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
>>
>>
>>
>> On Aug 12, 2020, at 12:01 PM, Adam Kimball  wrote:
>>
>> 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
>>
>>
>> -- 
>> 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
>>  
>> 
>> .
>>
>>
>>
> -- 
> 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/7a328cd4-005c-4c17-8c07-f2b0928b9fdfn%40googlegroups.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/4C78A01B-15EA-49D3-A6B8-0D551396CBAA%40topquadrant.com
>  
> 
> .
>
>

-- 
The topics of this mailing list 

Re: [topbraid-users] linking glossaries to ontologies ( or taxonomies)

['Luis Enrique Ramos García' via TopBraid Suite Users]

Hi guys,

thanks for your kindly reply, I will work on it, and let you know.


Luis

El vie, 23 feb 2024 a las 12:47, 'Bohms, H.M. (Michel)' via TopBraid Suite
Users () escribió:

> Fully agree.
>
>
>
> In SML the proposed “maps-to-term” relation is reusing rdfs:seeAlso.
>
>
>
>
>
> Dr. ir. H.M. Böhms (Michel)
> Scientist Specialist
> Mobility & Built Environment
>
> T:
> M: +31630381220
> E: michel.bo...@tno.nl
>
> Location <https://www.tno.nl/locaties/MSG>
>
>
>
>
>
> <https://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:* topbraid-users@googlegroups.com  *On
> Behalf Of *David Price
> *Sent:* vrijdag 23 februari 2024 11:10
> *To:* 'Felix Sasaki' via TopBraid Suite Users <
> topbraid-users@googlegroups.com>
> *Subject:* Re: [topbraid-users] linking glossaries to ontologies ( or
> taxonomies)
>
>
>
> Hi Luis,
>
>
>
> One note of caution …
>
>
>
> A Glossary Term is seldom “the same thing” as an ontology class/property
> or a database table/column. Instead, what we typically do is say that a
> class/property or table/column “maps to” the term.
>
>
>
> Glossary Terms are usually for a less technical audience, are
> technology-independent and are self contained in most cases.
>
>
>
> However, a class definition, for example, often takes its place in the
> class hierarchy into account and so is a more technical thing (e.g. a
>  is a  with 
> ).
>
>
>
> Additionally, need to remember that all instances of any subclass are also
> members of all superclasses and so every definition all the way up the
> class hierarchy is also applicable. That sometimes puts a lot of burden on
> glossary terms being reused as class definitions.
>
>
>
> So, RDF-wise it is certainly possible to do as Holger explained, but
> business need/requirements-wise it may not be the best practive. As I said,
> in our Data Asset+Glossary architecture solution Data Elements/Database
> Columns include a  “maps to term’ to Glossary Term relation allowing
> separate, clean definitions for the different audiences.
>
>
>
> Cheers,
>
> David
>
>
>
> UK +44 (0) 7788 561308
> US +1 (336) 283-0808
>
>
>
> On 23 Feb 2024, at 09:08, Holger Knublauch  wrote:
>
>
>
> Hi Luis,
>
>
>
> any asset collection can use assets/resources from other asset
> collections. Just owl:import the Glossary (from Settings > Includes). Then,
> to link a class with a glossary term, navigate to the definition of
> rdfs:Class or owl:Class and add a property/relationship there, with
> Glossary Terms as values. To navigate to rdfs:Class and owl:Class, find the
> "Up" button in the upper right corner of the Class Hierarchy panel, to
> switch to rdfs:Resource as root class.
>
>
>
> If you further want to copy values such as the definition into the
> classes, you could define a property that uses a sh:path expression such as
>
>
>
>ex:glossaryTerm/rdfs:comment
>
>
>
> or declare a sh:values rule that does the same. See
> https://www.linkedin.com/pulse/inferencing-shacl-using-shvalues-holger-knublauch-0metf/
>  for
> some background on sh:values rules.
>
>
>
> HTH
>
> Holger
>
>
>
>
>
> On 23 Feb 2024, at 8:28 am, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
>
>
> Hi guys,
>
>
>
> I wonder if there is a way to link glossaries to ontologies.
>
>
>
> I mean, let's say I have a group of geographical terms in a list, that I
> create as glossary, and then I would like to use this glossary definition
> to fill the skos:definition of the corresponding class (concept) in my
> ontology.
>
> Could you share any documentation or example of how I could do that?.
>
>
>
> Best regards
>
>
>
>
>
> Luis Ramos.
>
>
>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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

[topbraid-users] linking glossaries to ontologies ( or taxonomies)

['Luis Enrique Ramos García' via TopBraid Suite Users]

Hi guys, 

I wonder if there is a way to link glossaries to ontologies. 

I mean, let's say I have a group of geographical terms in a list, that I 
create as glossary, and then I would like to use this glossary definition 
to fill the skos:definition of the corresponding class (concept) in my 
ontology. 
Could you share any documentation or example of how I could do that?. 

Best regards


Luis Ramos. 

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/91b23e2e-9d7b-4c6a-8d08-423bff8fc06fn%40googlegroups.com.

[topbraid-users] duplicated superclasses with lcc ontology

['Luis Enrique Ramos García' via TopBraid Suite Users]

Dear All,

I realized when I upload the lcc  ontology 
(OMG), and importing all their dependencies, in some cases superclass 
definitions are duplicated, as shown in tb_1.png, I can remove the 
additional definitions, but in large ontologies it would e a time consuming 
task.

The result I would expect is like the one shown in tb_2.png, where I 
imported the same ontology, with all its dependencies, but definitions are 
not duplicated.

Is there a way to solve this?

Best regards


Luis Ramos.




-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/136e6516-d07f-496d-a3ef-2a6f261c77dbn%40googlegroups.com.

[topbraid-users] map explorer

['Luis Enrique Ramos García' via TopBraid Suite Users]

Dear All, 

I am interested in developing a minimum example of GeoSparql.

And I found that such support is possible in topbraid, according to this 
discussion.

https://groups.google.com/g/topbraid-users/c/2JFwDxyKsDk/m/jjxe80e_BgAJ

But, when I search for the map explorer panel, it seems not to be available.

Thus, I wonder if this is a restricted or limited feature?.

This is the current view of my tab explorer:[image: map explorer.png]


Best regards


Luis Ramos




-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/f0df2372-1ba1-4dba-bd00-c4223b7c2890n%40googlegroups.com.

Re: [topbraid-users] duplicating restrictions when loading gleif ontology

['Luis Enrique Ramos García' via TopBraid Suite Users]

Well,

Checking the code, I do not find any import declaration in the definition
of Entity, and for instance the restriction hasEntityExpirationDate has the
following code:



https://www.gleif.org/ontology/Base/hasEntityExpirationDate"/>
http://www.w3.org/2001/XMLSchema#nonNegativeInteger
">1
http://www.w3.org/2001/XMLSchema#dateTime"/>




I downloaded the ontology directly from here:

https://www.gleif.org/ontology/v1.0/Base/ontology.ttl


Luis


El mar, 4 abr 2023 a las 11:25, Holger Knublauch ()
escribió:

> Are some of those restrictions marked as owl:imported? Maybe there is
> confusion about the base URIs and it has cyclic imports so that it
> reimports itself again but then from the web? Blank nodes will just add up.
>
> Which owl:Restriction in particular is malformed? I just did a very brief
> look and saw that it has owl:maxCardinality "1" which is incorrect as those
> must be numbers not strings.
>
> Holger
>
>
> On 4 Apr 2023, at 10:12 am, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> Dear All,
>
> When I import the gleif
> <https://www.gleif.org/ontology/v1.0/Base/index-en.html> ontology into
> top braid composer, it seems to duplicate the restrictions, ans shown in
> the attached picture.
>
> I double checked the code, and could confirm that effectively the code of
> these restrictions is duplicated as in the example:
>
> rdfs:subClassOf [
>   a owl:Restriction ;
>   owl:maxQualifiedCardinality 1 ;
>   owl:onClass gleif-base:EntityExpirationReason ;
>   owl:onProperty gleif-base:hasEntityExpirationReason ;
> ] ;
>   rdfs:subClassOf [
>   a owl:Restriction ;
>   owl:maxQualifiedCardinality 1 ;
>   owl:onClass gleif-base:EntityExpirationReason ;
>   owl:onProperty gleif-base:hasEntityExpirationReason ;
> ] ;
>
> Thus, I wonder what could be the reason of this behavior?.
>
> Moreover,  the tool reports again:
>
> [Malformed OWL: Malformed OWL restriction]
>
>
> Best regards
>
>
> Luis Ramos
>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/7514288b-0519-43a8-96ba-1c5a40df01cdn%40googlegroups.com
> <https://groups.google.com/d/msgid/topbraid-users/7514288b-0519-43a8-96ba-1c5a40df01cdn%40googlegroups.com?utm_medium=email_source=footer>
> .
> 
>
>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/BE08B90F-3D90-47C9-8844-91757720D172%40topquadrant.com
> <https://groups.google.com/d/msgid/topbraid-users/BE08B90F-3D90-47C9-8844-91757720D172%40topquadrant.com?utm_medium=email_source=footer>
> .
>

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/CABy94XkYHr7jzTA4W0Yqq7ap%2BbdebJWvMY%2BeDGYS5sKC9urDPg%40mail.gmail.com.

[topbraid-users] duplicating restrictions when loading gleif ontology

['Luis Enrique Ramos García' via TopBraid Suite Users]

Dear All,

When I import the gleif 
 ontology into top 
braid composer, it seems to duplicate the restrictions, ans shown in the 
attached picture. 

I double checked the code, and could confirm that effectively the code of 
these restrictions is duplicated as in the example:

rdfs:subClassOf [
  a owl:Restriction ;
  owl:maxQualifiedCardinality 1 ;
  owl:onClass gleif-base:EntityExpirationReason ;
  owl:onProperty gleif-base:hasEntityExpirationReason ;
] ;
  rdfs:subClassOf [
  a owl:Restriction ;
  owl:maxQualifiedCardinality 1 ;
  owl:onClass gleif-base:EntityExpirationReason ;
  owl:onProperty gleif-base:hasEntityExpirationReason ;
] ;

Thus, I wonder what could be the reason of this behavior?.

Moreover,  the tool reports again:

[Malformed OWL: Malformed OWL restriction] 


Best regards


Luis Ramos

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/7514288b-0519-43a8-96ba-1c5a40df01cdn%40googlegroups.com.


gleif issues.pptx
Description: MS-Powerpoint 2007 presentation

Re: [topbraid-users] Malformed OWL restriction

['Luis Enrique Ramos García' via TopBraid Suite Users]

Hi Holger,

thanks for your quick answer, but that piece of code is not in top braid
side, in top braid is the following code:

a owl:Restriction ;
  owl:onDataRange xsd:boolean ;
  owl:onProperty lcc-cr:isIndependent ;
  owl:qualifiedCardinality 1 ;

Which I assume is the automatic translation of the definition you mentioned
above.

Then, I wonder what should the code look like in top braid to avoid this
warning?.


best wishes


Luis




El lun, 27 mar 2023 a las 15:22, Holger Knublauch ()
escribió:

> The offending definition is
>
> 
> 
> 
> 
>  rdf:datatype="nonNegativeInteger">1
> 
> 
>
> I don't know if this is valid OWL but in any case TopBraid doesn't know
> what to do with it and issues this error (which really is a warning) when
> trying to display that restriction. I don't think this is any cause of
> alarm as TopBraid will (I believe) just ignore this anyway. More generally,
> TopBraid does not handle all of OWL, especially not some of the rarely used
> OWL 2 constructs.
>
> Holger
>
>
> On 27 Mar 2023, at 2:16 pm, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> Dear All,
>
> I imported the Country Representation Ontolog
> <https://www.omg.org/spec/LCC/Countries/CountryRepresentation/>y (OMG)
> into TopBraid with no error reported during the process.
> However, after reviewing in details I found the error indicated in the
> first attached slide.
>
> In this case the restriction of "is independent" is indicated as Malformed
> owl restriction.
>
> I also checked the code (second slide), and found not clear reason for
> such an error.
>
> Moreover, in protégé no issue was indicated when running the reasoner on
> the same file, thus I wonder which could be the problem?.
>
> The country representation ontology was uploaded "as is" from OMG website,
> with no changes from my side.
>
>
> Best regards
>
>
> Luis Ramos
>
>
>
>
>
>
>
>
>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/f2978936-3456-4acf-950c-f467e823fe4dn%40googlegroups.com
> <https://groups.google.com/d/msgid/topbraid-users/f2978936-3456-4acf-950c-f467e823fe4dn%40googlegroups.com?utm_medium=email_source=footer>
> .
> 
>
>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/2EF779DA-9A0F-4ABD-B0A4-FDA644956AEA%40topquadrant.com
> <https://groups.google.com/d/msgid/topbraid-users/2EF779DA-9A0F-4ABD-B0A4-FDA644956AEA%40topquadrant.com?utm_medium=email_source=footer>
> .
>

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/CABy94XkcA2td1xvueAJgHzYwcoBZmd_xROdqPhL8qb6vK7EVcQ%40mail.gmail.com.

[topbraid-users] Malformed OWL restriction

['Luis Enrique Ramos García' via TopBraid Suite Users]

Dear All,

I imported the Country Representation Ontolog 
y (OMG) into 
TopBraid with no error reported during the process.
However, after reviewing in details I found the error indicated in the 
first attached slide.

In this case the restriction of "is independent" is indicated as Malformed 
owl restriction.

I also checked the code (second slide), and found not clear reason for such 
an error.

Moreover, in protégé no issue was indicated when running the reasoner on 
the same file, thus I wonder which could be the problem?.

The country representation ontology was uploaded "as is" from OMG website, 
with no changes from my side.


Best regards


Luis Ramos








-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/f2978936-3456-4acf-950c-f467e823fe4dn%40googlegroups.com.


Malformed OWL.pptx
Description: MS-Powerpoint 2007 presentation

Re: [topbraid-users] adding skos:changeNote to existing onotlogy

['Luis Enrique Ramos García' via TopBraid Suite Users]

Hi Holger,

Thanks for your quick answer.

Well, regarding your last comment, I am not trying to annotate an instance,
or a class, nor a property, but the ontology itself.
For that, I click on the "ontology" tab, and then in the Form panel,
finally click on the  "Undeclared Properties" tab,
where I can see the properties (skos: changeNote) I expect I could edit.

Then, I wonder how do I declare an skos annotation as (skos: changeNote)
SHACL property shape?.
Because, currently I can see  skos: changeNote  in the rdf/owl list tab,
and I really do not have a clue how to do that.


Best regards


Luis Ramos



















El vie, 24 mar 2023 a las 12:57, Holger Knublauch ()
escribió:

> Hi Luis Ramos,
>
> all properties that shall be editable on TopBraid forms need to be
> declared as SHACL property shapes. Without those the system wouldn't know,
> for example, the sh:datatype or sh:class that is needed to suggest edit
> widgets.
>
> From your screenshot I am not entirely sure which type of instances you
> want to annotate with these notes, but you can add the property
> declarations using the Ontology editor.
>
> Holger
>
> On 24 Mar 2023, at 9:46 am, 'Luis Enrique Ramos García' via TopBraid Suite
> Users  wrote:
>
> Dear All,
>
> I am working in a recently created ontology, that I built up based in
> other existing ones (importing them).
>
> Now, I want to add some annotations to this ontology, like
> skos:changeNote. In the current ontology there are just some of them, but I
> want to add my new ones.
>
> However, although these annotations appear in the
> "Undeclared Properties Tab", when I click on edit, none of these
> properties become become editable, and I do not have the possibility of
> adding a new one. (attached picture)
>
> Thus, I wonder what should I be doing wrong?, or what should be the right
> procedure to add an annotation?.
>
> Best regards
>
>
> Luis Ramos
>
>
>
>
>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/3a9a2010-3c19-436e-80ec-9b979f75d565n%40googlegroups.com
> <https://groups.google.com/d/msgid/topbraid-users/3a9a2010-3c19-436e-80ec-9b979f75d565n%40googlegroups.com?utm_medium=email_source=footer>
> .
> 
>
>
> --
> The topics of this mailing list include TopBraid EDG and related
> technologies such as SHACL.
> To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/833E2B11-C92B-45AC-8A6C-B9A8CD9616DD%40topquadrant.com
> <https://groups.google.com/d/msgid/topbraid-users/833E2B11-C92B-45AC-8A6C-B9A8CD9616DD%40topquadrant.com?utm_medium=email_source=footer>
> .
>

-- 
The topics of this mailing list include TopBraid EDG and related technologies 
such as SHACL.
To post to this group, send email to topbraid-users@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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/topbraid-users/CABy94Xng7t2gfezUqs9vWX2afZFM0jfZsyDzoFZVj%3DDSOj26%2Bg%40mail.gmail.com.