Need to add a license field to metadata

[mmisw]

From [email protected] on July 27, 2009 15:57:36

Certain ontologies that have a known license type would benefit from a field
that allowed for the selection of open source / open content licenses. These
would likely come from an ontology, though it's unclear if one exists.

Original issue: http://code.google.com/p/mmisw/issues/detail?id=157

[mmisw]

From [email protected] on July 27, 2009 16:01:24

Labels: ontmd

[mmisw]

From [email protected] on August 25, 2009 17:04:10

See this thread: http://www.nabble.com/ontology-of-(open-source)-licenses--td25064877.html And also the following MMI emails:

On Tue, Aug 25, 2009 at 4:33 PM, Carlos Rueda carueda@xxx wrote:

1. Since you are also pointing out issues with some of the entries at dbpedia, we can
   gain some control by specifying our own list. And we can just collect the desired
   dbpedia license URIs. In the GUI, we can show a few selected properties for each
   entry (eg., dbpprop:abstract, dbpprop:reference, dbpprop:author).

BTW: how can one enter a new license entry in dbpedia? Should it be entered in http://en.wikipedia.org/wiki/Open_source_license (or some where else) and then
dbpedia will take it from there (sorry, I ignore the details)?

2. (on a more technical aspect) I note that OMV includes a hasLicense property with
   domain LicenseModel. http://ontoware.org/frs/download.php/663/OMV_v2.4.1.owl http://ontoware.org/frs/download.php/669/OMV-Reportv2.4.1.pdf (see also attached synopsis)
   The ontology already contains around 9 license instances, although with just a label.
   The list can of course be extended. If we continue with the idea of incorporating
   more OMV stuff into our framework, we should come up with some integration strategy.
   I will continue thinking about this, but your comments are welcome.

Carlos

On Fri, Aug 21, 2009 at 6:58 PM, John Graybeal graybeal@xxx wrote:

Stephanie,

Lots of interesting responses about open source licenses. In the end, I think we have two choices:

(1) use the list at http://dbpedia.org/class/yago/OpenSourceLicenses (using dbpedia URIs)

(2) make our own list

I'm inclined to go with (1) for now, notwithstanding the objections I raise about versioning and deprecation (see my mail below). What do you all think?

John

Status: NeedMoreInfo
Owner: carueda

[mmisw]

From [email protected] on August 31, 2009 15:38:05

(summarizing some more mmi emails:)

On Wed, Aug 26, 2009 at 10:18 AM, Carlos Rueda carueda@xxx wrote:
...

Ideally, we would only use the external resource (dbpedia licenses list) to create the drop-down list with options for our ontology submitters. Unfortunately, the dbpedia resource is lacking some of the entries already found and, perhaps worse, it has some entries that do not correspond to licenses per se (*).

An initial approach is just to have a list of the specific dbpedia licenses we want to offer in the GUI (**).

As a way to capture that list of selected dbpedia entries, I've added a new column "dbpedia link" in our "licences" spreadsheet http://spreadsheets.google.com/pub?key=thBpjuENRnAnkEXa6Y6i4EA&output=html So, we can continue updating the spreadsheet anyway (and with the dbpedia link where appropriate). With some help, we can try to include the missing licenses/tags in wikipedia so the dbpedia resource gets updated as John described.

My next task in this is to include the license property ( https://code.google.com/p/mmisw/issues/detail?id=157 ) and preparing the code to populate the associated drop-down list in the GUI.

(*) http://dbpedia.org/page/Creative_Commons_licenses is particularly curious; it is not a specific license but talks about the CC family of licenses. It's unclear how this entry can be applied.

(**) BTW, the user can use the drop-down list to select the license but also will be able to specify the license directly in the corresponding field.

Status: Started
Labels: portal

[carueda]

mmisw/orr-portal#93