From 22bcb9175bfca1a169f6b15ec56ca5d322813b9d Mon Sep 17 00:00:00 2001 From: Troy Ronda Date: Thu, 13 May 2021 16:01:36 -0400 Subject: [PATCH] docs: remove local example (#9) Signed-off-by: Troy Ronda --- index.html | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/index.html b/index.html index 918bfd9..c426283 100644 --- a/index.html +++ b/index.html @@ -401,11 +401,9 @@

The did:orb Format

did-orb-format = "did:orb:" (orb-canonical-did / orb-scheme-did / unpublished-did) orb-canonical-did = min-graph-cid ":" did-suffix orb-scheme-did = (dht-scheme / webcas-scheme) ":" orb-canonical-did - unpublished-did = "interim:" (web-interim-scheme / local-interim-scheme) + unpublished-did = "interim:" reg-name ":" did-suffix [":" long-form-suffix-data] dht-scheme = ( "ipfs" ) webcas-scheme = "webcas:" reg-name - web-interim-scheme = reg-name ":" did-suffix - local-interim-scheme = "local" ":" did-suffix [":" long-form-suffix-data] reg-name = 1*idchar ; more constrained than [RFC3986] min-graph-cid = 10*idchar ; a short 3rd segment is reserved for schemes. did-suffix = 1*idchar @@ -519,16 +517,12 @@

Propagation Delay and Canonical IDs

to return a resolution result without additional prefix information. This situation typically occurs when there is a need to immediately use a freshly created DID suffix that hasn't yet been propagated. -
-            did:orb:interim:local:EiA329wd6Aj36YRmp7NGkeB5ADnVt8ARdMZMPzfXsjwTJA
+          
+            did:orb:interim:example.com:EiA329wd6Aj36YRmp7NGkeB5ADnVt8ARdMZMPzfXsjwTJA
           
-            did:orb:interim:local:EiA329wd6Aj36YRmp7NGkeB5ADnVt8ARdMZMPzfXsjwTJA:ey...
-          
- -
-            did:orb:interim:example.com:EiA329wd6Aj36YRmp7NGkeB5ADnVt8ARdMZMPzfXsjwTJA
+            did:orb:interim:example.com:EiA329wd6Aj36YRmp7NGkeB5ADnVt8ARdMZMPzfXsjwTJA:ey...
           
When an Orb Server has propagation information for a resolved DID, the server includes the min-graph-cid segment within the canonicalId @@ -538,6 +532,11 @@

Propagation Delay and Canonical IDs

After a DID controller sends a Create or Recover operation to an Orb Server, the resolution result may have no (or an outdated) min-graph-cid segment. The DID controller may need to retry resolution until the operation has been propagated and the CID becomes available. Once the CID is available, resolution responses contain the updated canonicalId property. + +

+ Since Orb is based on ActivityPub, we should have a domain available for interim DIDs. + Are there cases where we would indicate no domain with a value like 'local'? +