EKGF Documentation Preview

The Data Product (DPROD) Ontology

EKGF Documentation Preview

Specification PDFEKGF community draftOMG submission preview
Preamble

Abstract§

The concept of Data Products has emerged as organizations increasingly recognize the value of data as an asset to be managed and distributed like any other product. As more companies adopt decentralized data architectures, such as Data Mesh, the need for standardized methods to describe and manage data products consistently across platforms has become critical. This is where the dprod specification, built on W3C Linked Data standards, becomes essential. Without such a standard, organizations face significant challenges: inconsistent metadata across diverse data products, limited discoverability, and interoperability issues that hinder data integration from various sources. As data ecosystems grow, the lack of a common framework also impedes scalability, increases vendor lock-in, and makes it difficult to manage these products effectively.

DPROD offers a solution by providing a clear schema for describing data products, ensuring they are discoverable, interoperable, and treated with the same level of accountability as traditional products.

The W3C tech stack is perfectly suited to address these challenges because it was designed to foster interconnected, decentralized systems, providing a robust framework for creating metadata that is both machine-readable and human-understandable. DPROD enables consistent terminology across different platforms, domains, and organizations, allowing advanced users to semantically enrich their data products and connect them into distributed knowledge graphs.

As more organizations strive to build and scale data products, DPROD provides the standardization needed to ensure interoperability and unlock the full potential of decentralized data ecosystems in a controlled and mature way.

Status of This Document§

This is the EKGF community draft of DPROD 1.1, developed by the Enterprise Knowledge Graph Forum, a community of the Object Management Group (OMG). It is not an approved OMG specification.

This edition supports community review and implementation feedback before formal standardisation through the OMG Enterprise Knowledge Graph Platform Task Force. The companion OMG submission preview uses the same technical chapters, ontology, shapes and examples from the same repository revision, with submission-specific front matter.

The official published baseline is DPROD 1.0 beta 2. A future approved 1.1 publication requires an OMG-assigned document number, approval status, release date and authoritative version URL. This draft supplies none of those approval claims.

The legal preamble is retained from this repository without changing its wording. The closing provenance section identifies the exact source commit and generator used for this build. External ontology imports are not fetched implicitly.

Community preface§

About the Enterprise Knowledge Graph Forum§

The Enterprise Knowledge Graph Forum (EKGF) is an OMG community in which initiatives such as DPROD are developed and reviewed before they are handed over for formal standardisation. The Enterprise Knowledge Graph Platform Task Force provides the OMG standards process for this work.

This community edition invites practical feedback on the data product vocabulary, the optional Data Contracts profile and their examples. It is not an approved OMG specification and does not assign formal publication status to the draft.

Review and participation§

Use the DPROD issue tracker to report technical issues and the repository pull requests to propose improvements. The source repository is the shared basis for this community edition and the OMG submission preview; technical changes are made once and appear in both.

1. Scope§

The Data Product (DPROD) specification is a profile of the Data Catalog (DCAT) Vocabulary, designed to describe Data Products. This document defines the schema and provides examples of its use.

DPROD extends DCAT to enable publishers to describe Data Products and data services in a decentralized way. By using a standard model and ontology, DPROD facilitates the consumption and aggregation of metadata from multiple Data Marketplaces. This approach increases the discoverability of products and services, supports decentralized data publishing, and enables federated search across multiple sites using a uniform query mechanism and structure.

DPROD also defines an optional Data Contracts profile of the W3C Open Digital Rights Language odrl-model, with which the provider of a data product can publish the terms on which it is offered, and a consumer can record the contract under which it is used.

The namespace for DPROD terms is https://ekgf.org/dprod/spec/develop/

The suggested prefix for the DPROD namespace is dprod

DPROD follows two basic principles:

  • Decentralize Data Ownership: To make data integration more efficient, tasks should be shared among multiple teams. DCAT helps by offering a standard way to publish datasets in a decentralized manner.
  • Harmonize Data Schemas: Using shared schemas helps unify different data formats. For instance, the DPROD specification provides a common set of rules for defining a Data Product. Users of DPROD can extend this schema as needed.

The dprod specification builds on DCAT vocab-dcat-3 by connecting DCAT Data Services to DPROD Data Products using input and output ports. These ports are used to publish and consume data from a Data Product. DPROD treats ports as DCAT data services, so the data exchanged can be described using DCAT's highly expressive metadata around distributions and datasets. This approach also allows publishers to create their own descriptions for the data they are sharing. They can use a special property called conformsTo from DCAT to link to their own set of rules or guidelines for their data.

The DPROD specification has four main aims:

  • To provide unambiguous and sharable semantics to answer the question: 'What is a data product?'
  • Be simple for anyone to use, but expressive enough to power large data marketplaces
  • Allow organisations to reuse their existing data catalogues and dataset infrastructure
  • To share common semantics across different Data Products and promote harmonization

2. Conformance§

A data product is conformant with this specification if it satisfies the SHACL constraints provided in the file dprod-shapes.ttl.

Support for the Data Contracts profile is optional. A data offer, data contract or data use policy is conformant with this specification if it satisfies the SHACL constraints provided in the file dprod-contracts-shapes.ttl, and an evaluator of such policies is conformant if it produces the results defined by the profile's formal semantics.

3. Normative references§

Draft provenance note: Bibliographic editions were checked against the 1.0 beta 2 reference list, with repository-local citation records taken from this source revision. Confirm the selected editions for 1.1.

3.1 data mesh§

Data Mesh Architectures. Wikipedia. https://en.wikipedia.org/wiki/Data_mesh

3.2 dcterms§

DCMI Metadata Terms. DCMI Usage Board. DCMI. 20 January 2020. DCMI Recommendation. URL: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/

3.3 dprod§

Data Product Ontology. Tony Seale; Natasa Varytimou; Matthias Autrata; Pete Rivett; Marcel Fröhlich; Andrea Gioia; Jacobus Geluk; Ben Whittam Smith; Steve Fisher; Oli Bage; Ben Clinch; Carl Mattocks; Carlos Tubbax; Charles Ivie; Josh Cornejo. EKGF. https://ekgf.org/dprod/spec/develop/

3.4 iri§

Internationalized Resource Identifiers (IRIs). M. Duerst; M. Suignard. IETF. January 2005. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc3987

3.5 json-ld11§

JSON-LD 1.1. Gregg Kellogg; Pierre-Antoine Champin; Dave Longley. W3C. 16 July 2020. W3C Recommendation. URL: https://www.w3.org/TR/json-ld11/

3.6 odrl-model§

ODRL Information Model 2.2. Renato Iannella; Serena Villata. W3C. 15 February 2018. W3C Recommendation. URL: https://www.w3.org/TR/odrl-model/

3.7 owl2-quick-reference§

OWL 2 Web Ontology Language Quick Reference Guide (Second Edition). Jie Bao; Elisa Kendall; Deborah McGuinness; Peter Patel-Schneider. W3C. 11 December 2012. W3C Recommendation. URL: https://www.w3.org/TR/owl2-quick-reference/

3.8 prov-overview§

PROV-Overview. Paul Groth; Luc Moreau. W3C. 30 April 2013. W3C Working Group Note. URL: https://www.w3.org/TR/prov-overview/

3.9 rdf-schema§

RDF Schema 1.1. Dan Brickley; Ramanathan Guha. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/rdf-schema/

3.10 rdf11-concepts§

RDF 1.1 Concepts and Abstract Syntax. Richard Cyganiak; David Wood; Markus Lanthaler. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/rdf11-concepts/

3.11 rdf11-primer§

RDF 1.1 Primer. Guus Schreiber; Yves Raimond. W3C. 24 June 2014. W3C Working Group Note. URL: https://www.w3.org/TR/rdf11-primer/

3.12 rdf12-turtle§

RDF 1.2 Turtle. Gregg Kellogg; Dominik Tomaszuk. W3C. 29 August 2024. W3C Working Draft. URL: https://www.w3.org/TR/rdf12-turtle/

3.13 rfc5545§

Internet Calendaring and Scheduling Core Object Specification (iCalendar). B. Desruisseaux, editor. IETF. September 2009. RFC 5545. https://www.rfc-editor.org/rfc/rfc5545

3.14 shacl§

Shapes Constraint Language (SHACL). Holger Knublauch; Dimitris Kontokostas. W3C. 20 July 2017. W3C Recommendation. URL: https://www.w3.org/TR/shacl/

3.15 skos-reference§

SKOS Simple Knowledge Organization System Reference. Alistair Miles; Sean Bechhofer. W3C. 18 August 2009. W3C Recommendation. https://www.w3.org/TR/2009/REC-skos-reference-20090818/

3.16 swbp-xsch-datatypes§

XML Schema Datatypes in RDF and OWL. Jeremy Carroll; Jeff Pan. W3C. 14 March 2006. W3C Working Group Note. URL: https://www.w3.org/TR/swbp-xsch-datatypes/

3.17 turtle§

RDF 1.1 Turtle. Eric Prud'hommeaux; Gavin Carothers. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/turtle/

3.18 uri§

Uniform Resource Identifier (URI): Generic Syntax. T. Berners-Lee; R. Fielding; L. Masinter. IETF. January 2005. Internet Standard. URL: https://www.rfc-editor.org/rfc/rfc3986

3.19 vocab-dcat-3§

Data Catalog Vocabulary (DCAT) - Version 3. Simon Cox; Andrea Perego; Alejandra Gonzalez Beltran; Peter Winstanley; Riccardo Albertoni; David Browning. W3C. 22 August 2024. W3C Recommendation. URL: https://www.w3.org/TR/vocab-dcat-3/

3.20 xmlschema-2§

XML Schema Part 2: Datatypes Second Edition. Paul V. Biron; Ashok Malhotra. W3C. 28 October 2004. W3C Recommendation. URL: https://www.w3.org/TR/xmlschema-2/

4. Terms and Definitions§

All terms introduced in this specification are given definitions in the Data Product Model defined later.

5. Symbols§

The following acronyms are used in this specification.

6. Normative namespaces§

Namespaces and prefixes used in normative parts of this Profile are shown in the following table.

PrefixNamespace IRISource
dprodhttps://ekgf.org/dprod/spec/develop/dprod
dprod-shapeshttps://ekgf.org/dprod/spec/develop/shapes/dprod
dprod-contracts-shapeshttps://ekgf.org/dprod/spec/develop/contracts/shapes/dprod
dcathttp://www.w3.org/ns/dcat#vocab-dcat-3
dcthttp://purl.org/dc/terms/dcterms
odrlhttp://www.w3.org/ns/odrl/2/odrl-model
owlhttp://www.w3.org/2002/07/owl#owl2-quick-reference
provhttp://www.w3.org/ns/prov#prov-overview
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#rdf11-primer
rdfshttp://www.w3.org/2000/01/rdf-schema#rdf-schema
shhttp://www.w3.org/ns/shacl#shacl
skoshttp://www.w3.org/2004/02/skos/core#skos-reference
xsdhttp://www.w3.org/2001/XMLSchema#xmlschema-2

7. Data Product (DPROD) Model§

Data Mesh Architectures Data Mesh use input and output ports to manage how data enters and leaves a Data Product. These ports can handle different formats, schemas, and protocols. Input ports bring in data, while output ports send data to other Data Products for aggregation, reuse, analysis or reporting, etc.

In the vocab-dcat-3 framework, a Data Service is a way to describe services that provide access to data. Data Services give standardized, machine-readable descriptions of how to access one or more datasets or data processing functions.

Data Services specify how to access and download the data. In DPROD, Data Services are connected to Distributions by a property called isAccessServiceOf; on the Distribution one can specify formats (like CSV or JSON etc.) and provide metadata about the "physical model" of the data. Distributions link to Datasets and DCAT has a very rich vocabulary for describing every aspect of a dataset. Finally, Datasets use the conformsTo property to link to the "logical model" where one can specify one's own rich semantic metadata.

By linking Data Product ports to DCAT DataServices (vocab-dcat-3), DPROD can describe Data Products in a way that machines can read across the organization. This makes it easier for data teams to build and manage their own data products independently, while still working well with the rest of the organization's data.

Using standards like DCAT helps create a strong and clear way to define Data Products. It ensures that as data becomes more complex, the methods for describing, sharing, and using data stay consistent and reliable. It also allows different organizations to share data securely and in a standardized way.

Information model for the Profile

Overview of the DPROD model and its relationship with DCAT classes

The Profile consists of the following classes:

  • Data Mesh (dcat:Catalog) - The collection of Data Products
  • Data Product (dprod:DataProduct) - A data product may have input and output ports, code and metadata
  • Port (dcat:DataService) - A digital interface that provides access to a Dataset. This can be an HTTP URL, a Database or a FileShare, etc.
  • Distribution (dcat:Distribution) - A specific representation of a dataset (CSV, JSON, ADLS etc.) which can conform to a physical model
  • Dataset (dcat:Dataset) - A collection of related data that can conform to a logical model

7.1 UK Bonds in practice§

As DCAT Data Services, the DPROD input and output ports can specify connection details, they have distributions that define formats, and link to datasets that conform to shared schemas. In this example, the UK Bonds Data Product includes an output port, which is a RESTful API. This API delivers JSON data conforming to the shared FIBO specification for callable bonds.

Example
  {
    "@context": "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    "id": "https://y.com/products/uk-bonds",
    "type": "DataProduct",
    "title": "UK Bonds",
    "description": "UK Bonds is your one-stop-shop for all your bonds!",
    "dataProductOwner": "https://www.linkedin.com/in/tonyseale/",
    "dataProductLifecycleStatus": "https://ekgf.org/dprod/spec/develop/data/lifecycle-status/Consume",
    "outputPort": {
      "id": "https://y.com/products/uk-bonds/ports/10-year-api",
      "type": "DataService",
      "endpointURL": "https://y.com/uk-10-year-bonds",
      "isAccessServiceOf": {
        "id": "https://y.com/products/uk-bonds/distributions/10-year-json",
        "type": "Distribution",
        "format": "https://www.iana.org/assignments/media-types/application/json",
        "isDistributionOf": {
          "id": "https://y.com/products/uk-bonds/datasets/10-year",
          "type": "Dataset",
          "conformsTo": "https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/Bonds/CallableBond"
        }
      }
    }
  }

7.2 Working with JSON-LD contexts§

Note

DPROD publishes two JSON-LD contexts that denote the same graph. The examples in this specification use the simple context, dprod-simple.jsonld, which lets a document use plain terms such as outputPort, title, id and type. When DPROD JSON is combined with other JSON-LD contexts, use dprod-context.jsonld and prefixed terms such as dprod:outputPort and dct:title with the keywords @id and @type, so that neither side claims generic names such as title or format. Neither context has an @vocab, so an undefined term is visibly undefined rather than silently coined in the DPROD namespace.

The JSON above can be pasted into https://json-ld.org/playground to see the RDF it denotes.

Note

The following sections are driven by the Shapes definitions for DPROD, which represent the properties expected to be used for instances of the above classes. As such, they include properties defined by the DCAT specification which DPROD extends. The prefix in the identifier for each entry indicates the ontology defining the property.

8. Data Contracts§

A data product is only useful once someone can rely on it. The provider of a product commits to deliver data on a schedule, to keep it conformant to a schema, and to give notice before it changes; the consumer, in turn, agrees to use the data only in permitted ways and to meet obligations of its own, such as reporting usage. In a Data Mesh these commitments are made between many autonomous teams, so they need to be recorded in a form that machines can validate and evaluate, not just in prose.

DPROD Data Contracts is a profile of the W3C Open Digital Rights Language (ODRL) 2.2 odrl-model for exactly this purpose. It uses ODRL's own terms for everything ODRL already defines: a policy, its permissions, prohibitions and duties, the constraints on them, and the parties and assets they refer to.

8.1 DPROD extensions§

DPROD adds vocabulary only where ODRL leaves behaviour undefined:

  • Two policy types. A dprod:DataOffer is an odrl:Offer published by a data provider. A dprod:DataContract is an odrl:Agreement that records a consumer's acceptance of exactly one offer, through dprod:acceptsOffer, and binds both parties.
  • Bilateral duties. ODRL duties fall on the assignee. In a data contract the provider has duties too, so DPROD names the party that bears each duty (dprod:subjectOfDuty) and the party it is owed to (dprod:objectOfDuty).
  • Schedules and deadlines. A duty may recur on a reusable, identified dprod:Schedule (for example an RFC5545 recurrence rule with its start time and timezone), referenced through dprod:schedule, and each instance has a fulfilment window (dprod:deadline).
  • Authored status and computed state. A publisher records where an offer or contract is in its lifecycle. An evaluator computes, from observable facts, whether each duty is pending, active, fulfilled or violated (dprod:dutyState). The two are kept apart on purpose.
  • Deterministic evaluation. Every operand a constraint refers to is bound to one property on one normalised input (the authorisation request, a state-of-the-world snapshot, or the evaluation context itself), prohibitions always win over permissions, and the same inputs always produce the same decision.

Because it is a proper ODRL profile, every DPROD data contract is a valid ODRL 2.2 policy. An ODRL processor that knows nothing of DPROD can still read the permissions and prohibitions; a DPROD-aware processor additionally enforces duty state, bilateral duties and the evaluation rules.

The profile is defined by three files, published alongside this document: dprod-contracts.ttl (the vocabulary), dprod-contracts-shapes.ttl (the SHACL constraints an instance document must satisfy) and dprod-contracts-prof.ttl (the profile declaration). The normative evaluation semantics, which define what a conforming evaluator must compute, are maintained in the formal semantics document; authoring guidance for contract writers and policy writers is in the contracts documentation.

8.2 Optional adoption§

The Data Contracts profile is optional. A data product description conforms to DPROD whether or not it carries any policy; an implementation that does process contracts must satisfy the contracts shapes as stated in the Conformance section.

9. Data Contract Model§

A provider publishes a dprod:DataOffer, an odrl:Offer setting out the provider's duties, the consumer's rights and what is prohibited. When a consumer accepts it, the result is a dprod:DataContract, an odrl:Agreement that binds both parties, may add duties on the consumer, and links back to the offer it accepts. Each row of the figure names the property that carries it; DPROD terms are shown in blue. The lower part shows the state an evaluator computes for each duty.

A DataOffer is accepted to form a DataContract; each duty moves from Pending to Active, then to Fulfilled or Violated

Overview of DPROD Data Contracts: offer, acceptance, contract and duty state

A data product, or any of its datasets, distributions and data services, is an odrl:Asset when it appears as the odrl:target of a policy. Teams and organisations are odrl:Party instances. Both may be grouped into ODRL collections using odrl:partOf; DPROD evaluates membership over the transitive closure of that property, so a rule on a collection applies to everything in it.

The lifecycle of an offer or a contract is recorded with dprod:offerLifecycleStatus and dprod:contractLifecycleStatus. Both are sub-properties of the core dprod:lifecycleStatus and take any skos:Concept; DPROD ships dprod:DataContractLifecycleStatus, an optional concept scheme with the values dprod:Pending, dprod:Active, dprod:Fulfilled and dprod:Violated, which an enterprise may use, extend or replace.

A DPROD-aware evaluator answers the question "may this agent perform this action on this asset now?" It never reads a live graph while doing so. Instead the caller assembles one immutable dprod:EvaluationContext holding the authorisation request, a snapshot of the state of the world, the requesting agent and the clock. Each odrl:LeftOperand used in a constraint declares which of those inputs it reads (dprod:operandSource) and which single property it reads from it (dprod:operandProperty). A value that is missing, ambiguous or of the wrong type is an evaluation error rather than a silently false constraint. ODRL's own odrl:dateTime operand is bound to the context clock, and dprod:currentAgent to the requesting agent.

In this example the Trading Data Team offers its Market Price Data product with a single provider duty (deliver every 15 minutes, within 5 minutes of the scheduled time), one consumer permission and one prohibition. The Analytics Team has accepted the offer for 2026; the contract names both parties and links to the offer it accepts.

Example
  {
    "@context": [
      "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
      { "ex": "https://example.org/" }
    ],
    "id": "ex:tradingMarketData2026",
    "type": "DataContract",
    "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
    "assigner": "ex:tradingDataTeam",
    "assignee": "ex:analyticsTeam",
    "target": "ex:marketPrices",
    "contractLifecycleStatus": "Active",
    "effectiveDate": "2026-01-15T00:00:00Z",
    "expirationDate": "2026-12-31T23:59:59Z",
    "permission": {
      "type": "Permission",
      "assignee": "ex:analyticsTeam",
      "action": "display"
    },
    "acceptsOffer": {
      "id": "ex:marketDataFeed",
      "type": "DataOffer",
      "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
      "assigner": "ex:tradingDataTeam",
      "target": "ex:marketPrices",
      "offerLifecycleStatus": "Active",
      "obligation": {
        "type": "Duty",
        "subjectOfDuty": "ex:tradingDataTeam",
        "action": "ex:deliver",
        "schedule": {
          "id": "ex:every15Minutes",
          "type": "Schedule",
          "conformsTo": "dprod:Rfc5545ScheduleFormat",
          "scheduleExpression": "DTSTART;TZID=Europe/London:20260101T000000\nRRULE:FREQ=MINUTELY;INTERVAL=15"
        },
        "deadline": { "@value": "PT5M", "type": "xsd:duration" }
      },
      "permission": { "type": "Permission", "action": "display" },
      "prohibition": { "type": "Prohibition", "action": "distribute" }
    }
  }

ODRL terms are written as plain names, in the same way DCAT terms are in a data product description. The context knows that an action, an operator or a status names a vocabulary term, so "action": "display" denotes odrl:display and "contractLifecycleStatus": "Active" denotes dprod:Active. The offer is shown nested inside the contract for readability. In practice a provider publishes the offer once, as its own resource, and each contract that accepts it refers to it by identifier. The full version of this example, with the domain vocabulary, the parties and the evaluated duty instances, is in the Data Offer and Contract worked example.

The following class definitions are driven by the contracts Shapes, in the same way as the core model above. Only classes DPROD defines are listed here; the ODRL classes the profile reuses are defined by odrl-model, and the DPROD properties that extend them follow in the next section.

10. Vocabulary and constraints reference§

The following sections document the named vocabulary resources and SHACL shapes from this same repository revision. The preceding conformance clause identifies the authoritative shape files; the human-readable reference does not replace them.

10.1. OWL classes§

10.1.1 dprod:DataContract§

Activated data offer binding provider and consumer.

A DataContract is an activated DataOffer. - assigner: data provider (from offer) - assignee: data consumer Bilateral: both parties may have active duties.

dprod:DataContract
https://ekgf.org/dprod/spec/develop/DataContract
RDF predicateValue
rdf:typeowl:Class
rdfs:labeldata contract
rdfs:subClassOfodrl:Agreement
owl:disjointWithdprod:DataOffer
UML class diagram for data contract. Diagram labels: «Resource»; skos:; Concept; «Resource»; odrl:; Agreement; «owl:Class»; data contract; odrl:assignee [1..1]; odrl:assigner [1..1]; odrl:profile [1..*]; data product lifecycle status [0..0]; effective date : xsd:dateTime [0..1]; expiration date : xsd:dateTime [0..1]; offer lifecycle status [0..0]; «owl:Class»; data offer; odrl:assigner [1..1]; odrl:profile [1..*]; contract lifecycle status [0..0]; data product lifecycle status [0..0]; effective date : xsd:dateTime [0..1]; expiration date : xsd:dateTime [0..1]; accepts offer; 1..1; contract lifecycle; status; 0..1; offer lifecycle status; 0..1; owl:; disjointWith; data contract rdfs:subClassOf odrl:Agreement. data contract owl:disjointWith data offer. accepts offer rdfs:domain data contract. accepts offer rdfs:range data offer. contract lifecycle status rdfs:domain data contract. contract lifecycle status rdfs:range skos:Concept.«Resource»skos:Concept«Resource»odrl:Agreement«owl:Class»data contractodrl:assignee [1..1]odrl:assigner [1..1]odrl:profile [1..*]data product lifecycle status [0..0]effective date : xsd:dateTime [0..1]expiration date : xsd:dateTime [0..1]offer lifecycle status [0..0]«owl:Class»data offerodrl:assigner [1..1]odrl:profile [1..*]contract lifecycle status [0..0]data product lifecycle status [0..0]effective date : xsd:dateTime [0..1]expiration date : xsd:dateTime [0..1]accepts offer1..1contract lifecyclestatus0..1offer lifecycle status0..1owl:disjointWith
Class neighborhood: data contract [1]

10.1.2 dprod:DataOffer§

Policy offer defining data access terms.

A DataOffer is an Offer from a data provider. It defines permissions, duties, and prohibitions for data access. When accepted by a consumer, becomes a DataContract (Agreement).

dprod:DataOffer
https://ekgf.org/dprod/spec/develop/DataOffer
RDF predicateValue
rdf:typeowl:Class
rdfs:labeldata offer
rdfs:subClassOfodrl:Offer
UML class diagram for data offer. Diagram labels: «Resource»; skos:; Concept; «Resource»; odrl:; Offer; «owl:Class»; data contract; odrl:assignee [1..1]; odrl:assigner [1..1]; odrl:profile [1..*]; data product lifecycle status [0..0]; effective date : xsd:dateTime [0..1]; expiration date : xsd:dateTime [0..1]; offer lifecycle status [0..0]; «owl:Class»; data offer; odrl:assigner [1..1]; odrl:profile [1..*]; contract lifecycle status [0..0]; data product lifecycle status [0..0]; effective date : xsd:dateTime [0..1]; expiration date : xsd:dateTime [0..1]; accepts offer; 1..1; offer lifecycle status; 0..1; contract lifecycle; status; 0..1; owl:; disjointWith; data offer rdfs:subClassOf odrl:Offer. data contract owl:disjointWith data offer. accepts offer rdfs:domain data contract. accepts offer rdfs:range data offer. offer lifecycle status rdfs:domain data offer. offer lifecycle status rdfs:range skos:Concept.«Resource»skos:Concept«Resource»odrl:Offer«owl:Class»data contractodrl:assignee [1..1]odrl:assigner [1..1]odrl:profile [1..*]data product lifecycle status [0..0]effective date : xsd:dateTime [0..1]expiration date : xsd:dateTime [0..1]offer lifecycle status [0..0]«owl:Class»data offerodrl:assigner [1..1]odrl:profile [1..*]contract lifecycle status [0..0]data product lifecycle status [0..0]effective date : xsd:dateTime [0..1]expiration date : xsd:dateTime [0..1]accepts offer1..1offer lifecycle status0..1contract lifecyclestatus0..1owl:disjointWith
Class neighborhood: data offer [1]

10.1.3 dprod:DataProduct§

A rational, managed, and governed collection of data, with purpose, value and ownership, meeting consumer needs over a planned life-cycle.

A data product may have input and output ports, code and metadata

dprod:DataProduct
https://ekgf.org/dprod/spec/develop/DataProduct
RDF predicateValue
rdf:typerdfs:Class
rdf:typeowl:Class
rdfs:labeldata product
rdfs:subClassOfdcat:Resource
UML class diagram for data product. Diagram labels: «Resource»; skos:; Concept; «Resource»; dcat:; DataService; «Resource»; dcat:; Dataset; «Resource»; dcat:; Resource; «Resource»; odrl:; Policy; «Resource»; prov:; Agent; «owl:Class»; data product; dct:description : xsd:string; rdfs:label : xsd:string; contract lifecycle status [0..0]; domain; offer lifecycle status [0..0]; purpose : xsd:string; data product lifecycle; status; 0..1; data product owner; input dataset; odrl:; hasPolicy; input port; output dataset; output port; data product rdfs:subClassOf dcat:Resource. data product lifecycle status rdfs:domain data product. data product lifecycle status rdfs:range skos:Concept. data product owner rdfs:domain data product. data product owner rdfs:range prov:Agent. domain rdfs:domain data product. input dataset rdfs:domain data product. input dataset rdfs:range dcat:Dataset.«Resource»skos:Concept«Resource»dcat:DataService«Resource»dcat:Dataset«Resource»dcat:Resource«Resource»odrl:Policy«Resource»prov:Agent«owl:Class»data productdct:description : xsd:stringrdfs:label : xsd:stringcontract lifecycle status [0..0]domainoffer lifecycle status [0..0]purpose : xsd:stringdata product lifecyclestatus0..1data product ownerinput datasetodrl:hasPolicyinput portoutput datasetoutput port
Class neighborhood: data product [1]

10.1.4 dprod:Enumeration§

The superclass of enumeration lists referenced from data product related artifacts.

dprod:Enumeration
https://ekgf.org/dprod/spec/develop/Enumeration
RDF predicateValue
rdf:typerdfs:Class
rdf:typeowl:Class
rdfs:labelenumeration
UML class diagram for enumeration. Diagram labels: «owl:Class»; enumeration; «owl:Class»enumeration
Class neighborhood: enumeration [1]

10.1.5 dprod:EvaluationContext§

Immutable, provenance-bearing input graph for one policy evaluation.

The immutable container for runtime operand resolution. DPROD does not evaluate policies; an evaluator is an external program that implements this specification. The calling system that needs a decision constructs one EvaluationContext for each evaluation and supplies the authorization request, an immutable state-of-the-world snapshot, the requesting agent, and the evaluation clock through the four normative properties. The evaluator reads only this context. The context is a prov:Entity so implementations can retain the exact input provenance needed to reproduce and audit a decision. Evaluation never reads a live global graph or dereferences an undeclared source while resolving an operand binding.

dprod:EvaluationContext
https://ekgf.org/dprod/spec/develop/EvaluationContext
RDF predicateValue
rdf:typeowl:Class
rdfs:labelevaluation context
rdfs:subClassOfprov:Entity
UML class diagram for evaluation context. Diagram labels: «Resource»; odrl:; Party; «Resource»; prov:; Entity; «owl:Class»; evaluation context; clock : xsd:dateTime [1..1]; request [1..1]; agent; 1..1; state; 1..1; evaluation context rdfs:subClassOf prov:Entity. agent rdfs:domain evaluation context. agent rdfs:range odrl:Party. clock rdfs:domain evaluation context. clock rdfs:range xsd:dateTime. request rdfs:domain evaluation context. request rdfs:range rdfs:Resource. state rdfs:domain evaluation context. state rdfs:range prov:Entity.«Resource»odrl:Party«Resource»prov:Entity«owl:Class»evaluation contextclock : xsd:dateTime [1..1]request [1..1]agent1..1state1..1
Class neighborhood: evaluation context [1]

10.1.6 dprod:InformationSensitivityClassification§

A classification of the information within a dataset to indicate the level of control and protection that must be applied.

dprod:InformationSensitivityClassification
https://ekgf.org/dprod/spec/develop/InformationSensitivityClassification
RDF predicateValue
rdf:typerdfs:Class
rdf:typeowl:Class
rdfs:labelinformation sensitivity classification
rdfs:seeAlsohttps://spec.edmcouncil.org/cdmc/ontology/Classification/InformationSensitivity
UML class diagram for information sensitivity classification. Diagram labels: «Resource»; dcat:; Dataset; «owl:Class»; information sensitivity; classification; information sensitivity; classification; information sensitivity classification rdfs:domain dcat:Dataset. information sensitivity classification rdfs:range information sensitivity classification.«Resource»dcat:Dataset«owl:Class»information sensitivityclassificationinformation sensitivityclassification
Class neighborhood: information sensitivity classification [1]

10.1.7 dprod:OperandSource§

Closed set of normalized source nodes from which an operand value may be read.

An operand reads one direct property from exactly one normalized source: the authorization request, the immutable world snapshot, or the evaluation context itself. No other source and no graph traversal are supported.

dprod:OperandSource
https://ekgf.org/dprod/spec/develop/OperandSource
RDF predicateValue
rdf:typeowl:Class
rdfs:labeloperand source
owl:oneOf(dprod:requestSource, dprod:stateSource, dprod:contextSource)
UML class diagram for operand source. Diagram labels: «Resource»; odrl:; LeftOperand; «owl:Class»; operand source; operand source; operand source rdfs:domain odrl:LeftOperand. operand source rdfs:range operand source.«Resource»odrl:LeftOperand«owl:Class»operand sourceoperand source
Class neighborhood: operand source [1]

10.1.8 dprod:Schedule§

Reusable, identified definition of scheduled occurrences.

A Schedule defines when something occurs without defining what occurs or what the occurrence means. DPROD resources refer to it through dprod:schedule; the referring resource and property retain the business meaning. Each Schedule has one authoritative expression and identifies its exact representation through dct:conformsTo. Format-specific profiles may extend the built-in RFC 5545 and POSIX crontab formats.

dprod:Schedule
https://ekgf.org/dprod/spec/develop/Schedule
RDF predicateValue
rdf:typeowl:Class
rdfs:labelschedule
UML class diagram for schedule. Diagram labels: «owl:Class»; schedule; schedule expression : xsd:string [1..1]; schedule timezone : xsd:string [0..1]; rdfs:Resource; schedule; The dotted rdfs:Resource source is a presentation placeholder: no specific domain is declared in the selected inputs. It is not an asserted domain or a claim that no more specific domain can be entailed. schedule rdfs:range schedule. schedule expression rdfs:domain schedule. schedule expression rdfs:range xsd:string. schedule timezone rdfs:domain schedule. schedule timezone rdfs:range xsd:string.«owl:Class»scheduleschedule expression : xsd:string [1..1]schedule timezone : xsd:string [0..1]rdfs:Resourceschedule
Class neighborhood: schedule [1]

10.1.9 dprod:ScheduleFormat§

Identified grammar and interpretation rules for schedule expressions.

A ScheduleFormat identifies an exact schedule grammar or dialect rather than a general implementation family. Third parties may define additional formats and supply corresponding validation and processing profiles.

dprod:ScheduleFormat
https://ekgf.org/dprod/spec/develop/ScheduleFormat
RDF predicateValue
rdf:typeowl:Class
rdfs:labelschedule format
UML class diagram for schedule format. Diagram labels: «owl:Class»; schedule format; carries timezone : xsd:boolean [1..1]; carries timezone rdfs:domain schedule format. carries timezone rdfs:range xsd:boolean.«owl:Class»schedule formatcarries timezone : xsd:boolean [1..1]
Class neighborhood: schedule format [1]

10.1.10 dprod:SecuritySchemaType§

A classification encompassing a set of rules used for authentication and communication.

dprod:SecuritySchemaType
https://ekgf.org/dprod/spec/develop/SecuritySchemaType
RDF predicateValue
rdf:typerdfs:Class
rdf:typeowl:Class
rdfs:labelsecurity schema type
UML class diagram for security schema type. Diagram labels: «owl:Class»; security schema type; «owl:Class»security schema type
Class neighborhood: security schema type [1]

10.2. Object properties§

10.2.1 dprod:acceptsOffer§

The offer this contract activates.

dprod:acceptsOffer
https://ekgf.org/dprod/spec/develop/acceptsOffer
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataContract
rdfs:labelaccepts offer
rdfs:rangedprod:DataOffer

10.2.2 dprod:agent§

Requesting agent supplied for one policy evaluation.

dprod:agent
https://ekgf.org/dprod/spec/develop/agent
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domaindprod:EvaluationContext
rdfs:labelagent
rdfs:rangeodrl:Party

10.2.3 dprod:contractLifecycleStatus§

Where this contract sits in its administrative lifecycle — typically pre-effective, in force, completed, or breached; assigned by the contract management process.

Value is any skos:Concept; dprod:DataContractLifecycleStatus is one example concept scheme shipped with DPROD.

dprod:contractLifecycleStatus
https://ekgf.org/dprod/spec/develop/contractLifecycleStatus
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataContract
rdfs:labelcontract lifecycle status
rdfs:rangeskos:Concept
rdfs:subPropertyOfdprod:lifecycleStatus

10.2.4 dprod:dataProductLifecycleStatus§

The authored development lifecycle status of a data product.

Values are SKOS concepts. DPROD supplies dprod:DataProductLifecycleStatus as an optional reference concept scheme; enterprises may use another scheme.

dprod:dataProductLifecycleStatus
https://ekgf.org/dprod/spec/develop/dataProductLifecycleStatus
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataProduct
rdfs:labeldata product lifecycle status
rdfs:rangeskos:Concept
rdfs:subPropertyOfdprod:lifecycleStatus

10.2.5 dprod:dataProductOwner§

The agent that is accountable overall for the data product, including managing it through its lifecycle.

dprod:dataProductOwner
https://ekgf.org/dprod/spec/develop/dataProductOwner
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataProduct
rdfs:labeldata product owner
rdfs:rangeprov:Agent

10.2.6 dprod:domain§

The business or information area supported by the data product.

The domain is intended to be a resource in its own right. This specification does not constrain the class to be used.

dprod:domain
https://ekgf.org/dprod/spec/develop/domain
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataProduct
rdfs:labeldomain

10.2.7 dprod:dutyState§

The latest evaluation result for this duty, computed by an evaluator from observable facts; recomputed on demand rather than authored.

Value is any skos:Concept. The state machine in formal-semantics §5 is one possible interpretation. Implementations are free to use a different state vocabulary and/or state machine. This evaluator-computed property is deliberately separate from the authored dprod:lifecycleStatus hierarchy.

dprod:dutyState
https://ekgf.org/dprod/spec/develop/dutyState
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domainodrl:Duty
rdfs:labelduty state
rdfs:rangeskos:Concept

10.2.8 dprod:informationSensitivityClassification§

More granular classification that indicates the level of control and protection that must be applied to the asset due to the nature of the data and its sensitivity or importance to the organization.

dprod:informationSensitivityClassification
https://ekgf.org/dprod/spec/develop/informationSensitivityClassification
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindcat:Dataset
rdfs:labelinformation sensitivity classification
rdfs:rangedprod:InformationSensitivityClassification

10.2.9 dprod:inputDataset§

The source data made available to the data product through input data services. Depending on the lifecycle of the data product, this may be a stated or inferred relationship aligned with the input ports.

dprod:inputDataset
https://ekgf.org/dprod/spec/develop/inputDataset
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataProduct
rdfs:labelinput dataset
rdfs:rangedcat:Dataset

10.2.10 dprod:inputPort§

A set of services exposed by a data product to collect its source data and makes it available for further internal transformation. An input port can receive data from one or more upstream sources in a push (i.e. asynchronous subscription) or pop mode (i.e. synchronous query). Each data product may have one or more input ports.

dprod:inputPort
https://ekgf.org/dprod/spec/develop/inputPort
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataProduct
rdfs:labelinput port
rdfs:rangedcat:DataService

10.2.11 dprod:isAccessServiceOf§

The dataset distribution that is being offered through this data service.

dprod:isAccessServiceOf
https://ekgf.org/dprod/spec/develop/isAccessServiceOf
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindcat:DataService
rdfs:labelis access service of
rdfs:rangedcat:Distribution
owl:inverseOfdcat:accessService

10.2.12 dprod:isDistributionOf§

The dataset that this distribution makes available.

dprod:isDistributionOf
https://ekgf.org/dprod/spec/develop/isDistributionOf
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindcat:Distribution
rdfs:labelis distribution of
owl:inverseOfdcat:distribution

10.2.13 dprod:lifecycleStatus§

The authored position of a DPROD resource in its lifecycle.

Abstract super-property for authored lifecycle statuses. Concrete sub-properties define their resource-specific domains; values come from an open SKOS taxonomy.

dprod:lifecycleStatus
https://ekgf.org/dprod/spec/develop/lifecycleStatus
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:labellifecycle status
rdfs:rangeskos:Concept

10.2.14 dprod:not§

Logical negation on a constraint.

ODRL defines odrl:and and odrl:or on LogicalConstraint but lacks negation. DPROD adds dprod:not following the same pattern.

dprod:not
https://ekgf.org/dprod/spec/develop/not
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domainodrl:LogicalConstraint
rdfs:labelnot
rdfs:range(owl:unionOf: (odrl:Constraint, odrl:LogicalConstraint))

Example:

_:lc a odrl:LogicalConstraint ;
    dprod:not _:c1 .

10.2.15 dprod:objectOfDuty§

Party affected by the duty action.

The party affected by or receiving the result of the duty action. Sub-property of odrl:function for ODRL processor compatibility.

dprod:objectOfDuty
https://ekgf.org/dprod/spec/develop/objectOfDuty
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domainodrl:Duty
rdfs:labelobject
rdfs:rangeodrl:Party
rdfs:subPropertyOfodrl:function

10.2.16 dprod:offerLifecycleStatus§

Where this offer sits in its publication lifecycle — typically drafted, published, withdrawn, or superseded; assigned by the publisher.

Value is any skos:Concept; dprod:DataContractLifecycleStatus is one example concept scheme shipped with DPROD.

dprod:offerLifecycleStatus
https://ekgf.org/dprod/spec/develop/offerLifecycleStatus
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataOffer
rdfs:labeloffer lifecycle status
rdfs:rangeskos:Concept
rdfs:subPropertyOfdprod:lifecycleStatus

10.2.17 dprod:operandSource§

Normalized graph from which an operand reads its value.

Exactly one of dprod:requestSource, dprod:stateSource, or dprod:contextSource. The source is selected before the evaluator performs its single property lookup.

dprod:operandSource
https://ekgf.org/dprod/spec/develop/operandSource
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domainodrl:LeftOperand
rdfs:labeloperand source
rdfs:rangedprod:OperandSource

