this post was submitted on 24 Sep 2024
1 points (100.0% liked)

Fediverse stuff

0 readers
1 users here now

This is a magazine dedicated to posts about the Fediverse and things related to it. This is a MBin magazine, but you can follow it from Lemmy or Piefed as well. If you want to post specifically about Mbin feel free to post into !mbinmeta@gehirneimer.de

Recommended magazines

Rules

  1. Please stay on topic, if it's off-topic please write [META] in the title. Please report off-topic posts if you see them.
  2. Try to avoid drama related posts, for this type of content you can go to !fediverselore@lemmy.ca

founded 2 years ago
MODERATORS
Fitik@fedia.io
1
idk where to really put this (might turn into a blog post later or something). it's what you might call a "hot take", certainly a heterodox one to some parts of the broader #fediverse community. this (mastodon.social)
submitted 11 months ago by trwnh@mastodon.social to c/fediverse@fedia.io
96 comments fedilink hide all child comments
 

idk where to really put this (might turn into a blog post later or something). it's what you might call a "hot take", certainly a heterodox one to some parts of the broader #fediverse community. this is in response to recent discussion on "what do you want to see from AP/AS2 specs" (in context of wg rechartering) mostly devolving into people complaining about JSON-LD and extensibility, some even about namespacing in general (there was a suggestion to use UUID vocab terms. i'm not joking)

1/?

you are viewing a single comment's thread
view the rest of the comments
[–] trwnh@mastodon.social 1 points 11 months ago (1 children)

@by_caballero@mastodon.social yeah i'm not saying AP is "open-world" but rather it straddles the line

AS2 requiring the AS2 context is a bit weird from an LD perspective because it introduces weird "supremacy" conflicts especially with the "MUST NOT override" requirement

i've thought that perhaps jsonld context should only ever be a "progressive enhancement" to json, and that new apis or interchange formats should instead use expanded form, and processors should expand any compacted json(ld) before using it

[–] by_caballero@mastodon.social 1 points 11 months ago* (last edited 11 months ago) (1 children)

@trwnh oh interesting i didn't realize that you meant openworld/closedwforld that literally in the RDF sense, i thought you meant more in the protocol-design sense (of like "drop all unfamiliar properties" as is conventional for all JSON protocols versus "here is how you cautiously parse or preserve for others what you don't know")

[–] by_caballero@mastodon.social 1 points 11 months ago

@trwnh@mastodon.social but that's a difference without a distinction, perhaps