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
As an end user, I want to manage multiple profiles finely and decide who can see what profile, So that I can increase my privacy.
Preconditions:
N/A
Trigger:
N/A
Actors:
End users who care about their privacy.
Distinction:
Ideally I would like to be able to have a fine-grained control of my profile, because I may want to share my picture or phone number or home address with some people, and not with others. But this is difficult to handle in a resource-based scenario, except if every kind of data is its own resource.
Scenario:
When connecting to an application or joing a group, I can decide what profile I want to share.
I have one public profile (typically my webId) but I can also have multiple private profiles.
I know who can see what profile, and I can revoke that right at any moment.
Alternative case(s):
I can have not only several profiles, but also several identifiers (WebID, DIDs...)
Error scenario:
N/A
Acceptance Criteria:
N/A
References:
Private discussion with several people for whom this capacity is very important.
The text was updated successfully, but these errors were encountered:
To avoid confusion, can you please clarify the relationship between identities and profiles in your proposal?
The way I understand it is that an [entity]/user SHOULD be able to manage multiple identities (associated with different, unique identifiers). Each profile corresponds to a different identity in a one-to-one relation. An [entity] would have a master identity that manages/controls these other identities and hence the associated profiles.
To avoid confusion, can you please clarify the relationship between identities and profiles in your proposal?
In ActivityPods, an user has a single identity (WebID) but sensitive data are stored in a private profile, apart from the WebID (which must always be public). In the Pod management frontend, they can edit their public profile (= WebID) and their private profile. In the future, we may allow to have multiple private profiles, so they can be shared with different audiences.
The way I understand it is that an [entity]/user SHOULD be able to manage multiple identities (associated with different, unique identifiers). Each profile corresponds to a different identity in a one-to-one relation. An [entity] would have a master identity that manages/controls these other identities and hence the associated profiles.
That would be better for privacy, but as far as I understand it would be much more difficult to implement.
As an end user,
I want to manage multiple profiles finely and decide who can see what profile,
So that I can increase my privacy.
Preconditions:
N/A
Trigger:
N/A
Actors:
End users who care about their privacy.
Distinction:
Ideally I would like to be able to have a fine-grained control of my profile, because I may want to share my picture or phone number or home address with some people, and not with others. But this is difficult to handle in a resource-based scenario, except if every kind of data is its own resource.
Scenario:
When connecting to an application or joing a group, I can decide what profile I want to share.
I have one public profile (typically my webId) but I can also have multiple private profiles.
I know who can see what profile, and I can revoke that right at any moment.
Alternative case(s):
I can have not only several profiles, but also several identifiers (WebID, DIDs...)
Error scenario:
N/A
Acceptance Criteria:
N/A
References:
Private discussion with several people for whom this capacity is very important.
The text was updated successfully, but these errors were encountered: