linking images

[Bohms, H.M. (Michel)]

Is there a more specific annotation than rdfs:seeAlso to relate an image to a class?

(ie in skos, dcterms, etc.)

 

Thx for advice, Michel

 

Ps

Foaf:Image seems only ok for instances (since domain being owl:Thing) and we do not want to introduce punning…

 

 

Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E michel...@tno.nl Location   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.

 

[David Price]

Nothing in the core standards for this as far as I can see.

FWIW I don’t think I know of/never seen a customer project use any standard/public ontologies that publishes images for OWL classes they create, except of course in the HTML pages about an ontology. 

For example, Prov-O has a lot of nice pictures explaining the ontology but none are linked from the OWL itself - https://www.w3.org/TR/prov-o/#expanded-terms-figure is reached in this HTML source:

 <div id="starting-points-figure" style="text-align: center;" class="figure">
            <!-- When publishing to w3c: replace prov-o-diagrams/ with diagrams/ -->
            <!--img src="prov-o-diagrams/Starting-points-terms.png"-->
            <img src="diagrams/starting-points.svg" style="width: 60%; min-width: 25em; max-width: 60em" alt="PROV-O Starting Point terms">
            <div class="figcaption"><a href="#starting-points-figure">Figure 1</a>. 
            The three Starting Point classes and the properties that relate them.<br>
            The diagrams in this document depict Entities as yellow ovals,<br>
            Activities as blue rectangles, and Agents as orange pentagons.<br>
            The responsibility properties are shown in pink.
            </div>
      </div>

Anyway, just for fun I added rdfs:seeAlso to EDG owl:Class-defined properties and it works fine:

Cheers,

David

On 20 Jul 2021, at 10:35, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:

Is there a more specific annotation than rdfs:seeAlso to relate an image to a class?

(ie in skos, dcterms, etc.)

 

Thx for advice, Michel

 

Ps

Foaf:Image seems only ok for instances (since domain being owl:Thing) and we do not want to introduce punning…

 

 

Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E michel...@tno.nl Location

<image001.gif>

This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.

 

-- 
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/809411d54e314fe18a1fcfc87fbcd04b%40tno.nl.

UK +44 (0) 7788 561308

US +1 (336) 283-0808‬

[Bohms, H.M. (Michel)]

Thx David, very clear!

Indeed used as schematics maybe showing how to interprete attributes etc.

 

I guess, even when embedded in HTML, there is no special version of rdfs:seeAlso towards HTML resources?

 

Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E michel...@tno.nl Location

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.

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/F6BEDE2A-F051-4B7E-B86A-A2362D156EA4%40topquadrant.com.

[David Price]

On 20 Jul 2021, at 13:26, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:

Thx David, very clear!

Indeed used as schematics maybe showing how to interprete attributes etc.

 

I guess, even when embedded in HTML, there is no special version of rdfs:seeAlso towards HTML resources?

seeAlso does not refer to the HTML I pasted. That is from the W3C site supporting Prov-O.

There is no “special version” of any rdfs or owl annotation property.

Cheers,

David

 

Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E michel...@tno.nl Location   <image001.gif> 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.

 

Van: topbrai...@googlegroups.com <topbrai...@googlegroups.com> Namens David Price
Verzonden: dinsdag 20 juli 2021 13:04
Aan: topbrai...@googlegroups.com
Onderwerp: Re: [topbraid-users] linking images

 

Nothing in the core standards for this as far as I can see.

 

FWIW I don’t think I know of/never seen a customer project use any standard/public ontologies that publishes images for OWL classes they create, except of course in the HTML pages about an ontology. 

 

For example, Prov-O has a lot of nice pictures explaining the ontology but none are linked from the OWL itself - https://www.w3.org/TR/prov-o/#expanded-terms-figure is reached in this HTML source:

 <div id="starting-points-figure" style="text-align: center;" class="figure">

            <!-- When publishing to w3c: replace prov-o-diagrams/ with diagrams/ -->

            <!--img src="prov-o-diagrams/Starting-points-terms.png"-->

            <img src="diagrams/starting-points.svg" style="width: 60%; min-width: 25em; max-width: 60em" alt="PROV-O Starting Point terms">

            <div class="figcaption"><a href="#starting-points-figure">Figure 1</a>. 

            The three Starting Point classes and the properties that relate them.<br>

            The diagrams in this document depict Entities as yellow ovals,<br>

            Activities as blue rectangles, and Agents as orange pentagons.<br>

            The responsibility properties are shown in pink.

            </div>

      </div>

 

