License/Availability

Currently, VLO features two facets License and Availability

There seems to be a lot of confusion what the two facets should contain.

Facet/Concept Definitions

The two facets and their descriptions/definitions as stated in the ​facetConcepts.xml mapping file

facet	description	definition
availability	The usage conditions for the resource or tool	A rough description of the conditions under which the resource or tool can be used
license	The licensing conditions for the resource or tool	The name of the license or a very brief description of the licensing conditions under which the resource or tool can be used

Concept Links

		used for facet
prefLabel (CCR)	Isocat	Availability	Licence	comment in facetConcepts.xml	CCR definition
​license	​DC-2457	yes	yes	A description of the licensing conditions	A description of the licensing conditions under which the resource can be used. (source: CLARIN)
​availability	​DC-2453	yes	yes	A description of the terms of availability of the resource in simple words	A description of the terms of availability of the resource in simple words. (source: CLARIN)
​licence type	​DC-3800	yes	yes	licenceType: Indication of the type of a copyright licence	Indication of the type of a copyright licence. (source: NaLiDa)
​rights	​DC-6846	(yes) - only isocat link	(yes) - only isocat link	DASISH from DC Rights	Any rights information for this resource. (source: DASISH)
​license type	​DC-5439	yes	no (commented out)	The DC is used in the distributionType facet	A rights-based classification of language resources and tools, indicating the scope of the target audience (source: CLARIN Deliverable: D7S-2.1, "A report including Model Licensing Templates and Authorization and Authentication Scheme")
	​dcterms:license	no (commented out)	no (commented out)

Normalization of values

There is already a ​normalisation map used in production (committed 2015-04-23). But there are new values that are not mapped yet. ​Normalisation map as gsheet with already existing mappings (see normalisation map above) + new values encountered not yet normalized;
Values come from elements annotated with concepts linked to one of the two facets License/Availability.

See also the ​license categories as proposed by the Legal Issues Committee.

Missing values

Curently all the mapped concepts only cover around 60.000 records! ​Records with missing value for availability

Following profiles miss a value for availability facet:

Song (155403)
OLAC-DcmiTerms (142192)
imdi-profile-instance (88954)
teiHeader (82936)
mods (64629)
ArthurianFiction (59393)
DcmiTerms (46160)
SongScan (28448)
media-session-profile (23579)
SourceScan (21256)
Source (16519)
imdi-corpus (14693)
IDSAGD_Speaker (7997)
SongAudio (7961)
IDSAGD_Event (7710)
SymbolicMusicNotation (7557)
LCC_DataProviderProfile (6497)
Text (4417)
Performer (1530)
DiscAn_Case (1456)
Etstoel (998)
OLAC-DcmiTerms-ref-DWR (775)
OLAC-DcmiTerms-ref (656)
GTRP_sub_location (613)
JacobsstafVerhaal (583)
GBA-derived_sub_municipality (443)
Communication_Transcript (399)
ToponymProfile (399)
Communication_Recording (397)
DGDEvent (392)
DIDDD_sub_location (333)
DynaSAND_sub_location (267)
WebLichtWebService (247)
UserSubmission (161)
singlePaperPackage (108)
CRM (95)
LINDAT_CLARIN (91)
Fesli (55)
GBA-derived_sub_coroparea (40)
PhotoSinger (38)
LCC_CorpusProfile (35)
EMITX (29)
wnd_subcollection_core_data (28)
GBA-derived_sub_dialectarea (24)
TextCorpusProfile (23)
resourceInfo (20)
VK-book (19)
GBA-derived_sub_province (12)
DiscAn_TextCorpus (9)
ExperimentProfile (9)
IDSAGD_Corpus (8)
corpusProfile (5)
VirtualCollection (3)
ResourceBundle (2)
lexicalProfile (2)
BASWebService (1)
CRMCollection (1)
CenterProfile (1)
DGDCorpus (1)
EtstoelCollection (1)
FesliCollection (1)
GBA-derived (1)
GTRP (1)
LiteraryCorpusProfileML (1)
Soundbites (1)
ToolProfile (1)
ToolService (1)
VK-semantic (1)
WBD (1)
WLD (1)
Website (1)