Hi Erik,
On 04/07/2015 10:06 PM, Erik Wilde wrote:
[...]
> Atom is doing things differently because XML provides a better way of
> separating vocabularies with namespaces. that's an important benefit
> that neither JSON nor JSON-LD have. that also makes it easier to
> separate possible future spec changes from openness/extensions. again
> that's something that we don't get out of the box.
Could you please explain how do you see JSON-LD not having capacity to
separate vocabularies with namespaces?
In my online profile ATM I use vocabularies from 8 different namespaces
and will add more in next updates, including "as":
"http://www.w3.org/ns/activitystreams#"
$ curl https://wwelves.org/perpetual-tripper/ -H "Accept:
application/ld+json"
{
"@context": {
"@vocab": "http://schema.org/",
"cco": "http://purl.org/ontology/cco/core#",
"foaf": "http://xmlns.com/foaf/0.1/",
"doap": "http://usefulinc.com/ns/doap#",
"opo": "http://online-presence.net/opo/ns#",
"sec": "https://w3id.org/security#",
"ldp": "http://www.w3.org/ns/ldp#",
"hydra": "http://www.w3.org/ns/hydra/core#",
"id": "@id",
"type": "@type",
"attendeeIn": { "@reverse": "attendee" },
"authorOf": { "@reverse": "author" },
"currentLocation": "opo:currentLocation"
},
...
}