mirrors/fep
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 19:55:46 +00:00
Code Packages Wiki Activity

FEP-844e: Update proposal (#629)

Browse Source 
- Replaced "implementable features" with "capabilities".
- Added RFC-9421 / Ed25519 to the registry.
- Added implementations.
- Added `@context` to examples.

Reviewed-on: https://codeberg.org/fediverse/fep/pulls/629
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
This commit is contained in:
silverpill
2025-06-17 20:17:51 +02:00
committed by silverpill
parent 2a0dac7212
commit fc7c1de613
1 changed files with 19 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fep/844e/fep-844e.md
+19 -4
View File
@@ -25,13 +25,17 @@ An application can advertise its capabilities using the `implements` property on
This object might not be an actor. The value of `implements` property MUST be an array of `Link` objects, each containing the following properties:
- `href` (REQUIRED): the unique identifier of the implementable feature. The value MUST be an URI.
- `name` (RECOMMENDED): the short description of the implementable feature.
- `href` (REQUIRED): the unique identifier of the capability. The value MUST be an URI.
- `name` (RECOMMENDED): the short description of the capability.
Example:
```json
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://w3id.org/fep/844e"
],
"type": "Application",
"id": "https://social.example/server",
"implements": [
@@ -51,6 +55,10 @@ Example:
```json
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://w3id.org/fep/844e"
],
"id": "https://social.example/actors/1",
"type": "Person",
"inbox": "https://social.example/actors/1/inbox",
@@ -77,13 +85,20 @@ The reliance on the mechanism described in this document might increase implemen
Implementers MUST NOT use it in cases where capabilities can be inferred from properties and types of objects.
## Registry of implementable features
## Registry of software capabilities
(This section is non-normative.)
| Name | Identifier |
| --- | --- |
| RFC-9421: HTTP Message Signatures | https://datatracker.ietf.org/doc/html/rfc9421 |
| RFC-9421: HTTP Message Signatures | https://datatracker.ietf.org/doc/html/rfc9421 |
| RFC-9421 signatures using the Ed25519 algorithm | https://datatracker.ietf.org/doc/html/rfc9421#name-eddsa-using-curve-edwards25 |
## Implementations
- Streams
- Forte
- Mitra
## References