Skip to content

Update spec.md #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update spec.md #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
97d0923
Update spec.md
andorsk Mar 7, 2023
56582ad
Update spec/spec.md
andorsk Mar 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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, 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.
Expand Down Expand Up @@ -1460,4 +1460,4 @@ A conforming implementation ****MUST**** be capable of encrypting and decrypting

## Normative References

[[spec]]
[[spec]]