Formatters / DCAT-AP / Allow PO URI to be used for constraints.

[fxprunayre]

In DCAT-AP, the Publication Office vocabulary is used for license and the mapping was expecting ISO to encode original URI (eg. http://creativecommons.org/licenses/by/4.0/) and not PO ones (eg. http://publications.europa.eu/resource/authority/licence/CC_BY_4_0). So ISO record using PO URI was not returning the licence in DCAT-AP (and was in DCAT - because all licence URI are allowed).

The vocabulary is encoded with the following and skos:exactMatch was used for the mapping:

   <skos:Concept rdf:about="http://publications.europa.eu/resource/authority/licence/CC_BY_4_0"
                 at:deprecated="false">
...
      <skos:exactMatch rdf:resource="http://creativecommons.org/licenses/by/4.0/"/>

Adding also rdf:about to allow PO URI to be used in ISO record.

Eg. if

         <mri:resourceConstraints>
            <mco:MD_LegalConstraints>
               <mco:useConstraints>
                  <mco:MD_RestrictionCode codeList="http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml#MD_RestrictionCode"
                                          codeListValue="otherRestrictions"/>
               </mco:useConstraints>
               <mco:otherConstraints>
                  <gcx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/ConditionsApplyingToAccessAndUse/noConditionsApply">No conditions apply to access and use.</gcx:Anchor>
               </mco:otherConstraints>
            </mco:MD_LegalConstraints>
         </mri:resourceConstraints>
         <mri:resourceConstraints>
            <mco:MD_LegalConstraints>
               <mco:useConstraints>
                  <mco:MD_RestrictionCode codeList="http://standards.iso.org/iso/19115/resources/Codelists/cat/codelists.xml#MD_RestrictionCode"
                                          codeListValue="license"/>
               </mco:useConstraints>
               <mco:otherConstraints>
                  <gcx:Anchor xlink:href="http://publications.europa.eu/resource/authority/licence/BSL_1_0">BSL</gcx:Anchor>
               </mco:otherConstraints>
               <mco:otherConstraints>
                  <gcx:Anchor xlink:href="http://creativecommons.org/licenses/by/4.0/">Ces données sont disponibles sous licence CC-BY 4.0 (original).</gcx:Anchor>
               </mco:otherConstraints>
            </mco:MD_LegalConstraints>
         </mri:resourceConstraints>

DCAT (preserve all URI)

<dct:license>
<dct:LicenseDocument rdf:about="http://inspire.ec.europa.eu/metadata-codelist/ConditionsApplyingToAccessAndUse/noConditionsApply"/>
</dct:license>
<dct:license>
<dct:LicenseDocument rdf:about="http://publications.europa.eu/resource/authority/licence/BSL_1_0"/>
</dct:license>
<dct:license>
<dct:LicenseDocument rdf:about="http://creativecommons.org/licenses/by/4.0/"/>

DCAT-AP (only allow PO URI)

<dct:accessRights>
<dct:RightsStatement rdf:about="http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/noLimitations"/>
</dct:accessRights>
<dct:license>
<dct:LicenseDocument rdf:about="http://publications.europa.eu/resource/authority/licence/BSL_1_0"/>
</dct:license>
<dct:license>
<dct:LicenseDocument rdf:about="http://publications.europa.eu/resource/authority/licence/CC_BY_4_0"/>

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

Funded by Service Public de Wallonie

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[GeryNi]

Seems good !

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}