10.2.18 dprod:outputDataset§

The data that is exposed by the data product through output data services in a way that can be understood and trusted. Depending on the lifecycle of the data product, this may be a stated or inferred relationship aligned with the output ports.

dprod:outputDataset
https://ekgf.org/dprod/spec/develop/outputDataset
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataProduct
rdfs:labeloutput dataset
rdfs:rangedcat:Dataset

10.2.19 dprod:outputPort§

A set of services exposed by a data product to share the generated data in a way that can be understood and trusted.

dprod:outputPort
https://ekgf.org/dprod/spec/develop/outputPort
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindprod:DataProduct
rdfs:labeloutput port
rdfs:rangedcat:DataService

10.2.20 dprod:protocol§

A protocol (possibly one of many options) used to communicate with this data service.

dprod:protocol
https://ekgf.org/dprod/spec/develop/protocol
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindcat:DataService
rdfs:labelprotocol

10.2.21 dprod:request§

Authorization request supplied for one policy evaluation.

Selects the normalized request node used by dprod:requestSource operand bindings.

dprod:request
https://ekgf.org/dprod/spec/develop/request
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domaindprod:EvaluationContext
rdfs:labelrequest
rdfs:rangerdfs:Resource

10.2.22 dprod:schedule§

Reusable schedule governing occurrences associated with a resource.

Links any DPROD or ODRL resource to an identified dprod:Schedule. This property deliberately has no domain: duties, permissions, maintenance arrangements, backup obligations, and other resources may all refer to a schedule. The referring resource determines what the occurrences mean.

dprod:schedule
https://ekgf.org/dprod/spec/develop/schedule
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:labelschedule
rdfs:rangedprod:Schedule

10.2.23 dprod:securitySchemaType§

The security schema type used for authentication and communication with this Data Service.

dprod:securitySchemaType
https://ekgf.org/dprod/spec/develop/securitySchemaType
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:ObjectProperty
rdfs:domaindcat:DataService
rdfs:labelsecurity schema type

10.2.24 dprod:state§

Immutable state-of-the-world snapshot supplied for one policy evaluation.

Selects the normalized snapshot node used by dprod:stateSource operand bindings. The object is supplied by the calling system that builds the evaluation context, never an instruction to query live external state.

dprod:state
https://ekgf.org/dprod/spec/develop/state
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domaindprod:EvaluationContext
rdfs:labelstate
rdfs:rangeprov:Entity

10.2.25 dprod:subjectOfDuty§

Party bearing the duty (must perform the action).

The duty bearer. When omitted, the bearer is the policy's assignee (odrl:assignee), or the requesting agent in a policy without one; provider duties name the provider explicitly. Sub-property of odrl:function for ODRL processor compatibility.

dprod:subjectOfDuty
https://ekgf.org/dprod/spec/develop/subjectOfDuty
RDF predicateValue
rdf:typeowl:ObjectProperty
rdfs:domainodrl:Duty
rdfs:labelsubject
rdfs:rangeodrl:Party
rdfs:subPropertyOfodrl:function

10.3. Datatype properties§

10.3.1 dprod:carriesTimeZone§

Whether expressions in this schedule format embed their own timezone.

Declared by every dprod:ScheduleFormat. When false, each Schedule using the format must declare dprod:scheduleTimeZone; when true, the expression is the timezone authority. This flag lets validation enforce timezone completeness for extension formats without knowing their grammar.

dprod:carriesTimeZone
https://ekgf.org/dprod/spec/develop/carriesTimeZone
RDF predicateValue
rdf:typeowl:DatatypeProperty
rdfs:domaindprod:ScheduleFormat
rdfs:labelcarries timezone
rdfs:rangexsd:boolean

10.3.2 dprod:clock§

Immutable timestamp at which policy evaluation occurs.

dprod:clock
https://ekgf.org/dprod/spec/develop/clock
RDF predicateValue
rdf:typeowl:DatatypeProperty
rdfs:domaindprod:EvaluationContext
rdfs:labelclock
rdfs:rangexsd:dateTime

10.3.3 dprod:deadline§

Time constraint for duty fulfillment.

Supports multiple forms: - xsd:dateTime: absolute deadline (e.g., 2026-12-31T23:59:59Z) - xsd:duration: relative to activation (e.g., P30D, PT24H) For duration: deadline = activationTime + duration. No rdfs:range declared because the range is a union of datatypes; SHACL enforces the allowed types.

dprod:deadline
https://ekgf.org/dprod/spec/develop/deadline
RDF predicateValue
rdf:typeowl:DatatypeProperty
rdfs:domainodrl:Duty
rdfs:labeldeadline

10.3.4 dprod:effectiveDate§

When the offer or contract becomes effective.

dprod:effectiveDate
https://ekgf.org/dprod/spec/develop/effectiveDate
RDF predicateValue
rdf:typeowl:DatatypeProperty
rdfs:domain(owl:unionOf: (dprod:DataOffer, dprod:DataContract))
rdfs:labeleffective date
rdfs:rangexsd:dateTime

10.3.5 dprod:expirationDate§

When the offer or contract expires.

dprod:expirationDate
https://ekgf.org/dprod/spec/develop/expirationDate
RDF predicateValue
rdf:typeowl:DatatypeProperty
rdfs:domain(owl:unionOf: (dprod:DataOffer, dprod:DataContract))
rdfs:labelexpiration date
rdfs:rangexsd:dateTime

10.3.6 dprod:purpose§

A description of the objectives and intended usage of the data product.

dprod:purpose
https://ekgf.org/dprod/spec/develop/purpose
RDF predicateValue
rdf:typerdf:Property
rdf:typeowl:DatatypeProperty
rdfs:domaindprod:DataProduct
rdfs:labelpurpose
rdfs:rangexsd:string

10.3.7 dprod:scheduleExpression§

The single authoritative expression of a schedule.

dprod:scheduleExpression
https://ekgf.org/dprod/spec/develop/scheduleExpression
RDF predicateValue
rdf:typeowl:DatatypeProperty
rdfs:domaindprod:Schedule
rdfs:labelschedule expression
rdfs:rangexsd:string

10.3.8 dprod:scheduleTimeZone§

IANA timezone used to interpret a schedule expression.

Required when the selected schedule format does not carry its own timezone (dprod:carriesTimeZone false). When the format embeds a timezone in the expression, the expression is authoritative and this property, if present, must agree with it.

dprod:scheduleTimeZone
https://ekgf.org/dprod/spec/develop/scheduleTimeZone
RDF predicateValue
rdf:typeowl:DatatypeProperty
rdfs:domaindprod:Schedule
rdfs:labelschedule timezone
rdfs:rangexsd:string

10.4. Named individuals§

10.4.1 Named individual: context source§

Instance of: dprod:OperandSource

Evaluation context node containing built-in agent and clock values.

dprod:contextSource
https://ekgf.org/dprod/spec/develop/contextSource
RDF predicateValue
rdf:typeowl:NamedIndividual
rdf:typedprod:OperandSource
rdfs:labelcontext source

10.4.2 Named individual: request source§

Instance of: dprod:OperandSource

Normalized authorization request node.

The request node built by the calling system: what is being asked for (agent, action, asset) plus every request fact the policies need, flattened onto that node. It is plain RDF, not an odrl:Request.

dprod:requestSource
https://ekgf.org/dprod/spec/develop/requestSource
RDF predicateValue
rdf:typeowl:NamedIndividual
rdf:typedprod:OperandSource
rdfs:labelrequest source

10.4.3 Named individual: state source§

Instance of: dprod:OperandSource

Immutable normalized state-of-the-world snapshot node.

dprod:stateSource
https://ekgf.org/dprod/spec/develop/stateSource
RDF predicateValue
rdf:typeowl:NamedIndividual
rdf:typedprod:OperandSource
rdfs:labelstate source

10.5. Concept schemes§

10.5.1 dprod:DataContractLifecycleStatus§

Optional reference concept scheme covering common statuses (Pending, Active, Fulfilled, Violated). It can be used with authored offer and contract lifecycle-status properties. Implementations are free to use it, extend it, or use a different skos:ConceptScheme entirely. dprod:dutyState is an evaluator-computed state and is not part of the lifecycle-status hierarchy.

dprod:DataContractLifecycleStatus
https://ekgf.org/dprod/spec/develop/DataContractLifecycleStatus
RDF predicateValue
dct:titleDPROD Data Contract Lifecycle Status
rdf:typeskos:ConceptScheme
rdfs:labelDPROD data contract lifecycle status
skos:hasTopConceptdprod:Active
skos:hasTopConceptdprod:Fulfilled
skos:hasTopConceptdprod:Pending
skos:hasTopConceptdprod:Violated

Concepts in this scheme

10.5.1.1 dprod:Active§

Condition satisfied, action required; in force.

dprod:Active
https://ekgf.org/dprod/spec/develop/Active
RDF predicateValue
rdf:typeskos:Concept
rdfs:labelactive
skos:prefLabelactive
skos:topConceptOfdprod:DataContractLifecycleStatus
10.5.1.2 dprod:Fulfilled§

Action performed; obligations complete.

dprod:Fulfilled
https://ekgf.org/dprod/spec/develop/Fulfilled
RDF predicateValue
rdf:typeskos:Concept
rdfs:labelfulfilled
skos:prefLabelfulfilled
skos:topConceptOfdprod:DataContractLifecycleStatus
10.5.1.3 dprod:Pending§

Condition not yet satisfied; not yet in force.

dprod:Pending
https://ekgf.org/dprod/spec/develop/Pending
RDF predicateValue
rdf:typeskos:Concept
rdfs:labelpending
skos:prefLabelpending
skos:topConceptOfdprod:DataContractLifecycleStatus
10.5.1.4 dprod:Violated§

Deadline passed without performance; breached.

dprod:Violated
https://ekgf.org/dprod/spec/develop/Violated
RDF predicateValue
rdf:typeskos:Concept
rdfs:labelviolated
skos:prefLabelviolated
skos:topConceptOfdprod:DataContractLifecycleStatus

10.5.2 dprod:DataProductLifecycleStatus§

An optional reference taxonomy for data product lifecycle statuses. Enterprises may use, extend, or replace this scheme with their own skos:ConceptScheme.

DPROD does not prescribe a closed set of data product lifecycle statuses.

dprod:DataProductLifecycleStatus
https://ekgf.org/dprod/spec/develop/DataProductLifecycleStatus
RDF predicateValue
dct:titleDPROD Data Product Lifecycle Status
rdf:typeskos:ConceptScheme
rdfs:labeldata product lifecycle status
rdfs:seeAlsohttps://edmcouncil.org/wp-content/uploads/2024/03/EDMWebinar_DPSIG_04-30-Presentation.pdf#page=7

10.6. SHACL node shapes§

10.6.1 dprod-contracts-shapes:AgreementShape§

Validates an odrl:Agreement policy as a DPROD policy: it must declare the DPROD contracts profile, contain at least one permission, prohibition or obligation, and name exactly one odrl:assigner and exactly one odrl:assignee.

dprod-contracts-shapes:AgreementShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/AgreementShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelagreement shape
sh:nameAgreement Shape
sh:nodedprod-contracts-shapes:NonEmptyClausesConstraint
sh:propertydprod-contracts-shapes:ProfilePropertyGroup
sh:property(sh:maxCount: 1; sh:message: Agreement must have exactly one assignee.; sh:minCount: 1; sh:path: odrl:assignee)
sh:property(sh:maxCount: 1; sh:message: Agreement must have exactly one assigner.; sh:minCount: 1; sh:path: odrl:assigner)
sh:targetClassodrl:Agreement
rdfs:isDefinedBydprod-contracts-shapes:

10.6.2 dprod-contracts-shapes:AssetCollectionShape§

Restricts an odrl:AssetCollection to explicit membership through odrl:partOf. DPROD does not resolve collections from odrl:source or narrow them with odrl:refinement, so neither may be used.

dprod-contracts-shapes:AssetCollectionShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/AssetCollectionShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelexplicit asset collection shape
sh:property(sh:maxCount: 0; sh:message: DPROD contracts support explicit collection membership only; collection odrl:refinement is not supported.; sh:path: odrl:refinement)
sh:property(sh:maxCount: 0; sh:message: DPROD contracts support explicit collection membership only; odrl:source collection resolution is not supported.; sh:path: odrl:source)
sh:targetClassodrl:AssetCollection
rdfs:isDefinedBydprod-contracts-shapes:

10.6.3 dprod-contracts-shapes:ConstraintShape§

Validates an odrl:Constraint: it must have exactly one odrl:leftOperand, exactly one odrl:operator and at least one odrl:rightOperand.

dprod-contracts-shapes:ConstraintShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/ConstraintShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelconstraint shape
sh:nameConstraint Shape
sh:property(sh:message: Constraint must have a rightOperand.; sh:minCount: 1; sh:path: odrl:rightOperand)
sh:property(sh:maxCount: 1; sh:message: Constraint must have exactly one leftOperand.; sh:minCount: 1; sh:path: odrl:leftOperand)
sh:property(sh:maxCount: 1; sh:message: Constraint must have exactly one operator.; sh:minCount: 1; sh:path: odrl:operator)
sh:targetClassodrl:Constraint
rdfs:isDefinedBydprod-contracts-shapes:

10.6.4 dprod-contracts-shapes:DataContractShape§

Validates a dprod:DataContract: it must declare the DPROD contracts profile, contain at least one permission, prohibition or obligation, name exactly one odrl:assigner (the data provider) and one odrl:assignee (the data consumer), and accept exactly one dprod:DataOffer through dprod:acceptsOffer. It may carry one dprod:contractLifecycleStatus and single xsd:dateTime values for dprod:effectiveDate and dprod:expirationDate.

dprod-contracts-shapes:DataContractShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/DataContractShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labeldata contract shape
sh:nameData Contract Shape
sh:nodedprod-contracts-shapes:NonEmptyClausesConstraint
sh:propertydprod-contracts-shapes:ContractLifecycleStatusPropertyGroup
sh:propertydprod-contracts-shapes:ProfilePropertyGroup
sh:property(sh:maxCount: 1; sh:message: DataContract must have exactly one assignee (data consumer).; sh:minCount: 1; sh:path: odrl:assignee)
sh:property(sh:maxCount: 1; sh:message: DataContract must have exactly one assigner (data provider).; sh:minCount: 1; sh:path: odrl:assigner)
sh:property(sh:class: dprod:DataOffer; sh:maxCount: 1; sh:message: DataContract must reference exactly one DataOffer.; sh:minCount: 1; sh:path: dprod:acceptsOffer)
sh:property(sh:datatype: xsd:dateTime; sh:maxCount: 1; sh:message: effectiveDate, if present, must be a single xsd:dateTime value.; sh:path: dprod:effectiveDate)
sh:property(sh:datatype: xsd:dateTime; sh:maxCount: 1; sh:message: expirationDate, if present, must be a single xsd:dateTime value.; sh:path: dprod:expirationDate)
sh:targetClassdprod:DataContract
rdfs:isDefinedBydprod-contracts-shapes:

10.6.5 dprod-contracts-shapes:DataOfferShape§

Validates a dprod:DataOffer: it must declare the DPROD contracts profile, contain at least one permission, prohibition or obligation, and name exactly one odrl:assigner, the data provider. It may carry one dprod:offerLifecycleStatus and single xsd:dateTime values for dprod:effectiveDate and dprod:expirationDate.

dprod-contracts-shapes:DataOfferShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/DataOfferShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labeldata offer shape
sh:nameData Offer Shape
sh:nodedprod-contracts-shapes:NonEmptyClausesConstraint
sh:propertydprod-contracts-shapes:OfferLifecycleStatusPropertyGroup
sh:propertydprod-contracts-shapes:ProfilePropertyGroup
sh:property(sh:maxCount: 1; sh:message: DataOffer must have exactly one assigner.; sh:minCount: 1; sh:path: odrl:assigner)
sh:property(sh:datatype: xsd:dateTime; sh:maxCount: 1; sh:message: effectiveDate, if present, must be a single xsd:dateTime value.; sh:path: dprod:effectiveDate)
sh:property(sh:datatype: xsd:dateTime; sh:maxCount: 1; sh:message: expirationDate, if present, must be a single xsd:dateTime value.; sh:path: dprod:expirationDate)
sh:targetClassdprod:DataOffer
rdfs:isDefinedBydprod-contracts-shapes:

10.6.6 dprod-contracts-shapes:DutyOnlyPropertiesShape§

Ensures that dprod:deadline, dprod:subjectOfDuty and dprod:objectOfDuty are used only on duties. Their subject must be an odrl:Duty and must not also be an odrl:Permission or odrl:Prohibition, so OWL domain inference cannot silently give a rule a second, ODRL-disjoint rule type.

dprod-contracts-shapes:DutyOnlyPropertiesShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/DutyOnlyPropertiesShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelduty-only properties shape
sh:classodrl:Duty
sh:messagedprod:deadline, dprod:subjectOfDuty and dprod:objectOfDuty are duty-only: the subject must be an odrl:Duty and not an odrl:Permission or odrl:Prohibition.
sh:nameDuty-Only Properties Shape
sh:not(sh:class: odrl:Permission)
sh:not(sh:class: odrl:Prohibition)
sh:targetSubjectsOfdprod:deadline
sh:targetSubjectsOfdprod:objectOfDuty
sh:targetSubjectsOfdprod:subjectOfDuty
rdfs:isDefinedBydprod-contracts-shapes:

10.6.7 dprod-contracts-shapes:DutyShape§

Validates an odrl:Duty: it must have exactly one odrl:action and may carry at most one each of dprod:deadline (an xsd:dateTime or xsd:duration), dprod:schedule (an identified dprod:Schedule), dprod:subjectOfDuty and dprod:objectOfDuty (each an odrl:Party), and dprod:dutyState (a skos:Concept).

dprod-contracts-shapes:DutyShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/DutyShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelduty shape
sh:nameDuty Shape
sh:propertydprod-contracts-shapes:DutyStatePropertyGroup
sh:property(sh:maxCount: 1; sh:message: Deadline must be xsd:dateTime or xsd:duration.; sh:or: ((sh:datatype: xsd:dateTime), (sh:datatype: xsd:duration)); sh:path: dprod:deadline)
sh:property(sh:maxCount: 1; sh:message: Duty must have exactly one action.; sh:minCount: 1; sh:path: odrl:action)
sh:property(sh:class: odrl:Party; sh:maxCount: 1; sh:message: Duty object must be a single odrl:Party.; sh:path: dprod:objectOfDuty)
sh:property(sh:class: dprod:Schedule; sh:maxCount: 1; sh:message: Duty schedule must be a single IRI identifying a dprod:Schedule.; sh:nodeKind: sh:IRI; sh:path: dprod:schedule)
sh:property(sh:class: odrl:Party; sh:maxCount: 1; sh:message: Duty subject must be a single odrl:Party.; sh:path: dprod:subjectOfDuty)
sh:targetClassodrl:Duty
rdfs:isDefinedBydprod-contracts-shapes:

10.6.8 dprod-contracts-shapes:EvaluationContextShape§

Validates a dprod:EvaluationContext, the input to policy evaluation: it must have exactly one dprod:request graph root, exactly one dprod:state snapshot typed as prov:Entity, exactly one dprod:agent identified by an IRI and typed as odrl:Party, and exactly one dprod:clock xsd:dateTime.

dprod-contracts-shapes:EvaluationContextShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/EvaluationContextShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelevaluation context shape
sh:property(sh:class: odrl:Party; sh:maxCount: 1; sh:message: An evaluation context must have exactly one dprod:agent typed as odrl:Party.; sh:minCount: 1; sh:nodeKind: sh:IRI; sh:path: dprod:agent)
sh:property(sh:datatype: xsd:dateTime; sh:maxCount: 1; sh:message: An evaluation context must have exactly one dprod:clock xsd:dateTime.; sh:minCount: 1; sh:path: dprod:clock)
sh:property(sh:maxCount: 1; sh:message: An evaluation context must have exactly one dprod:request graph root.; sh:minCount: 1; sh:nodeKind: sh:BlankNodeOrIRI; sh:path: dprod:request)
sh:property(sh:class: prov:Entity; sh:maxCount: 1; sh:message: An evaluation context must have exactly one immutable dprod:state snapshot, typed as prov:Entity.; sh:minCount: 1; sh:nodeKind: sh:BlankNodeOrIRI; sh:path: dprod:state)
sh:targetClassdprod:EvaluationContext
rdfs:isDefinedBydprod-contracts-shapes:

10.6.9 dprod-contracts-shapes:LeftOperandShape§

Validates every odrl:LeftOperand, whether declared as such or used as the object of odrl:leftOperand. Apart from the built-in operands dprod:currentAgent and odrl:dateTime, each must bind exactly one dprod:operandSource (requestSource, stateSource or contextSource) and exactly one IRI-valued dprod:operandProperty, so the operand resolves to a value in the evaluation context.

