- From: 陳信屹 <tyson@slashlife.ai>
- Date: Fri, 12 Dec 2025 09:11:09 +0800
- To: Daniel Ramos <daniel@echosystems.ai>
- Cc: public-s-agent-comm@w3.org
- Message-ID: <CAGRPLTMMF9-dVNe=TpHMSwpodQ3aYbNDVG6wt6S9ZowNZGmwLQ@mail.gmail.com>
Thanks Daniel . It would be helpful if you can contribute a CG note for stateful KR bridge . I am working on the CG notes for AgentIDL, liaisons. Daniel Ramos <daniel@echosystems.ai>於 2025年12月12日 週五,上午2:14寫道: > Tyson, > > Thanks for tightening the scope and explicitly allowing SDK implementation > pattern discussion. I’m supportive of the updated draft. A few quick, > concrete suggestions: > > > - Liaisons/Alignment: Consider an explicit liaison note to WebAgents > (interoperability TF) and AIKR, since there’s overlap on interaction > semantics and stateful KR bridges. > - Stateful KR Bridge: Call out that “stateful knowledge systems” can > include spatial/graph representations (e.g., 3D/Euclidean graphs) to avoid > ambiguity with purely text/vector stores. > - Interop/Test Vectors: Add a non‑normative deliverable for an > interoperability test corpus (sample AgentIDL specs + SHACL shapes + > example semantic logs) so implementers have concrete fixtures. > - Discovery/Hypermedia: In the “Interaction Semantics/Conformance” > section, a brief nod to discovery (hypermedia entry points, well‑known > URIs) would anchor the charter to Web architecture best practices. > > I’m happy to contribute examples for the stateful KR bridge and semantic > logs if that’s useful. The charter structure and decision model look good > to me. > > > > Daniel >
Received on Friday, 12 December 2025 01:11:25 UTC