KERI Implementer's Call 05/23/2024

[pfeairheller]

The Primary contact (or backup) for each repo please comment on this discussion prior to the meeting date listed in the title with your update for the week...

KERIpy - @m00sey (main), @pfeairheller (back up)
SignifyPy - @pfeairheller , @m00sey (back up)
KERIA - @rodolfomiranda , @2byrds (backup)
Signify-TS - @kentbull , @daniellenskjö (backup)
Cesride - @kentbull , @daidoji (backup)
Kerific - @kordwarshuis
WOT-Terms - @henkvancann

[pfeairheller]

SigPy:

• No updates

[kordwarshuis]

Kerific:

• No updates

[2byrds]

KERIA:
WebOfTrust/keria#230 is wrapping up.
@pfeairheller updated KERIpy to run parsing locally and provide a delegation escrow processor https://github.com/WebOfTrust/keripy/pull/786/files
@pfeairheller update KERIA agents to leverage the newly available delegation escrow WebOfTrust/keria#246
@2byrds made a complimentary PR to allow the user to approve the delegation after the interaction seal has been added to the KEL and successfully ran the test that @lenkan created as part of issue 230 https://github.com/WebOfTrust/keria/pull/247/files

[henkvancann]

Kerisse (WOT-terms):
Request issue 147: The KERI/ACDC/CESR specifications in spec-up have just one source file: spec.md. This makes it hard to make the term definitions widely available. Could somebody at least cut it in three parts, having the terms-definitions in a separate .md file, called terms_and_definitions.md in each spec.

[henkvancann]

None of the administrators of the repos at hand happened to be present. @SmithSamuelM, @m00sey, @pfeairheller : would you accept a PR to logically split the spec.md up in at least three sources files per repo, once we mitigated the objection and offer edit buttons per section on the frontend side? Spec-up combines the sections into one spec using specs.json.

[pfeairheller]

Yes, I am fine with that approach

[henkvancann]

Done: PRs of the splitted spec.md with clear references to the sub file names for KERI, ACDC and CESR
trustoverip/tswg-keri-specification#179
trustoverip/tswg-cesr-specification#100
trustoverip/tswg-acdc-specification#104
The KERI spec PR looks a bit messy, but it's not. The reason I wasn't able to branch off this activity was that spec-up / github.io wouldn't generate my production site on my user account on the new branch. After looking into it for 2 hrs I chose the practical way: if you accept the PRs and merge them, I will bring in again the older (already discussed and accepted) changes I proposed earlier, but hadn't come to a merge yet

[m00sey]

keripy updates for fixing delegation on main:

WebOfTrust/keripy#784
WebOfTrust/keripy#786

[kentbull]

SigTS

Merged PRs

• fix: remove development from workflow triggers
  • good for publishing an NPM package
• fix: do not include src files in npm package
• signedFetch more generic/configurable aligning it with fetch api

New PRs

• fix: export hab state types from main export
• fix: delete contact by prefix

Other than this there has been some dependent work in KERIA and KERIpy to fix delegation.

CESRide

Nothing new the last week

[edeykholt]

Discussion topics?

1. Signify-ts queries for SignifyClient and the managed identifiers.
2. Discussion of user experience topics (from ACME-V 4/4 call) https://docs.google.com/document/d/14OxmKHltU3PW79uZsk7WP9HsMUbXqpcd3VAqkArWqw4/edit#heading=h.q6lfh4clrcuk

[pSchlarb]

Just bringing WebOfTrust/keripy#775 to attention, not sure if here is the right place to do so.