context: add featured definition #717

Merged
floatingghost merged 1 commits from erincandescent/akkoma:context-featured into develop 2024-04-03 10:22:10 +00:00
Contributor

This was missing from our context, which caused interoperability issues for people who do context-based JSON-LD processing

This was missing from our context, which caused interoperability issues for people who do context-based JSON-LD processing
erincandescent added 1 commit 2024-03-02 20:59:09 +00:00
ci/woodpecker/pr/build-amd64 Pipeline is pending Details
ci/woodpecker/pr/build-arm64 Pipeline is pending Details
ci/woodpecker/pr/docs Pipeline is pending Details
ci/woodpecker/pr/lint Pipeline is pending Details
ci/woodpecker/pr/test Pipeline is pending Details
94b326ddde
context: add featured definition
This was missing from our context, which caused interoperability issues with
people who do context processing
Member

I guess the followigng should also be added then to account for #682?

sharkey: "https://joinsharkey.org/ns#",
backgroundUrl: "sharkey:backgroundUrl",
I guess the followigng should also be added then to account for #682? ```json sharkey: "https://joinsharkey.org/ns#", backgroundUrl: "sharkey:backgroundUrl", ```
Author
Contributor

oh yeah likely, will follow up with that

oh yeah likely, will follow up with that
Member

I just learned litepub-0.1.jsonld isn’t just an *oma thing but comes from https://litepub.social/

At the one hand, adding non-standard stuff to it maybe confusing, on the other hand LitePub is stalled for soon 5 years so it might not matter anyway.
JSON not having first-class comments makes adding a delimiter between standard LitePub and our extensions a bit more diffuclt. Mayhaps we can add a second file, or maybe it doesn’t matter at all?

I just learned `litepub-0.1.jsonld` isn’t just an \*oma thing but comes from https://litepub.social/ At the one hand, adding non-standard stuff to it maybe confusing, on the other hand LitePub is stalled for soon 5 years so it might not matter anyway. JSON not having first-class comments makes adding a delimiter between standard LitePub and our extensions a bit more diffuclt. Mayhaps we can add a second file, or maybe it doesn’t matter at all?
Author
Contributor

I was thinking about that; it would be aesthetically pleasing to rename the file. But I wanted to separate that change

I was thinking about that; it would be aesthetically pleasing to rename the file. But I wanted to separate that change
Author
Contributor

(by the way sorry for not following up on these - I was on a business trip to Paris)

(by the way sorry for not following up on these - I was on a business trip to Paris)
Member

(by the way sorry for not following up on these - I was on a business trip to Paris)

no worries, all good

> (by the way sorry for not following up on these - I was on a business trip to Paris) no worries, all good
erincandescent force-pushed context-featured from 94b326ddde to 8fbd771d6e 2024-04-01 11:39:54 +00:00 Compare
Oneric approved these changes 2024-04-01 23:28:57 +00:00

yep, all good, thanks!

yep, all good, thanks!
floatingghost merged commit b8393ad9ed into develop 2024-04-03 10:22:10 +00:00
floatingghost deleted branch context-featured 2024-04-03 10:22:10 +00:00
Sign in to join this conversation.
No description provided.