Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://social.coop/users/smallcircles/statuses/111871792852689722">smallcircles (Humanity Now 🕊) (smallcircles@social.coop)'s status on Sunday, 04-Feb-2024 16:22:02 JST</a><a href="https://social.coop/@smallcircles" title="smallcircles@social.coop"><img src="https://gnusocial.jp/avatar/20921-48-20221109043055.webp" width="48" height="48" alt="smallcircles (Humanity Now 🕊)" style="position: absolute; left: 0; top: 0;">smallcircles (Humanity Now 🕊)</a><div><a href="https://techhub.social/@manlycoffee/111870578918180970" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://techhub.social/@manlycoffee">@manlycoffee</a> given that protocol extensibility isn't well defined, protocol flavors are created all the time, protocol decay introduced (broad interop becomes ever harder). Imho there's merit in considering <a href="https://social.coop/tags/ActivityPub" rel="tag">#ActivityPub</a> to be JSON-first and have a JSON-LD approach for those who wanna go the extra mile.</p><p>An extension for a particular domain requires docs/specs and validation, where JSON-LD isn't best suited. See:</p><p><a href="https://socialhub.activitypub.rocks/t/activitypub-a-linked-data-spec-or-json-spec-with-linked-data-profile/3647" rel="nofollow noreferrer">https://socialhub.activitypub.rocks/t/activitypub-a-linked-data-spec-or-json-spec-with-linked-data-profile/3647</a></p><p><a href="https://socialhub.activitypub.rocks/t/linkml-for-definition-of-activitypub-extension-schemas/3838" rel="nofollow noreferrer">https://socialhub.activitypub.rocks/t/linkml-for-definition-of-activitypub-extension-schemas/3838</a></p><p><a href="https://socialhub.activitypub.rocks/t/initiative-activitypub-step-on-board-integration-guide/3542" rel="nofollow noreferrer">https://socialhub.activitypub.rocks/t/initiative-activitypub-step-on-board-integration-guide/3542</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2674494#notice-5300987">In conversation</a><time datetime="2024-02-04T16:22:02+09:00" title="Sunday, 04-Feb-2024 16:22:02 JST">about 10 months ago</time> <span>from <span><a href="https://social.coop/@smallcircles/111871792852689722" rel="external" title="Sent from social.coop via ActivityPub">social.coop</a></span></span><a href="https://social.coop/@smallcircles/111871792852689722">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/2210561">Untitled attachment</a></label><br></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
smallcircles (Humanity Now 🕊) (smallcircles@social.coop)'s status on Sunday, 04-Feb-2024 16:22:02 JSTsmallcircles (Humanity Now 🕊)
in reply to
- Sal Rahman
@manlycoffee given that protocol extensibility isn't well defined, protocol flavors are created all the time, protocol decay introduced (broad interop becomes ever harder). Imho there's merit in considering #ActivityPub to be JSON-first and have a JSON-LD approach for those who wanna go the extra mile.
An extension for a particular domain requires docs/specs and validation, where JSON-LD isn't best suited. See:
https://socialhub.activitypub.rocks/t/activitypub-a-linked-data-spec-or-json-spec-with-linked-data-profile/3647
https://socialhub.activitypub.rocks/t/linkml-for-definition-of-activitypub-extension-schemas/3838
https://socialhub.activitypub.rocks/t/initiative-activitypub-step-on-board-integration-guide/3542
In conversationabout 10 months ago from social.cooppermalink
Attachments
1. Untitled attachment

Public

Embed Notice

HTML Code

Corresponding Notice