@everton137 I recommend doing your own research. Some of the points being made about BSky don't appear accurate to me. I see a lot of community involvement in developing alternative UIs and other components of the stack (like tagging). There has been talk about having parts of ATProto standardized at the IETF, but they're waiting until the architecture is mature and proven (unlike AP). As a "losing" protocol, they gained 4MM new users just in the last month. 2x the MAU of the Fediverse.
Posts
-
I just sent the final proofs of the #ActivityPub book to the editors at O'Reilly. -
Have you ever wondered why #ActivityPub/AS2 has two media types?@naturzukunft @nik @evan By severe restrictions, I mean only allowing a list of URLs to external context documents and treating that as a list of extension identifiers (if I understood correctly). Ironically, some of most widely used AP extensions (Mastodon, for example) don't use this technique and embed their own context.
-
Have you ever wondered why #ActivityPub/AS2 has two media types?@naturzukunft @nik I have similar feelings, but I understand the points @evan makes (to some extent). Most Fediverse developers are not interested in learning Linked Data technologies. However, I think the JSON-LD / plain JSON ambiguity in AP causes more problems for those developers than it solves (if it solves any). I don't see any significant extensibility support for plain JSON consumers, although it's claimed to provide it if severe restrictions are placed on JSON-LD context usage.
-
@Identitywoman Thanks very much for your work on Fediforum.@Identitywoman Thanks very much for your work on Fediforum. In your presentation about the IETF and related topics, you showed a slide with three books related to groups and community development. I didn't type fast enough to record the names of all of them. Can you share the names (I think I have the first two, but they might be interesting to someone else too). Thanks!
-
Have you ever wondered why #ActivityPub/AS2 has two media types?One quote from the W3C discussion: "the first question is what the "metamodel" of AS really is. is it some improvement/variation of AS1's JSON foundation, or is it JSON-LD and thus RDF? my claim is that it cannot reasonably be both." Well said! /cc @nik
-
Have you ever wondered why #ActivityPub/AS2 has two media types?Have you ever wondered why #ActivityPub/AS2 has two media types? Here's a historical discussion about the tradeoffs between activity+json and ld+json. Does anybody know why they decided to use *both* media types?
https://www.w3.org/wiki/Socialwg/Media_type_for_AS2 -
I see discussions sometimes about developing recipe applications for #ActivityPub/AS2.I see discussions sometimes about developing recipe applications for #ActivityPub/AS2. In that spirit, I wrote a blog post describing how to use the schema.org Recipe type in an AS2 conformant manner. It's mostly a thought exercise about possibilities since most AP implementations won't render an AS2 conformant recipe correctly, if at all.
https://www.stevebate.net/extending-activitypub-a-recipe/ -
A week or two I mentioned that Activity Streams 2.0 (and #ActivityPub) do not require the AS2 context URL in a message when using an AS2 HTTP content type.A week or two I mentioned that Activity Streams 2.0 (and #ActivityPub) do not require the AS2 context URL in a message when using an AS2 HTTP content type. However, Mastodon *does* require it. Ironically, it doesn't appear to require its own JSON-LD toot extension context (or security context) to be in the incoming AP messages.
-
I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language. -
I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language. -
I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language. -
I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language. -
I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language. -
I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language.@evan @nik Using the OWL Ontology for validation is not ideal for multiple reasons. 1) It's not maintained, 2) it's not complete (only AS2, no AP), 3) it's not fully consistent with normative AS2, 4) it requires RDF, which requires JSON-LD processing of AP messages, 5) if you want message validation, you'll need write code to do something that already exists (SHACL, ShEx). I recommend JSON Schema for plain JSON applications.
-
I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language.@nik What's this well-defined RDFS vocabulary (vs the normative JSON-LD context)? Do you mean the non-normative (and non-maintained) AS2 OWL ontology? A JSON Schema definition could define constraints that can be used for plain JSON message validation (and developer documentation) for specific AP interoperability domains (microblogging, forums, online markets, etc.). And it would be useful for non-RDF (plain JSON) consumers given AP is primarily intended to be used in that context (per @evan ).
-
I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language.I think it’s not correct when #ActivityPub thought leaders consider JSON-LD a schema definition language. I don't think it's an effective alternative to JSON Schema (for JSON) or SHACL or ShEx (for RDF). JSON-LD can’t be used to describe structure and constraints of data, for example. It's primarily an RDF serialization and the only benefit I see for AP is preventing property name clashes when doing full JSON-LD processing. I hope this topic will be reconsidered someday in ActivityPub 2.0.
-
My favorite valid Activity Streams 2.0 JSON object: {}.My favorite valid Activity Streams 2.0 JSON object: {}.
(But only if sent with an AS2 MIME content type).
-
I'm still not clear about the discussion we had yesterday.@evan Right, the RDF differs because the Collection's JSON-LD serialization is different in the paged serialization. I'd prefer that the Collection representation wouldn't change for paging, but I know that's another aspect of AS2 that will not change. Linked Data Platform (LDP) Paging describes a different way that doesn't couple the Collection and page representations so tightly. IIRC, they use Link headers for page refs and transient objects (in AP terms) for pages. https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html
-
I'm still not clear about the discussion we had yesterday.@evan Yes, that’s essentially it. The AS2 Collection paging is a whole other discussion. The RDF triples are accurately representing what’s in the page-related JSON-LD, but the JSON-LD isn’t literally serializing one item in a Collection. It’s serializing a Collection referencing a CollectionPage (via `first`) that references one item (which is consistent with the RDF triples).
-
I'm still not clear about the discussion we had yesterday.@evan I'm not exactly clear about the analogy, but maybe someday we'll say that's how it worked in ActivityPub up until version 2.0!