Resources

Resource properties

The following properties address R6, i.e. can help determine and/or resolve rights and access issues.

• identification of the IPR holder(s): resourceProvider, iprHolder
• identification of sources of potential need for restricted licences: personalDataIncluded, personalDataDetails, sensitiveDataIncluded, sensitiveDataDetails, anonymized, anonymizationDetails.

DatasetDistribution and SoftwareDistribution

These are subclasses of dcat:Distribution catering for the distict features of data and software resources, such as different distribution mediums (service or source code for software, content files or forms accessible via interfaces for data resources), descriptive features (size for text, audio, video, image files, technical requirements on the input / output of software).

Distribution properties

Properties of the Distribution subclasses include:

• linking to policy documents regulating the access conditions, addressing R1 and R1a: licenceTerms (see examples 1 - 6) and accessRights
• describing restrictions related to the billing module, time restrictions or membership to a group and addressing R4: cost, membershipInstitution, availabilityStartDate, availabilityEndDate. These are used in combination with the licenceTerms to refine licences with additional restrictions. (see examples 5 - 6).

The property licenceTerms addresses R1 and R1a. It is the property used for linking LRTs to the policy statements (class LicenceTerms) and it is mandatory in order to ensure legitimate access by end-users (see examples 1 - 5). Normally, each >Distribution must have one licence attached. Multiple licences are also possible for the same Distribution in the following cases:

• a data resource (e.g. a lexicon or corpus) which is accessible with an interface; in this case, the data and the interface may be available with different licences (see example 3)
• a collection composed of subsets released with different licences; for instance, a corpus or lexicon created with the same principles, but released with different conditions for different languages (see example 4).

In both cases, the access procedure must take into account all licences attached to this Distribution.

LRTs whose licence is not identified in the formal description may be included in a catalogue for information purposes only, clearly marked as such and described with at least an access statement which is added with the accessRights property.

Policies (Licences and Terms of use/service)

LicenceTerms

This class covers legal documents, i.e., licences and terms of use or service for data resources and software.

Licence properties

The following set of properties addresses identification of the licence and access to the licence text (R2 and R3) are:

The property conditionOfUse aims to encode the main conditions associated with the use of a LRT (e.g. non commercial use, use by academic users only, etc.) as described in R4a and R4b. These can also be represented as odrl properties (permission, prohibition, duty), but are also added as an object property for two reasons: (a) facilitating LRT providers with no or little prior experience of writing policies in ODRL; (b) supporting the implementation of a filter enhancing the discoverability of LRTs in a catalogue (R3). The class ConditionOfUse contains a set of instances that are typical of licences in the LRT domain.

The object property licenceCategory addresses R4; i.e., it supports the encoding of terms that can be mapped to actions granting access to LRTs and the authorization procedures required for them. As with conditionOfUse, these can be mapped to ODRL rules and added to the RDF representations of a licence.

A set of such mappings has already been made for the typical cases in the LRT domain and is available below.

Parties

Party roles and types

With respect to the transactions of LRT distribution, the following roles can be identified:

• Resource providers
• Resource consumers (end users)
• Hosting/Distributing entities.

For the scope of the current profile, these roles do not need to be formally represented, as the ODRL roles odrl:assigner and odrl:assignee suffice.

In terms of legal status, distributing entities can only be organizations, resource providers can be both organizations and individuals, while resource consumers can be only individuals, affiliated or not to organizations. These can be described with any relevant vocabulary such as W3C vCard Ontology, FOAF Vocabulary enriched with META-SHARE and ODRL properties, as required.

Party properties

The only property specific to this profile is the userType, which distinguishes LRT consumers into commercial and academic ones. This is required because this distinction is related to restrictions on using an LRT or on the price or billing model of an LRT.

Actions

Operations

To cover the operations performed in the context of this profile, the following concepts are used from the ODRL and META-SHARE vocabularies: odrl:execute, odrl:Aggregate, ms:Download, ms:Process and ms:Combine.

Actions for Constraints

The following subclasses of odrl:Action are required in use with constraints on rules to describe common practices in the domain of LRT distribution: SignIn, Authorize, SignLicence, Report, Deposit.

