update

dprod.html

@@ -161,15 +161,17 @@ <h2>Data Product (DPROD) Model</h2>
 <UL>
     <li> Data Mesh (<code>dcat:Catalog</code>) - The collection of Data Products </li>
     <li> Data Product (<code>dprod:DataProduct</code>) - A data product may have input and output ports, code and metadata</li>
-    <li> Port (<code>dcat:DataService</code>) - A digital interface that provides access to a Dataset. The can be a HTTPEndpoint, a Database or a FileShare etc</li>
+    <li> Port (<code>dcat:DataService</code>) - A digital interface that provides access to a Dataset. The can be a HTTP URL, a Database or a FileShare etc</li>
     <li> Distribution (<code>dcat:Distribution</code>) - A specific representation of a dataset (CSV, JSON, ADLS etc) with it own physical mode if needed</li>
     <li> Dataset (<code>dcat:Dataset</code>) - A collection of data related that conforms to a logical model</li>
 </ul>
 </p>
 <p>
-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.
 </p>
-
+  <p>
+  In this example the UK Bonds Data Product has an output port that is a RESTful API that returns JSON that conforms to the shared FIBO specification for callable bonds.
+  </p>
 
   <pre id="eg12" class="example hljs json">
   {
@@ -293,27 +295,21 @@ <h2>offersDistribution</h2>
 
       </section>
 
-      <section>
-      <h2>RESTDataService</h2>
-        Accessed using http verbs with parameters, may be defined using OpenAPI
-
-      </section>
-
       <section>
       <h2>ObjectDataService</h2>
         Structured API, e.g. gRPC, CORBA, SOAP, ORM
 
       </section>
 
       <section>
-      <h2>StreamingDataService</h2>
-        Data is continuously made available
+      <h2>GraphQLDataService</h2>
+        Single REST endpoint, with structure given by GraphQL schema
 
       </section>
 
       <section>
-      <h2>FileDataService</h2>
-        Uses file-like access methods. May or may not be streaming if the file is continuously wriitten to
+      <h2>StreamingDataService</h2>
+        Data is continuously made available
 
       </section>
 
@@ -324,8 +320,8 @@ <h2>DatabaseDataService</h2>
       </section>
 
       <section>
-      <h2>QueuingDataService</h2>
-        Streams using a queue or topic e.g. MQTT, Kafka, DDS
+      <h2>RESTDataService</h2>
+        Accessed using http verbs with parameters, may be defined using OpenAPI
 
       </section>
 
@@ -336,14 +332,14 @@ <h2>DataProductLifecycleStatus</h2>
       </section>
 
       <section>
-      <h2>Enumeration</h2>
-        The superclass of enumeration lists referenced from Data Product related artifacts
+      <h2>FileDataService</h2>
+        Uses file-like access methods. May or may not be streaming if the file is continuously wriitten to
 
       </section>
 
       <section>
-      <h2>GraphQLDataService</h2>
-        Single REST endpoint, with structure given by GraphQL schema
+      <h2>QueuingDataService</h2>
+        Streams using a queue or topic e.g. MQTT, Kafka, DDS
 
       </section>
 
@@ -353,6 +349,12 @@ <h2>CallbackDataService</h2>
 
       </section>
 
+      <section>
+      <h2>Enumeration</h2>
+        The superclass of enumeration lists referenced from Data Product related artifacts
+
+      </section>
+
       <section>
       <h2>Dataset</h2>
         see http://www.w3.org/ns/dcat#Dataset