chore(deps): update dependency ckan/ckanext-dcat to v2

[renovate]

This PR contains the following updates:

Package	Update	Change
ckan/ckanext-dcat	major	1.7.0 → 2.4.3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

ckan/ckanext-dcat (ckan/ckanext-dcat)

v2.4.3

Compare Source

• Python 3.14 support (#​377)
• Fix version property on DCAT AP v3 (owl.versionInfo -> dcat.version) (#​378)
• Support multiple temporal coverage periods (#​375)
• Fix ontology for adms:status (#​364)
• Fix translation for contact name (#​367)
• Fix Croissant helper chaining (#​366)

v2.4.2

Compare Source

• Improve handling of multilingual properties in Agent properties (#​360)
• Fix AttributeError on CKAN 2.12 (#​363)

v2.4.1

Compare Source

• Fix regression redirect from /dataset to /dataset_series (#​362)
• Provide default language in Croissant JSON-LD context (#​361)
• Added IDCATURIGenerator
  plugin interface to allow customization of the URIs generation (#​351)
• Added support for new fields to DCAT classes: dcat:Dataset (prov:wasGeneratedBy, prov:qualifiedAttribution,
  dcat:hasVersion), dcat:Catalog (foaf:homepage), dcat:DataService (dct:conformsTo, dct:format,
  dct:identifier, dct:language, dct:rights, dcat:landingPage, dcat:keyword) (#​352)
• Add HealthDCAT-AP mapping to CKAN field mapping table (#​347)
• Docs: Add HealthDCAT-AP mapping to CKAN field mapping table (#​347)

v2.4.0

Compare Source

• Add support for Dataset Series via integration with ckanext-dataset-series.
  Ckanext-dataset-series takes care of all the underlying management of the series, and ckanext-dcat exposes them
  using dcat:DatasetSeries classes. Check the documentation for all details on how to set them up.
• Add trusted_data_holder field to HealthDCAT-AP schema (#​345)
• Fix TIME namespace definition to include trailing hash (#), ensuring compliance with W3C Time Ontology and DCAT-AP. This may require updates for custom profiles relying on the old variant. (#​344)
• Add missing URIRefOrLiteral import in profiles module. (#​343)

v2.3.0

Compare Source

• New profile to support the Croissant format.
  Croissant is a community standard for describing ML datasets. The new croissant plugin allows a CKAN site to
  expose its datasets using the Croissant format specification. Check the documentation for more information on schema mapping, features supported and examples. Thanks to @​Reikyo for their contributions (#​339, #​341)
• Fix has_version in HealthDCAT schema (#​336)
• Include dependencies in pyproject.toml, publish extension on PyPI. This means that starting from ckanext-dcat 2.3.0 the extension can be installed by running:

    pip install ckanext-dcat
  

  The requirements files (requirements.txt and dev-requirements.txt) have been kept in place, so all
  existing installation workflows should keep working.

v2.2.0

Compare Source

• New profile for the HealthDCAT-AP application profile. Check the
  documentation for all details. Thanks to folks at Health-RI for the contribution
  (#​326)
• Support for Qualified relations at the dcat:Dataset level in all DCAT base profiles (97ca441)
• Fix parsing of spatial properties when using scheming (#​327)
• Add VCARD.hasURL property parsing/serialization (#​324)
• Support for rdflib 7.2 (date parsing) (#​323)
• Fix: Move has version from distribution to dataset (#​322)
• Decouple dcat and structured_data plugins (#​329)

v2.1.0

Compare Source

• New base profile for the DCAT US v3 specification.
  All mandatory properties and most of the recommended and optional ones are supported. During the
  implementation of this work a few adjustments have been done to the base DCAT profile (#​314) :

  • Support for temporal and spatial resolutions in distributions, which were missing on the DCAT AP profiles
  • Allow multiple values for dct:creator in DCAT AP

• Multilingual support in DCAT profiles. Multilingual support is provided via integration
  with ckanext-fluent. Check the documentation for full details (#​318)

• At the serialization level, a new triple will be added for each of the defined languages

• Support for multiple agents when parsing (#​317)

• Improve serialization of statements, using RDFS.label in line with the DCAT 3 spec recommendation (#​313)

• Store UIDs from contact clases (#​312)

• Fix input issues for access_rights field (#​309)

• Add has_version to the full DCAT AP schema (#​306)

• Add pyproject.toml file (#​304)

• Decouple extension from ckanext-scheming (#​303)

• Add support for dct:creator in base DCAT profiles (#​302)

• Fix DCAT date validator on empty values (#​297)

• Add support for hydra collection type PartialCollectionView (#​299)

v2.0.0

Compare Source

• New profile for DCAT-AP v3, euro_dcat_ap_3, which is now
  the default. Existing sites willing to stick with DCAT-AP v2.x can specify the profile in the configuration if they
  are not doing so yet (ckan.dcat.rdf.profiles = euro_dcat_ap_2). The new euro_dcat_ap_3 profile relies on
  ckanext-scheming metadata schemas (see below).

• Support for standard CKAN ckanext-scheming schemas.
  The DCAT profiles now seamlessly integrate with fields defined via the YAML or JSON scheming files.
  Sites willing to migrate to a scheming based metadata schema can do
  so by adding the euro_dcat_ap_scheming profile at the end of their profile chain (e.g.
  ckanext.dcat.rdf.profiles = euro_dcat_ap_2 euro_dcat_ap_scheming), which will modify the existing profile
  outputs to the expected format by the scheming validators. Sample schemas are provided
  in the ckanext/dcat/schemas folder. See the documentation
  for all details. Some highlights of the new scheming based profiles (#​281):

  • Actual list support in the API output for list properties like dct:language
  • Multiple objects now allowed for properties like dcat:ContactPoint, dct:spatial or dct:temporal
  • Custom validators for date values that allow xsd:gYear, xsd:gYearMonth, xsd:date and xsd:dateTime

• SHACL validation for DCAT-AP 2.1.1 profile (scheming and legacy).
  SHACL validation made surface the following issues in the existing profiles, which are now fixed (#​288):

  • Cast dcat:byteSize and dcat:spatialResolutionInMeters as Decimal, not float
  • Allow only one value of dcat:spatialResolutionInMeters and dcat:temporalResolution
  • Only output the WKT version of geometries in locn:geometry, dcat:bbox and dcat:centroid. Sites that for some reason
    require GeoJSON (or both) can use the ckanext.dcat.output_spatial_format config option
    to choose which format to use
  • When using the euro_dcat_ap_2 profile, don't output temporal extent namespaced
    both with schema and dcat, just with the latter (dcat:startDate and dcat:endDate)

• CKAN 2.11 support and requirements updates (#​270)

• New ckan dcat consume and ckan dcat produce CLI commands (#​279)

• Revamped documentation, now hosted at https://docs.ckan.org/projects/ckanext-dcat (#​296)

• Parse dcat:spatialResolutionInMeters as float (#​285)

• Split profile classes into their own separate files (#​282)

• Catch Not Authorized in View (#​280)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.