[TRACKING] FEP-67ff: FEDERATION.md #157

New issue

Open

opened 2023-09-08 09:21:29 +00:00 by helge · 4 comments

helge commented

2023-09-08 09:21:29 +00:00

Owner

The proposal has been received. Thank you!

This issue tracks discussions and updates to the proposal during the DRAFT period.

Please post links to relevant discussions as comment to this issue.

dateReceived: 2023-09-05

If no further actions are taken, the proposal may be set by editors to WITHDRAWN on 2024-09-04 (in 1 year).

The [proposal](https://codeberg.org/fediverse/fep/src/branch/main/fep/67ff/fep-67ff.md) has been received. Thank you! This issue tracks discussions and updates to the proposal during the `DRAFT` period. Please post links to relevant discussions as comment to this issue. `dateReceived`: 2023-09-05 If no further actions are taken, the proposal may be set by editors to `WITHDRAWN` on 2024-09-04 (in 1 year).

helge commented

2023-09-08 09:23:27 +00:00

Author

Owner

Discussion topic https://socialhub.activitypub.rocks/t/fep-67ff-federation-md/3555

cc @silverpill

Discussion topic https://socialhub.activitypub.rocks/t/fep-67ff-federation-md/3555 cc @silverpill

helge added the

FEP Draft

label 2023-09-21 07:43:11 +00:00

silverpill commented

2024-04-21 10:53:56 +00:00

Owner

I'm requesting final comments.

avidseeker commented

2024-07-15 17:29:26 +00:00

Contributor

XMPP has a similar implementation XEP-0453 of a schema called DOAP (Description of a Project).

It includes the following fields:

xep: The URL to the XEP document. (Required)
status: The support status by this project, can be 'complete', 'partial', 'planned', 'deprecated', 'removed' or 'wontfix'. (Required)
version: XEP version implemented by this software. (Optional)
since: Software version this support first appeared in. (Optional)
note: Any implementation note the project deems relevant. (Optional)

A human-readable FEDERATION.md is great, but it should also be joined with something like FEDERATION.json that is machine-readable. It makes it possible to have automated lists of software support status such as: https://xmpp.org/extensions/. I'd also suggest to have a schema close to DOAP schema, just so that we're not re-inventing the wheel.

XMPP has a similar implementation [XEP-0453](https://xmpp.org/extensions/xep-0453.html) of a schema called [DOAP (Description of a Project)](https://github.com/ewilderj/doap). It includes the following fields: * xep: The URL to the XEP document. (Required) * status: The support status by this project, can be 'complete', 'partial', 'planned', 'deprecated', 'removed' or 'wontfix'. (Required) * version: XEP version implemented by this software. (Optional) * since: Software version this support first appeared in. (Optional) * note: Any implementation note the project deems relevant. (Optional) A human-readable FEDERATION.md is great, but it should also be joined with something like FEDERATION.json that is machine-readable. It makes it possible to have automated lists of software support status such as: https://xmpp.org/extensions/. I'd also suggest to have a schema close to DOAP schema, just so that we're not re-inventing the wheel.

silverpill commented

2024-07-15 18:22:27 +00:00

Owner

A machine-readable NodeInfo implementation report has been proposed in FEP-6481. Another idea was to use the instance actor (link). I don't have a strong opinion on file vs nodeinfo vs actor, that should probably be decided by people who develop testing tools.

A machine-readable NodeInfo implementation report has been proposed in [FEP-6481](https://codeberg.org/fediverse/fep/src/branch/main/fep/6481/fep-6481.md). Another idea was to use the instance actor ([link](https://socialhub.activitypub.rocks/t/fep-67ff-federation-md/3555/5)). I don't have a strong opinion on file vs nodeinfo vs actor, that should probably be decided by people who develop testing tools.