Skip to content
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

Jump to bottom

interestedParty description - normative requirements could be clearer #724

Open
kathryn-ods opened this issue Aug 20, 2024 · 0 comments
Open

interestedParty description - normative requirements could be clearer #724

kathryn-ods opened this issue Aug 20, 2024 · 0 comments
Labels
schema descriptions

Comments

@kathryn-ods
Copy link
Contributor

kathryn-ods commented Aug 20, 2024 •
edited
Loading

Currently the description is "if interestedParty is a string, the interested party MAY be an entity or a person." The use of MAY here could be confusing. Clearer wording could be "The interested party MUST be one of: the recordId for an entity, the recordId for a person, or an Unspecified Record object."
@kathryn-ods kathryn-ods changed the title interestedParty description. interestedParty description - normative requirements could be clearer Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
schema descriptions
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kd-ods @kathryn-ods