Examples

Examples of LRTs

ex:Resource1 a ms:Corpus ;
  ms:distribution 
    [ ms:datasetDistributionForm ms:downloadable 
      dct:license <http://purl.org/NET/rdflicense/cc-by4.0>
    ]

					
ex:Resource1 a ms:Corpus ;
  ms:distribution 
    [ ms:datasetDistributionForm ms:downloadable ;
      dct:license <http://purl.org/NET/rdflicense/cc-by4.0>
    ]
  ms:distribution 
    [ ms:datasetDistributionForm ms:accessibleWithInterface ; 
      dct:license <http://purl.org/NET/rdflicense/cc-by4.0>
    ]

	
ex:Resource1 a ms:ToolService ;
  ms:distribution 
    [ ms:softwareDistributionForm ms:webservice ;
      dct:license <http://rdflicense.appspot.com/rdflicense/cc-by4.0.ttl> ;
      dct:license <http://purl.org/NET/rdflicense/APACHE2.0.ttl>
    ]

ex:Resource1 a ms:Corpus ;
  ms:distribution 
    [ ms:datasetDistributionForm ms:downloadable ;
      dct:license <http://rdflicense.appspot.com/rdflicense/cc-by4.0.ttl> ;
      dct:license <http://rdflicense.appspot.com/rdflicense/cc-by-nc-4.0.ttl>
    ]

    
ex:Resource1 a ms:Corpus ;
  ms:distribution 
    [ ms:datasetDistributionForm ms:downloadable ;
      dct:license < http://rdflicense.appspot.com/rdflicense/elra-end-user.ttl> ; 
      ms:userType ms:academic
    ]
    [ ms:datasetDistributionForm ms:downloadable ;
      dct:license < http://rdflicense.appspot.com/rdflicense/elra-end-user.ttl> ; 
      ms:cost [ 
      ms:amount "10000" ; 
      ms:currency ms:euro
      ]
      ms:userType ms:commercial
    ] 

ex:Resource1 a ms:Corpus ;
  ms:distribution 
    [ ms:datasetDistributionForm ms:downloadable ;
      dct:license <http://purl.org/NET/rdflicense/cc-by4.0> ;
      ms:availabilityStartDate "2021-06-30"
    ] .

Examples of Licences

<http://purl.org/NET/rdflicense/ilsp/CC0-1.0>
  a odrl:Policy ;
  rdfs:label "Creative Commons Zero v1.0 Universal" ;
  dct:source <https://creativecommons.org/publicdomain/zero/1.0/legalcode> ;
  dct:language <http://www.lexvo.org/page/iso639-3/eng> ;
  dct:identifier "CC0-1.0" ;
  rdfs:seeAlso <http://spdx.org/licenses/CC0-1.0> ;
  ms:licenceCategory ms:allowsDirectAccess ;
  ms:licenceCategory ms:allowsProcessing ;
  ms:conditionOfUse ms:noConditions ;
  odrl:permission [
          a odrl:Permission ;
          odrl:action ms:download , odrl:execute , ms:process, odrl:aggregate 
  ] .

 <http://purl.org/NET/rdflicense/elra-var>
  a odrl:Policy ;
  rdfs:label " LANGUAGE RESOURCES VALUE-ADDED-RESELLER AGREEMENT" ;
  dct:source <http://www.elda.org/media/filer_public/2014/08/01/var_140312.pdf> ;
  dct:language <http://www.lexvo.org/page/iso639-3/eng> ;
  ms:conditionOfUse ms:noRedistribution , ms:languageEngineeringResearch , ms:spatialConstraint , cc:Attribution ;
  ms:licenceCategory ms:allowsAccessWithSignature ;
  ms:licenceCategory ms:requiresUserAuthentication ;
  ms:licenceCategory ms:allowsProcessing ;
  odrl:permission [
          a odrl:Permission ;
          odrl:action ms:download , ms:process, ms:execute, odrl:aggregate, ms:combine ;
                odrl:constraint
                        [ a odrl:Constraint ;
                          odrl:operator odrl:eq ;
                          odrl:spatial "only at assignee's site"
                        ] ;
                        [ a odrl:Constraint ;
                          odrl:operator odrl:eq ;
                          odrl:purpose ms:languageEngineeringResearch
                        ] ;
                        [ a odrl:Constraint ;
                          odrl:operator odrl:eq ;
                          odrl:assignee ms:sign
              ] ;
                        [ a odrl:Constraint ;
                          odrl:operator odrl:eq ;
                          odrl:assignee ms:signIn
                        ] 
                odrl:duty
                        [ odrl:action cc:Attribution
                        ] 
    ] ;
  odrl:prohibition
              [ odrl:action cc:Distribution
              ] . 

<http://purl.org/NET/rdflicense/ilsp/ms-c-nored>
  a odrl:Policy ;
  rdfs:label "META-SHARE Commercial NoRedistribution" ;
  dct:source <http://www.meta-net.eu/meta-share/meta-share-licenses/META-SHARE%20Commercial%20%20NoRedistribution_v0%207.pdf> ;
  ms:conditionOfUse ms:noRedistribution , ms:languageEngineeringResearch , ms:attribution ;
  ms:licenceCategory ms:requiresUserAuthorization ;
  ms:licenceCategory ms:allowsProcessing ;
  odrl:permission [
          a odrl:Permission ;
          odrl:action ms:download , ms:process, ms:execute, odrl:aggregate, ms:combine ;
                odrl:constraint
                        [ a       odrl:Constraint ;
                          odrl:operator odrl:eq ;
                          odrl:spatial "only at assignee's site"
                        ] ;
                odrl:constraint
                        [ a       odrl:Constraint ;
                          odrl:operator odrl:eq ;
                          odrl:purpose ms:languageEngineeringResearch
                        ] ;
                odrl:constraint
                        [ a odrl:Constraint ;
                          odrl:operator odrl:eq ;
                          odrl:assignee ms:authorize
                        ] ;
                odrl:duty
                        [ odrl:action cc:Attribution
                        ] 
              ] ;
  ] ;
  odrl:prohibition
              [ odrl:action cc:Distribution
              ] .

Processing

of 0 - 100 characters per day: the user has to pay 10 USD;

from 101 - 500 chars per day: 50 USD


[]   a odrl:Duty;
     odrl:action   [
              a md:Compensate ;
odrl:payAmount    10.00 ;
             odrl:unit         <https://www.wikidata.org/wiki/Q4917> ;  # USD
             odrl:unitOfCount  [ a ms:Character ] ;
             odrl:refinement [ 
      odrl:operator odrl:lt ;
      odrl:count 100 ;
      odrl:meteredTime odrl:lteq ";P1D&"
] 
           ] , [
              a                md:Compensate ;
odrl:payAmount    50.00 ;
             odrl:unit         <https://www.wikidata.org/wiki/Q4917> ;  # USD
             odrl:unitOfCount  [ a ms:Character ] ;
             odrl:refinement [ 
      odrl:operator odrl:gt ;
      odrl:count 100 ;
      odrl:meteredTime odrl:lteq "P1D"
], [
      odrl:operator odrl:lt ;
      odrl:count 500 ;
      odrl:meteredTime odrl:lteq "P1D"
]
           ]
 .

Execution of service for up to 100 characters per day

[]   a odrl:Permission ;
     odrl:action   [
              a odrl:execute ;
             odrl:unitOfCount  [ a ms:Character ] ;
             odrl:refinement [ 
			odrl:operator odrl:lt ;
 			odrl:count 100 ;
			odrl:meteredTime odrl:lteq "P1D"
      ]   
]  .

Execution of service for up to 100 characters per day

Execution of service for up to 100 API calls and up to 10 GB of processing volume per day
[]   a odrl:Permission ;
     odrl:action   [
              a odrl:execute ;
             odrl:unitOfCount  [ a ms:apiCall ] ;
             odrl:refinement [ 
			odrl:operator odrl:lt ;
 			odrl:count 100 ;
			odrl:meteredTime odrl:lteq "P1D"
 ] ;
             odrl:unitOfCount  [ a ms:processedGB ] ;
             odrl:refinement [ 
			odrl:operator odrl:lt ;
 			odrl:count 10 ;
			odrl:meteredTime odrl:lteq "P1D"
 ] 
]  .

Acknowledgements

This work has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No 825182: Prêt-à-LLOD and the COST Action "Nexus Linguarum" (CA18209)

A service supporting the transformation of XML files of licences into ODRL policies was developed in Athens in July 2021 by the Institute for Language and Speech Processing (Athena RC) and the Ontology Engineering Group (Universidad Politécnica de Madrid) available at https://rdflicense.linkeddata.es/service.html and as an API at https://rdflicense.linkeddata.es/swagger-ui.html

A. User requirements

User requirements on LRT hosting/distributing entities from LRT providers

UR1. As an LRT provider, I want to make available my LRT with a licence

UR2. As an LRT provider, I want to make available different forms of my LRT with different licences.

UR3. As an LRT provider, I want to be able to release my LRT with a custom licence that includes access restrictions.

UR4. As a provider of a commercial LT, I want to limit access to my service based on a count of specific units (e.g., count of API requests, characters to be processed, audio/video seconds to be processed) for a limited time period (e.g., on a weekly basis)

UR5. As a provider of a commercial LT, I want to give access to my service with a billing model that takes into account counts (cf. R4).

User requirements on LRT hosting/distributing entities from LRT consumers

UR6. As an LRT consumer, I want to search for LRTs based on their licences.

UR7. As an LRT consumer, I want to search for LRTs based on broad usage conditions.

UR8. As an LRT consumer, I want to obtain access to (use, deploy, process, download, …) an LRT

UR9. As an LRT consumer, I want to view the licence of an LRT.

UR10. As an LRT consumer, I want to be able to combine LRTs.

User requirements of LRT hosting/distributing entities

UR11. As a distributing entity, I want to give access to LRTs and impose restrictions based on their licensing conditions

a. allow users to download/access/consume data resources/services/tools with permissive licences without any interaction

b. give access to authorized users only for LRTs requiring authorization

c. enforce signature to users before getting access to a resource/service for licences that require signature

d. enforce conditions stemming from multiple licences on the same distribution (e.g. combination of software & data)

e. give access to authenticated users only for LRTs requiring authentication

f. I want to support a billing module that takes into account reductions / restrictions for members of a group

UR12. As a distributing entity, I want to monitor the use of LT processing services in order to limit or bill users when accessing them

UR13. As a distributing entity, I want to support LRT providers in attaching a single or multiple licences on distributions of LRTs

UR14. As a distributing entity, I want to ask the providers to describe the conditions of use for the new licences

UR15. As a distributing entity, I want to have information that may affect its licence (e.g. inclusion of non-anonymized sensitive data)

UR16. As a distributing entity, I want to know the usage conditions under which a LRT is released, preferably in a machine readable form.

UR17. As a distributing entity, I want to aggregate the set of licences of multiple data resources into one set of licences for a collection or attach a single licence on a collection of resources

B. Dataset of licences

To facilitate providers of LRTs, a set of licences in ODRL is available at ? in the form of three interpretations:

• following this profile targeting entities responsible for granting access to LRTs
• by the entity that has originally published the licences targeting end-users
• as interpreted by dallic, targeting end-users.

The META-SHARE interpretation of licences includes the SPDX identifier, thus linking the licences to the official SPDX License List. The SPDX License List includes a standardized short identifier, full name, vetted license text including matching guidelines markup as appropriate, and a canonical permanent URL for each license and exception; it is available at the spdx github in various serialization formats.

The META-SHARE set of licences includes representations for popular licences in the domain of LRTs, both standard ones, such as Creative Commons, but also standard licences created specifically for the distribution of LRTs, namely ELRA, META-SHARE and CLARIN licences.

C. Mappings for transformation of META-SHARE elements to ODRL policies

Mappings for condition of use

Mappings for licence category

The first two values of the licence category (allowsDirectAccess & allowsProcessing) specify the types of actions that the distributing entity may perform, while the other values refine the constraints on which these actions are performed.