dprod-contracts-shapes:LeftOperandShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/LeftOperandShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelleft operand shape
sh:messageEvery left operand must declare exactly one dprod:operandProperty, which must be IRI-valued.
sh:messageEvery left operand must declare exactly one dprod:operandSource: requestSource, stateSource, or contextSource.
sh:nameLeft Operand Shape
sh:or((sh:in: (dprod:currentAgent, odrl:dateTime)), (sh:property: (sh:maxCount: 1; sh:minCount: 1; sh:nodeKind: sh:IRI; sh:path: dprod:operandProperty)))
sh:or((sh:in: (dprod:currentAgent, odrl:dateTime)), (sh:property: (sh:in: (dprod:requestSource, dprod:stateSource, dprod:contextSource); sh:maxCount: 1; sh:minCount: 1; sh:nodeKind: sh:IRI; sh:path: dprod:operandSource)))
sh:targetClassodrl:LeftOperand
sh:targetObjectsOfodrl:leftOperand
rdfs:isDefinedBydprod-contracts-shapes:

10.6.10 dprod-contracts-shapes:LogicalConstraintShape§

Validates an odrl:LogicalConstraint: it must use exactly one of the logical operators odrl:and, odrl:or or dprod:not, each with a single operand list.

dprod-contracts-shapes:LogicalConstraintShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/LogicalConstraintShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labellogical constraint shape
sh:messageLogicalConstraint must have exactly one of: odrl:and, odrl:or, or dprod:not.
sh:nameLogical Constraint Shape
sh:targetClassodrl:LogicalConstraint
sh:xone((sh:property: (sh:maxCount: 1; sh:minCount: 1; sh:path: odrl:and)), (sh:property: (sh:maxCount: 1; sh:minCount: 1; sh:path: odrl:or)), (sh:property: (sh:maxCount: 1; sh:minCount: 1; sh:path: dprod:not)))
rdfs:isDefinedBydprod-contracts-shapes:

10.6.11 dprod-contracts-shapes:NonEmptyClausesConstraint§

Reusable node constraint requiring a DPROD policy to carry at least one rule: an odrl:permission, odrl:prohibition or odrl:obligation. Set, Offer, Agreement, DataOffer and DataContract shapes apply it through sh:node.

dprod-contracts-shapes:NonEmptyClausesConstraint
https://ekgf.org/dprod/spec/develop/contracts/shapes/NonEmptyClausesConstraint
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelnon-empty clauses constraint
sh:messagePolicy must have at least one permission, prohibition, or obligation.
sh:or((sh:property: (sh:minCount: 1; sh:path: odrl:permission)), (sh:property: (sh:minCount: 1; sh:path: odrl:prohibition)), (sh:property: (sh:minCount: 1; sh:path: odrl:obligation)))
rdfs:isDefinedByNot declared in collected sources.

10.6.12 dprod-contracts-shapes:OfferShape§

Validates an odrl:Offer policy as a DPROD policy: it must declare the DPROD contracts profile, contain at least one permission, prohibition or obligation, and name exactly one odrl:assigner, the party making the offer.

dprod-contracts-shapes:OfferShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/OfferShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labeloffer shape
sh:nameOffer Shape
sh:nodedprod-contracts-shapes:NonEmptyClausesConstraint
sh:propertydprod-contracts-shapes:ProfilePropertyGroup
sh:property(sh:maxCount: 1; sh:message: Offer must have exactly one assigner.; sh:minCount: 1; sh:path: odrl:assigner)
sh:targetClassodrl:Offer
rdfs:isDefinedBydprod-contracts-shapes:

10.6.13 dprod-contracts-shapes:PartOfShape§

Validates ODRL collection membership: odrl:partOf must link an odrl:Asset or odrl:AssetCollection to an odrl:AssetCollection, or an odrl:Party or odrl:PartyCollection to an odrl:PartyCollection.

dprod-contracts-shapes:PartOfShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/PartOfShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelODRL collection membership shape
sh:messageodrl:partOf must link an odrl:Asset to an odrl:AssetCollection or an odrl:Party to an odrl:PartyCollection.
sh:or((sh:class: odrl:Asset; sh:property: (sh:class: odrl:AssetCollection; sh:path: odrl:partOf)), (sh:class: odrl:AssetCollection; sh:property: (sh:class: odrl:AssetCollection; sh:path: odrl:partOf)), (sh:class: odrl:Party; sh:property: (sh:class: odrl:PartyCollection; sh:path: odrl:partOf)), (sh:class: odrl:PartyCollection; sh:property: (sh:class: odrl:PartyCollection; sh:path: odrl:partOf)))
sh:targetSubjectsOfodrl:partOf
rdfs:isDefinedBydprod-contracts-shapes:

10.6.14 dprod-contracts-shapes:PartyCollectionShape§

Restricts an odrl:PartyCollection to explicit membership through odrl:partOf. DPROD does not resolve collections from odrl:source or narrow them with odrl:refinement, so neither may be used.

dprod-contracts-shapes:PartyCollectionShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/PartyCollectionShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelexplicit party collection shape
sh:property(sh:maxCount: 0; sh:message: DPROD contracts support explicit collection membership only; collection odrl:refinement is not supported.; sh:path: odrl:refinement)
sh:property(sh:maxCount: 0; sh:message: DPROD contracts support explicit collection membership only; odrl:source collection resolution is not supported.; sh:path: odrl:source)
sh:targetClassodrl:PartyCollection
rdfs:isDefinedBydprod-contracts-shapes:

10.6.15 dprod-contracts-shapes:PermissionShape§

Validates an odrl:Permission rule: it must have exactly one odrl:action and at most one odrl:target. When the target is absent, the permission inherits the policy-level target.

dprod-contracts-shapes:PermissionShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/PermissionShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelpermission shape
sh:namePermission Shape
sh:property(sh:maxCount: 1; sh:message: Permission may have at most one target (inherits from policy if absent).; sh:path: odrl:target)
sh:property(sh:maxCount: 1; sh:message: Permission must have exactly one action.; sh:minCount: 1; sh:path: odrl:action)
sh:targetClassodrl:Permission
rdfs:isDefinedBydprod-contracts-shapes:

10.6.16 dprod-contracts-shapes:PolicyShape§

Validates every odrl:Policy, whatever its subclass, by requiring it to declare odrl:profile with the DPROD contracts profile IRI, so that only policies that opt into DPROD semantics are evaluated by DPROD.

