chore: apply change requests from review

juliapampus · juliapampus · commit 4ed72e4b4835 · 2025-06-27T14:05:47.000+02:00
diff --git a/specifications/catalog/catalog.protocol.md b/specifications/catalog/catalog.protocol.md
@@ -7,7 +7,7 @@ abstract [=Message=] exchange format. The concrete [=Message=] exchange wire for
 
 The [=Catalog Protocol=] reuses properties from the DCAT and ODRL vocabularies with restrictions defined in this
 specification. This is done implicitly by the use of the JSON schemas and JSON-LD-contexts that are part of the [=Dataspace Protocol=].
-Servers _MUST NOT_ process properties that are not part of the schemas.
+Servers _MAY_ process properties that are not part of the schemas.
 
 ## Message Types
 
@@ -94,7 +94,7 @@ An [=Offer=] contains the following attributes:
 
 - An [=Offer=] _MUST_ be unique to a [=Dataset=] since the target of the [=Offer=] is derived from its enclosing context.
 
-- [=Offers=] _MUST NOT_ contain any `target` attributes. The value of the `target` attribute _MUST_ be the [=Dataset=] identifier. (_NOTE: If the [=Offer=] is used in an enclosing [=Catalog=] or [=Dataset=], there must not be any `target` attribute set._)
+- [=Offers=] _MAY_ contain any `target` attributes. The value of the `target` attribute _MUST_ be the [=Dataset=] identifier. (_NOTE: If the [=Offer=] is used in an enclosing [=Catalog=] or [=Dataset=], there must not be any `target` attribute set._)
 
 ### ERROR - Catalog Error
 
diff --git a/specifications/negotiation/contract.negotiation.binding.https.md b/specifications/negotiation/contract.negotiation.binding.https.md
@@ -124,7 +124,7 @@ Authorization: ...</pre>
 **Response**
 
 If the message is successfully processed, the [=Provider=] _MUST_ return an HTTP 200 (OK) response. The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Contract Negotiation Event Endpoint {#negotiations-providerpid-events-post}
 
@@ -168,7 +168,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Contract Negotiation=]'s state is successfully transitioned, the [=Provider=] _MUST_ return an HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Contract Negotiation Termination Endpoint {#negotiations-providerpid-termination-post}
 
@@ -188,7 +188,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Contract Negotiation=]'s state is successfully transitioned, the [=Provider=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ## Consumer Path Bindings
 
@@ -284,7 +284,7 @@ Authorization: ...</pre>
 **Response**
 
 If the message is successfully processed, the [=Consumer=] _MUST_ return an HTTP 200 (OK) response. The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Contract Agreement Endpoint {#negotiations-consumerpid-agreement-post}
 
@@ -303,7 +303,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Contract Negotiation=]'s state is successfully transitioned, the [=Consumer=] _MUST_ return an HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Contract Negotiation Event Endpoint {#negotiations-consumerpid-events-post}
 
@@ -322,7 +322,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Contract Negotiation=]'s state is successfully transitioned, the [=Consumer=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Contract Negotiation Termination Endpoint {#negotiations-consumerpid-termination-post}
 
