In ActivityPub, these are all equivalent:
"type":"Banana"
"type":["Banana"]
"type":{"＠id":"Banana"}
"type":[{"＠id":"Banana"}]
"type":{"id":"Banana"}
"type":[{"id":"Banana"}]
"＠type":"Banana"
"＠type":["Banana"]
"＠type":{"＠id":"Banana"}
"＠type":[{"＠id":"Banana"}]
"＠type":{"id":"Banana"}
"＠type":[{"id":"Banana"}]
What do you think about JSON-LD language maps for "preferredUsername"?
I.e., preferredUsernameMap.
"preferredUsernameMap": {
"en": "hello",
"fa": "درود",
"ko": "안녕하세요"
}
The "which BIT" and the - as I call it - #LinkedData conundrum, I addressed recently in a #SocialHub topic on the #JSONLD vs plain #JSON nature of #ActivityPub. Inspired to write a long and personal #SocialExperience tale on my travels in wild #fedi lands. See..
https://social.coop/@smallcircles/116368803389082089
The #EU @ngi #grant programs and the hard work of @nlnet to distribute @EUCommission Horizon Europe #funding has done wonders to take #fediverse where it stands today. In my article I list all the many #FOSS projects that received stimulus and support during the years.
However something fundamental has been lacking in the mandate on who is eligible. Coding is Social. The support does not cover the rich tapestry of #expertise that end-to-end #solutions need during their lifecycle. Does not include fostering cohesive #technology ecosystems, healthy #OpenStandards evolution.
Effectively this creates a 'handover point' of software code from poor FOSS to others who earn a living with it.
As precursor to my blog post announcement later today, here's my #SocialHub response to the topic on how to treat the #LinkedData based #ActivityPub open standard where messages can be expressed both as plain #JSON as well as in #JSONLD, leading to the most costly misconception that has dragged the #fediverse sideways from its original promise and power..
https://socialhub.activitypub.rocks/t/practices-around-json-formatting-of-json-ld-messages/8628/24
Fediverse-we-have is at a major inflection point And so I did, and seeing all the discussion here for which I thank you all, I decided to put in way more effort than originally intended, and delving into much deeper subject matter. The article quotes @SorteKanin and mentions others in this thread, especially @silverpill as the pillar who upholds the FEP process today. I read the discussion with interest, but skipping the implementation details, to take a broader perspective. All of you are rig...
> As an aside, I'm quite liking the ActivityPub APIs so far, although ld-json does leave me feeling like there's a fair jump from "script that works" to "actually does everything the spec would theoretically allow".
There's the "linked data conundrum" as I call it, which recently reared its head again, triggered by a #SocialHub post I created the other day:
https://socialhub.activitypub.rocks/t/practices-around-json-formatting-of-json-ld-messages/8628
The #LinkedData conundrum is the eternal friction between the plain #JSON and the #JSONLD view of the #ActivityPub social web. And it has never really be solved. I consider it one of the misconception that led to endless discussion, confusion, and waste of time. For the ActivityPub API which hold the promise to correct course towards a more standards-compliant #fediverse, I created an issue on the subject..
https://github.com/swicg/activitypub-api/issues/63
Followed by another on protocol design..
ActivityPub is primarily a Linked Data standard. It offers an option for developers to treat it as plain JSON for convenient processing by web technologies. I wonder about the common practice to @context mapping of namespaces to avoid use of namespace prefix in the body of the JSON message. Aren’t we making things too convenient? The problem is that ActivityStreams is a much overused and overloaded vocabulary already, where developers try (and are even encouraged) to map their own application ...
Are there any good talks or videos on JSON-LD in the context of the Fediverse? I've already looked at https://json-ld.org/learn/, but I'm wondering if there are any more recent or Fediverse-focused talks.
Today "ActivityStreams: Where do you want to go to today?" might be a slogan we borrowed from Microsoft.
The question is whether #ActivityStreams should be used - besides all the things it is already being used for - to also map to file systems.
The #LinkedData nature of #ActivityPub is generally shunned in favor of plain #JSON. That in itself is fine, as long as:
a) information still represents valid #JSONLD.
b) information models still follow data modeling best practices.
c) information models are designed with #interoperability in mind.
Not saying your approach is good or bad, just observing that everyone mapping and overloading their own app-specific semantics to the poor AS vocab looks to me a worst-practice. We can get away with it, as we made post-facto interop the poor man's accepted practice, lacking more rigorous extension process and guidance.
There are likely existing standardized ontologies.
@reiver ⊼ (Charles) 
🫧 socialcoding..
PPC Land
Samuel Brinkmann
Vivien (dentelle & numérique)