fix: resolve broken links (#60)

* fix: resolve broken links * chore: add dataset json
International-Data-Spaces-Association · Mar 8, 2023 · 5cac117 · 5cac117
1 parent 7cf8abb
commit 5cac117
Show file tree

Hide file tree

Showing 2 changed files with 50 additions and 8 deletions.
diff --git a/catalog/message/dataset.json b/catalog/message/dataset.json
@@ -0,0 +1,42 @@
+{
+  "@context":  "https://w3id.org/dspace/1/0/context.json",
+  "@id": "urn:uuid:3afeadd8-ed2d-569e-d634-8394a8836d57",
+  "@type": "dcat:Dataset",
+  "dct:title": "Traffic Data",
+  "dct:description": "Traffic data sample extract",
+  "dcat:keyword": [
+    "traffic"
+  ],
+  "odrl:hasPolicy": {
+    "@context": {
+      "@vocab": "https://www.w3.org/TR/odrl-model/"
+    },
+    "@id": "urn:uuid:2828282:3dd1add8-4d2d-569e-d634-8394a8836a88",
+    "permission": [
+      {
+        "action": "use",
+        "constraint": [
+          {
+            "leftOperand": {
+              "@value": "spatial"
+            },
+            "rightOperand": {
+              "@value": "EU"
+            },
+            "operator": "EQ"
+          }
+        ],
+        "duty": []
+      }
+    ],
+    "prohibition": [],
+    "obligation": []
+  },
+  "dcat:distribution": [
+    {
+      "@type": "dcat:Distribution",
+      "dct:format": "dspace:s3+push",
+      "dcat:accessService": "urn:uuid:4aa2dcc8-4d2d-569e-d634-8394a8834d77"
+    }
+  ]
+}
diff --git a/transfer/transfer.process.binding.https.md b/transfer/transfer.process.binding.https.md
@@ -49,7 +49,7 @@ Authorization: ...
 ```
 
 If the transfer process is found and the client is authorized, the provider connector must return an HTTP 200 (OK) response and a body containing
-the [TransferProcess](./message/transfer.process.json):
+the [TransferProcess](./message/transfer-process.json):
 
 ```
 {
@@ -97,7 +97,7 @@ is included with or absent from the `callbackAddress` when resolving full URL.
 The @id is the correlation id that will be used for callback messages.
 
 The provider connector must return an HTTP 201 (Created) response with the location header set to the location of the transfer process and a body containing
-the [TransferProcess](./message/transfer.process.json) message:
+the [TransferProcess](./message/transfer-process.json) message:
 
  ```
  Location: /transfers/urn:uuid:71f8dfab-9337-4e9d-a4c7-524e04443f16
@@ -118,21 +118,21 @@ Note that if the location header is not an absolute URL, it must resolve to an a
 
 #### 2.6.1 POST
 
-The consumer connector can POST a [TransferStartMessage](./message/transfer.start.message.json) to attempt to start a transfer process after it has been suspended. If the transfer
+The consumer connector can POST a [TransferStartMessage](./message/transfer-start-message.json) to attempt to start a transfer process after it has been suspended. If the transfer
 process state is successfully transitioned, the producer must return HTTP code 200 (OK). The response body is not specified and clients are not required to process it.
 
 ### 2.7 The provider `transfers/:id/completion` resource
 
 #### 2.7.1 POST
 
-The consumer connector can POST a [TransferCompletionMessage](./message/transfer.completion.message.json) to complete a transfer process. If the transfer
+The consumer connector can POST a [TransferCompletionMessage](./message/transfer-completion-message.json) to complete a transfer process. If the transfer
 process state is successfully transitioned, the provider must return HTTP code 200 (OK). The response body is not specified and clients are not required to process it.
 
 ### 2.8 The provider `transfers/:id/termination` resource
 
 #### 2.8.1 POST
 
-The consumer connector can POST a [TransferTerminationMessage](./message/transfer.termination.message.json) to terminate a transfer process. If the transfer
+The consumer connector can POST a [TransferTerminationMessage](./message/transfer-termination-message.json) to terminate a transfer process. If the transfer
 process state is successfully transitioned, the provider must return HTTP code 200 (OK). The response body is not specified and clients are not required to process it.
 
 ### 2.9 The provider `transfers/:id/suspension` resource
@@ -154,21 +154,21 @@ be `https://connector.consumer.com/callback/transfers/:id/start`.
 
 #### 3.2.1 POST
 
-The provider connector can POST a [TransferStartMessage](./message/transfer.start.message.json) to indicate the start of a transfer process. If the transfer
+The provider connector can POST a [TransferStartMessage](./message/transfer-start-message.json) to indicate the start of a transfer process. If the transfer
 process state is successfully transitioned, the consumer must return HTTP code 200 (OK). The response body is not specified and clients are not required to process it.
 
 ### 3.3 The consumer `transfers/:id/completion` resource
 
 #### 3.3.1 POST
 
-The provider connector can POST a [TransferCompletionMessage](./message/transfer.completion.message.json) to complete a transfer process. If the transfer
+The provider connector can POST a [TransferCompletionMessage](./message/transfer-completion-message.json) to complete a transfer process. If the transfer
 process state is successfully transitioned, the consumer must return HTTP code 200 (OK). The response body is not specified and clients are not required to process it.
 
 ### 3.4 The consumer `transfers/:id/termination` resource
 
 #### 3.4.1 POST
 
-The provider connector can POST a [TransferTerminationMessage](./message/transfer.termination.message.json) to terminate a transfer process. If the transfer
+The provider connector can POST a [TransferTerminationMessage](./message/transfer-termination-message.json) to terminate a transfer process. If the transfer
 process state is successfully transitioned, the consumer must return HTTP code 200 (OK). The response body is not specified and clients are not required to process it.
 
 ### 3.5 The consumer `transfers/:id/suspension` resource