# A namespace for things defined in FEPs

**URL:** <https://socialhub.activitypub.rocks/t/a-namespace-for-things-defined-in-feps/2374>\
**Category:** Community\
**Created:** [April 7, 2022, 9:35am UTC](https://socialhub.activitypub.rocks/t/a-namespace-for-things-defined-in-feps/2374 "2022-04-07T09:35:02Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Sebastian](https://socialhub.activitypub.rocks/user_avatar/socialhub.activitypub.rocks/sebastian/32/38_2.png) [@Sebastian](https://socialhub.activitypub.rocks/u/Sebastian)\
**Post date:** [April 8, 2022, 11:28am UTC](https://socialhub.activitypub.rocks/t/a-namespace-for-things-defined-in-feps/2374/9 "2022-04-08T11:28:34Z")

</div>

> [@aschrijver](#):
>
> that most implementations do not support yet

Which do not support it?  
If they do not support multiple type, it is not ActivityPub at all.  
If they do not support some of the type, it is fine as long the ActivityPub type(s) are supported. But I choosed the example cause if I understood correctly in “Common Domain”, you proposed to use `sioc:` to describe our systems.

---

_[View the full topic](https://socialhub.activitypub.rocks/t/a-namespace-for-things-defined-in-feps/2374)._
