Curation/Normalisation of licensing information

• What?
  • Curation/Normalisation of licensing information
• Who?
  • Menzo, Oddrun, Twan, Matej
• When?
  • 2017-06-28, 10.00 - 11.00 CEST
• Where?
  • Google Hangouts: ​https://hangouts.google.com/call/u5u6nb5abbc53ismfed5emby6ae

Documents

• ​CLARINO-licence overview .gsheet
  • created by Gunn Inger Lyse and ?,
  • presented at LREC 2014
  • used by COMEDI

• ​LicenseAvailabilityMap.gsheet
  • extracted from the records in VLO
  • reviewed by Kirster and Penny, mapping
  • used as basis for the normalisation map applied currently in VLO: ​https://github.com/clarin-eric/VLO-mapping/tree/master/uniform-maps ​https://github.com/clarin-eric/VLO-mapping/blob/master/uniform-maps/LicenseAvailabilityMap.xml

• wiki-page: Taskforces/Curation/ValueNormalization/License
  • older information on Curation of the Licensing information

Older draft attempts:

• ​Notes on Curation of License/Availability facets from CAC 2015, Wroclaw
• ​License/Availability - profile coverage.gsheet (status 2016-02)
• ​License / Availability Facets Analysis (2016-12)

Notes

CLARINO overview is comprehensive consolidated overview of the various licensing, refined also by the "secondary licensing laundry tags". Thus it is a good (the best) candidate to become the licenses-vocabulary for CLARIN and be correspondingly maintained in CLAVAS.

Issues

• Ownership
  Oddrun: CLARINO not being funded in the next period, we will not have the capacities for assuming the ownership, thus willing to hand over

• Identifiers
  reuse the (canonic) URLs for the licenses, or assign own handles? Oftentimes there are no stable, reliable URLs for individual licenses. Own handles would allow another layer of indirection, which is under our control. Still pointing to (possibly various) representations of the Licenses via rdf:seeAlso or similar.

examples:

https://creativecommons.org/licenses/by-nc/4.0/
https://kitwiki.csc.fi/twiki/bin/view/FinCLARIN/ClarinEula?ACA=1&ID=1&AFFIL=EDU&BY=1&LOC=1&NORED=1&DEP=1	
http://www.gnu.org/licenses/fdl.html

• Modelling laundry tags
  If each license is represented as a skos:Concept, how to express the additional information about the licenses, especially the laundry tags (and license family) options:
  • additional RDF properties (OpenSKOS supports any RDF-properties beyond SKOS) (Does appropriate vocabulary exist, or do we have to come up with custom one?)
    • Note Twan: The ​Creative Commons Rights Expression Language might serve as a basis and/or inspiration (also used by e.g. Europeana for EDM)
  • as separate skos:Concepts in own skos:ConceptScheme "License categories" and skos:related between the license- and category concepts

Action points

• update the Analysis of the data in VLO
• compare and match ​CLARINO-licence overview against ​LicenseAvailabilityMap
• Decide how to model the information about licenses in CLAVAS (RDF)
• arrange another video-conf end of August

[primarily on Matej & co., soliciting feedback, support from Menzo, Oddrun, Gunn Inger, CLIC etc. as needed]

• test-import the licenses into CLAVAS [Menzo]

=> aiming for Annual meeting as milestone to present (ideally):

• the vocabulary
• it's integration in the Component Registry
• harmonized VLO-mappings and representation of licensing information in the records detail view