-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Additional check: if interestedParty is a string, the interested party MAY be an entity or a person. #129
Comments
Valid data 1 - generic test set
Valid data 2 - interestedParty is an entity
Invalid data 1 - interestedParty is a string that is not a recordId
Invalid data 2 - interestedParty is the recordId of a relationship statement
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Interpretation of this wording - "The interested party MUST be one of: the recordId for an entity, the recordId for a person, or an Unspecified Record object"
Check 1: If interestedParty is a string check interestedParty refers to a recordId
On fail:
Error message: interested party must be a recordId for a statement in the data set or an UnspecifiedRecord object.
Info message: subject: [VALUE]
Check 2: The recordId in subject refers to an entity statement or person statement
On fail
Error message: Interested party is the recordId of a relationship statement. Interested party can only refer to an entity statement or person statement.
Info message: subject: [VALUE]
The text was updated successfully, but these errors were encountered: