context: add featured definition

erincandescent commented

2024-03-02 20:59:09 +00:00

Contributor

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

Oneric commented

2024-03-02 22:24:48 +00:00

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", ```

erincandescent commented

2024-03-02 22:42:27 +00:00

Author

Contributor

oh yeah likely, will follow up with that

👍 1

Oneric commented

2024-03-09 15:46:25 +00:00

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?

erincandescent commented

2024-03-09 15:52:31 +00:00

Author

Contributor

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