Frameworks & Standards
DCAT
DCAT is the W3C Data Catalog Vocabulary. It gives publishers a common RDF vocabulary for describing catalogs, datasets, data services, distributions, versions, access rights, policies, provenance, and quality information.
Buyer question
"Can Legra make data assets discoverable and interoperable across catalogs, marketplaces, and other organizations?"
Legra fit
| Assessment area | Legra fit | Status |
|---|---|---|
| Catalogs and datasets | Legra can represent catalogs and datasets as RDF graph data and can query them through SPARQL. | Native fit |
| Services and endpoints | Legra exposes graph query and graph store endpoints that can be described as data services. | Native fit |
| Versioning | DCAT 3 includes versioning concepts. Legra has native branch, commit, and delta history. | Native fit |
| Distributions | Describe available distributions and connect them to the export or access method you provide. | Partial fit |
| Federated discovery | Catalog metadata can describe data products published by different organizations. | Partial fit |
What Legra can say
Use DCAT metadata to describe datasets, their owners, and their access methods. Review changes to those descriptions alongside changes to the data.
That matters for buyers because catalog metadata becomes operational evidence, not marketing copy:
- A dataset description can point to the exact branch or commit it describes.
- A distribution can point to the query endpoint, export, or service that serves it.
- A service description can identify its purpose, owner, and available queries.
- Access rights and policy metadata can be tied to workspace membership and encryption.
- Quality and conformance metadata can be tied to validation rules and validation reports.
Assessment boundary
A complete DCAT publishing workflow depends on the specific catalog, distribution, service, and publication process a buyer wants to operate.