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

fix(comid): bring ValueTriple into alignment with rev05 #124

Merged
merged 1 commit into from
Aug 14, 2024
Merged

Conversation

setrofim
Copy link
Contributor

@setrofim setrofim commented Aug 14, 2024

At rev00, for reference/endorsed value triples, the CoRIM spec associated an environment with one or more measurements, allowing for two layers of multiplicity.

Since rev01, and up to (current) rev05, the spec removed the second layer, now associating an environment with exactly one measurement.

This commit brings our implementation into alignment with the spec, replacing ValueTriple.Measurements collection with the single ValueTriple.Measurement.

This addresses #123

@thomas-fossati thomas-fossati changed the title fix(comid): bring ValueTriple into alignment with rev04 fix(comid): bring ValueTriple into alignment with rev05 Aug 14, 2024
Copy link
Contributor

@thomas-fossati thomas-fossati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

At rev00, for reference/endorsed value triples, the CoRIM spec
associated an environment with one or more measurements, allowing for
two layers of multiplicity.

Since rev01, and up to (current) rev05, the spec removed the second
layer, now associating an environment with exactly one measurement.

This commit brings our implementation into alignment with the spec,
replacing ValueTriple.Measurements collection with the single
ValueTriple.Measurement.

Signed-off-by: Sergei Trofimov <[email protected]>
Copy link
Contributor

@yogeshbdeshpande yogeshbdeshpande left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@setrofim setrofim merged commit be7ec48 into main Aug 14, 2024
9 checks passed
@setrofim setrofim deleted the triples-fix branch August 14, 2024 10:54
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

Successfully merging this pull request may close these issues.

3 participants