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.

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

Consider removing statement ordering requirements #706

Open
kd-ods opened this issue Jun 11, 2024 · 0 comments
Open

Consider removing statement ordering requirements #706

kd-ods opened this issue Jun 11, 2024 · 0 comments

Comments

@kd-ods
Copy link
Collaborator

kd-ods commented Jun 11, 2024

In BODS 0.4 we decided NOT to add a requirement to the effect that "the declarationSubject value of each Statement must match the recordId value of at least one other Statement". The rationale was that this is a stringent requirement which is a relatively heavy lift for the publisher without there being evidence that there is a need for it at the user end. Additionally, with clarity in 0.4 about representing changing BO info over time, there is at least one publishing pattern which would not align with this requirement. That is: a publisher might make regular snapshot datasets available, releasing delta files in between times. Minimal delta files wouldn't meet this additional requirement.

The same thing can be said about the existing (updated) requirement:

the interestedParty and subject values of a Relationship statement, when they are a recordId value, MUST match the recordId value of at least one other prior Statement in the array.

Consider the removal of this requirement.

Originally posted by @kd-ods in #490 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant