resources: didwebs-tf-2024-01-12
This data as json
| id | type | name | url | maintainer | status | last_checked | date | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| didwebs-tf-2024-01-12 | meeting | did:webs Task Force meeting, 2024-01-12 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998030 | Trust over IP (did:webs Task Force) | quiet | 2026-10-15 | 2024-01-12 | 2024 | practitioner | official | public | Discussion focused on separating normative from informative material before release (issue 120): working back from the normative statements, keeping informative text to a minimum and moving the rest to an appendix, implementation guide or separate paper, following the ToIP (Trust over IP) specification template. A section-by-section review covered core characteristics, the method name, the method-specific identifier ABNF (Augmented Backus-Naur Form), whether statements about the KERI AID (autonomic identifier) should be normative and reference the KERI specifications, and the point that W3C does not allow non-normative references, so a SCID (self-certifying identifier) might be specified at bare minimum. The state of the Hyperledger Labs reference implementation was also on the agenda. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998030 | https://zoom.us/rec/share/s_IiwW9wOtlXHFfu3AlPy0O28zlvrDT-naKVPNX3DnRlvBGf8WxWr_SOSPt96zY.ZfYeUSPyHJDudA0R?startTime=1705071805000 | didwebs-task-force | 1 | 0 |