From 68b60732b6dfe0d7fdadb8f37675e84fe1e5f3a4 Mon Sep 17 00:00:00 2001 From: Tracy Kuhrt Date: Tue, 23 Jan 2024 08:01:53 -0700 Subject: [PATCH] Rename AFJ to Credo Signed-off-by: Tracy Kuhrt --- .../credo-high-level-arch.png} | Bin docs/projects/credo-ts.md | 15 ++++++++------- 2 files changed, 8 insertions(+), 7 deletions(-) rename docs/assets/projects/{afj/afj-high-level-arch.png => credo/credo-high-level-arch.png} (100%) diff --git a/docs/assets/projects/afj/afj-high-level-arch.png b/docs/assets/projects/credo/credo-high-level-arch.png similarity index 100% rename from docs/assets/projects/afj/afj-high-level-arch.png rename to docs/assets/projects/credo/credo-high-level-arch.png diff --git a/docs/projects/credo-ts.md b/docs/projects/credo-ts.md index 3ec42a2e..d4eab864 100644 --- a/docs/projects/credo-ts.md +++ b/docs/projects/credo-ts.md @@ -1,21 +1,22 @@ -# Agent Framework JavaScript +# Credo ## Project Description -Agent Framework JavaScript has evolved significantly since its inception as a Hyperledger Aries project. Initially, it heavily relied on Hyperledger standards such as DIDComm, Indy, and AnonCreds. However, with advancements in verifiable credential technology and the emergence of new standards, the framework underwent multiple refactoring and modularization processes to maintain interoperability. +Credo has evolved significantly since its inception as a Hyperledger Aries project. Initially, it heavily relied on Hyperledger standards such as DIDComm, Indy, and AnonCreds. However, with advancements in verifiable credential technology and the emergence of new standards, the framework underwent multiple refactoring and modularization processes to maintain interoperability. This allowed for the inclusion of non-Hyperledger standards like W3C Verifiable Credentials with Data Integrity Proofs, DIF Presentation Exchange, OpenID4VC, and SD-JWT integration. As industry requirements shifted towards greater modularity, it became apparent that a unified framework may be better. -The future direction for Agent Framework JavaScript involves adopting a compartmentalized approach consisting of single-purpose libraries designed to work together seamlessly, building on what is already out there. This transition will take considerable effort and will, therefore, be gradual. +The future direction for Credo involves adopting a compartmentalized approach consisting of single-purpose libraries designed to work together seamlessly, building on what is already out there. This transition will take considerable effort and will, therefore, be gradual. In order to expand the framework's support for standards beyond the Hyperledger ecosystem, a reassessment of its governance was necessary. The OpenWallet Foundation (OWF) was chosen as a steward due to its commitment to promoting interoperability without directly developing or maintaining standard protocols. -![afj-high-level-arch.png](../assets/projects/afj/afj-high-level-arch.png) +![credo-high-level-arch.png](../assets/projects/credo/credo-high-level-arch.png) ## Source Repositories -- [openwallet-foundation/agent-framework-javascript](https://github.com/openwallet-foundation/agent-framework-javascript) -- [openwallet-foundation/agent-framework-javascript-ext](https://github.com/openwallet-foundation/agent-framework-javascript-ext) +- [openwallet-foundation/credo-ts](https://github.com/openwallet-foundation/credo-ts) +- [openwallet-foundation/credo-ts-ext](https://github.com/openwallet-foundation/credo-ts-ext) +- [openwallet-foundation/credo-ts-docs](https://github.com/openwallet-foundation/credo-ts-docs) ## Chat Channel -- [#agent-framework-js](https://discord.com/channels/1022962884864643214/1179453305856991263) on the [OpenWallet Foundation Discord server](https://discord.gg/openwalletfoundation) +- [#credo](https://discord.com/channels/1022962884864643214/1179453305856991263) on the [OpenWallet Foundation Discord server](https://discord.gg/openwalletfoundation)