- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Thu, 13 Nov 2014 00:04:07 +0100
- To: Owen Shepherd <owen.shepherd@e43.eu>, Christopher Allan Webber <cwebber@dustycloud.org>
- CC: Markus Lanthaler <markus.lanthaler@gmx.net>, public-socialweb@w3.org
On 11/12/2014 11:50 PM, Owen Shepherd wrote: > Whether we define our own types as aliases of others - e.g. "as:Person > owl:sameType vcard:Individual" - or just refer to others is kind of > immaterial, though I'm in favor of the aliasing because that > implementers don't have to think "People come from VCard, Events come > from iCalendar, businesses come from Org..." I see limitations with depending to much on inference, for example unhosted[1] apps which run fully in a browser as for today don't have any reasoners available (javascrip) :( I plan to experiment with including asserted triples in data I publish even if a reasoner could infer them. This could help less sophisticated clients. Following your example, I could do: "@type": ["Person", "vcard:Individual"] or as I already use in my web profile [2] "@type": ["Person", "foaf:Person"] which in my case maps Person to http://schema.org/Person (via "@vocab": "http://schema.org" in the context, but could map to as:Person or whatever. Here again I most likely will struggle more with predicates, since you can't do in JSON-LD "actor schema:agent": "https://wwelves.org/perpetual-tripper" AFAIK only RDFa has elegant way to easily use multiple predicates with same object and subject pair as above [1] http://unhosted.org [2] curl -H "Accept: application/ld+json" https://wwelves.org/perpetual-tripper/
Received on Wednesday, 12 November 2014 23:06:19 UTC