@@ -341,4 +341,4 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Contract Negotiation=]'s state is successfully transitioned, the [=Consumer=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
diff --git a/specifications/negotiation/contract.negotiation.protocol.md b/specifications/negotiation/contract.negotiation.protocol.md
@@ -127,7 +127,7 @@ complete [=Agreement=].
 - An [=Agreement=] _MUST_ contain a `timestamp` property defined as an [XSD DateTime](https://www.w3schools.com/XML/schema_dtypes_date.asp) type.
 
 - An [=Agreement=] _MUST_ contain an `assigner` and `assignee`. The contents of these properties are a dataspace-specific
-  unique identifier of the [=Agreement=] parties. These identifiers _MUST NOT_ be the same as the
+  unique identifier of the [=Agreement=] parties. These identifiers _MAY_ be the same as the
   identifiers of the [=Participant Agents=] negotiating the [=Agreement=] (e.g., [=Connectors=]).
 
 - An [=Agreement=] _MUST_ contain a `target` property. None of its Rules, however, _MUST_ have any `target`
@@ -239,11 +239,4 @@ An [=Agreement=] contains the following attributes:
 | **Properties** | <p data-include="message/table/contractnegotiationerror.html" data-include-format="html"></p> |
 
 The Contract Negotiation Error is an object returned by a [=Consumer=] or [=Provider=] indicating an error has occurred.
-It does not cause a state transition.
-
-| Field         | Type          | Description                                                  |
-|---------------|---------------|--------------------------------------------------------------|
-| `consumerPid` | UUID          | The [=Contract Negotiation=] unique identifier on [=Consumer=] side. |
-| `providerPid` | UUID          | The [=Contract Negotiation=] unique identifier on [=Provider=] side. |
-| `code`        | String        | An optional implementation-specific error code.              |
-| `reason`      | Array[object] | An optional array of implementation-specific error objects.  |
+It does not cause a state transition.
diff --git a/specifications/transfer/transfer.process.binding.https.md b/specifications/transfer/transfer.process.binding.https.md
@@ -116,7 +116,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Transfer Process=]'s state is successfully transitioned, the [=Provider=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Transfer Completion Endpoint {#transfers-providerpid-completion-post}
 
@@ -135,7 +135,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Transfer Process=]'s state is successfully transitioned, the [=Provider=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Transfer Termination Endpoint {#transfers-providerpid-termination-post}
 
@@ -154,7 +154,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Transfer Process=]'s state is successfully transitioned, the [=Provider=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Transfer Suspension Endpoint {#transfers-providerpid-suspension-post}
 
@@ -173,7 +173,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Transfer Process=]'s state is successfully transitioned, the [=Provider=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ## Consumer Callback Path Bindings
 
@@ -211,7 +211,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Transfer Process=]'s state is successfully transitioned, the [=Consumer=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Transfer Completion Endpoint {#transfers-consumerpid-completion-post}
 
@@ -230,7 +230,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Transfer Process=]'s state is successfully transitioned, the [=Consumer=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Transfer Termination Endpoint {#transfers-consumerpid-termination-post}
 
@@ -249,7 +249,7 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Transfer Process=]'s state is successfully transitioned, the [=Consumer=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it.
+not specified and clients _MAY_ process it.
 
 ### Transfer Suspension Endpoint {#transfers-consumerpid-suspension-post}
 
@@ -268,4 +268,4 @@ Authorization: ...</pre>
 **Response**
 
 If the [=Transfer Process=]'s state is successfully transitioned, the [=Consumer=] _MUST_ return HTTP code 200 (OK). The response body is
-not specified and clients _MUST NOT_ process it. 
+not specified and clients _MAY_ process it. 
diff --git a/specifications/transfer/transfer.process.protocol.md b/specifications/transfer/transfer.process.protocol.md
@@ -117,7 +117,7 @@ The Transfer Request Message is sent by a [=Consumer=] to initiate a [=Transfer
 Note that [=Providers=] _SHOULD_ implement idempotent behavior for [Transfer Request Messages](#transfer-request-message)
 based on the value of `consumerPid`. [=Providers=] _MAY_ choose to implement idempotent behavior for a certain period of
 time. For example, until a [=Transfer Process=] has completed and been archived after an implementation-specific expiration period,
-repeated sending of [Transfer Request Messages](#transfer-request-message) _MUST NOT_ change the state of the [=Transfer Process=]. If a
+repeated sending of [Transfer Request Messages](#transfer-request-message) does not change the state of the [=Transfer Process=]. If a
 request for the given `consumerPid` has already been received *and* the same [=Consumer=] sent the original message
 again, the [=Provider=] _SHOULD_ respond with an appropriate [Transfer Start Message](#transfer-start-message).
 
