-
Notifications
You must be signed in to change notification settings - Fork 16
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
Proposal to rephrase the Reg_Info definition #113
Conversation
Good clarification, with a few nits to reduce and clarify the text |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great improvement, a couple of small suggestions
Co-authored-by: Steve Lasker <[email protected]> Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Steve Lasker <[email protected]>
Co-authored-by: Jon Geater <[email protected]> Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Jon Geater <[email protected]>
Signed-off-by: steve lasker <[email protected]>
All edits have been addressed. I believe this is ready for merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as it addresses all feedback and clarifies the conversations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer "The key/value pair semantics are application-specific, or even possibly specified by each Issuer for each of their Feed." but I am fine with both formulations. Thanks.
Merging as this is a well discussed pattern with SCITT Co-authored-by: Orie Steele <[email protected]>
Thanks, @fournet |
Fixes #112