Open
Description
Should the DSNP specification define rules and semantics of handles? Currently, handles are left as a DSNP system-specific concern, see for example Frequency's handle system. Non-DSNP systems have different approaches to handles, such as DNS-rooted handles in AT Protocol.
What is the minimal level of specification within DSNP that would bring handles into the protocol?
- Should handles be required to be universally unique addresses?
- Can a universal namespace for handles be mandated without an assumption of there being a single consensus system?
- Can the specification support a plurality of implementation approaches to handles?
- Where do handles come into play in the spec? (Activity Content Note, Profile?)
Metadata
Metadata
Assignees
Labels
No labels