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

8.2 Use of the term "portability" #25

Open
martchcl opened this issue Aug 30, 2022 · 0 comments
Open

8.2 Use of the term "portability" #25

martchcl opened this issue Aug 30, 2022 · 0 comments
Assignees
Labels
priority: medium This issue is important to resolve before the next release. type: content The issue involves normative content; resolution requires group consensus.

Comments

@martchcl
Copy link
Contributor

fully portable.

Allan Thomson
10:37 24 Aug
is this term well-defined and understood? I think I know what it means but for example, can I take a ToIP Identity that was defined on an iOS Phone and move it to a Google Android phone or a Linux desktop? I think the intent to this statement is 'yes' but some might think that portable just means between a phone and a cloud of the same vendor that defined the identifier.

Example: passkeys that can't be shared across OS vendor ecosystems.

Daniel Hardman
07:09 25 Aug
+1 to the question. I also agree with Allan's definition, but would add a second one as well. "Fully portable" implies that the identifier can be moved to different infrastructure (e.g., a different blockchain, or no blockchain at all).

@talltree talltree self-assigned this Oct 17, 2022
@talltree talltree added priority: medium This issue is important to resolve before the next release. type: content The issue involves normative content; resolution requires group consensus. labels Oct 17, 2022
@talltree talltree changed the title 8.2 Identifiers 8.2 Use of the term "portability" Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium This issue is important to resolve before the next release. type: content The issue involves normative content; resolution requires group consensus.
Projects
None yet
Development

No branches or pull requests

2 participants