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

[mwherman2000]

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]

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

[msporny]

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