Publish ontology in link open data cloud?

[tillmo]

one can publish an ontology under a w3id URI using OnToology http://ontoology.linkeddata.es/

Here some slides with some screenshot about OnToology's features: https://www.slideshare.net/MariaPovedaVillalon/new-trends-in-ontological-engineering-practices-and-tools

[Ludee]

I just talked to the ontology experts of Uni Leipzig and they suggested OnToology as well. Happy to see that the issue already existed. Who will be responsible for this task? RLI? OvGU?

[p-kuckertz]

This issue has now also been assigned to me. Although I had a quick look in OnToology and now think I have a rough idea what it is about, I'm lacking the context - also about my involvement. What is the current status of this issue (and expectations, requirements)?

[Ludee]

We should evaluate and document pro and cons. As I understand it, this is important for Ontologies and LOD. The process seems quite simple:

How to use it

1. Enter your repo as user/repo i.e. myuser/myrepo (it does not work with organizations at the moment).
2. You will be redirected to Github to authorize OnToology to access your repo.
3. Update your ontology and push.
4. OnToology will create pull request including generated files (documentation, diagrams and evaluation)
5. Merge the pull request created by OnToology

Shall we do it already or wait for the first OEO release?

[p-kuckertz]

I don't yet get the connection to LOD. What exactly can OnToology do for us and how would we benefit? Maybe it makes sense to know that before implementing it?

[l-emele]

@Ludee @p-kuckertz : Any updates on this issue? Anything relevant for the next release or can we move this issue to an other milestone?

[l-emele]

@Ludee @p-kuckertz : Any updates on this issue? Anything relevant for the next release or can we move this issue to an other milestone?

@Ludee @tillmo : Any updates?

[l-emele]

@MGlauer @jannahastings : Do you anything about the state of this issue? Do we need it for the next release?

[jannahastings]

I don't have any update for this issue, but I think our release is not at all dependent on this issue. I don't think it will require any changes to the ontology (?) -- it is just a process of letting this other server know about the ontology. I recommend we postpone this until after the factsheets are represented, as that seems higher priority for our users.

[sfluegel05]

I'm not sure what we want to do with OnToology exactly. It provides a lot of services including documentation, visualization and evaluation. But the only thing we want to do is generating a w3id URI. Is that correct?

Also, we should look at the compatibility problems between the OEO and OnToology (see section Limitations at the bottom of this page):

• OnToology does not support OWL functional-style syntax
• OnToology does not support repositories under a Github organization

[jannahastings]

It seems to me that given the compatibility problems @sfluegel05 identified, we cannot use OnToology as suggested? Can the original requesters @tillmo @Ludee comment on how essential this is?

[Ludee]

There is a suggested workaround:

If you have an organization repository (or a repository that is not under your repository) you can fork that repository and add the fork url (your-username/the-repo-name).

If you wish I am picking out this issue and try it.

[Ludee]

I created a fork and tested the process: https://github.com/Ludee/ontology/tree/master/OnToology

While loading the OEO from the repo it throws an error. I think it is due the the multi module of the OEO. Loading only the oeo-physical doesn't work as well. I contacted the OnToology service to get more information.

[Ludee]

I got an answer to my questions:

• OnToology does not support OWL functional-style syntax

Regarding the functional-style, we are referring here to this syntax: https://www.w3.org/TR/owl-xmlsyntax/

• How do we deal with a multi module ontology?

There are two options. The easiest is to publish each ontology separately using OnToology. OnToology allows you to publish each ontology using w3id with a custom name. The second option provides more control, which is to publish the ontology on your server. OnToology allows you to download the bundle which contains the needed resources (e.g., documentation in html, diagrams, evaluation report). It also comes with .htaccess to help server the ontology using Apache.

[MGlauer]

The second option sounds more feasible for our needs as we publish on our own servers already. I do not understand the second part:

OnToology allows you to download the bundle which contains the needed resources (e.g., documentation in html, diagrams, evaluation report). It also comes with .htaccess to help server the ontology using Apache.

Is there more information on these materials and where to get them?

[Ludee]

I don't understand this part as well. As the OEO is already published on the OEP we should go with that option. Can you continue with the technical part @MGlauer I can send you the contact and mail exchange.

[MGlauer]

I can send you the contact and mail exchange.

Yes, please. As it stands right now, I would not know how to proceed.

[stap-m]

@MGlauer are there any updates on this issue?

[MGlauer]

Yes. Publication in OLS requires us to fill out a form. I will prepare the corresponding document and post it here.

[l-emele]

Yes. Publication in OLS requires us to fill out a form. I will prepare the corresponding document and post it here.

@MGlauer : It is now almost a year since your comment. Any progress?