Exploratory Names

Exploratory properties of good name choices:

• Short
• No collisions
• Should not snark/pun on existing similar solutions (like Solid Pods, for example)
• Should not make people think “This already exists; Google Drive / Dropbox”
  • bengo: e.g. “encrypted”? +1 – manu
• Should not suggest that this is more secure or decentralized than it really is.
  • bengo: As CCG has discussed, there are many definitions of ‘decentralized’, and there is usually a better choice of words.
  • bengo: Im new to the spec, but I was under the impression it would be possible to implement SDS in a very traditional/centralized architecture, while also enabling some new ones.

Exploratory properties of names that may not be important:

• globally unique
• resolvable
• works with posix tools for resolving names. A valid name could be ‘enrypted.data’, whois encrypted.data
• name is syntax-compatible with other standards
• decision reached via Formal Consensus
  • bengo: I believe it’s probably possible to make this decision via this protocol, but not desirable if fielding concerns takes more than x weeks (x=4?). Mitigation: if consensus takes longer than y weeks, group could vote on a resolution to bound the debate to z weeks.