# Wiki: Vision for a Fedi Specification

**URL:** <https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563>\
**Category:** Prosocial foundations\
**Tags:** wiki, social-web, vision\
**Created:** [November 14, 2024, 10:09am UTC](https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563 "2024-11-14T10:09:40Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![helge](https://discuss.coding.social/user_avatar/discuss.coding.social/helge/32/252_2.png) [@helge](https://discuss.coding.social/u/helge)\
**Post date:** [November 18, 2024, 1:35pm UTC](https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563/10 "2024-11-18T13:35:43Z")

</div>

Hi jens. Welcome 👋 And thanks for your contribution.

> [@jfinkhaeuser](#):
>
> I’d personally stay away from the “social web” term. Most people will read “web” and think HTTP. That’d clash with the above shift in design approach.

I have a long list of thoughts on this. I start with the following quote

> [@aschrijver](#):
>
> Most important that we start speaking a common language, a Ubiquitous language (UL), right from the start.

I think these two statements go hand in hand: We need a language to describe a Fedi specification that has a few properties. I’m using the vision concept from above.

#### Vision / Concept: A common and inclusive language to work on

#### Functional requirements

- Provide reusable templates for tasks

#### Non-functional requirements

- Be inclusive; avoid terms that people find offensive, e.g. allowlist not whitelist.
- Minimal friction to clarify what something means
- Language does not suggest a solution

Second @jfinkhaeuser Would you be willing to take a look from time to time that we do not preclude the use of non HTTP technologies when not necessary?

Third: I personally think I made the first mistake here by talking about “Vision for a Fedi Specification”. I think the use of “a” implies that the result will be a single document. This is kind of not what I expect. I think that the result of “specifying the Fediverse” would be a sequence of documents, some of them being able to be used by arbitrary network technologies, some requiring HTTP.

---

_[View the full topic](https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563)._
