Formatter / DCAT improvements forllowing HVD reporting

[fxprunayre]

Formatter / DCAT / EU / Fix conformsTo URI for DCAT-AP and add legislations.

Formatter / DCAT / Use relation API to populates link

Adds:

• dcat:inSeries
• dcat:seriesMember
• dct:relation
• dct:source
• dct:references
• dct:servcesDataset

Formatter / DCAT / Service / Endpoint description can also be a link with function information.

Formatter / DCAT / Distribution

• Add support for DQ spec and report reference as foaf:page
• Fix when function is not defined or empty
• Add modified date based on resource revision
• Add dcat:mediaType
• Copy resource language
• Case insensitive matching of format

Formatter / DCAT / Avoid to generate URI not starting with http (which will be RDF invalid). Add missing match on online resource name and DQ citation link.

Formatter / DCAT / EU publication file type expect http URI not https. Also add additional iana types.

Formatter / DCAT / Limit dcat:theme element to EU data themes. Keywords are encoded using dct:subject if with Anchor and dcat:keyword for label.

Formatter / DCAT / EU validator complains about this.

Formatter / DCAT / Add ADMS license type and EU access rights.

• Based on license URL add corresponding ADMS type
• Based on accessConstraint type add EU access type

<dct:LicenseDocument rdf:about="https://creativecommons.org/licenses/by-sa/2.0">
    <dct:type>
       <skos:Concept rdf:about="http://purl.org/adms/licencetype/ViralEffect-ShareAlike">
          <skos:prefLabel xml:lang="en">Viral effect (a.k.a. Share-alike)</skos:prefLabel>
          <skos:notation>ViralEffect-ShareAlike</skos:notation>
          <skos:inScheme rdf:resource="http://purl.org/adms/licencetype/1.0"/>
       </skos:Concept>
    </dct:type>
    <dct:type>
       <skos:Concept rdf:about="http://purl.org/adms/licencetype/Attribution">
          <skos:notation>Attribution</skos:notation>
          <skos:prefLabel xml:lang="en">Attribution</skos:prefLabel>
          <skos:inScheme rdf:resource="http://purl.org/adms/licencetype/1.0"/>
       </skos:Concept>
    </dct:type>
 </dct:LicenseDocument>
</dct:license>

<dct:accessRights>
 <dct:RightsStatement rdf:about="http://publications.europa.eu/resource/authority/access-right/PUBLIC"/>
</dct:accessRights>

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

[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.}