One thing I've been wondering about just now is why in some examples I see "id" and "type" fields prefixed with @ in JSON-LD, whereas others don't do this?
@darius
ah, I see now (using `curl -H 'Accept: application/ld+json' https://www.w3.org/ns/activitystreams`) that the activitystreams default context aliases @id and @type, presumable for convenience when using the actual JSON in e.g. JS code.
Gregory's Server
@darius
ah, I see now (using `curl -H 'Accept: application/ld+json' https://www.w3.org/ns/activitystreams`) that the activitystreams default context aliases @id and @type, presumable for convenience when using the actual JSON in e.g. JS code.