-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Tracy Kuhrt <tracy.a.kuhrt@accenture.com>
- Loading branch information
Showing
2 changed files
with
8 additions
and
7 deletions.
There are no files selected for viewing
File renamed without changes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ## 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) |