dprod-contracts-shapes:PolicyShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/PolicyShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelpolicy shape
sh:namePolicy Shape
sh:property(sh:hasValue: dprod:contracts/profile/; sh:message: DPROD policies must declare odrl:profile <https://ekgf.org/dprod/spec/develop/contracts/profile/>.; sh:minCount: 1; sh:path: odrl:profile)
sh:targetClassodrl:Policy
rdfs:isDefinedBydprod-contracts-shapes:

10.6.17 dprod-contracts-shapes:ProhibitionShape§

Validates an odrl:Prohibition rule: it must have exactly one odrl:action and at most one odrl:target. When the target is absent, the prohibition inherits the policy-level target.

dprod-contracts-shapes:ProhibitionShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/ProhibitionShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelprohibition shape
sh:nameProhibition Shape
sh:property(sh:maxCount: 1; sh:message: Prohibition may have at most one target (inherits from policy if absent).; sh:path: odrl:target)
sh:property(sh:maxCount: 1; sh:message: Prohibition must have exactly one action.; sh:minCount: 1; sh:path: odrl:action)
sh:targetClassodrl:Prohibition
rdfs:isDefinedBydprod-contracts-shapes:

10.6.18 dprod-contracts-shapes:RejectAnonymousScheduleShape§

Requires every dprod:Schedule to be identified by an IRI, so a schedule can be referenced, shared and audited. Kept separate from the schedule shape so its message applies only to blank-node schedules.

dprod-contracts-shapes:RejectAnonymousScheduleShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectAnonymousScheduleShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject anonymous schedule
sh:messageA Schedule must have an IRI identifier.
sh:nodeKindsh:IRI
sh:targetClassdprod:Schedule
rdfs:isDefinedBydprod-contracts-shapes:

10.6.19 dprod-contracts-shapes:RejectConsequenceShape§

Rejects odrl:consequence, which DPROD contracts do not support: DPROD defines no consequence semantics for unfulfilled duties.

dprod-contracts-shapes:RejectConsequenceShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectConsequenceShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject consequence
sh:property(sh:maxCount: 0; sh:message: DPROD contracts do not support odrl:consequence.; sh:path: odrl:consequence; sh:severity: sh:Violation)
sh:targetSubjectsOfodrl:consequence
rdfs:isDefinedByNot declared in collected sources.

10.6.20 dprod-contracts-shapes:RejectInheritAllowedShape§

Rejects odrl:inheritAllowed, which DPROD contracts do not support: DPROD defines no policy inheritance.

dprod-contracts-shapes:RejectInheritAllowedShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectInheritAllowedShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject inheritAllowed
sh:property(sh:maxCount: 0; sh:message: DPROD contracts do not support odrl:inheritAllowed.; sh:path: odrl:inheritAllowed; sh:severity: sh:Violation)
sh:targetSubjectsOfodrl:inheritAllowed
rdfs:isDefinedByNot declared in collected sources.

10.6.21 dprod-contracts-shapes:RejectInheritFromShape§

Rejects odrl:inheritFrom, which DPROD contracts do not support: DPROD defines no policy inheritance.

dprod-contracts-shapes:RejectInheritFromShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectInheritFromShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject inheritFrom
sh:property(sh:maxCount: 0; sh:message: DPROD contracts do not support odrl:inheritFrom.; sh:path: odrl:inheritFrom; sh:severity: sh:Violation)
sh:targetSubjectsOfodrl:inheritFrom
rdfs:isDefinedByNot declared in collected sources.

10.6.22 dprod-contracts-shapes:RejectMixedLifecycleStatusOnDataContractShape§

Keeps lifecycle statuses separate: a dprod:DataContract uses only dprod:contractLifecycleStatus and must not carry dprod:dataProductLifecycleStatus or dprod:offerLifecycleStatus.

dprod-contracts-shapes:RejectMixedLifecycleStatusOnDataContractShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectMixedLifecycleStatusOnDataContractShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject mixed lifecycle status on data contract shape
sh:property(sh:maxCount: 0; sh:message: DataContract must not use dprod:dataProductLifecycleStatus.; sh:path: dprod:dataProductLifecycleStatus)
sh:property(sh:maxCount: 0; sh:message: DataContract must not use dprod:offerLifecycleStatus.; sh:path: dprod:offerLifecycleStatus)
sh:targetClassdprod:DataContract
rdfs:isDefinedBydprod-contracts-shapes:

10.6.23 dprod-contracts-shapes:RejectMixedLifecycleStatusOnDataOfferShape§

Keeps lifecycle statuses separate: a dprod:DataOffer uses only dprod:offerLifecycleStatus and must not carry dprod:dataProductLifecycleStatus or dprod:contractLifecycleStatus.

dprod-contracts-shapes:RejectMixedLifecycleStatusOnDataOfferShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectMixedLifecycleStatusOnDataOfferShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject mixed lifecycle status on data offer shape
sh:property(sh:maxCount: 0; sh:message: DataOffer must not use dprod:contractLifecycleStatus.; sh:path: dprod:contractLifecycleStatus)
sh:property(sh:maxCount: 0; sh:message: DataOffer must not use dprod:dataProductLifecycleStatus.; sh:path: dprod:dataProductLifecycleStatus)
sh:targetClassdprod:DataOffer
rdfs:isDefinedBydprod-contracts-shapes:

10.6.24 dprod-contracts-shapes:RejectMixedLifecycleStatusOnDataProductShape§

Keeps lifecycle statuses separate: a dprod:DataProduct uses only dprod:dataProductLifecycleStatus and must not carry dprod:offerLifecycleStatus or dprod:contractLifecycleStatus.

dprod-contracts-shapes:RejectMixedLifecycleStatusOnDataProductShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectMixedLifecycleStatusOnDataProductShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labeldata product lifecycle status separation shape
sh:property(sh:maxCount: 0; sh:message: DataProduct must not use dprod:contractLifecycleStatus.; sh:path: dprod:contractLifecycleStatus)
sh:property(sh:maxCount: 0; sh:message: DataProduct must not use dprod:offerLifecycleStatus.; sh:path: dprod:offerLifecycleStatus)
sh:targetClassdprod:DataProduct
rdfs:isDefinedBydprod-contracts-shapes:

10.6.25 dprod-contracts-shapes:RejectObsoleteContractLifecycleStatusSpellingShape§

Rejects the obsolete spelling dprod:contractLifeCycleStatus. A contract's lifecycle status uses dprod:contractLifecycleStatus.

dprod-contracts-shapes:RejectObsoleteContractLifecycleStatusSpellingShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectObsoleteContractLifecycleStatusSpellingShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject obsolete contract lifecycle status spelling
sh:property(sh:maxCount: 0; sh:message: dprod:contractLifeCycleStatus is obsolete; use dprod:contractLifecycleStatus.; sh:path: dprod:contractLifeCycleStatus; sh:severity: sh:Violation)
sh:targetSubjectsOfdprod:contractLifeCycleStatus
rdfs:isDefinedByNot declared in collected sources.

10.6.26 dprod-contracts-shapes:RejectObsoleteDprodMemberOfShape§

Rejects the obsolete dprod:memberOf property. Collection membership uses odrl:partOf.

dprod-contracts-shapes:RejectObsoleteDprodMemberOfShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectObsoleteDprodMemberOfShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject obsolete dprod:memberOf
sh:property(sh:maxCount: 0; sh:message: dprod:memberOf is obsolete; use odrl:partOf.; sh:path: dprod:memberOf; sh:severity: sh:Violation)
sh:targetSubjectsOfdprod:memberOf
rdfs:isDefinedByNot declared in collected sources.

10.6.27 dprod-contracts-shapes:RejectObsoleteDprodPartOfShape§

Rejects the obsolete dprod:partOf property. Collection membership uses odrl:partOf.

dprod-contracts-shapes:RejectObsoleteDprodPartOfShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectObsoleteDprodPartOfShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject obsolete dprod:partOf
sh:property(sh:maxCount: 0; sh:message: dprod:partOf is obsolete; use odrl:partOf.; sh:path: dprod:partOf; sh:severity: sh:Violation)
sh:targetSubjectsOfdprod:partOf
rdfs:isDefinedByNot declared in collected sources.

10.6.28 dprod-contracts-shapes:RejectObsoleteOfferLifecycleStatusSpellingShape§

Rejects the obsolete spelling dprod:offerLifeCycleStatus. An offer's lifecycle status uses dprod:offerLifecycleStatus.

dprod-contracts-shapes:RejectObsoleteOfferLifecycleStatusSpellingShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectObsoleteOfferLifecycleStatusSpellingShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject obsolete offer lifecycle status spelling
sh:property(sh:maxCount: 0; sh:message: dprod:offerLifeCycleStatus is obsolete; use dprod:offerLifecycleStatus.; sh:path: dprod:offerLifeCycleStatus; sh:severity: sh:Violation)
sh:targetSubjectsOfdprod:offerLifeCycleStatus
rdfs:isDefinedByNot declared in collected sources.

10.6.29 dprod-contracts-shapes:RejectObsoleteRecurrenceShape§

Rejects the obsolete dprod:recurrence property on any subject. Recurring obligations are expressed with dprod:schedule referencing an identified dprod:Schedule.

dprod-contracts-shapes:RejectObsoleteRecurrenceShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectObsoleteRecurrenceShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject obsolete recurrence property
sh:property(sh:maxCount: 0; sh:message: dprod:recurrence is obsolete; use dprod:schedule with an identified dprod:Schedule.; sh:path: dprod:recurrence; sh:severity: sh:Violation)
sh:targetSubjectsOfdprod:recurrence
rdfs:isDefinedBydprod-contracts-shapes:

10.6.30 dprod-contracts-shapes:RejectOperandPathShape§

Rejects the obsolete dprod:path property. An operand is bound to a single dprod:operandSource and dprod:operandProperty against a normalized source graph, not to a property path.

dprod-contracts-shapes:RejectOperandPathShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectOperandPathShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelobsolete operand path rejection shape
sh:property(sh:maxCount: 0; sh:message: dprod:path is obsolete; normalize the source graph and use dprod:operandSource plus dprod:operandProperty.; sh:path: dprod:path; sh:severity: sh:Violation)
sh:targetSubjectsOfdprod:path
rdfs:isDefinedBydprod-contracts-shapes:

10.6.31 dprod-contracts-shapes:RejectRemedyShape§

Rejects odrl:remedy, which DPROD contracts do not support: DPROD defines no remedy semantics for violated prohibitions.

dprod-contracts-shapes:RejectRemedyShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectRemedyShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject remedy
sh:property(sh:maxCount: 0; sh:message: DPROD contracts do not support odrl:remedy.; sh:path: odrl:remedy; sh:severity: sh:Violation)
sh:targetSubjectsOfodrl:remedy
rdfs:isDefinedByNot declared in collected sources.

10.6.32 dprod-contracts-shapes:RejectRequestShape§

Rejects odrl:Request policies. DPROD does not yet define Offer-Request-Agreement semantics, so support for requests is deferred.

dprod-contracts-shapes:RejectRequestShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectRequestShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject request policy
sh:sparql(sh:message: DPROD contracts reject odrl:Request because Offer-Request-Agreement semantics are undefined; support is deferred.; sh:select: SPARQL SELECT query 1; sh:severity: sh:Violation)
sh:targetClassodrl:Request
rdfs:isDefinedByNot declared in collected sources.
10.6.32.1 SPARQL query 1§

DPROD contracts reject odrl:Request because Offer-Request-Agreement semantics are undefined; support is deferred.

SELECT $this WHERE { $this a odrl:Request }

10.6.33 dprod-contracts-shapes:RejectRuntimeReferenceShape§

Rejects the obsolete dprod:RuntimeReference class. A runtime value is declared as an odrl:LeftOperand with one dprod:operandSource and one dprod:operandProperty binding.

dprod-contracts-shapes:RejectRuntimeReferenceShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectRuntimeReferenceShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelobsolete runtime reference rejection shape
sh:property(sh:maxCount: 0; sh:message: dprod:RuntimeReference is obsolete; declare an odrl:LeftOperand with one source/property binding.; sh:path: rdf:type; sh:severity: sh:Violation)
sh:targetClassdprod:RuntimeReference
rdfs:isDefinedBydprod-contracts-shapes:

10.6.34 dprod-contracts-shapes:RejectTicketShape§

Rejects odrl:Ticket policies, which DPROD contracts do not support.

dprod-contracts-shapes:RejectTicketShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectTicketShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject ticket policy
sh:sparql(sh:message: DPROD contracts do not support odrl:Ticket.; sh:select: SPARQL SELECT query 1; sh:severity: sh:Violation)
sh:targetClassodrl:Ticket
rdfs:isDefinedByNot declared in collected sources.
10.6.34.1 SPARQL query 1§

DPROD contracts do not support odrl:Ticket.

SELECT $this WHERE { $this a odrl:Ticket }

10.6.35 dprod-contracts-shapes:RejectXoneShape§

Rejects the ODRL exclusive-or logical operator odrl:xone, which DPROD contracts do not support. A logical constraint uses odrl:and, odrl:or or dprod:not.

dprod-contracts-shapes:RejectXoneShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/RejectXoneShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelreject xone operator
sh:property(sh:maxCount: 0; sh:message: DPROD contracts do not support xone operator.; sh:path: odrl:xone; sh:severity: sh:Violation)
sh:targetSubjectsOfodrl:xone
rdfs:isDefinedByNot declared in collected sources.

10.6.36 dprod-contracts-shapes:ScheduleFormatShape§

Validates a dprod:ScheduleFormat, including third-party formats: it must state exactly once, as an xsd:boolean dprod:carriesTimeZone, whether its expressions embed a timezone. The schedule shape relies on this to enforce timezone completeness.

dprod-contracts-shapes:ScheduleFormatShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/ScheduleFormatShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelschedule format shape
sh:property(sh:datatype: xsd:boolean; sh:maxCount: 1; sh:message: A ScheduleFormat must declare dprod:carriesTimeZone so validators can enforce timezone completeness.; sh:minCount: 1; sh:path: dprod:carriesTimeZone)
sh:targetClassdprod:ScheduleFormat
rdfs:isDefinedBydprod-contracts-shapes:

10.6.37 dprod-contracts-shapes:ScheduleReferenceShape§

Validates every use of dprod:schedule: each value must be an IRI that identifies a dprod:Schedule, never a blank node or literal.

dprod-contracts-shapes:ScheduleReferenceShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/ScheduleReferenceShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelschedule reference shape
sh:property(sh:class: dprod:Schedule; sh:message: Schedule references must be IRIs identifying dprod:Schedule resources.; sh:nodeKind: sh:IRI; sh:path: dprod:schedule)
sh:targetSubjectsOfdprod:schedule
rdfs:isDefinedBydprod-contracts-shapes:

10.6.38 dprod-contracts-shapes:ScheduleShape§

Validates a dprod:Schedule: it must conform to exactly one identified dprod:ScheduleFormat through dct:conformsTo and carry exactly one dprod:scheduleExpression string, with an optional IANA dprod:scheduleTimeZone. RFC 5545 expressions must contain DTSTART with a TZID and an RRULE, and a declared timezone must match that TZID. POSIX crontab expressions must have exactly five fields. A schedule whose format carries no timezone must declare one.

dprod-contracts-shapes:ScheduleShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/ScheduleShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelschedule shape
sh:property(sh:maxCount: 1; sh:message: Schedule format must be an identified dprod:ScheduleFormat.; sh:minCount: 1; sh:nodeKind: sh:IRI; sh:or: ((sh:in: (dprod:Rfc5545ScheduleFormat, dprod:PosixCrontabScheduleFormat)), (sh:class: dprod:ScheduleFormat)); sh:path: dct:conformsTo)
sh:property(sh:datatype: xsd:string; sh:maxCount: 1; sh:message: Schedule must have exactly one authoritative expression as an xsd:string.; sh:minCount: 1; sh:path: dprod:scheduleExpression)
sh:property(sh:datatype: xsd:string; sh:maxCount: 1; sh:message: scheduleTimeZone must be one IANA timezone name.; sh:path: dprod:scheduleTimeZone; sh:pattern: ^[A-Za-z0-9._+-]+(/[A-Za-z0-9._+-]+)*$)
sh:sparql(sh:message: POSIX crontab schedules must contain exactly five time fields.; sh:select: SPARQL SELECT query 1)
sh:sparql(sh:message: RFC 5545 schedules must include DTSTART with TZID and RRULE (optionally EXDATE/RDATE lines); RRULE parts must be standard and must not repeat FREQ.; sh:select: SPARQL SELECT query 2)
sh:sparql(sh:message: Schedules whose format carries no timezone must declare one IANA timezone.; sh:select: SPARQL SELECT query 3)
sh:sparql(sh:message: scheduleTimeZone must match the TZID embedded in the RFC 5545 expression.; sh:select: SPARQL SELECT query 4)
sh:targetClassdprod:Schedule
rdfs:isDefinedBydprod-contracts-shapes:
10.6.38.1 SPARQL query 1§

POSIX crontab schedules must contain exactly five time fields.

PREFIX dct: <http://purl.org/dc/terms/>
PREFIX dprod: <https://ekgf.org/dprod/spec/develop/>
SELECT $this
WHERE {
  $this dct:conformsTo dprod:PosixCrontabScheduleFormat ;
        dprod:scheduleExpression ?expression .
  FILTER (
    !REGEX(STR(?expression), "^([^ \t\r\n]+[ \t]+){4}[^ \t\r\n]+$") ||
    CONTAINS(STR(?expression), "\n") ||
    CONTAINS(STR(?expression), "\r")
  )
}
10.6.38.2 SPARQL query 2§

RFC 5545 schedules must include DTSTART with TZID and RRULE (optionally EXDATE/RDATE lines); RRULE parts must be standard and must not repeat FREQ.

PREFIX dct: <http://purl.org/dc/terms/>
PREFIX dprod: <https://ekgf.org/dprod/spec/develop/>
SELECT $this
WHERE {
  $this dct:conformsTo dprod:Rfc5545ScheduleFormat ;
        dprod:scheduleExpression ?expression .
  FILTER (!REGEX(
    STR(?expression),
    "^DTSTART;TZID=[A-Za-z0-9._+-]+(/[A-Za-z0-9._+-]+)*:[0-9]{8}T[0-9]{6}(\r?\n(EXDATE|RDATE)(;[A-Za-z0-9-]+=[^:;\r\n]+)*:[^\r\n]+)*\r?\nRRULE:FREQ=(SECONDLY|MINUTELY|HOURLY|DAILY|WEEKLY|MONTHLY|YEARLY)(;(UNTIL|COUNT|INTERVAL|BYSECOND|BYMINUTE|BYHOUR|BYDAY|BYMONTHDAY|BYYEARDAY|BYWEEKNO|BYMONTH|BYSETPOS|WKST)=[^;\r\n]+)*(\r?\n(EXDATE|RDATE)(;[A-Za-z0-9-]+=[^:;\r\n]+)*:[^\r\n]+)*$"
  ))
}
10.6.38.3 SPARQL query 3§

Schedules whose format carries no timezone must declare one IANA timezone.

PREFIX dct: <http://purl.org/dc/terms/>
PREFIX dprod: <https://ekgf.org/dprod/spec/develop/>
SELECT $this
WHERE {
  $this dct:conformsTo ?format .
  FILTER (?format = dprod:PosixCrontabScheduleFormat ||
          EXISTS { ?format dprod:carriesTimeZone false })
  FILTER NOT EXISTS { $this dprod:scheduleTimeZone ?timeZone }
}
10.6.38.4 SPARQL query 4§

scheduleTimeZone must match the TZID embedded in the RFC 5545 expression.

PREFIX dct: <http://purl.org/dc/terms/>
PREFIX dprod: <https://ekgf.org/dprod/spec/develop/>
SELECT $this
WHERE {
  $this dct:conformsTo dprod:Rfc5545ScheduleFormat ;
        dprod:scheduleExpression ?expression ;
        dprod:scheduleTimeZone ?timeZone .
  BIND (REPLACE(STR(?expression), "^DTSTART;TZID=([^:]+):(.|\n|\r)*$", "$1") AS ?embedded)
  FILTER (STR(?timeZone) != ?embedded)
}

10.6.39 dprod-contracts-shapes:SetShape§

Validates an odrl:Set policy as a DPROD policy: it must declare the DPROD contracts profile and contain at least one permission, prohibition or obligation. A policy-level odrl:target is allowed and is inherited by the policy's rules.

dprod-contracts-shapes:SetShape
https://ekgf.org/dprod/spec/develop/contracts/shapes/SetShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelset shape
sh:nameSet Shape
sh:nodedprod-contracts-shapes:NonEmptyClausesConstraint
sh:propertydprod-contracts-shapes:ProfilePropertyGroup
sh:property(sh:message: Set policy may declare a policy-level target (inherited by rules).; sh:path: odrl:target)
sh:targetClassodrl:Set
rdfs:isDefinedBydprod-contracts-shapes:

10.6.40 dprod-shapes:DataProductShape§

A rational, managed, and governed collection of data, with purpose, value and ownership, meeting consumer needs over a planned life-cycle.

A data product may have input and output ports, code and metadata

dprod-shapes:DataProductShape
https://ekgf.org/dprod/spec/develop/shapes/DataProductShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labeldata product shape
sh:propertydprod-shapes:DataProduct-dataProductLifecycleStatus
sh:propertydprod-shapes:DataProduct-dataProductOwner
sh:propertydprod-shapes:DataProduct-description
sh:propertydprod-shapes:DataProduct-domain
sh:propertydprod-shapes:DataProduct-hasPolicy
sh:propertydprod-shapes:DataProduct-inputDataset
sh:propertydprod-shapes:DataProduct-inputPort
sh:propertydprod-shapes:DataProduct-label
sh:propertydprod-shapes:DataProduct-outputDataset
sh:propertydprod-shapes:DataProduct-outputPort
sh:propertydprod-shapes:DataProduct-purpose
sh:targetClassdprod:DataProduct
rdfs:isDefinedBydprod-shapes:

10.6.41 dprod-shapes:DataServiceShape§

A collection of operations that provides access to one or more datasets or data processing functions.

dprod-shapes:DataServiceShape
https://ekgf.org/dprod/spec/develop/shapes/DataServiceShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labeldata service shape
sh:propertydprod-shapes:DataService-endpointDescription
sh:propertydprod-shapes:DataService-endpointURL
sh:propertydprod-shapes:DataService-isAccessServiceOf
sh:propertydprod-shapes:DataService-protocol
sh:propertydprod-shapes:DataService-securitySchemaType
sh:targetClassdcat:DataService
rdfs:isDefinedBydprod-shapes:

10.6.42 dprod-shapes:DatasetShape§

A collection of data, published or curated by a single source, and available for access or download in one or more representations.

dprod-shapes:DatasetShape
https://ekgf.org/dprod/spec/develop/shapes/DatasetShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labeldataset shape
sh:propertydcat:Dataset-informationSensitivityClassification
sh:propertydprod-shapes:Dataset-conformsTo
sh:propertydprod-shapes:Dataset-description
sh:propertydprod-shapes:Dataset-distribution
sh:propertydprod-shapes:Dataset-hasPolicy
sh:propertydprod-shapes:Dataset-label
sh:propertydprod-shapes:Dataset-type
sh:targetClassdcat:Dataset
rdfs:isDefinedBydprod-shapes:

10.6.43 dprod-shapes:DistributionShape§

A specific representation of a dataset. A dataset might be available in multiple serializations that may differ in various ways, including natural language, media-type or format, schematic organization, temporal and spatial resolution, level of detail or profiles (which might specify any or all of the above).

dprod-shapes:DistributionShape
https://ekgf.org/dprod/spec/develop/shapes/DistributionShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labeldistribution shape
sh:propertydprod-shapes:Distribution-accessService
sh:propertydprod-shapes:Distribution-conformsTo
sh:propertydprod-shapes:Distribution-format
sh:propertydprod-shapes:Distribution-isDistributionOf
sh:targetClassdcat:Distribution
rdfs:isDefinedBydprod-shapes:

10.6.44 dprod-shapes:InformationSensitivityClassificationShape§

A classification of the information within a dataset to indicate the level of control and protection that must be applied.

dprod-shapes:InformationSensitivityClassificationShape
https://ekgf.org/dprod/spec/develop/shapes/InformationSensitivityClassificationShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelinformation sensitivity classification shape
sh:targetClassdprod:InformationSensitivityClassification
rdfs:isDefinedBydprod-shapes:

10.6.45 dprod-shapes:SecuritySchemaTypeShape§

A classification encompassing a set of rules used for authentication and communication.

dprod-shapes:SecuritySchemaTypeShape
https://ekgf.org/dprod/spec/develop/shapes/SecuritySchemaTypeShape
RDF predicateValue
rdf:typesh:NodeShape
rdfs:labelsecurity schema type shape
sh:targetClassdprod:SecuritySchemaType
rdfs:isDefinedBydprod-shapes:

10.7. SHACL property shapes§

10.7.1 dcat:Dataset-informationSensitivityClassification§

More granular classification that indicates the level of control and protection that must be applied to the asset due to the nature of the data and its sensitivity or importance to the organization.

dcat:Dataset-informationSensitivityClassification
http://www.w3.org/ns/dcat#Dataset-informationSensitivityClassification
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldataset information sensitivity classification shape
sh:classdprod:InformationSensitivityClassification
sh:pathdprod:informationSensitivityClassification
rdfs:isDefinedBydprod-shapes:

10.7.2 dprod-contracts-shapes:ContractLifecycleStatusPropertyGroup§

Optional authored lifecycle status for a DataContract. The value must be a skos:Concept; DPROD's scheme is optional and profiles may use an enterprise taxonomy.

dprod-contracts-shapes:ContractLifecycleStatusPropertyGroup
https://ekgf.org/dprod/spec/develop/contracts/shapes/ContractLifecycleStatusPropertyGroup
RDF predicateValue
rdf:typesh:PropertyShape
sh:classskos:Concept
sh:maxCount1
sh:messagecontractLifecycleStatus, if present, must be a single skos:Concept value.
sh:namecontract lifecycle status
sh:nodeKindsh:IRI
sh:pathdprod:contractLifecycleStatus
rdfs:isDefinedByNot declared in collected sources.

10.7.3 dprod-contracts-shapes:DutyStatePropertyGroup§

Optional evaluated state for a Duty. Value must be a skos:Concept; the four DPROD-defined concepts (Pending, Active, Fulfilled, Violated) are the canonical vocabulary that the standard evaluation algorithm transitions between.

dprod-contracts-shapes:DutyStatePropertyGroup
https://ekgf.org/dprod/spec/develop/contracts/shapes/DutyStatePropertyGroup
RDF predicateValue
rdf:typesh:PropertyShape
sh:classskos:Concept
sh:maxCount1
sh:messagedutyState, if present, must be a single skos:Concept value.
sh:nameduty state
sh:nodeKindsh:IRI
sh:pathdprod:dutyState
rdfs:isDefinedByNot declared in collected sources.

10.7.4 dprod-contracts-shapes:OfferLifecycleStatusPropertyGroup§

Optional authored lifecycle status for a DataOffer. The value must be a skos:Concept; DPROD's scheme is optional and profiles may use an enterprise taxonomy.

dprod-contracts-shapes:OfferLifecycleStatusPropertyGroup
https://ekgf.org/dprod/spec/develop/contracts/shapes/OfferLifecycleStatusPropertyGroup
RDF predicateValue
rdf:typesh:PropertyShape
sh:classskos:Concept
sh:maxCount1
sh:messageofferLifecycleStatus, if present, must be a single skos:Concept value.
sh:nameoffer lifecycle status
sh:nodeKindsh:IRI
sh:pathdprod:offerLifecycleStatus
rdfs:isDefinedByNot declared in collected sources.

10.7.5 dprod-contracts-shapes:ProfilePropertyGroup§

The ODRL profile IRI a policy must declare to be recognised as DPROD. Reused by Set, Offer, Agreement, DataOffer, and DataContract shapes.

dprod-contracts-shapes:ProfilePropertyGroup
https://ekgf.org/dprod/spec/develop/contracts/shapes/ProfilePropertyGroup
RDF predicateValue
rdf:typesh:PropertyShape
sh:hasValuedprod:contracts/profile/
sh:messageDPROD policies must declare odrl:profile <https://ekgf.org/dprod/spec/develop/contracts/profile/>.
sh:minCount1
sh:nameprofile
sh:pathodrl:profile
rdfs:isDefinedByNot declared in collected sources.

10.7.6 dprod-shapes:DataProduct-dataProductLifecycleStatus§

The authored development lifecycle status of the data product.

dprod-shapes:DataProduct-dataProductLifecycleStatus
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-dataProductLifecycleStatus
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product lifecycle status shape
sh:classskos:Concept
sh:maxCount1
sh:messagedataProductLifecycleStatus, if present, must be a single skos:Concept value.
sh:pathdprod:dataProductLifecycleStatus
rdfs:isDefinedBydprod-shapes:

10.7.7 dprod-shapes:DataProduct-dataProductOwner§

The agent that is accountable overall for the data product, including managing it through its lifecycle.

dprod-shapes:DataProduct-dataProductOwner
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-dataProductOwner
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product owner shape
sh:classprov:Agent
sh:pathdprod:dataProductOwner
rdfs:isDefinedBydprod-shapes:

10.7.8 dprod-shapes:DataProduct-description§

A free text description of the data product.

dprod-shapes:DataProduct-description
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-description
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product description shape
sh:datatypexsd:string
sh:pathdct:description
rdfs:isDefinedBydprod-shapes:

10.7.9 dprod-shapes:DataProduct-domain§

The business or information area supported by the data product.

The target class is left open

dprod-shapes:DataProduct-domain
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-domain
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product domain shape
sh:pathdprod:domain
rdfs:isDefinedBydprod-shapes:

10.7.10 dprod-shapes:DataProduct-hasPolicy§

An ODRL conformant policy expressing the rights associated with the data product. This is an inferred relationship based on the rights expressed on the individual datasets of the data product.

dprod-shapes:DataProduct-hasPolicy
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-hasPolicy
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product has policy shape
sh:classodrl:Policy
sh:pathodrl:hasPolicy
rdfs:isDefinedBydprod-shapes:

10.7.11 dprod-shapes:DataProduct-inputDataset§

The source data made available to the data product through input data services. Depending on the lifecycle of the data product, this may be a stated or inferred relationship aligned with the input ports.

dprod-shapes:DataProduct-inputDataset
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-inputDataset
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product input dataset shape
sh:classdcat:Dataset
sh:pathdprod:inputDataset
rdfs:isDefinedBydprod-shapes:

10.7.12 dprod-shapes:DataProduct-inputPort§

A set of services exposed by a data product to collect its source data and makes it available for further internal transformation. An input port can receive data from one or more upstream sources in a push (i.e. asynchronous subscription) or pop mode (i.e. synchronous query). Each data product may have one or more input ports.

dprod-shapes:DataProduct-inputPort
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-inputPort
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product input port shape
sh:classdcat:DataService
sh:pathdprod:inputPort
rdfs:isDefinedBydprod-shapes:

10.7.13 dprod-shapes:DataProduct-label§

The name given to the data product.

dprod-shapes:DataProduct-label
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-label
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product label shape
sh:datatypexsd:string
sh:pathrdfs:label
rdfs:isDefinedBydprod-shapes:

10.7.14 dprod-shapes:DataProduct-outputDataset§

The data that is exposed by the data product through output data services in a way that can be understood and trusted. Depending on the lifecycle of the data product, this may be a stated or inferred relationship aligned with the output ports.

dprod-shapes:DataProduct-outputDataset
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-outputDataset
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product output dataset shape
sh:classdcat:Dataset
sh:pathdprod:outputDataset
rdfs:isDefinedBydprod-shapes:

10.7.15 dprod-shapes:DataProduct-outputPort§

A set of services exposed by a data product to share the generated data in a way that can be understood and trusted.

dprod-shapes:DataProduct-outputPort
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-outputPort
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product output port shape
sh:classdcat:DataService
sh:pathdprod:outputPort
rdfs:isDefinedBydprod-shapes:

10.7.16 dprod-shapes:DataProduct-purpose§

A description of the objectives and intended usage of the data product.

dprod-shapes:DataProduct-purpose
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-purpose
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product purpose shape
sh:datatypexsd:string
sh:pathdprod:purpose
rdfs:isDefinedBydprod-shapes:

10.7.17 dprod-shapes:DataProduct-type§

The nature or genre of the data product.

dprod-shapes:DataProduct-type
https://ekgf.org/dprod/spec/develop/shapes/DataProduct-type
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata product description shape
sh:pathdct:type
rdfs:isDefinedBydprod-shapes:

10.7.18 dprod-shapes:DataService-endpointDescription§

A description of the services available via the end-points, including their operations, parameters etc.

dprod-shapes:DataService-endpointDescription
https://ekgf.org/dprod/spec/develop/shapes/DataService-endpointDescription
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata service endpoint description shape
sh:pathdcat:endpointDescription
rdfs:isDefinedBydprod-shapes:

10.7.19 dprod-shapes:DataService-endpointURL§

The root location or primary endpoint of the service.

dprod-shapes:DataService-endpointURL
https://ekgf.org/dprod/spec/develop/shapes/DataService-endpointURL
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata service endpoint URL shape
sh:pathdcat:endpointURL
rdfs:isDefinedBydprod-shapes:

10.7.20 dprod-shapes:DataService-isAccessServiceOf§

The dataset distribution that is being offered through this data service.

dprod-shapes:DataService-isAccessServiceOf
https://ekgf.org/dprod/spec/develop/shapes/DataService-isAccessServiceOf
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata service is access service of shape
sh:classdcat:Distribution
sh:pathdprod:isAccessServiceOf
rdfs:isDefinedBydprod-shapes:

10.7.21 dprod-shapes:DataService-protocol§

A protocol (possibly one of many options) used to communicate with this data service.

dprod-shapes:DataService-protocol
https://ekgf.org/dprod/spec/develop/shapes/DataService-protocol
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata service protocol shape
sh:pathdprod:protocol
rdfs:isDefinedBydprod-shapes:

10.7.22 dprod-shapes:DataService-securitySchemaType§

The security schema type used for authentication and communication with this Data Service.

dprod-shapes:DataService-securitySchemaType
https://ekgf.org/dprod/spec/develop/shapes/DataService-securitySchemaType
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldata service security schema type shape
sh:classdprod:SecuritySchemaType
sh:pathdprod:securitySchemaType
rdfs:isDefinedBydprod-shapes:

10.7.23 dprod-shapes:Dataset-conformsTo§

A model, schema, ontology, view or profile that the dataset conforms to.

dprod-shapes:Dataset-conformsTo
https://ekgf.org/dprod/spec/develop/shapes/Dataset-conformsTo
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldataset conforms to shape
sh:pathdct:conformsTo
rdfs:isDefinedBydprod-shapes:

10.7.24 dprod-shapes:Dataset-description§

Free text description of the dataset.

dprod-shapes:Dataset-description
https://ekgf.org/dprod/spec/develop/shapes/Dataset-description
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldataset distribution shape
sh:datatypexsd:string
sh:pathdct:description
rdfs:isDefinedBydprod-shapes:

10.7.25 dprod-shapes:Dataset-distribution§

An available distribution of the dataset.

dprod-shapes:Dataset-distribution
https://ekgf.org/dprod/spec/develop/shapes/Dataset-distribution
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldataset distribution shape
sh:classdcat:Distribution
sh:pathdcat:distribution
rdfs:isDefinedBydprod-shapes:

10.7.26 dprod-shapes:Dataset-hasPolicy§

An ODRL conformant policy expressing the rights associated with the resource.

dprod-shapes:Dataset-hasPolicy
https://ekgf.org/dprod/spec/develop/shapes/Dataset-hasPolicy
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldataset has policy shape
sh:pathodrl:hasPolicy
rdfs:isDefinedBydprod-shapes:

10.7.27 dprod-shapes:Dataset-label§

The name given to the dataset

dprod-shapes:Dataset-label
https://ekgf.org/dprod/spec/develop/shapes/Dataset-label
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldataset label shape
sh:datatypexsd:string
sh:pathrdfs:label
rdfs:isDefinedBydprod-shapes:

10.7.28 dprod-shapes:Dataset-type§

The type or genre of the dataset.

dprod-shapes:Dataset-type
https://ekgf.org/dprod/spec/develop/shapes/Dataset-type
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldataset type shape
sh:pathdct:type
rdfs:isDefinedBydprod-shapes:

10.7.29 dprod-shapes:Distribution-accessService§

A data service that gives access to the distribution of the dataset.

dprod-shapes:Distribution-accessService
https://ekgf.org/dprod/spec/develop/shapes/Distribution-accessService
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldistribution access service shape
sh:classdcat:DataService
sh:pathdcat:accessService
rdfs:isDefinedBydprod-shapes:

10.7.30 dprod-shapes:Distribution-conformsTo§

The schema that the distribution conforms to that is format and technology dependent.

dprod-shapes:Distribution-conformsTo
https://ekgf.org/dprod/spec/develop/shapes/Distribution-conformsTo
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldistribution conforms to shape
sh:pathdct:conformsTo
rdfs:isDefinedBydprod-shapes:

10.7.31 dprod-shapes:Distribution-format§

The file format of the distribution.

dprod-shapes:Distribution-format
https://ekgf.org/dprod/spec/develop/shapes/Distribution-format
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldistribution format shape
sh:pathdct:format
rdfs:isDefinedBydprod-shapes:

10.7.32 dprod-shapes:Distribution-isDistributionOf§

The dataset that this distribution makes available.

dprod-shapes:Distribution-isDistributionOf
https://ekgf.org/dprod/spec/develop/shapes/Distribution-isDistributionOf
RDF predicateValue
rdf:typesh:PropertyShape
rdfs:labeldistribution is distribution of shape
sh:classdcat:Dataset
sh:pathdprod:isDistributionOf
rdfs:isDefinedBydprod-shapes:

10.8. Profiles§

10.8.1 dprod:contracts/profile/§

Proper ODRL 2.2 profile for deterministic data governance. Uses ODRL terms for standard constructs; adds lifecycle state, deadline, reusable schedules, data contracts, transitive ODRL collection matching, one-hop operand bindings over normalized immutable input nodes, and logical negation.

dprod:contracts/profile/
https://ekgf.org/dprod/spec/develop/contracts/profile/
RDF predicateValue
dct:modified
dct:titleDPROD Data Contracts — ODRL 2.2 Profile Extension
rdf:typeprof:Profile
prof:hasResource(dct:conformsTo: sh:; dct:title: DPROD Contracts SHACL Shapes; rdf:type: prof:ResourceDescriptor; prof:hasArtifact: dprod:dprod-contracts-shapes.ttl; prof:hasRole: role:validation)
prof:hasResource(dct:conformsTo: http://www.w3.org/TR/owl2-overview/; dct:title: DPROD Contracts Ontology; rdf:type: prof:ResourceDescriptor; prof:hasArtifact: dprod:dprod-contracts.ttl; prof:hasRole: role:vocabulary)
prof:hasTokendprod
prof:isProfileOfodrl:core
prof:isProfileOfdprod:profile/
odrl:conflictodrl:prohibit
rdfs:isDefinedByNot declared in collected sources.

10.8.2 dprod:profile/§

DPROD core is an application profile of DCAT 3. It reuses dcat:Catalog, dcat:DataService, dcat:Distribution and dcat:Dataset, and adds dprod:DataProduct with its input and output ports to describe data products in a decentralized way.

dprod:profile/
https://ekgf.org/dprod/spec/develop/profile/
RDF predicateValue
dct:modified
dct:titleDPROD Core — DCAT 3 Application Profile
rdf:typeprof:Profile
prof:hasResource(dct:conformsTo: http://www.w3.org/TR/owl2-overview/; dct:format: text/turtle; dct:title: DPROD Ontology; rdf:type: prof:ResourceDescriptor; prof:hasArtifact: dprod:dprod.ttl; prof:hasRole: role:vocabulary)
prof:hasResource(dct:format: text/html; dct:title: DPROD Specification; rdf:type: prof:ResourceDescriptor; prof:hasArtifact: dprod:specification/; prof:hasRole: role:specification)
prof:hasResource(dct:conformsTo: sh:; dct:format: text/turtle; dct:title: DPROD SHACL Shapes; rdf:type: prof:ResourceDescriptor; prof:hasArtifact: dprod:dprod-shapes.ttl; prof:hasRole: role:validation)
prof:hasResource(dct:conformsTo: https://www.w3.org/TR/json-ld11/; dct:format: application/ld+json; dct:title: DPROD JSON-LD Context; rdf:type: prof:ResourceDescriptor; prof:hasArtifact: dprod:dprod-context.jsonld; prof:hasRole: role:schema)
prof:hasTokendprod-core
prof:isProfileOfhttps://www.w3.org/TR/vocab-dcat-3/
rdfs:isDefinedByNot declared in collected sources.

11. SBA Pool Rates§

Rates for SBA Pool that are Mortgage Backed Securities.

The data product is provided through 3 ports:

  • 1st port: providing all sba pool rates through a query to a database
  • 2nd port: providing only EMEA rates through an api
  • 3rd port: providing only US rates through a Kafka topic
{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://y.com/vocabulary/" }
  ],
  "id": "https://y.com/products/sba-pool-rates",
  "type": "DataProduct",
  "identifier": "sba-pool-rates",
  "title": "SBA Pool Rates",
  "description": "Rates for SBA Pool that are Mortgage Backed Securities. The data product is provided through 3 ports, one of them proving all SBA pool rates through a query to a database, another port providing EMEA only rates through an api and another one providing US only rates through a Kafka topic",
  "dataProductOwner": "https://www.schema.xxx/person/johnSmith",
  "dataProductLifecycleStatus": "https://ekgf.org/dprod/spec/develop/data/lifecycle-status/Consume",
  "outputPort": [
    {
      "id": "https://y.com/service/sba-pool-rate-tabular-prod1",
      "type": "DataService",
      "identifier": "sba-pool-rate-tabular-prod1",
      "ex:environment": "PROD",
      "endpointURL": "jdbc:oracle:thin@sd656-5656-6745.ldn.organiation.com:43534/PGPERG.WORLD",
      "ex:sql": "select * from ...",
      "isAccessServiceOf": {
        "id": "https://y.com/distribution/sba-pool-rate-tabular",
        "type": "Distribution",
        "identifier": "sba-pool-rate-tabular",
        "format": "https://www.iana.org/assignments/media-types/application/sql",
        "isDistributionOf": {
          "id": "https://y.com/dataset/sba-pool-rate",
          "type": "Dataset",
          "identifier": "sba-pool-rate",
          "conformsTo": "https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/MortgageBackedSecurities/SBA-Pool"
        }
      }
    },
    {
      "id": "https://y.com/service/sba-pool-rate-emea-api-prod1",
      "type": "DataService",
      "identifier": "sba-pool-rate-emea-api-prod1",
      "ex:environment": "PROD",
      "endpointURL": "https://example.org/mbs/SBA-Pool-location-emea",
      "conformsTo": "https://y.com/resources/users.yaml",
      "isAccessServiceOf": {
        "id": "https://y.com/distribution/sba-pool-rate-emea-json1",
        "type": "Distribution",
        "identifier": "sba-pool-rate-emea-json1",
        "format": "https://www.iana.org/assignments/media-types/application/json",
        "isDistributionOf": {
          "id": "https://y.com/dataset/sba-pool-rate-emea",
          "type": "Dataset",
          "identifier": "sba-pool-rate-emea",
          "description": "SBA pool data that cover EMEA accessed through an api",
          "spatial": "https://y.com/country/EMEA",
          "conformsTo": "https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/MortgageBackedSecurities/SBA-Pool"
        }
      }
    },
    {
      "id": "https://y.com/service/sba-pool-rate-json-prod1",
      "type": "DataService",
      "identifier": "sba-pool-rate-json-prod1",
      "endpointURL": "kafka://q1.debt.mbs.dataset.us",
      "isAccessServiceOf": {
        "id": "https://y.com/distribution/sba-pool-rate-json",
        "type": "Distribution",
        "identifier": "sba-pool-rate-json",
        "format": "https://www.iana.org/assignments/media-types/application/json",
        "conformsTo": "http://confluent-registry-y/rates-json-schema.json",
        "ex:schemaCompatibility": "backwards compatible",
        "isDistributionOf": {
          "id": "https://y.com/dataset/sba-pool-rate-us",
          "type": "Dataset",
          "identifier": "sba-pool-rate-us",
          "spatial": "https://y.com/country/US",
          "conformsTo": "https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/MortgageBackedSecurities/SBA-Pool"
        }
      }
    }
  ]
}

12. Core Data Product Extensions§

For real world data products, the core data product details will be part of a wider set of metadata that allows the data and data product to be used effectively.

Below is an example of extending the DPROD data product, specifically by adding an agreement to a data product.

In this example, a Data Product Agreement is defined as a subclass of FIBO Agreement.

Definition of a simple Agreement based on FIBO:

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    {
      "fibo": "http://spec.edmcouncil.org/fibo/ontology/FND/Agreements/MetadataFNDAgreements/#",
      "ex": "http://example.org/dp#"
    }
  ],
  "@graph": [
    {
      "id": "ex:isSubjectToAgreement",
      "type": "rdf:Property",
      "label": "Data Product is Subject To FIBO Agreement",
      "rdfs:domain": { "id": "dprod:DataProduct" },
      "rdfs:range": { "id": "ex:DataProductAgreement" }
    },
    {
      "id": "ex:DataProductAgreement",
      "type": "rdfs:Class",
      "label": "DataProductAgreement",
      "rdfs:subClassOf": { "id": "fibo:Agreement" }
    }
  ]
}

A full definition of agreements for data products is likely to be more complex than a single class and may use other information models or their profiles (such as ODRL Policy) or create dedicated definitions.

Below is an example of a Data Product with an associated Data Product Agreement with an effective date.

Using the agreement:

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    {
      "fibo": "http://spec.edmcouncil.org/fibo/ontology/FND/Agreements/MetadataFNDAgreements/#",
      "ex": "http://example.org/dp#"
    }
  ],
  "@graph": [
    {
      "id": "https://y.com/data-product/company-sales",
      "type": "DataProduct",
      "outputPort": {
        "id": "https://y.com/data-product/company-sales/port/2025-sales",
        "type": "DataService",
        "label": "Sales",
        "endpointURL": "https://y.com/data-product/company-sales/port/2025-sales",
        "isAccessServiceOf": {
          "id": "https://y.com/data-product/company-sales/distribution/2025-sales",
          "type": "Distribution",
          "format": "https://www.iana.org/assignments/media-types/application/json",
          "isDistributionOf": {
            "id": "https://y.com/data-product/company-sales/dataset/2025-sales",
            "type": "Dataset",
            "label": "Sales",
            "conformsTo": "https://y.com/schema/Sale"
          }
        }
      },
      "ex:isSubjectToAgreement": { "id": "ex:VVSimpleAgreement" }
    },
    {
      "id": "ex:VVSimpleAgreement",
      "type": "ex:DataProductAgreement",
      "label": "Very Simple Data Product Agreement",
      "fibo:hasEffectiveDate": { "type": "xsd:date", "@value": "2024-08-31" }
    }
  ]
}

13. Data Schema§

The Data Product provides to the consumers (dprod:outputDataset) datasets defined based on DCAT. Datasets should be described (dcat:conforms) with logical models. Logical models describe business entities and their properties (attributes and relationships) with consistent business terms and they are technology independent. Ideally, logical models are based on existing standards eg, FIBO, CDM etc. If a logical model does not exist to describe the dataset, then the dataset publisher can create one, preferably by using SHACL modelling language:

Example of a Dataset conforming to a SHACL Schema:

exampleDataset dcat:conforms exampleSchema:DatasetLogicalSchema.
exampleSchema:DatasetLogicalSchema a owl:Ontology, dct:Standard.

Based on SHACL all entities that exist in the dataset are Node Shapes (1). The attributes of the entities are described as Property Shapes with sh:datatype (2) The relationships are also defined as Property Shaped with sh:class the target class of the relationship (3)

@prefix dc:            <http://purl.org/dc/elements/1.1/> .
@prefix rdfs:          <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh:            <http://www.w3.org/ns/shacl#> .
@prefix xsd:           <http://www.w3.org/2001/XMLSchema#> .
@prefix example:       <https://y.com/schema/> .
@prefix exampleSchema: <https://y.com/schema/logical/> .

# definition of the entity as a Node Shape (1)
example:Account a sh:NodeShape ;
    # human readable name of the entity
    rdfs:label "Account"@en ;
    # description of the entity
    dc:description "An Account is..." ;
    # an account has a property shape Account Age. 
    # Definition of the property shape follows (2)
    sh:property example:Account-AccountAge ; 
    # an account has a property shape Account Branch. 
    # Definition of the property shape follows (3)
    sh:property example:Account-AccountBranch ;     
    rdfs:isDefinedBy exampleSchema:DatasetLogicalSchema;
.

# (2) Definition of the Account-AccountAge property shape
#     describing that an account MUST have exactly one
#     AccountAge attribute and its datatype is integer
example:Account-AccountAge a sh:PropertyShape ;   
    sh:path example:AccountAge ;
    sh:datatype xsd:integer ;
    sh:minCount 1 ;
    sh:maxCount 1 ;
    rdfs:isDefinedBy exampleSchema:DatasetLogicalSchema ;
.

# (3) Definition of the Account-AccountBranch property shape
#     describing than an account must have at least one 
#     Account Branch which is another entity
example:Account-AccountBranch a sh:PropertyShape ;   
    sh:path example:AccountBranch ;
    sh:class  example:Branch ;
    sh:minCount 1 ;
    rdfs:isDefinedBy exampleSchema:DatasetLogicalSchema ;
.

# definition of the entity Branch as a Node Shape (1)
example:Branch a sh:NodeShape ;
    rdfs:label "Branch"@en ;
    dc:description "A Branch is.." ;
    rdfs:isDefinedBy exampleSchema:DatasetLogicalSchema ;
.
{
  "@context": "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
  "id": "https://y.com/products/equity-trade-xxx",
  "type": "DataProduct",
  "title": "Equity Trade XXX",
  "description": "Trade data defining the outcome of equity trades between parties in different stock markets, where the terms are primarily reflected in the tradable product. Additionally, Trade includes attributes such as the trade date, transacting parties, and settlement terms. Some attributes, such as the parties, are already defined in the Party Product and are simply referenced in Trade",
  "outputPort": {
    "id": "https://y.com/service/equity-trade-euronext-paris",
    "type": "DataService",
    "endpointURL": "abfss://datasetsv1@demo.dfs.core.windows.net/demo/full/trade-euronext",
    "isAccessServiceOf": {
      "id": "https://y.com/distribution/equity-trade-euronext-paris-parquet",
      "type": "Distribution",
      "format": "https://www.iana.org/assignments/media-types/application/vnd.apache.parquet",
      "isDistributionOf": {
        "id": "https://y.com/dataset/equity-trade-euronext-paris",
        "type": "Dataset",
        "title": "Equity Trade Euronext Paris XXX",
        "conformsTo": "https://spec.edmcouncil.org/fibo/ontology/BP/Process/FinancialContextAndProcess/SecuritiesTrade"
      }
    }
  }
}

14. Data Quality§

  • DQV is a standard vocabulary to describe data quality and is proposed along with the DCAT vocabulary to measure the quality of datasets.
  • It is based on 3 basic entities: Dimensions, the Metrics that belong to its dimension, and the Measurement for each metric.
  • Data Quality can be computed at different levels, eg. data product, dataset, table, column level etc.
  • Usually, data quality metrics are measured at a dataset level and can inform more higher-level quality metrics at a data product level.
{
  "@context": "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
  "@graph": [
    {
      "id": "https://y.com/derived-quality-measurementA",
      "type": "QualityMeasurement",
      "value": 1,
      "computedOn": { "id": "https://y.com/products/uk-bonds", "type": "DataProduct" },
      "isMeasurementOf": {
        "id": "https://y.com/metric/stale-dataset-count",
        "type": "Metric",
        "label": "Number of stale datasets"
      }
    },
    {
      "id": "https://y.com/quality-measurement-B",
      "type": "QualityMeasurement",
      "value": false,
      "computedOn": {
        "id": "https://y.com/products/uk-bonds/yearlyPrices",
        "type": "Dataset"
      },
      "isMeasurementOf": {
        "id": "https://y.com/metric/expected-distribution-frequency-achieved",
        "type": "Metric",
        "label": "Expected distribution frequency achieved"
      }
    },
    {
      "id": "https://y.com/products/uk-bonds",
      "type": "DataProduct",
      "outputPort": {
        "id": "https://y.com/service/uk-bonds-quality-report",
        "type": "DataService",
        "endpointURL": "https://y.com/uk-bonds/quality-report",
        "isAccessServiceOf": {
          "id": "https://y.com/distribution/uk-bonds-quality-report",
          "type": "Distribution",
          "isDistributionOf": {
            "id": "https://y.com/dataset/uk-bonds-quality-measurements",
            "type": "Dataset",
            "conformsTo": "http://www.w3.org/ns/dqv#QualityMeasurement"
          }
        }
      }
    }
  ]
}

15. Equity Trade§

Example of a data product for Equity Trades.

The Equity Trades Data Product provides two datasets to the consumers: one for trades in London Stock Exchange (LSEG) and one in Euronext.

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://y.com/vocabulary/" }
  ],
  "id": "https://y.com/products/equity-trade-xxx",
  "type": "DataProduct",
  "identifier": "equity-trade-xxx",
  "title": "Equity Trade XXX",
  "description": "Trade data defining the outcome of equity trades between parties in different stock markets, where the terms are primarily reflected in the tradable product. Additionally, Trade includes attributes such as the trade date, transacting parties, and settlement terms. Some attributes, such as the parties, are already defined in the Party Product and are simply referenced in Trade",
  "dataProductOwner": "https://www.schema.xxx/person/AnnTaylor",
  "dataProductLifecycleStatus": "https://ekgf.org/dprod/spec/develop/data/lifecycle-status/Consume",
  "outputPort": [
    {
      "id": "https://y.com/service/equity-trade-euronext-xxx-adls-prod-1",
      "type": "DataService",
      "identifier": "equity-trade-euronext-xxx-tabular-adls-prod",
      "endpointURL": "abfss://datasetsv1@demo.dfs.core.windows.net/demo/full/trade-euronext",
      "description": "Details for accessing storage account",
      "isAccessServiceOf": {
        "id": "https://y.com/distribution/equity-trade-euronext-xxx-tabular",
        "type": "Distribution",
        "identifier": "equity-trade-euronext-xxx-tabular",
        "format": "https://www.iana.org/assignments/media-types/application/vnd.apache.parquet",
        "conformsTo": "https://cdm.finos.org/docs/event-model",
        "isDistributionOf": {
          "id": "https://y.com/dataset/equity-trade-euronext-paris",
          "type": "Dataset",
          "identifier": "equity-trade-euronext-paris-xxx",
          "title": "Equity Trade Euronext Paris XXX",
          "ex:datasetOwner": { "id": "https://www.schema.xxx/person/JohnBarks" },
          "conformsTo": "https://cdm.finos.org/docs/event-model"
        }
      }
    },
    {
      "id": "https://y.com/service/equity-trade-lseg-xxx-adls-prod-1",
      "type": "DataService",
      "identifier": "equity-trade-lseg-xxx-tabular-adls-prod",
      "endpointURL": "abfss://datasetsv1@demo.dfs.core.windows.net/demo/full/trade-lseg",
      "description": "Details for accessing storage account",
      "isAccessServiceOf": {
        "id": "https://y.com/distribution/equity-trade-lseg-xxx-tabular",
        "type": "Distribution",
        "identifier": "equity-trade-lseg-xxx-tabular",
        "format": "https://www.iana.org/assignments/media-types/application/vnd.apache.parquet",
        "conformsTo": "https://cdm.finos.org/docs/event-model",
        "isDistributionOf": {
          "id": "https://y.com/dataset/equity-trade-lseg-xxx",
          "type": "Dataset",
          "identifier": "equity-trade-lseg-xxx",
          "title": "Equity Trade LSEG XXX",
          "conformsTo": "https://cdm.finos.org/docs/event-model"
        }
      }
    }
  ]
}

16. Data Rights§

ODRL is a W3C standard to describe rights and entitlements. Based on ODRL, data product and dataset publishers can describe policies in a consistent, standard and machine-readable manner. Policies contain permissions and prohibitions on specific actions that are required to be met by stakeholders.

In addition, policies may be limited by constraints (eg. temporal or geographical constraints) and duties (eg. payments) that may be imposed on the permissions.

Policies and their permitted or prohibited actions can be described at different levels, eg. a policy can target a data product, a dataset, a data service or even a column.

Sophisticated engines should interpret and enforce the ODRL policies at the appropriate level eg.:

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .
@prefix examplePolicy: <https://data.org/policy/> .
@prefix exampleProduct: <https://data.org/data-product/> .
@prefix exampleDataset: <https://data.org/dataset/> .

examplePolicy:A odrl:target exampleProduct:ProductA .
examplePolicy:B odrl:target exampleDataset:DatasetA1 .

An example of an agreement follows, that describes permission to use all the datasets of the product if the user is working inside EMEA or APAC:

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "reg": "https://www.region.taxonomy/v/1/" }
  ],
  "id": "https://data.org/policy/examplePolicyA",
  "type": "Agreement",
  "permission": [
    {
      "target": { "id": "https://data.org/data-product/equity-trade-xxx" },
      "action": "use",
      "assignee": {
        "id": "https://example.org/DataDepartment/emea-and-apac-staff",
        "type": "PartyCollection",
        "refinement": [
          {
            "leftOperand": "odrl:spatial",
            "operator": "isAnyOf",
            "rightOperand": [
              { "id": "reg:EMEA" },
              { "id": "reg:APAC" }
            ]
          }
        ]
      }
    }
  ]
}
{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "reg": "https://www.region.taxonomy/v/1/" }
  ],
  "id": "https://data.org/policy/56456df-dfg-34535345-5545",
  "type": "Agreement",
  "permission": [
    {
      "target": { "id": "https://data.org/data-product/equity-trade-xxx" },
      "assigner": { "id": "https://schema.org/person/AdamSmith" },
      "assignee": {
        "id": "https://example.org/DataDepartment/emea-and-apac-staff",
        "type": "PartyCollection",
        "source": { "id": "https://example.org/DataDepartment" },
        "refinement": [
          {
            "leftOperand": "odrl:spatial",
            "operator": "isAnyOf",
            "rightOperand": [
              { "id": "reg:EMEA" },
              { "id": "reg:APAC" }
            ],
            "description": "Permission to read all the datasets of the product if the user is working inside EMEA or APAC"
          }
        ]
      },
      "action": "use"
    }
  ]
}

17. Observability Ports§

An Observability Port is a designated interface or endpoint in a system or application specifically used for monitoring and diagnostic purposes. It allows external tools or services to collect and analyze data related to the system's performance, health, and behaviour. By exposing metrics, logs, and traces through this port, administrators and developers can gain insights into the system's state, troubleshoot issues, and ensure it operates efficiently and reliably.

17.1 Defining Observability Ports in DPROD§

DPROD has a schema-first design. The first thing to do is define a schema for the logging information. It could be a schema based on OpenTelemetry, but this uses RLOG (which is a semantic ontology for logging).

To find the Observability Port, query the ports to identify the ones that return an RLOG:Entry:

outputPort >> isAccessServiceOf >> isDistributionOf >> conformsTo >> rlog:Entry

17.2 Example Data Product with Observability Port§

One can see that the example data product has two ports, one with the data and one with the logging. This query will return the URI of the port that returns logging data: https://y.com/uk-bonds/observability-port.

Here is an example of a data product with an observability port:

{
  "@context": "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
  "@graph": [
    {
      "id": "https://y.com/data-product/uk-bonds",
      "type": "DataProduct",
      "inputPort": [
        {
          "id": "https://y.com/data-product/uk-bonds/port/2024-data",
          "type": "DataService"
        }
      ],
      "outputPort": [
        {
          "id": "https://y.com/data-product/uk-bonds/port/2024-observability",
          "type": "DataService",
          "label": "Observability Port",
          "endpointURL": "https://y.com/data-product/uk-bonds/port/2024-observability",
          "isAccessServiceOf": {
            "type": "Distribution",
            "format": "https://www.iana.org/assignments/media-types/application/json",
            "isDistributionOf": {
              "id": "https://y.com/data-product/uk-bonds/dataset/2024-observability",
              "type": "Dataset",
              "conformsTo": "https://y.com/schema/ObservabilityLog"
            }
          }
        },
        {
          "id": "https://y.com/data-product/uk-bonds/port/2024-data",
          "type": "DataService",
          "label": "Data Port",
          "endpointURL": "https://y.com/data-product/uk-bonds/port/2024-data",
          "isAccessServiceOf": {
            "type": "Distribution",
            "format": "https://www.iana.org/assignments/media-types/application/json",
            "isDistributionOf": {
              "id": "https://y.com/data-product/uk-bonds/dataset/2024-data",
              "type": "Dataset",
              "conformsTo": "https://y.com/schema/Data"
            }
          }
        }
      ]
    }
  ]
}

Given that the schema defines the class for an observation, it can be used to find all observability ports on data product like this:

[https://y.com/data-product/uk-bonds/port/2024-observability] >> isAccessServiceOf >> isDistributionOf >> conformsTo >> https://y.com/schema/ObservabilityLog

In Linked Data a SPARQL query would do that:

SELECT ?port
WHERE
{ 
  ?port a dcat:DataService .
  ?port (dprod:isAccessServiceOf/dprod:isDistributionOf)/dcat:conformsTo rlog:Entry
}

This query will return the URI of the port that provides logging data: https://y.com/data-product/uk-bonds/port/2024-observability.

18. Data Lineage§

It is important to be able to trace the lineage of data. Within DPROD, this can be done in two ways: at a high level from one data product to another and, if desired, at the more detailed level of the underlying datasets.

18.1 High Level Lineage: Between Data Products§

Data products have input and output ports, and one data product’s input port will point to another data product’s output port.

This allows a user to query the lineage. The data products all have URLs as identifiers, and properties all connect to each other, so a query can walk from one data product to the downstream data products that feed it.

One can follow the path that leads from one data product to another like this:

Data Product >> inputPort >> isAccessServiceOf >> isDistributionOf >> Input Data Product 

The following example data has three data products that connect to each other through their input and output ports:

{
  "@context": "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
  "@graph": [
    {
      "id": "https://y.com/data-product/company-finance",
      "type": "DataProduct",
      "inputPort": [
        {
          "id": "https://y.com/data-product/company-sales/port/2025-sales",
          "type": "DataService"
        },
        {
          "id": "https://y.com/data-product/company-hr/port/2025-payroll",
          "type": "DataService"
        }
      ],
      "outputPort": {
        "id": "https://y.com/data-product/company-sales/port/2025-balance-sheet",
        "type": "DataService",
        "label": "Balance Sheet",
        "endpointURL": "https://y.com/data-product/company-sales/port/2025-c",
        "isAccessServiceOf": {
          "type": "Distribution",
          "format": "https://www.iana.org/assignments/media-types/application/json",
          "isDistributionOf": {
            "id": "https://y.com/data-product/company-sales/dataset/2025-balance-sheet",
            "type": "Dataset",
            "conformsTo": "https://y.com/schema/BalanceSheet"
          }
        }
      }
    },
    {
      "id": "https://y.com/data-product/company-sales",
      "type": "DataProduct",
      "outputPort": {
        "id": "https://y.com/data-product/company-sales/port/2025-sales",
        "type": "DataService",
        "label": "Sales",
        "endpointURL": "https://y.com/data-product/company-sales/port/2025-sales",
        "isAccessServiceOf": {
          "type": "Distribution",
          "format": "https://www.iana.org/assignments/media-types/application/json",
          "isDistributionOf": {
            "id": "https://y.com/data-product/company-sales/dataset/2025-sales",
            "type": "Dataset",
            "label": "Sales",
            "conformsTo": "https://y.com/schema/Sale"
          }
        }
      }
    },
    {
      "id": "https://y.com/data-product/company-hr",
      "type": "DataProduct",
      "outputPort": {
        "id": "https://y.com/data-product/company-sales/port/2025-payroll",
        "type": "DataService",
        "label": "Payroll",
        "endpointURL": "https://y.com/data-product/company-hr/port/2025-payroll",
        "isAccessServiceOf": {
          "type": "Distribution",
          "format": "https://www.iana.org/assignments/media-types/text/csv",
          "isDistributionOf": {
            "id": "https://y.com/data-product/company-sales/dataset/2025-payroll",
            "type": "Dataset",
            "label": "Payroll",
            "conformsTo": "https://y.com/schema/Payroll"
          }
        }
      }
    }
  ]
}

Given this example data, starting at the data product https://y.com/data-product/company-finance, one could walk the relationships to find the input data products that feed it:

https://y.com/data-product/company-finance >> 
    :inputPort >> 
    :isAccessServiceOf >> 
    :isDistributionOf >> [
        https://y.com/data-product/company-sales, 
        https://y.com/data-product/company-hr
    ]

In Linked Data, this would use a query such as:

PREFIX :      <https://y.com/data-product/>
PREFIX rdfs:  <http://www.w3.org/2000/01/rdf-schema#>
PREFIX dprod: <https://ekgf.org/dprod/spec/develop/>

SELECT DISTINCT ?input
WHERE
{ 
  :company-finance dprod:inputPort ?inputPort .
  ?inputPort dprod:isAccessServiceOf/dprod:isDistributionOf/rdfs:label ?input .
}

18.2 Detailed Level: Between Datasets§

To track lineage at a more granular level, one can also use PROV (https://www.w3.org/TR/prov-o/) at the dataset level.

@prefix dap:     <https://data.csiro.au/dap/> .
@prefix dcat:    <http://www.w3.org/ns/dcat#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix prov:    <http://www.w3.org/ns/prov#> .
@prefix rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs:    <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd:     <http://www.w3.org/2001/XMLSchema#> .

dap:atnf-P366-2003SEPT
  rdf:type dcat:Dataset ;
  dcterms:bibliographicCitation "Burgay, M; McLaughlin, M; Kramer, M; Lyne, A; Joshi, B; Pearce, G; D'Amico, N; Possenti, A; Manchester, R; Camilo, F (2017): Parkes observations for project P366 semester 2003SEPT. v1. CSIRO. Data Collection. https://doi.org/10.4225/08/598dc08d07bb7" ;
  dcterms:title "Parkes observations for project P366 semester 2003SEPT"@en ;
  dcat:landingPage <https://data.csiro.au/dap/landingpage?pid=csiro:P366-2003SEPT> ;
  prov:wasGeneratedBy dap:P366 ;
  .

dap:P366
  rdf:type prov:Activity ;
  dcterms:type <http://dbpedia.org/resource/Observation> ;
  prov:startedAtTime "2000-11-01"^^xsd:date ;
  prov:used dap:Parkes-radio-telescope ;
  prov:wasInformedBy dap:ATNF ;
  rdfs:label "P366 - Parkes multibeam high-latitude pulsar survey"@en ;
  rdfs:seeAlso <https://doi.org/10.1111/j.1365-2966.2006.10100.x> ;
  .

See: https://www.w3.org/TR/vocab-dcat-3/#examples-dataset-provenance.

19. Collections and Target Inheritance§

Two ODRL mechanisms keep large contracts short, and DPROD gives both a precise meaning.

Target inheritance. A rule with no odrl:target of its own inherits every target of its policy. The bundle offer names three products at policy level. Its blanket rules, read permitted and redistribution prohibited, say nothing about targets and so apply to all three. The aggregation permission is about the bundle as a whole, so it names that asset explicitly. The contract names the same three targets, so its read permission covers them too; without them, a rule with no target would apply to any asset.

Collections. Assets and parties are grouped with odrl:partOf into an odrl:AssetCollection or odrl:PartyCollection, and a rule addressed to a collection applies to every member. DPROD evaluates membership over the transitive closure of odrl:partOf. So the contract's assignee is the whole Trading Division and both of its teams are covered, and a rule on the reference data collection covers the country-codes table inside it. Only explicit membership is supported; ODRL's derived collections (odrl:source with odrl:refinement) are rejected by the profile.

Membership is stated on the member, pointing up at its collection, so the members cannot be nested inside the contract. This is the one example that needs a @graph: the contract first, then the collection memberships.

A contract accepts exactly one offer. If a consumer wants a subset of what a provider publishes, the provider publishes an offer for that subset, or a multi-target offer such as this one.

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "@graph": [
    {
      "id": "ex:tradingDivisionBundle2026",
      "type": "DataContract",
      "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
      "assigner": "ex:dataPlatformTeam",
      "assignee": "ex:tradingDivision",
      "target": ["ex:marketPrices", "ex:referenceData", "ex:riskMetrics"],
      "permission": {
        "type": "Permission",
        "label": "Every team in the Trading Division may read",
        "assignee": "ex:tradingDivision",
        "action": "read"
      },
      "acceptsOffer": {
        "id": "ex:marketDataBundle",
        "type": "DataOffer",
        "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
        "assigner": "ex:dataPlatformTeam",
        "target": ["ex:marketPrices", "ex:referenceData", "ex:riskMetrics"],
        "permission": [
          {
            "type": "Permission",
            "label": "Read: applies to all three targets",
            "action": "read"
          },
          {
            "type": "Permission",
            "label": "Aggregate: applies to the bundle as a whole",
            "action": "aggregate",
            "target": "ex:marketDataBundleAsset"
          }
        ],
        "prohibition": {
          "type": "Prohibition",
          "label": "No redistribution: applies to all three targets",
          "action": "distribute"
        }
      }
    },
    { "id": "ex:tradingDivision", "type": "PartyCollection" },
    {
      "id": "ex:tradingDataTeam",
      "type": "Party",
      "partOf": "ex:tradingDivision"
    },
    {
      "id": "ex:analyticsTeam",
      "type": "Party",
      "partOf": "ex:tradingDivision"
    },
    { "id": "ex:referenceData", "type": "AssetCollection" },
    {
      "id": "ex:countryCodes",
      "type": "Asset",
      "partOf": "ex:referenceData"
    }
  ]
}

20. Data Offer and Contract§

A data contract in DPROD is an ODRL 2.2 policy. The provider of a data product publishes a dprod:DataOffer (an odrl:Offer) stating what it commits to deliver, what consumers may do with the data, and what they may not do. A consumer accepts that offer, and the acceptance is recorded as a dprod:DataContract (an odrl:Agreement) that names both parties and points at the offer through dprod:acceptsOffer.

Below, the Trading Data Team offers its market prices with two commitments of its own, a delivery every 15 minutes with a 5-minute deadline and conformance to a published schema, and one duty the consumer takes on, a monthly usage report. Consumers may display and derive from the data but may not redistribute it. The Analytics Team has accepted the offer for 2026.

Three things are worth noticing:

  • The provider's duties name their bearer. dprod:subjectOfDuty says who must act. The usage report has no subject in the offer because the consumer is not yet known; it becomes the consumer's duty when the contract is made.
  • Rules inherit the offer's target. Only the schema-conformance duty states its own odrl:target, because it is about the schema rather than the data.
  • The contract binds the named consumer. It restates the rules that now apply to the Analytics Team, each with an odrl:assignee; a contract must carry at least one rule of its own.
  • The offer is shown nested inside the contract so the whole agreement can be read top to bottom. In practice the provider publishes the offer once and each contract refers to it by its identifier.

ODRL terms are written as plain names, just as DCAT terms are in a data product description. The simple context knows that an action, an operator or a status names a vocabulary term, so "action": "display" denotes odrl:display without any wrapping. Only values whose datatype the context cannot know, such as a deadline that may be a duration or a timestamp, carry an explicit type.

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:tradingMarketData2026",
  "type": "DataContract",
  "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
  "assigner": "ex:tradingDataTeam",
  "assignee": "ex:analyticsTeam",
  "target": "ex:marketPrices",
  "contractLifecycleStatus": "Active",
  "effectiveDate": "2026-01-15T00:00:00Z",
  "expirationDate": "2026-12-31T23:59:59Z",
  "permission": {
    "type": "Permission",
    "assignee": "ex:analyticsTeam",
    "action": "display"
  },
  "prohibition": {
    "type": "Prohibition",
    "assignee": "ex:analyticsTeam",
    "action": "distribute"
  },
  "acceptsOffer": {
    "id": "ex:marketDataFeed",
    "type": "DataOffer",
    "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
    "assigner": "ex:tradingDataTeam",
    "target": "ex:marketPrices",
    "offerLifecycleStatus": "Active",
    "obligation": [
      {
        "type": "Duty",
        "subjectOfDuty": "ex:tradingDataTeam",
        "action": "ex:deliver",
        "schedule": {
          "id": "ex:every15Minutes",
          "type": "Schedule",
          "conformsTo": "dprod:Rfc5545ScheduleFormat",
          "scheduleExpression": "DTSTART;TZID=Europe/London:20260101T000000\nRRULE:FREQ=MINUTELY;INTERVAL=15"
        },
        "deadline": { "@value": "PT5M", "type": "xsd:duration" }
      },
      {
        "type": "Duty",
        "subjectOfDuty": "ex:tradingDataTeam",
        "action": "ex:conformTo",
        "target": "ex:marketDataSchema"
      },
      {
        "type": "Duty",
        "action": "ex:reportUsage",
        "schedule": {
          "id": "ex:monthlyOnThe1st",
          "type": "Schedule",
          "conformsTo": "dprod:Rfc5545ScheduleFormat",
          "scheduleExpression": "DTSTART;TZID=Europe/London:20260101T000000\nRRULE:FREQ=MONTHLY;BYMONTHDAY=1"
        },
        "deadline": { "@value": "P5D", "type": "xsd:duration" }
      }
    ],
    "permission": [
      { "type": "Permission", "action": "display" },
      { "type": "Permission", "action": "derive" }
    ],
    "prohibition": [
      { "type": "Prohibition", "action": "distribute" }
    ]
  }
}

21. Data Use Policy§

Not every rule about data is a contract between two parties. An organisation also has standing rules: who may read employee data and for what purpose, what must be logged, what may never be done. These are expressed as an odrl:Set, an ODRL policy with no assigner or assignee, and evaluated by the same DPROD evaluator as a contract. The profile's fixed conflict rule applies: a prohibition always wins over a permission.

The HR data access policy shows the constraint patterns a policy writer typically needs:

  • Purpose, using ODRL's own odrl:purpose operand.
  • Role, through the permission's odrl:assignee.
  • Classification, so the audit-logging duty applies only to confidential data. Its target is the access log, not the employee data, so it is stated explicitly.
  • Set membership, with odrl:isNoneOf and a list of values.
  • Logical combination. An odrl:LogicalConstraint with odrl:and, and DPROD's dprod:not for negation: model training is forbidden unless the environment is the isolated one.
  • Retention, as a duty to delete once the retention period is exceeded.