Anyway, just for fun I added rdfs:seeAlso to EDG owl:Class-defined properties and it works fine:

 

 

<image002.png>

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/5f78e08612584f7db4717c6571fe2d95%40tno.nl.

UK +44 (0) 7788 561308

US +1 (336) 283-0808‬

[Rob Atkinson]

I have had the same requirement - I added a new property "explanatory image" - and also "canonicalExample" for RDF instances matching the model and "implementationExample" for implementations of the model in other forms (such as XML)

We are using asciidocs and pyLode to generate documentation automatically from models via the SPARQL endpoint.  Still looking for automated (by default) diagramming options. -i.e. a shape that uses the 

Which brings us to a idea thats been floating around - how TQ users might share shapes that enable external OWL to be used within the EDG environment - since its obviously not scalable or appropriate to wait till TQ includes these in the core.  A "EDG model extension" pattern that can be SHACL validated to plug in a new ontology into an EDG environment seems like a good thing - anyone got such a thing already that can be shared? 

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/2549B348-532C-43F2-B417-BAEEC6D8637B%40topquadrant.com.

[Bohms, H.M. (Michel)]

Hi Rob

 

Is there some text missing after:

 

-i.e. a shape that uses the  …..

 

It would help me understand the actual broader issue you triggered (broader than just my need to have a standard link towards a jpg/png, less generic than seeAlso).

 

I am not understanding now how my simple technical issue ‘brings us to’ the broader issue wrt externel owl usage..

 

Thx michel

 

Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E michel...@tno.nl Location

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.

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

[Irene Polikoff]

RDFS and OWL define a few properties that are to be used to describe classes and properties e.g., RDFS:subClassOf for classes. These are available in EDG because RDFS/OWL defines this.

There are also properties like RDFS:label and comment that are traditionally used in ontologies. They are available in EDG for classes and properties because TopQuadrant added definitions (shapes) for them.

A given ontology may decide to use other properties when describing classes. For example, RDFS:seeAlso or SKOS:altLabel or my:canonicalExample. This is typically done without declaring that a given property will be used to describe a class and what it’s values should be. Such practice presents an issue for editing tools. Without definitions they can’t know what fields to make available for a given resource and what their values may be e.g., should this be a number, a string, HTML, image, link to another resource, etc.

When one loads an external ontology into EDG, they will be able to see values of such “undefined” properties, if they check the box for this option in the Form’s settings menu. However, they will not be able to edit the values - as no shapes exist for them.

To be able to create and edit values of these properties, there needs to be a shape defining them. Rob is asking if anyone already created some additional useful shapes for describing classes that they are willing to share.

On Jul 21, 2021, at 2:35 AM, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <topbrai...@googlegroups.com> wrote:



Hi Rob

 

Is there some text missing after:

 

-i.e. a shape that uses the  …..

 

It would help me understand the actual broader issue you triggered (broader than just my need to have a standard link towards a jpg/png, less generic than seeAlso).

 

I am not understanding now how my simple technical issue ‘brings us to’ the broader issue wrt externel owl usage..

 

Thx michel

 

Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E michel...@tno.nl Location

<image001.gif>

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/d3a9c6d900164c98ae702f589a6dcab0%40tno.nl.

[Rob Atkinson]

yes - sorry I managed to lose some text there.. I was going to refer to the edg:classDiagram view as a default image source but allowing it to be overridden with a custom version..

Irene is right - looking to see if there is a reusable solution out there,   

but also a question for TQ regarding possibilities for mechanisms for the user community to have a library of components we can share and draw - like the extensive plug-in managers and community marketplaces most IDEs and common platforms come with these days.  

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/4F538BE1-F0E6-4BAF-97BD-3A4C2FD52994%40topquadrant.com.

[Irene Polikoff]

We are considering hosting a Git repository for such extensions.

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