guidance on the use of prov:qualifiedAttribution on Dataset would be welcome

[NielsHoffmann]

This is a remark coming from the GeoDCAT-AP 3.0.0 pilot.

On the Dataset there are properties defined for (a.o.) publisher, custodian and contact point. The same information can also be provided using the qualifiedAttribution property, which recommends the use of the ResponsiblePartyRole codelist that contains those same values and more.

I appreciate the value of defining the most important roles as direct attributes. I do think it would be good to add an explanation to section 8.5 to clarify this and to clarify when to use wich option.

Since all of the above mentioned properties are optional in GeoDCAT-AP it creates room for multiple implementations and therefore makes it more difficult to search for these properties. (essentially needing to check both options for the presence of a publisher for example)