I find it rather disappointing (in ActivityStreams in general), by the way: on the first sight it's a part of the Semantic Web, but the approaches seem to differ from common ones, and the specification itself mentions that there's merely compatibility with one of the serialization formats (JSON-LD).
> but transport and actor resolution are not well specified
There's this for ActivityPub though: "Publicly facing content SHOULD use HTTPS URIs", and bits such as "The outbox accepts HTTP POST requests, with behaviour described in Client to Server Interactions", "clients MUST discover the URL of the actor's outbox from their profile and then MUST make an HTTP POST request". Authentication is not specified, but apparently de facto it will be some hacks on top of HTTP, too.
Putting those two together, it seems to mostly aim the popular nowadays combination of HTTP and JSON (just RDF/semweb-friendly).
I find it rather disappointing (in ActivityStreams in general), by the way: on the first sight it's a part of the Semantic Web, but the approaches seem to differ from common ones, and the specification itself mentions that there's merely compatibility with one of the serialization formats (JSON-LD).
> but transport and actor resolution are not well specified
There's this for ActivityPub though: "Publicly facing content SHOULD use HTTPS URIs", and bits such as "The outbox accepts HTTP POST requests, with behaviour described in Client to Server Interactions", "clients MUST discover the URL of the actor's outbox from their profile and then MUST make an HTTP POST request". Authentication is not specified, but apparently de facto it will be some hacks on top of HTTP, too.
Putting those two together, it seems to mostly aim the popular nowadays combination of HTTP and JSON (just RDF/semweb-friendly).
reply