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

Incorporate additional custom proof options #88

Merged
merged 7 commits into from
Jul 30, 2024

Conversation

Wind4Greg
Copy link
Contributor

@Wind4Greg Wind4Greg commented Jul 1, 2024

This PR addresses issue #74. It updates the proof configuration procedures to use a clone of the options input and then updates the procedures accordingly.


Preview | Diff

Copy link
Member

@TallTed TallTed left a comment

Choose a reason for hiding this comment

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

Editorial. Grammar, etc.

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
Set <var>proofConfig</var>.<var>verificationMethod</var> to
<var>options</var>.<var>verificationMethod</var>.
Set |proofConfig|.<var>@context </var>to
|unsecuredDocument|.<var>@context</var>.
Copy link
Contributor

@dlongley dlongley Jul 2, 2024

Choose a reason for hiding this comment

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

This seems like it was erroneously copied from the jcs cryptosuite ... am I just misreading it? It looks like it might be in the wrong place because I didn't see it in the jcs cryptosuite in this spec.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think this is right. Before we can canonize the proofConfig we need to add @context. Right? This was something that we had to fix way back when I started figuring out how to generate the test vectors...

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah, yes, ok.

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
@msporny
Copy link
Member

msporny commented Jul 15, 2024

@Wind4Greg merge conflicts, please fix.

@dlongley and @Wind4Greg, I can't tell if we still need to make changes on this PR or not.

@msporny msporny requested a review from dlongley July 15, 2024 15:33
@Wind4Greg
Copy link
Contributor Author

@msporny fixed merge conflicts as best I could. Don't know if I dropped some punctuation updates or not. A lot of small editorial updates have been happening.

Set <var>proofConfig</var>.<var>verificationMethod</var> to
<var>options</var>.<var>verificationMethod</var>.
Set |proofConfig|.<var>@context </var>to
|unsecuredDocument|.<var>@context</var>.
Copy link
Contributor

Choose a reason for hiding this comment

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

Ah, yes, ok.

@msporny msporny added normative This item is a substantive or normative change. CR1 labels Jul 30, 2024
@msporny msporny merged commit 4e3bb98 into w3c:main Jul 30, 2024
2 checks passed
@msporny
Copy link
Member

msporny commented Jul 30, 2024

Normative, multiple reviews, changes requested and made, no objections, merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CR1 normative This item is a substantive or normative change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants