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/?

  • infinite love ⴳ@mastodon.socialOP
    link
    fedilink
    arrow-up
    1
    ·
    1 month ago

    @[email protected] 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

    • bumblefudge@mastodon.social
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 month ago

      @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”)