---
# System prepended metadata

title: The Web5 Platform

---

# The Web5 Platform


Open Questions for call:
* ENG DRI for Web5?
* Contributing?
* OSE apps to refactor to Web5?
  * TODO App?
  * Dignal?
  * Yeeter?
  * CLI - interacting w/ Web5 from command line (JavaScript CLI app)
  * ALR - issue tasks to OSE asking for refactoring to Web5. 
  * OSE to start w/ in-page usage of these, pendind code Frank is working on right now for DID creation stuff

[Site Map](https://hackmd.io/RZ5B8Hp6TIGcC9tnDtZ3fw?view) implications:
* Bobbilee/Moe suggesting we restructure for Austin: focusing on web5-js and guides and content around that
* ALR note: consider how future top-level projects like tbDEX slate alongside that
* ...and how subprojects like DWN, SSI Suite are structured with lesser prominence; those direct usages are for more expert cases.

Installation requirements:
* Qs:
  * Where are we releasing to? Are there versioning/naming conventions?
  * Nick: can we name space our JS libraries with something like "@tbd/*"? That way users can differentiate between Web5 libraries made by us vs other libs that might get made?
    * Answer: https://www.npmjs.com/package/@tbd54566975/web5

Use cases we want to highlight:
* 

Contains:
* web5-js API:
  * **DID**
    * Create DIDs
      * did:ion
      * did:key
    * Resolving DIDs
    * Manage key material associated with DIDs
    * TODO: Bridge solutions for ION in JS until they can be ready in SSI-SDK in Go
  * **DWN**
    * Records
      * Write
      * Delete
      * Query
      * Read
    * Protocols
      * Configure
      * Query
  * **Agent App Interactions (Desktop)**
    * Request DID (with authn)
    * Request Permission
    * Deliver VC
