This topic is in reaction to the following (and would be OT there):
I am sorry in advance if this shows technical ignorance (to my regret and own fault I don’t manage to get rid of non-technical stuff in favor of ‘deep work’ and coding).
In Fediverse Futures: Visions & dreams. Feedback wanted I make a case in elaborating business cases for specific application domains, aligning with the idea of defining specific and standardized Linked Data vocabularies for that (think ForgeFed) and implementations able to handle them (think go-fed, openEngiadina, BonFire, etc.)
(PS I also suggested Domain Driven Design as an excellent way to elaborate these vocabularies)
In terms of the namespace to use for them, a
https://activitypub.dev/fep/ns# wouldn’t cut it then. The namespace should specifically address the application / business domain that the vocabulary extension targets, e.g.
or (different scheme):
Or something else entirely, as @pukkamustard suggests we elaborate.