Skip to content

Latest commit

 

History

History
47 lines (38 loc) · 3.5 KB

README.md

File metadata and controls

47 lines (38 loc) · 3.5 KB

Examples

All examples reference dprod-simple.jsonld, the simple DPROD JSON-LD context, and are written in plain terms: outputPort, title, id, type. Each plain term maps to the same IRI and value coercion as its prefixed form in dprod-context.jsonld, so a document denotes the same graph whichever context it uses. Use the prefixed context (dprod:outputPort, dct:title, @id, @type) when combining DPROD with other JSON-LD contexts, where generic names such as title or target would collide. Neither context has an @vocab, so a misspelt term stays visibly undefined instead of being silently coined in the DPROD namespace. See issues #93 and #246.

Every example here — the standalone files, the JSON-LD and Turtle snippets in each README.md, and the worked examples in the specification itself — is validated by tests/test_examples.py on every build: it must parse, expand against the generated context without dropping a term, and produce triples in which IRI-valued properties are resources rather than literals.

Implemented

  • SBA Pool Rates - Mortgage-backed securities rates served through three ports: database query, API, and Kafka topic.
  • Equity Trade - Equity trades data product providing datasets for London Stock Exchange and Euronext.
  • Data Lineage - Tracing lineage between data products via input/output ports and at the dataset level using PROV.
  • Data Rights - Describing rights and entitlements on data products and datasets using ODRL policies.
  • Data Quality - Measuring dataset quality using the W3C Data Quality Vocabulary (DQV).
  • Data Schema - Describing dataset schemas using SHACL node shapes and property shapes.
  • Observability Ports - Exposing monitoring and diagnostic data through a dedicated observability port.
  • Core Data Product Extensions - Extending a data product with additional metadata such as FIBO-based agreements.

Data Contracts

Examples of the DPROD Data Contracts profile (ODRL 2.2). They render as their own section of the specification and validate against dprod-contracts/dprod-contracts-shapes.ttl.

  • Data Offer and Contract - A provider's offer, the consumer's contract that accepts it, and the evaluated duties.
  • Provider Duties - The four service-level duty patterns: delivery, schema conformance, change notification and quality.
  • Lifecycle and Versioning - Authored offer and contract status, evaluator-computed duty state, and offer version chains.
  • Data Use Policy - An organisational policy with no named parties: purpose, classification and environment constraints, prohibitions, and logical combination.
  • Collections and Target Inheritance - Asset and party collections with odrl:partOf, multi-target offers, and rule-level target override.
  • Evaluation Context - How operands bind to the request, the world snapshot and the built-in agent and clock, and what an evaluator is given.
  • ODCS Mapping - An Open Data Contract Standard document expressed as a DPROD data offer.

Planned

  • Apply DCAT
  • Gleif
  • OpenData file