Friday, February 01, 2008

OmegaWiki and licenses ... a thought

There are many dictionaries around and there is no real central place for them because they are under different licenses and some are proprietary.

There is an approach to so called authoritative databases which get connected to OmegaWiki, but in some way that is problematic since you don't see the whole stuff "together" - you need to go from the community "place" to the other one and vice versa to see if there are contents.

Like always when I do things in the house I have ideas and often can see things like a picture in my mind.

Bèrto is changing the architecture of the Database and we will have a new version, that is OmegaWiki 2.0.

The database design I saw is really easy to understand and so it is also easy to "imagine" new stuff.

Now the data within the community database is licensed under CC-BY and GFDL license - Francis (Apertium) just told me in the chat that there is a really good Friulan dictionary under GPL license. So why not include this into OW? I already hear you know: but that is GPL and with that not compatible ....

Well if I look at an expression page right now we have the lemma + the definition and sometimes various different definitions that are defined meanings. IMHO it would make sense to be able to see the contents that refer to that very same lemma from other dictionaries. The only thing needed is "tagging the entries as being part of this or that license" and therefore they are shown under a different header. You would have some thing:

Contents available under CC-BY and GFDL double license
Contents available under GFDL license
Contents available under GPL license

As long as we don't allow for the export of mixed licensed lists I don't see a problem, because the contents show up one after the other, like book titles. I am wondering if this fits in the actual database without the need to have separate ones where you then need to connect to ...

It is just a thought not really thought out well ... but there is something in there
...
Post a Comment