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

Definition of the term "client" in regard to SSI principles #261

Closed
marceljay opened this issue Apr 17, 2020 · 8 comments
Closed

Definition of the term "client" in regard to SSI principles #261

marceljay opened this issue Apr 17, 2020 · 8 comments
Assignees
Labels
editorial Editors should update the spec then close pending close Issue will be closed shortly if no objections

Comments

@marceljay
Copy link

I think it would help to clarify what the term client means in the current spec's context. Providing some pragmatic examples to illustrate the role in terms of e.g. DID creation, could help understanding.

The usage of the term confused me in regard to DID CRUD operations and storage of cryptographic key material. There is probably some connection to the term DID Controller, which likewise, is quite abstract.

Especially if we discuss the significance of SSI (human identity) and it's second rule Control. Users must control their identities. I would like to understand the relation to decentralization aspects. This confusion on my part is furthermore amplified since some teams working on DIDs make use of the term Self-Sovereign Identity Provider which by itself sounds a bit centralized.

@kdenhartog kdenhartog added the editorial Editors should update the spec then close label Apr 17, 2020
@kdenhartog
Copy link
Member

This is a more simple way of wording the problem that I was trying to describe in #210

It might be worth taking a look at that issue as well, but I'm in support of adding some language around what you've described.

Heads up @talltree this seems similar to that other discussion we were having over there.

@OR13
Copy link
Contributor

OR13 commented Jun 23, 2020

client "a program that is capable of obtaining a service provided by another program."... in the context of DIDs, i think its the same... anything that uses a resolver is probably a client of a resolver... etc...

@peacekeeper
Copy link
Contributor

I would be in favor of replacing "client" with "DID controller" in sections 7.2.1, 7.2.3, and 7.2.4, and replacing it with "requesting party" in section 7.2.2, in line with the recently merged #350.

As for other occurrences of the term "client" in the spec, I would replace or clarify them on a case-by-case basis. In some cases, I think we can replace "client" with "implementation" or "application" or "DID resolver".

@peacekeeper
Copy link
Contributor

@marceljay do you have any further thoughts on this and about my last comment? I'd be happy to try write a PR to address this issue.

@peacekeeper
Copy link
Contributor

@marceljay any further thoughts on this? Otherwise I will try to write a PR to replace or clarify the term "client" throughout the document.

@marceljay
Copy link
Author

Sorry, I am working on a different project and haven't had looked into the spec ever since.

I think your suggestions are very beneficial. I would add that in those cases where the spec refers to actual software, I would make that clear, just as you suggested.
e.g. client-application or client-implementationcould work well too.

@peacekeeper peacekeeper added the pr exists There is an open PR to address this issue label Sep 8, 2020
@peacekeeper peacekeeper added pending close Issue will be closed shortly if no objections and removed pr exists There is an open PR to address this issue labels Sep 20, 2020
@peacekeeper
Copy link
Contributor

I think this was addressed by #393 and we should be able to close this issue.. Any objections?

@brentzundel
Copy link
Member

No comments since marked pending close, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial Editors should update the spec then close pending close Issue will be closed shortly if no objections
Projects
None yet
Development

No branches or pull requests

5 participants