Hi Bert,
in Italy we created a license vocabulary (reusing part of the controlled vocabulary mentioned in the current DCAT-AP specifications). The licenses we included are those currently used in the Italian open data catalogues we harvest.
You can find the vocabulary here: https://github.com/italia/daf-ontologie-vocabolari-controllati/tree/master/VocabolariControllati/Licenze (there are labels in ITA, ENG, DEU, FRA).

@bertvannuffelen The same issue was brought up on Joinup a year ago.
The ODI's Open Data Rights Statement Vocabulary has two properties, attributionText and attributionURL that could be used.
As to the fee, I remember a discussion on that issue during the development of DCAT-AP where it was decided that paid-for datasets were out of scope. An existing approach is available at schema.org which does not make price a property of a resource, but connects the resource and its price through an intermediate entity Offer.
The Working Group should discuss whether attribution text and price specification are to be considered for a future version of DCAT-AP

@giorgialodi, thanks for the pointer.
@makxdekkers: this is an interesting reference. I found in https://creativecommons.org/ns a vocabulary however the cc:attributionName is associated with work and not with the license as a clause.
I have a look to the ODRS to see if this matches better our intentions.

kr
Bert

Germany did just the same as Italy (http://www.dcat-ap.de/def/licenses/). Maybe an indicator that such a thing could be useful on the European level.
The German application profile also introduced licenseAttributionByText as a property of the distribution. Personally, I feel that something like a Rights Statement (ODRS) - as a resource that describes the relationship between a Dataset and its Licence(s), and is also used to describe additional contextual information that applies to the re-use of a dataset - is the way forward.

There is also an Licence NAL at the Publications Office: http://publications.europa.eu/mdr/authority/licence/. There is currently no link to this NAL in DCAT-AP v1.1, but it could be included in a new version.

Proposed resolution | No change.

No change. Note discussion at DXWG, see: w3c/dxwg#114