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

Conditional endorsement triple processing order "is important" #335

Open
deeglaze opened this issue Oct 23, 2024 · 2 comments
Open

Conditional endorsement triple processing order "is important" #335

deeglaze opened this issue Oct 23, 2024 · 2 comments

Comments

@deeglaze
Copy link
Collaborator

The order should not be important so long as additions are followed by triple processing that has a condition that could match it. We don’t want to impose other order dependencies unless you need to stratify triple processing more explicitly.

Given that we’re defining a processing order for base triples, it should also be allowable for profiles to specify when their triples get processed if indeed order is important. Will they always be after the base triples, or can they be specified to happen at any time?

@deeglaze
Copy link
Collaborator Author

See also #321

@nedmsmith
Copy link
Collaborator

Given that we’re defining a processing order for base triples, it should also be allowable for profiles to specify when their triples get processed if indeed order is important. Will they always be after the base triples, or can they be specified to happen at any time?

Evidence is the only CM type that doesn't require a condition. All the other CM types presume some sort of condition. Even the optional stages imply some sort of ACS condition has to exist before the stage can be processed.

Profiles shouldn't, IMO, be permitted to change the basic assumption that an ACS condition has to be satisfied as a pre-condition to processing a profile defined triple. The spec normative claims that the ACS in in a consistent state at the end of phase 4. If a profile is permitted to inject itself before phase 4 it should be held to the same standard. But possibly, the spec should not permit this. Essentially, we would be saying profile defined phases are always optional and hence would be applied when the other optional phases are performed. I'm not sure I have an opinion about the ordering of optional phases. Ideally, that wouldn't matter, but if it does, it would be OK for the profile to say which other optional phases should go first. At least that is my initial thinking.

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

No branches or pull requests

2 participants