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

5.1.2 StructuredDocuments and EncryptedDocuments use simple 'id' properties while streams use a URI #30

Closed
mwherman2000 opened this issue Feb 15, 2021 · 2 comments

Comments

@mwherman2000
Copy link

  1. Why are streams identified by a URI (e.g. http://...) and not an 'id'.

  2. What if the EDV server instance or the client app doesn't support HTTP, for example?

@mwherman2000
Copy link
Author

That is, the identifiers used for:

  • StructuredDocuments
  • EncryptedDocuments
  • streams
    should be:
  • of the same type (e.g. URIs including DIDs)
  • should be independent of where data vault and server instance the data vault is mounted and the documents/streams reside (e.g. not be fully qualitied URIs/HTTP URLs).
  • at best, should be URI relative to the data vault and the service instance is the data vault is mounted on.
    Else this creates issues for:
  • replicated resources
  • moving (remounting) a data vault from one server instance to another

@dmitrizagidulin dmitrizagidulin transferred this issue from decentralized-identity/confidential-storage May 25, 2021
@msporny
Copy link
Contributor

msporny commented Jul 8, 2021

This issue is stale (the format has changed), and is overtaken by issue #63. Closing.

@msporny msporny closed this as completed Jul 8, 2021
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

No branches or pull requests

2 participants