Every operand a policy reads must say where its value comes from. Each is declared the first time it is used, with one dprod:operandSource and one dprod:operandProperty; later uses just name it.

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:hrDataAccessPolicy",
  "type": "Set",
  "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
  "target": "ex:employeeData",
  "permission": [
    {
      "type": "Permission",
      "label": "HR Analytics may read, for analytics",
      "assignee": "ex:hrAnalyticsTeam",
      "action": "read",
      "constraint": {
        "type": "Constraint",
        "leftOperand": {
          "id": "odrl:purpose",
          "operandSource": "requestSource",
          "operandProperty": "odrl:purpose"
        },
        "operator": "eq",
        "rightOperand": { "id": "ex:analytics" }
      }
    },
    {
      "type": "Permission",
      "label": "Compliance may read, for compliance",
      "assignee": "ex:complianceTeam",
      "action": "read",
      "constraint": {
        "type": "Constraint",
        "leftOperand": "odrl:purpose",
        "operator": "eq",
        "rightOperand": { "id": "ex:compliance" }
      }
    }
  ],
  "obligation": [
    {
      "type": "Duty",
      "label": "Access to confidential data must be logged within an hour",
      "action": "ex:log",
      "target": "ex:accessLog",
      "constraint": {
        "type": "Constraint",
        "leftOperand": {
          "id": "ex:classification",
          "operandSource": "requestSource",
          "operandProperty": "ex:classification"
        },
        "operator": "eq",
        "rightOperand": { "id": "ex:confidential" }
      },
      "deadline": { "@value": "PT1H", "type": "xsd:duration" }
    },
    {
      "type": "Duty",
      "label": "Delete after 7 years",
      "action": "delete",
      "constraint": {
        "type": "Constraint",
        "leftOperand": {
          "id": "ex:retentionPeriod",
          "operandSource": "requestSource",
          "operandProperty": "ex:retentionPeriod"
        },
        "operator": "gt",
        "rightOperand": { "@value": "P7Y", "type": "xsd:duration" }
      }
    }
  ],
  "prohibition": [
    {
      "type": "Prohibition",
      "label": "No external sharing",
      "action": "distribute"
    },
    {
      "type": "Prohibition",
      "label": "No use outside production or staging",
      "action": "use",
      "constraint": {
        "type": "Constraint",
        "leftOperand": {
          "id": "ex:environment",
          "operandSource": "requestSource",
          "operandProperty": "ex:environment"
        },
        "operator": "isNoneOf",
        "rightOperand": {
          "@list": [
            { "id": "ex:production" },
            { "id": "ex:staging" }
          ]
        }
      }
    },
    {
      "type": "Prohibition",
      "label": "No model training, unless in an isolated environment",
      "action": "use",
      "constraint": {
        "type": "LogicalConstraint",
        "and": {
          "@list": [
            {
              "type": "Constraint",
              "leftOperand": {
                "id": "ex:processingMode",
                "operandSource": "requestSource",
                "operandProperty": "ex:processingMode"
              },
              "operator": "eq",
              "rightOperand": { "id": "ex:modelTraining" }
            },
            {
              "type": "LogicalConstraint",
              "not": {
                "type": "Constraint",
                "leftOperand": "ex:environment",
                "operator": "eq",
                "rightOperand": { "id": "ex:isolated" }
              }
            }
          ]
        }
      }
    }
  ]
}

22. Evaluation Context§

DPROD is a specification, not a program. It defines what a policy means and what a conformant evaluator must do with it, but nothing in DPROD receives a request or returns a decision. An evaluator is an external program, written or chosen by an implementer, that follows this specification to answer one question: may this agent perform this action on this asset, now, under these policies?

A decision is made in three steps:

  1. The calling system (for example an application, an API gateway or a data platform) needs a decision. It gathers every fact the policies need and builds one immutable dprod:EvaluationContext with four parts: the request, a state-of-the-world snapshot, the requesting agent and the clock.
  2. The evaluator receives the policies and that context. It reads nothing else: no live graph, no database and no network.
  3. It resolves each operand with a single lookup, applies the policies and returns a decision. A missing, multiple or wrongly typed value is an evaluation error, never a quietly false constraint.

Each odrl:LeftOperand a policy uses says where in the context its value comes from with dprod:operandSource, and which single property to read there with dprod:operandProperty:

  • requestSource reads from the request: a node built by the calling system to describe what is being asked for (who, which action, which asset) together with any facts about the request that policies need. It is plain RDF, not an odrl:Request.
  • stateSource reads from the state snapshot: facts about the world at the time of the request, such as whether the market is open, frozen by the calling system as a prov:Entity so their provenance can be kept.
  • contextSource reads from the context itself, which is how the built-in agent and clock operands work.

This policy permits internal recipients to use market prices while the market is open. ex:recipientType is read from the request and ex:marketOpen from the state snapshot:

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:marketHoursPolicy",
  "type": "Set",
  "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
  "target": "ex:marketPrices",
  "permission": {
    "type": "Permission",
    "action": "use",
    "constraint": {
      "type": "LogicalConstraint",
      "and": {
        "@list": [
          {
            "type": "Constraint",
            "leftOperand": {
              "id": "ex:recipientType",
              "operandSource": "requestSource",
              "operandProperty": "ex:recipientType"
            },
            "operator": "eq",
            "rightOperand": { "id": "ex:internal" }
          },
          {
            "type": "Constraint",
            "leftOperand": {
              "id": "ex:marketOpen",
              "operandSource": "stateSource",
              "operandProperty": "ex:marketOpen"
            },
            "operator": "eq",
            "rightOperand": true
          }
        ]
      }
    }
  }
}

Facts more than one hop away. Policies often depend on a fact that is not stored directly on the request. Suppose use of market prices is permitted only to recipients whose organisation is regulated in the EU. In the source data that fact is two hops from the agent:

@prefix ex: <https://example.org/> .

ex:alice ex:memberOf ex:acmeBank .
ex:acmeBank ex:regulatedIn ex:EU .

An operand cannot follow ex:memberOf and then ex:regulatedIn; earlier drafts allowed that with dprod:path, which has been removed. Instead the calling system, which already knows who Alice is and can query that data, resolves the join while building the request and writes the answer onto the request as a single property. The policy then reads it in one lookup:

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:euRecipientPolicy",
  "type": "Set",
  "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
  "target": "ex:marketPrices",
  "permission": {
    "type": "Permission",
    "action": "use",
    "constraint": {
      "type": "Constraint",
      "leftOperand": {
        "id": "ex:recipientRegulator",
        "operandSource": "requestSource",
        "operandProperty": "ex:recipientRegulatedIn"
      },
      "operator": "eq",
      "rightOperand": { "id": "ex:EU" }
    }
  }
}

The normalised request carries the resolved value:

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:request-2026-03-02-0915",
  "assignee": "ex:alice",
  "action": "use",
  "target": "ex:marketPrices",
  "ex:recipientRegulatedIn": { "id": "ex:EU" }
}

This keeps the evaluator a pure, one-lookup function of its input. The join happens in the calling system, where the data lives, and its result becomes part of the immutable context, so a later audit sees exactly the value the decision was based on. A fact that describes the world rather than the request, such as whether the market is open, is flattened onto the state snapshot in the same way and read with stateSource.

The document below is the evaluation context an evaluator would be given for Alice's request at 09:15 on 2 March. Against the market-hours policy at the top of this example it yields a permit. DPROD's dprod:currentAgent and ODRL's standard odrl:dateTime are built-in operands bound to the context's agent and clock, and need no declaration.

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:evaluation-2026-03-02-0915",
  "type": "EvaluationContext",
  "agent": { "id": "ex:alice", "type": "Party" },
  "clock": "2026-03-02T09:15:00Z",
  "request": {
    "assignee": "ex:alice",
    "action": "use",
    "target": "ex:marketPrices",
    "ex:recipientType": { "id": "ex:internal" }
  },
  "state": { "type": "Entity", "ex:marketOpen": true }
}

23. Lifecycle and Versioning§

DPROD keeps two questions apart. Where is this offer or contract in its administrative life? is answered by a person or a contract-management process and recorded with dprod:offerLifecycleStatus or dprod:contractLifecycleStatus. Has this obligation been met? is answered by an evaluator from observable facts and recorded with dprod:dutyState. Both take any skos:Concept; DPROD ships the optional scheme with Pending, Active, Fulfilled and Violated, and an enterprise may substitute its own.

The example shows both, plus versioning:

  • A version chain. Customer API v2 supersedes v1 through prov:wasRevisionOf. The retired offer stays in the graph with its status set to Fulfilled, so contracts that accepted it remain interpretable.
  • A contract in force, Active, with its effective and expiration dates.
  • Duty instances. When the daily delivery duty is evaluated, each occurrence becomes its own odrl:Duty with a computed state: the 4 February delivery was made on time, the 5 February one missed its 30-minute window, and the 6 February one is not yet due.

Duty state is deliberately not a sub-property of dprod:lifecycleStatus: it is derived, and re-deriving it must never change an authored status.

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:analyticsCustomerData2026",
  "type": "DataContract",
  "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
  "assigner": "ex:dataPlatformTeam",
  "assignee": "ex:analyticsTeam",
  "contractLifecycleStatus": "Active",
  "effectiveDate": "2026-02-01T00:00:00Z",
  "expirationDate": "2026-12-31T23:59:59Z",
  "acceptsOffer": {
    "id": "ex:customerApiV2",
    "type": "DataOffer",
    "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
    "assigner": "ex:dataPlatformTeam",
    "target": "ex:customerData",
    "offerLifecycleStatus": "Active",
    "effectiveDate": "2026-01-01T00:00:00Z",
    "obligation": {
      "type": "Duty",
      "subjectOfDuty": "ex:dataPlatformTeam",
      "action": "ex:deliver",
      "schedule": {
        "id": "ex:dailyAt0700",
        "type": "Schedule",
        "conformsTo": "dprod:Rfc5545ScheduleFormat",
        "scheduleExpression": "DTSTART;TZID=Europe/London:20260101T070000\nRRULE:FREQ=DAILY"
      },
      "deadline": { "@value": "PT30M", "type": "xsd:duration" }
    },
    "wasRevisionOf": {
      "id": "ex:customerApiV1",
      "type": "DataOffer",
      "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
      "assigner": "ex:dataPlatformTeam",
      "target": "ex:customerData",
      "offerLifecycleStatus": "Fulfilled",
      "expirationDate": "2025-12-31T23:59:59Z",
      "permission": { "type": "Permission", "action": "use" }
    }
  },
  "obligation": [
    {
      "id": "ex:delivery-2026-02-04",
      "type": "Duty",
      "subjectOfDuty": "ex:dataPlatformTeam",
      "objectOfDuty": "ex:analyticsTeam",
      "action": "ex:deliver",
      "deadline": { "@value": "2026-02-04T07:30:00Z", "type": "xsd:dateTime" },
      "dutyState": "Fulfilled"
    },
    {
      "id": "ex:delivery-2026-02-05",
      "type": "Duty",
      "subjectOfDuty": "ex:dataPlatformTeam",
      "objectOfDuty": "ex:analyticsTeam",
      "action": "ex:deliver",
      "deadline": { "@value": "2026-02-05T07:30:00Z", "type": "xsd:dateTime" },
      "dutyState": "Violated"
    },
    {
      "id": "ex:delivery-2026-02-06",
      "type": "Duty",
      "subjectOfDuty": "ex:dataPlatformTeam",
      "objectOfDuty": "ex:analyticsTeam",
      "action": "ex:deliver",
      "deadline": { "@value": "2026-02-06T07:30:00Z", "type": "xsd:dateTime" },
      "dutyState": "Pending"
    }
  ]
}

24. ODCS Mapping§

The Open Data Contract Standard (ODCS) describes a data contract as a YAML document that bundles schema, quality rules, service levels, team and infrastructure. DPROD Contracts covers a narrower question, the rights and obligations, and leaves schema to DCAT and SHACL and infrastructure to deployment descriptors. The two are complementary. This example translates the policy parts of the ODCS reference document into a DPROD data offer; each rule's label names the ODCS field it came from.

ODCSDPROD
kind: DataContract, status: active, versiondprod:DataOffer, dprod:offerLifecycleStatus, dct:hasVersion
team ownerodrl:assigner
slaProperties frequency and timeOfAvailabilitya delivery duty with a dprod:schedule and a dprod:deadline
slaProperties generalAvailability and endOfSupportdprod:effectiveDate and dprod:expirationDate
quality nullValues mustBe 0, scheduled nightlya conformance duty constrained on completeness, with a dprod:schedule
slaProperties retentiona duty to odrl:delete beyond the retention period
roles with access: readan odrl:Permission for the role's party
description.limitationsan odrl:Prohibition

ODCS fields that are workflow or operations rather than policy, such as approver chains, severity and servers, have no counterpart and stay in ODCS.

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:sellerDataContract",
  "type": "DataOffer",
  "description": "Views built on top of the seller tables. Predict sales over time.",
  "hasVersion": "1.1.0",
  "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
  "assigner": "ex:sellerDataTeam",
  "target": "ex:sellerData",
  "offerLifecycleStatus": "Active",
  "effectiveDate": "2022-05-12T09:30:10-08:00",
  "expirationDate": "2032-05-12T09:30:10-08:00",
  "obligation": [
    {
      "type": "Duty",
      "label": "slaProperties frequency + timeOfAvailability: daily, by 09:00",
      "subjectOfDuty": "ex:sellerDataTeam",
      "action": "ex:deliver",
      "schedule": {
        "id": "ex:dailyAt0900",
        "type": "Schedule",
        "conformsTo": "dprod:Rfc5545ScheduleFormat",
        "scheduleExpression": "DTSTART;TZID=Europe/London:20260101T090000\nRRULE:FREQ=DAILY"
      },
      "deadline": { "@value": "PT1H", "type": "xsd:duration" }
    },
    {
      "type": "Duty",
      "label": "quality nullValues mustBe 0, checked nightly",
      "subjectOfDuty": "ex:sellerDataTeam",
      "action": "ex:conformTo",
      "schedule": {
        "id": "ex:nightlyAt2000",
        "type": "Schedule",
        "conformsTo": "dprod:Rfc5545ScheduleFormat",
        "scheduleExpression": "DTSTART;TZID=Europe/London:20260101T200000\nRRULE:FREQ=DAILY"
      },
      "constraint": {
        "type": "Constraint",
        "leftOperand": {
          "id": "ex:completeness",
          "operandSource": "requestSource",
          "operandProperty": "ex:completeness"
        },
        "operator": "eq",
        "rightOperand": { "@value": "100", "type": "xsd:decimal" }
      }
    },
    {
      "type": "Duty",
      "label": "slaProperties retention: delete after 3 years",
      "action": "delete",
      "constraint": {
        "type": "Constraint",
        "leftOperand": {
          "id": "ex:retentionPeriod",
          "operandSource": "requestSource",
          "operandProperty": "ex:retentionPeriod"
        },
        "operator": "gt",
        "rightOperand": { "@value": "P3Y", "type": "xsd:duration" }
      }
    }
  ],
  "permission": {
    "type": "Permission",
    "label": "roles: microstrategy_user_opr, access: read",
    "assignee": "ex:reportingUsers",
    "action": "read"
  },
  "prohibition": {
    "type": "Prohibition",
    "label": "description.limitations: no buyer information",
    "action": "derive"
  }
}

25. Provider Duties§

Most of what a data contract promises is expressed as duties on the provider. DPROD needs no new rule type for this: each is an ordinary odrl:Duty in the offer's odrl:obligation, with dprod:subjectOfDuty naming the provider as the party that must act. Four patterns cover almost every service-level commitment:

  • Delivery. dprod:schedule (an identified dprod:Schedule, here an RFC 5545 rule with its start time and timezone) says when each delivery is due and dprod:deadline how long after that the provider has to deliver.
  • Schema conformance. The duty is about the schema, not the data, so it states its own odrl:target instead of inheriting the offer's.
  • Change notification. A deadline with no schedule is a lead time.
  • Quality. A conformance duty with an odrl:constraint. The constraint's left operand is declared where it is used: dprod:operandSource and dprod:operandProperty tell an evaluator to read ex:timeliness from the authorisation request.

Consumer duties use exactly the same construct, minus the subject.

{
  "@context": [
    "https://ekgf.org/dprod/spec/develop/dprod-simple.jsonld",
    { "ex": "https://example.org/" }
  ],
  "id": "ex:riskMetricsOffer",
  "type": "DataOffer",
  "profile": "https://ekgf.org/dprod/spec/develop/contracts/profile/",
  "assigner": "ex:dataPlatformTeam",
  "target": "ex:riskMetrics",
  "obligation": [
    {
      "type": "Duty",
      "label": "Delivery: every day at 07:00, within 30 minutes",
      "subjectOfDuty": "ex:dataPlatformTeam",
      "action": "ex:deliver",
      "schedule": {
        "id": "ex:dailyAt0700",
        "type": "Schedule",
        "conformsTo": "dprod:Rfc5545ScheduleFormat",
        "scheduleExpression": "DTSTART;TZID=Europe/London:20260101T070000\nRRULE:FREQ=DAILY"
      },
      "deadline": { "@value": "PT30M", "type": "xsd:duration" }
    },
    {
      "type": "Duty",
      "label": "Schema conformance",
      "subjectOfDuty": "ex:dataPlatformTeam",
      "action": "ex:conformTo",
      "target": "ex:riskMetricsSchema"
    },
    {
      "type": "Duty",
      "label": "Change notification: 14 days notice",
      "subjectOfDuty": "ex:dataPlatformTeam",
      "action": "ex:notify",
      "target": "ex:schemaChanges",
      "deadline": { "@value": "P14D", "type": "xsd:duration" }
    },
    {
      "type": "Duty",
      "label": "Quality: data must be real-time",
      "subjectOfDuty": "ex:dataPlatformTeam",
      "action": "ex:conformTo",
      "constraint": {
        "type": "Constraint",
        "leftOperand": {
          "id": "ex:timeliness",
          "operandSource": "requestSource",
          "operandProperty": "ex:timeliness"
        },
        "operator": "eq",
        "rightOperand": { "id": "ex:realtime" }
      }
    }
  ]
}

A. Acknowledgements§

The editors gratefully acknowledge the feedback and contributions made by individuals who have participated in EDM Council's CDMC team.

B. Document provenance§

This record identifies the generator and the source revisions collected for this publication. Committers below describe recent repository changes, rather than authorship of the whole document.

Generated by
Grapharch 0.2.26 (build 78)
Build operator
Build operator was not recorded.

Generator source commit: 615760949a54246d2cb29b1b164478fa3ed0ccdf

Generator build: 78

Source repository

Repository
https://github.com/EKGF/dprod.git
Source commit
c608d8e6caf56dd73d6ebccde390fa595c37a412
Source state
Committed source tree pinned to this exact revision.

Recent committers

Up to five commits, following the first-parent history from the source commit. This is not the full contributor list.

  1. GitHub
    c608d8e6caf56dd73d6ebccde390fa595c37a412
  2. GitHub
    b62d69bdb67d244e5435a499e940aee3413a9164
  3. GitHub
    7f7b6229f218cbddabf90a374b507873ba4d445d
  4. GitHub
    8b4968a74fd1541c765a72ee2a7bb06ab7e48bb7
  5. GitHub
    a316c490124a631a0939199c667150812335f22e

Diagram interpretation

Class diagrams use UML shorthand for asserted OWL facts and declared SHACL constraints, without inference or a claim that validation passed. RDF properties remain independent resources even when drawn as class members or labelled associations. Domain/range declarations alone do not impose requiredness or cardinality. A property with a declared domain and range is a labelled association from the domain to the range; a datatype property, or one without a specific range, is an attribute of its domain. Multiple domains or ranges apply conjunctively, not as alternatives: each declared domain-range pair is drawn and holds for every use of the property. An explicitly declared union domain is drawn as one source box whose class alternatives are joined by or. A dotted rdfs:Resource source box is a presentation placeholder when no specific domain is declared in the selected inputs, not an asserted domain or a claim that none can be entailed. Simple existential subclass restrictions use a class-scoped association with target-end 1..* and {qualified}, meaning at least one value in the named filler class; this does not constrain all property values or declare a global range. Datatype-qualified restrictions appear as class fields with the declared datatype and bracketed count of distinct data values; they do not declare a global property range. Qualified cardinality associations show n..* for minima, n for exact counts, or 0..n for maxima at the named target with {qualified}: only values in that target class count, and other property values are not excluded. A zero maximum prohibits values in that named target class; it is never omitted. A simple zero qualified minimum imposes no restriction and is omitted visually. An existential with a simple zero-minimum filler still requires a value; a positive qualified minimum or exact count on the same class and property already guarantees that existence. Unsupported anonymous OWL expressions remain explicit. Types and counts from simple property shapes enrich the UML notation. Identical qualifiers are shown once; where declaring shapes disagree, the disputed type or multiplicity is omitted from the drawing and remains in the dedicated shape documentation. No shape is chosen arbitrarily and conflicting counts are not silently intersected. An absent count imposes no lower or upper bound beyond zero or unbounded, respectively. Complex constraints require the linked full shape definition. Original OWL facts and shape provenance remain in the published source graph. Some diagrams show at most five complete OWL relationship groups within an eighteen-fact budget, selected in deterministic IRI order; omitted groups remain in the published source graph. These views are not exhaustive. Names from the same ontology as the documented class are shown by label; names from another ontology add their prefixed name in parentheses, and unlabelled names show their prefixed name.

Search this specification