GeoDCAT-AP [PR]: Use of dct:licenses and dct:accessRights

References

This issue has been reported by Antoine Isaac.

http://joinup.ec.europa.eu/mailman/archives/dcat_application_profile-geo/2015-August/000191.html

 

Explanation

Draft 6 of the GeoDCAT-AP specification uses dct:license and dct:accessRights instead of dct:rights. But the example that is in the annex II.15, is closer to the GNU example in that is in the DC guide.

[

[] dcat:distribution [ a dcat:Distribution ;

        dct:license [ a dct:LicenseDocument ;

            rdfs:label "Reuse is authorised according to the European Commission legal notice at http://ec.europa.eu/geninfo/legal_notices_en.htm"@en ] ;

        dct:accessRights [ a dct:RightsStatement ;

            rdfs:label "no limitation"@en ] ] .

]

Antoine points out that the object of dct:license in the example could rather be the object of a (more general) dct:rights statement. In case of using dct:license with an instance of dct:LicenseDocument, it could have been written:

[

[] dcat:distribution [ a dcat:Distribution ;

dct:license <http://ec.europa.eu/geninfo/legal_notices_en.htm> ;

          ]

]

 

The GeoDCAT-AP proposal is related to the reference standard. ISO defines different types of constraints, distinguishing between access and use. Dublin Core does something similar with dct:license and dct:accessRights, whereas dct:rights (super-property of both) covers both access and use.

It is going to be discussed how to proceed with the example provided in the GeoDCAT-AP specifications, as it could be unclear. However, the corresponding "element" in ISO uses free text. Therefore, the example reflects what it could be obtained when transforming an ISO record into a (Geo)DCAT-AP one.

In addition, the ISO schema allows URLs, and some data providers are currently using this feature to provide the link to the licence document. Thus, the GeoDCAT-AP WG considered this option in the GeoDCAT-AP XSLT, i.e. when a licence URL is specified, this is used as the URI of the licence document.

The XSLT documentation has a specific section on this ("Use conditions / licence URI"). It is also meant to collect and elaborate common / best practices for the use of HTTP URIs in geospatial metadata, not limited to licences, which might be addressed also by the SDW WG.

Component

Documentation

Category

improvement

Comments

Mon, 14/09/2015 - 21:47

Tue, 13/10/2015 - 06:40

Hi,

The solution is not really clear to me, but it seems that's probably the best you can do, so I'm fine with it!

Antoine

Tue, 22/12/2015 - 07:52

In GeoDCAT-AP Draft 7, both the representation of licence as a blank note and as a URI are provided. A note was added stating that minting URIs for licence documents is a recommended good practice.

 

# Resource metadata in GeoDCAT-AP

 

[] dcat:distribution [ a dcat:Distribution ;

     dct:license [ a dct:LicenseDocument ;

       rdfs:label "Reuse is authorised according to the European Commission legal notice at

                   http://ec.europa.eu/geninfo/legal_notices_en.htm"@en ] ;

     dct:accessRights [ a dct:RightsStatement ;

       rdfs:label "no limitation"@en ] ] .

 

# Resource metadata in GeoDCAT-AP (using URI for the licence)

 

[] dcat:distribution [ a dcat:Distribution ;

     dct:license <http://ec.europa.eu/geninfo/legal_notices_en.htm&gt; ;

     dct:accessRights [ a dct:RightsStatement ;

       rdfs:label "no limitation"@en ] ] .

The content of this field is kept private and will not be shown publicly.