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

Swap relying party for requesting party Will fix #248 #350

Merged
merged 1 commit into from
Jul 28, 2020

Conversation

philarcher
Copy link
Contributor

@philarcher philarcher commented Jul 16, 2020

In line with the WG's resolution on 2020-06-30, this minimal PR swaps the 3 instances of 'replying party' for 'requesting party'. If merged, Issue #248 can be closed. The closely related issue in the Use Cases document, (issue 39 in that repo) has been closed and the UCR now consistently refers to requesting parties (actually, it refers to Requesting Parties, with upper case R and P, which is a difference from the core spec but probably not something to worry about too much).


Preview | Diff

In line with the WG's [resolution on 2020-06-30](https://www.w3.org/2019/did-wg/Meetings/Minutes/2020-06-30-did#resolution1), this minimal PR swaps the 3 instances of 'replying party' for 'requesting party'. If merged, Issue #248 can be closed. The closely related issue in the Use Cases document, ([issue 39](w3c/did-use-cases#39) in that repo) has been closed and the UCR now consistently refers to requesting parties (actually, it refers to Requesting Parties, with upper case R and P, which is a difference from the core spec but probably not something to worry about too much).
Copy link
Member

@msporny msporny left a comment

Choose a reason for hiding this comment

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

LGTM.

@msporny
Copy link
Member

msporny commented Jul 28, 2020

I was waiting for more reviewers, seeing none, and assuming that this isn't a controversial PR (it's editorial), and given that is resolves issue #248, and given that it'll be easy to back out if someone objects post-merge... I'm going to merge this.

Editorial, at least one review by an Editor, no objections, it's been 12 days (giving people enough time to review/object), resolves an issue if merged... merging.

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.

2 participants