Conformance
+As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this Profile are non-normative. + Everything else in this Profile is normative.
+ +The key words MAY, MUST, MUST NOT, RECOMMENDED, SHOULD, and SHOULD NOT are to be interpreted as described in [[!RFC2119]].
+
+ Namespaces and prefixes used in normative parts of this Profile are shown in the following table. Data Catalog Vocabulary (DCAT) is a W3C standard that facilitates interoperability between data catalogs published on the web. By using DCAT to declare input and output ports, Semantic Data Products can effectively describe the details of the data services they provide, including the datasets and the operations that can be performed on them.
+
+Semantic Data Products take advantage of this by defining ports that specify not only the data format and structure but also the semantics—meaning the meaning and relationships of the data elements. This allows for the integration of data across different domains, as the shared semantics ensure that all stakeholders have a common understanding of the data, which is critical in a Data Mesh architecture.
+
+A Data Mesh is a decentralized approach to data architecture and organizational design. The fundamental idea behind a Data Mesh is to treat data as a product, with the goal being that these data products can be easily discovered, understood, and consumed across technical and business boundaries.
+
+By mapping to DCAT DataServices, these Semantic Data Products can describe their functionality in a standard way that can be programmatically understood and used, making the data easily accessible and shareable across the organization. This approach facilitates a self-serve data infrastructure, where domain-oriented data teams can autonomously build and maintain their data products yet ensure that these products can interact and integrate seamlessly with the rest of the data ecosystem within an organization.
+
+In a broader sense, using standards like DCAT contributes to a powerful and expressive model for a Data Mesh, allowing for greater agility, scalability, and innovation. It ensures that as the data landscape becomes increasingly complex, the fundamental mechanisms for describing, sharing, and manipulating data remain robust and standard across the organization.
+
+
+The Profile consists of the following classes:
+Normative namespaces
+
+
+
+
+
+
+
+
+ Prefix
+ Namespace IRI
+ Source
+
+
+
+
+ dcat
+
+
+ http://www.w3.org/ns/dcat#
+ [[VOCAB-DCAT-3]]
+
+
+
+
+ dct
+
+
+ http://purl.org/dc/terms/
+ [[DCTERMS]]
+
+
+
+
+
+ odrl
+
+
+ http://www.w3.org/ns/odrl/2/
+ [[ODRL-VOCAB]]
+
+
+
+
+ sdo
+
+
+ https://schema.org
+ [[SCHEMA-ORG]]
+
+
+
+
+
+
+ vcard
+
+
+ http://www.w3.org/2006/vcard/ns#
+ [[VCARD-RDF]]
+ Data Product (DPROD) Model
+ 
+
+
+dprod:DataProduct) - A data product may have input and output ports, code and metadatadcat:DataService) - A digital interface that provides access to a Datasetdcat:Distribution) - A specific representation of a datasetdcat:Dataset) - A collection of data related dcat:Catalog) - The collection of Data Products
+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. +
+ + +
+{
+ "@id": "https://y.com/products/uk-bonds",
+ "@type": "dprod:DataProduct",
+ "dprod:title": "UK Bonds",
+ "dprod:description": "UK Bonds is your one-stop-shop for all ...",
+ "dprod:outputPort": {
+ "@type": "dprod:Port",
+ "dcat:endpointURL": "https://y.com/uk-10-year-bonds",
+ "dcat:servesDataset": {
+ "@type": "dcat:Dataset",
+ "dcat:conformsTo": "fibo:CallableBond",
+ },
+ }
+}
+
+
+ The examples in map the type of the above classes to @type in the JSON-LD serialisations. You can use JSON-LD to extend the familiar JSON syntax with the shared semantics defined by DCAT and DPROD
+