You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should we add a comparison routine to each of the CoMID measurement values?
For example, if a verifier wants to compare an SVN with a reference SVN, they would implement the comparison algorithm for SVN as defined in the base CoRIM spec. But this isn't efficient. Instead of each verifier needing to convert the SVN to one of the tagged-svn types and compare the two measurements based on the SVN sub-type (exact-value or min-value), we can do that in the CoRIM repo.
Given each mval type has its comparison algorithm, it'd be best if these types implemented a "Compare" routine that compares it with another mval.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered:
Should we add a comparison routine to each of the CoMID measurement values?
For example, if a verifier wants to compare an SVN with a reference SVN, they would implement the comparison algorithm for SVN as defined in the base CoRIM spec. But this isn't efficient. Instead of each verifier needing to convert the SVN to one of the tagged-svn types and compare the two measurements based on the SVN sub-type (exact-value or min-value), we can do that in the CoRIM repo.
Given each mval type has its comparison algorithm, it'd be best if these types implemented a "Compare" routine that compares it with another mval.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered: