-
Notifications
You must be signed in to change notification settings - Fork 78
Open
Description
As below description at the document:
(1) did:wba format example
did:wba format example:
did:wba:example.com:alice
(2) did document example
{
"@context": [ // Defines vocabularies and namespaces used in the document
"https://www.w3.org/ns/did/v1", // W3C DID core vocabulary
"https://w3id.org/security/suites/ed25519-2020/v1", // Ed25519 signature suite
],
"id": "did:wba:example.com%3A8800:user:alice", // DID identifier, uniquely identifies this agent, note the port number ':' is URL encoded (%3A)
"authentication": [ // Specifies verification methods that can be used for authentication (proving control of the DID)
{
"id": "did:wba:example.com%3A8800:user:alice#key-1",
"type": "Ed25519VerificationKey2020", // Another signature algorithm (EdDSA - Edwards-curve Digital Signature Algorithm)
"controller": "did:wba:example.com%3A8800:user:alice",
"publicKeyMultibase": "zH3C2AVvLMv6gmMNam3uVAjZpfkcJCwDwnZn6z3wXmqPV" // Public key in Multibase format, the most important field, used for authentication
}
],
"service": [ // Optional: defines a list of service endpoints associated with this DID
{
"id": "did:wba:example.com%3A8800:user:alice#agent-description", // Unique identifier for the service endpoint
"type": "AgentDescription", // Service type, used to discover the agent's description document
"serviceEndpoint": "https://agent-network-protocol.com/agents/example/ad.json" // URL where the service can be accessed (in this example, the agent description file)
}
// There may be other service endpoints...
]
}
Question:
We can see the url can be ended with "user:alice", "user:alice#key-1" and "user:alice#agent-description". Sometimes the content after the # symbol is a key, and sometimes it is agent-description. It is difficult to make a clear distinction solely based on the current definition of did:wba, which will lead to confusion.
Metadata
Metadata
Assignees
Labels
No labels