Design solution did:webs identifier-resolution on KERISSE github pages

[henkvancann]

Cause: we've been discussing authenticated curation of KERISSE content & functionality, thereby using our own technology: KERI.
Topic of this discussion: how to solve did:webs identifier-resolution on KERISSE github pages with the current state of development.
Possibility: to combine did-webs testing & implementation on KERISSE github pages.

[henkvancann]

I've tested the docker container IIW tutorial: https://github.com/peacekeeper/did-webs-iiw37-tutorial . Got it going, with support of Markus and team (thanks again!).

We could use the administrative identifier of Github, but that has two weaknesses:

1. we'd like to use KERI identifiers instead of relying on the onboarding done by Github.
2. we trust a username / password combination for the authentication at all times.

My investigation in using KERI identifiers raised questions.

A. Wondering if I get it right:

• although the AID is created in the indirect mode, the docker container itself is ephemeral. That means: if I get an update (of the code) in the Docker container there's no way to continue with state and the incepted AID in the container. It's a limited tutorial setup. Right?
• If I'd like to use external witnesses (outside the container), this can be done?!
• Anyone could register an AID anywhere, anytime, set up their publicly reachable witnesses, run them, create a did:webs DID document, upload them to any publicly reachable server, fulfil the OOBI resolution process and start curating KERISSE content by using this identifer?
• Anyone anytime anywhere can validate the signatures of the curator using did-webs resolution, either remote of local (preferred).

B. Questions

• OOBI Resolution (discovery) is two-way for every relationship for the curation established. Is there no other way to do the discovery of a group of AIDs that curate the content of KERISSE?
• If I'd like to use the AID in the github page of KERISSE, which is https://weboftrust.github.io/WOT-terms, how would this look like. How to sign off content there?
• Could we authorize a certain set of AID to do certain curations? And if so how would this be done?
• How to stay in control of the AID generated by the tutorial docker container?