From 97d09234d456035d47652303e734d2f3861690cd Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Wed, 8 Mar 2023 00:53:24 +0530 Subject: [PATCH 1/2] Update spec.md --- spec/spec.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/spec.md b/spec/spec.md index 8ea038a..225e5c2 100644 --- a/spec/spec.md +++ b/spec/spec.md @@ -1023,7 +1023,7 @@ Protocol Definition objects are declarative rules within `ProtocolConfigure` mes } ``` -- The _Protocols Definition_ object ****MUST**** contain a `labels` property, and its value ****MUST**** be an object composed as follows: +- The _Protocols Definition_ object ****MUST**** contain a `labels` property, it's key ****MUST**** represent a unique path and its value ****MUST**** be an object composed as follows: - The object ****MUST**** contain a `dataFormat` property, and its value ****MUST**** be an array of strings that indicate the format of the data in accordance with its MIME type designation. The most common format is JSON, which is indicated by setting the value of the `dataFormat` property to `application/json`. - The object ****MAY**** contain a `schema` property, and if present its value ****MUST**** be a valid URI string that identifies the protocol the definition pertains to. - The object ****MAY**** contain a `purpose` property, and if present its value ****MUST**** be a string that provides a description for how the data is being used in the protocol. This information will often be used by User Agent applications to display in user consent UI. @@ -1460,4 +1460,4 @@ A conforming implementation ****MUST**** be capable of encrypting and decrypting ## Normative References -[[spec]] \ No newline at end of file +[[spec]] From 56582add34fee9d31deebeb8b24f9bdde8080c38 Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Tue, 14 Mar 2023 13:30:27 +0530 Subject: [PATCH 2/2] Update spec/spec.md Co-authored-by: Ted Thibodeau Jr --- spec/spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/spec.md b/spec/spec.md index 225e5c2..c17a14e 100644 --- a/spec/spec.md +++ b/spec/spec.md @@ -1023,7 +1023,7 @@ Protocol Definition objects are declarative rules within `ProtocolConfigure` mes } ``` -- The _Protocols Definition_ object ****MUST**** contain a `labels` property, it's key ****MUST**** represent a unique path and its value ****MUST**** be an object composed as follows: +- The _Protocols Definition_ object ****MUST**** contain a `labels` property, its key ****MUST**** represent a unique path and its value ****MUST**** be an object composed as follows: - The object ****MUST**** contain a `dataFormat` property, and its value ****MUST**** be an array of strings that indicate the format of the data in accordance with its MIME type designation. The most common format is JSON, which is indicated by setting the value of the `dataFormat` property to `application/json`. - The object ****MAY**** contain a `schema` property, and if present its value ****MUST**** be a valid URI string that identifies the protocol the definition pertains to. - The object ****MAY**** contain a `purpose` property, and if present its value ****MUST**** be a string that provides a description for how the data is being used in the protocol. This information will often be used by User Agent applications to display in user consent UI.