#social 2020-08-03

2020-08-03 UTC
jussi, sl007 and zucchini joined the channel
#
zucchini
when dereferencing a URI with "accept: application/ld+json", is the server expected to return the single node or can it also return properties about other nodes? For example if I dereference foobar.org/alice is the server expected to return only the alice node or can it also embed other nodes (for example the friends of alice)?
#
@dodyg
Another possible fun project to try on Orleans would be implementing ActivityPub server https://www.w3.org/TR/activitypub/
(twitter.com/_/status/1290181717202853898)
sl007 joined the channel
#
csarven
zucchini: Server may. AS2 or AP does not prohibit the inclusion of additional objects or even (re)using other vocabularies to refer to them.
#
zucchini
csarven: how do you parse it then if you have an arbitrary number of nodes, completely different vocabularies, and maybe also the object is not served "compacted" (compacted as defined by jsonld that is)?
#
csarven
The specs only define the primary object or collections and particular vocab with context. How clients discover/use anything beyond that is not specified as per AS2/AP. So, basically you're just looking into plain ol' Linked Data.
#
csarven
Clients that only understand AS2/AP obviously wouldn't do anything with additional information.
#
csarven
see note on JSON-LD
#
zucchini
csarven: thank you very much, the "Note: JSON-LD" answers my question
#
csarven
If you want include friends of Alice, you can use foaf:knows or schema:knows or whatever and just nest
#
csarven
or use vcard
#
sl007
For a practical example e.g. the https://openengiadina.net GeoPub demo (select a "Person" and click "load mored data") and code https://gitlab.com/openengiadina/geopub
#
nightpool[m]
zucchini: just to answer some of your questions more specifically, since there are some nuances here: AS2 documents must always be rooted at a single node, and compacted to at LEAST the normative context definition at https://www.w3.org/ns/activitystreams
#
nightpool[m]
https://www.w3.org/TR/activitystreams-core/#jsonld has some more restrictions on what is required, since it tries to ensure compatibility between JSON-LD and pure JSON processors (although it unfortunately can't do so in the presence of extensions)
#
zucchini
nightpool[m]: yes thank you I think I understand
#
csarven
re "pure JSON", beyond @graph, is there anything?
#
nightpool[m]
csarven: hmm?
#
nightpool[m]
not sure I understand your question
#
csarven
nightpool[m]: Beyond minor syntactical stuff, AFAIK there is not much to extending data, reusing vocabs..
#
csarven
Naturally, interop will depend on which set of specs the parties are acknowledging.
#
nightpool[m]
yeah, the syntactical stuff is the main thing I was advising against.
#
csarven
pretty low on my list of worries :)
sl007 and trwnh joined the channel