cleanup endpoint section and some todos (#142)

* cleanup endpoint section and some todos

Signed-off-by: 2byrds <2byrds@gmail.com>

* fixed bullet point formatting

Signed-off-by: 2byrds <2byrds@gmail.com>

* more in meeting edits for service endpoints, etc.

Signed-off-by: 2byrds <2byrds@gmail.com>

---------

Signed-off-by: 2byrds <2byrds@gmail.com>

spec/appendix.md

@@ -22,7 +22,7 @@ See also: decentralized identifier, [[ref: self-certifying identifier (SCID)]].
 ### Terminology
 
 [[def: AID controlled identifiers, AID controlled identifier]]
-~ Any identifier, including `did:webs` DIDs, that have the same AID are by definition referencing the same identity. As defined by [KERI]() TODO: Add link to KERI documentation here.
+~ Any identifier, including `did:webs` DIDs, that have the same AID are by definition referencing the same identity. As defined in the [KERI specification](https://trustoverip.github.io/tswg-keri-specification/#controller-application)
 
 [[def: authentic chained data container (ACDC), ACDC, ACDCs]]
 ~ a variant of [[ref: the Verifiable Credential (VC) specification]] that inherits the security model derived from [[ref: KERI]], as defined by the [[ref:  ACDC specification]]. See [WebOfTrust glossary](https://weboftrust.github.io/WOT-terms/docs/glossary/authentic-chained-data-container) for more detail.

spec/diddocuments.md

@@ -417,42 +417,7 @@ For more information, see the [[ref: key agreement]] and [[ref: other key commit
     }
     ```
 
-1. KERI service endpoints roles beyond `witness` SHOULD be defined using Location Scheme and Endpoint Authorization records in KERI.
-
-The following table contains the current set of endpoint roles in KERI and maps the current roles in KERI to service `type` values in the resulting DID documentsis:
-| Role | Description |
-|:-----|:------------|
-|`controller` | The association of the key controller of an AID.  These are always self-referential. |
-|`witness` | A witness for an AID.  This role is already cryptographically committed to the KEL of the source AID and thus does not require and explicit `rpy` authroization event.|
-|`registrar` | Currently unused.|
-| `watcher` | A componenet serving as a Watcher as defined by the KERI protocol (beyond the scope of this document).|
-|`judge` | Currently unused. |
-|`juror` | Currently unused. |
-|`peer` | Currently unused. |
-|`mailbox` | A component authorized to serve as a store and forward mailbox for the source identifier.  This component usually provides a persistent internet connection for AID controllers that are usually off line.|
-|`agent` | A component authorized to serve as an agent running with persistent internet connection.  Provides more funcitonality than a `mailbox`|
-
-TODO: Detail the transformation with an example, for example:
-```json
-{
-  "service": [
-      {
-        "id":"#Bgoq68HCmYNUDgOz4Skvlu306o_NY-NrYuKAVhk3Zh9c",
-        "type": "DIDCommMessaging", 
-        "serviceEndpoint": "https://bar.example.com"
-      }
-      {
-        "id":"#BuyRFMideczFZoapylLIyCjSdhtqVb31wZkRKvPfNqkw",
-        "type": "KERIAgent", 
-        "serviceEndpoint": {
-          "tcp": "tcp://bar.example.com:5542",
-          "https": "https://bar.example.com" 
-        }
-      }
-  ]
-}
-```
-TODO:  Propose a new role in KERI to map to the existing [DIDCommMessaging](https://www.w3.org/TR/did-spec-registries/#didcommmessaging) service type declared in DID Specification Registries.
+1. KERI service endpoints roles beyond `witness` SHOULD be defined using Location Scheme and Endpoint Authorization records in KERI. See the [KERI specification](https://trustoverip.github.io/tswg-keri-specification/#oobi-url-iurl) For more information about KERI roles.
 
 > In KERI, service endpoints are defined by 2 sets of signed data using Best Available Data - Read, Update, Nullify ([[ref: BADA-RUN]]) rules for data processing.  The protocol ensures that all data is signed in transport and at rest and versioned to ensure only the latest signed data is available.
 

spec/impl_guide.md

@@ -275,3 +275,25 @@ This snippet demonstrates how these events occur in the full keri.cesr file. Not
 }-VA0-FABENro7uf0ePmiK3jdTo2YCdXLqW7z7xoP6qhhBou6gBLe0AAAAAAAAAAAAAAAAAAAAAAAENro7uf0ePmiK3jdTo2YCdXLqW7z7xoP6qhhBou6gBLe-AABAADQOX208DAmZEPb2v0XXF0N6WgxOdOxB3AsCBJds_vbAr7v1PQBA4MWNsXc8unk5UykbB8j538XGkzLtujekvIP
 ```
 
+### Adding service endpoint roles in KERI
+
+* A hypothetical new role that could be submitted to KERI, would be the DIDCommMessaging role. It could be specified 
+```json
+{
+  "service": [
+      {
+        "id":"#Bgoq68HCmYNUDgOz4Skvlu306o_NY-NrYuKAVhk3Zh9c",
+        "type": "DIDCommMessaging", 
+        "serviceEndpoint": "https://bar.example.com"
+      }
+      {
+        "id":"#BuyRFMideczFZoapylLIyCjSdhtqVb31wZkRKvPfNqkw",
+        "type": "KERIAgent", 
+        "serviceEndpoint": {
+          "tcp": "tcp://bar.example.com:5542",
+          "https": "https://bar.example.com" 
+        }
+      }
+  ]
+}
+```

spec/privacy_considerations.md

@@ -32,15 +32,15 @@ The root of trust for KERI identifiers is entropy and therefore offers no direct
 two modes of communication, direct mode and indirect mode.  Direct mode allows for pairwise (n-wise as well) relationships that
 can be used to establish private relationships.
 
-TODO: link to KERI docs for additional information about direct and indirect modes.
+See the KERI specification for [more information about direct and indirect modes](https://trustoverip.github.io/tswg-keri-specification/#introduction).
 
 ### Identification
 
 The root of trust for KERI identifiers is entropy and therefore offers no direct means of identification.  In addition, KERI provides
 two modes of communication, direct mode and indirect mode.  Direct mode allows for pairwise (n-wise as well) relationships that
 can be used to establish private relationships.
 
-TODO: link to KERI docs for additional information regarding prefix generation and for a comparison between Direct and Indirect modes.
+See the KERI specification for [more information about secure bindings and prefix derivation](https://trustoverip.github.io/tswg-keri-specification/#keris-secure-bindings)
 
 ### Secondary Use
 

specs.json

@@ -24,7 +24,6 @@
         "interop_profiles.md",
         "normative_references.md",
         "informative_references.md",
-        "acknowledgements_authors.md",
         "appendix.md",
         "impl_guide.md"
       ],