From 79cdc8efeb844cb7578615a04ecf8ce89cd327b0 Mon Sep 17 00:00:00 2001
From: tonyseale
Date: Wed, 22 Nov 2023 20:30:50 +0000
Subject: [PATCH] add label
---
code/script.py | 3 +--
docs/respec/template.html | 13 +++++++++----
ontology/dprod/dprod.ttl | 3 ++-
3 files changed, 12 insertions(+), 7 deletions(-)
diff --git a/code/script.py b/code/script.py
index 3c79405..000501f 100644
--- a/code/script.py
+++ b/code/script.py
@@ -4,7 +4,6 @@
import jinja2
import rdflib
-from jinja2 import Environment, PackageLoader, select_autoescape
from rdflib import Graph, URIRef, DCTERMS, SH
from rdflib.namespace import OWL, RDF, RDFS, XSD, DCAT
import json
@@ -77,7 +76,7 @@ def add_to_context(uri):
rdf_property = RdfProperty(name=short_name(s), uri=s)
class_obj.properties.append(rdf_property)
for s1, p1, o1 in g.triples((rdf_property.uri, None, None)):
- rdf_property.__dict__[short_name(p1)] = o1
+ rdf_property.__dict__[short_name(p1)] = o1
elif OWL.ObjectProperty in types:
for s, p, o in g.triples((uri, RDFS.range, None)):
context[name] = {"@id": str(uri), "@type": str(o)}
diff --git a/docs/respec/template.html b/docs/respec/template.html
index c511e5f..baf4193 100644
--- a/docs/respec/template.html
+++ b/docs/respec/template.html
@@ -161,15 +161,17 @@ Data Product (DPROD) Model
- 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. The can be a HTTPEndpoint, a Database or a FileShare etc
+ - Port (
dcat:DataService
) - A digital interface that provides access to a Dataset. The can be a HTTP URL, a Database or a FileShare etc
- Distribution (
dcat:Distribution
) - A specific representation of a dataset (CSV, JSON, ADLS etc) with it own physical mode if needed
- Dataset (
dcat:Dataset
) - A collection of data related that conforms to a logical model
-Because DCAT DataService maps to the Data Mesh notion of a port we can declare a DataProduct by and specify and input and output ports. This allows user to connect their Data Products to Datasets and from there onto shared Ontologies.
+ DPROD maps to the Data Mesh notion of a port to the DCAT notion of a DataService, so we can declare a DataProduct by and specify and input and output ports and these ports are Dataservice. This allows user to connect their Data Products to Datasets and from there onto shared Ontologies.
-
+
+In this example, the UK Bonds Data Product features an output port, which is a RESTful API. This API returns JSON data that conforms to the shared FIBO specification for callable bonds.
+
{
@@ -188,7 +190,7 @@ Data Product (DPROD) Model
"dcterms:format": "https://www.iana.org/assignments/media-types/application/json",
"belongsToDataset": {
"@type": "dcat:Dataset",
- "dcat:conformsTo": "fibo:CallableBond"
+ "dcat:conformsTo": "https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/Bonds/CallableBond"
}
}
}
@@ -212,6 +214,9 @@ {{prop.name}}
Identifier: | dprod:{{prop.name}} |
+ {% if prop.label is not none %}
+ Label: | {{prop.label}} |
+ {% endif %}
Notes: | {{prop.description}} |
Domain: | {{prop.domain}} |
Range: | {{prop.range}} |
diff --git a/ontology/dprod/dprod.ttl b/ontology/dprod/dprod.ttl
index 4531519..170272a 100644
--- a/ontology/dprod/dprod.ttl
+++ b/ontology/dprod/dprod.ttl
@@ -287,7 +287,7 @@ dprod:DataService-offersDistribution
dprod:offersDistribution
a rdfs:Property, owl:ObjectProperty ;
- dc:description "he dataset distribution that is being offered through this Data Service"@en ;
+ dc:description "The dataset distribution that is being offered through this Data Service"@en ;
rdfs:isDefinedBy dprod:;
owl:inverseOf dcat:accessService;
rdfs:domain dcat:DataService;
@@ -300,6 +300,7 @@ dprod:dataProductOwner
rdfs:isDefinedBy dprod:;
rdfs:domain dprod:DataProduct;
rdfs:range dct:Agent;
+ rdfs:label "Data Product Owner" ;
.
dprod:inputPort