Under which license is released?

[EmidioStani]

The tool under which license is released?

[floresbakker]

Also here: I have to dive deeper into the license structure. It is meant as open source but I have to get back to you on the exact license structure. Can you inform me on how you intend to use OntoReSpec?

[EmidioStani]

I am creating simply a catalogue of open source tools for semantic engineers,

[floresbakker]

Ok! When I create a release for this repository, I will also make clear the license situation.

[rmfranken]

👀 I'm also interested in trying out your tool. We have a similar one, but this looks better! https://github.com/sdsc-ordes/respecter

We want to use these tools for publishing ontologies for clients - all open source.

[floresbakker]

👀 I'm also interested in trying out your tool. We have a similar one, but this looks better! https://github.com/sdsc-ordes/respecter

We want to use these tools for publishing ontologies for clients - all open source.

That is nice to hear! It encourages me to make it even better. You can see here an example of a generated OntoReSpec document:

https://floresbakker.github.io/htmlvoc/

The extra bonus is that not only you get a HTML file, you also get a RDF file containing a representation of the HTML file, modeling every atom and aspect of it in Linked Data.

[rmfranken]

I'm happy to dive deeper, and perhaps see if parts of the code in our own tools can be contributed here, but the lack of license does put me off. If I fall in love with your tool I might not be able legally use it! 😄

[floresbakker]

Decided to go with CC-BY. Unorthodox for software, yet OntoReSpec is 95% a datamodel in RDF (executable through a SHACL engine) so that makes sense after all, I believe.

[EmidioStani]

I think you can split the license for the models (cc-by is generally adopted) and that one for the tools

[floresbakker]

How do you split a license within a repository?

[EmidioStani]

Simply place one in each folder and in the Readme.md just put a summary