- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Fri, 8 Aug 2014 01:36:33 +0100
- To: David Janes <davidjanes@davidjanes.com>
- Cc: Linked JSON <public-linked-json@w3.org>
Received on Friday, 8 August 2014 00:37:05 UTC
If you use properties which you define and only use on the same type of resource, you can in the vocabulary where the property is defined add rdfs:domain to the implied type of the subject (and rdfs:range to type the object) It would however require additional RDFS or OWL reasoning beyond the regular JSON-LD processing to get those typing triples. In RDF stores like Jena this is normally just a simple configuration option combined with loading the vocabulary. On 7 Aug 2014 20:34, "David Janes" <davidjanes@davidjanes.com> wrote: > Let's say I have some temperature / humidity data > > { > "temperature" : 22.1, > "humidity" : 44 > } > > I can mark this up semantically using JSON-LD as follows (note the JSON-LD > at the link is a little wonky right now in terms of naming): > { > "@type" : "https://iotdb.org/iotdb/models/firmata-dht11", > "@context" : "https://iotdb.org/iotdb/models/firmata-dht11", > "temperature" : 22.1, > "humidity" : 44 > } > > Great, this record now has a type and proper definitions for temperature > and humidity. > > But let's say I want to leave the record alone and use HTTP Links headers > to annotate, as per [1]. Obviously I get the @context. But how do I get the > @type associated with the record? > > [1] http://www.w3.org/TR/json-ld/#interpreting-json-as-json-ld > > Regards, > > D. > > >
Received on Friday, 8 August 2014 00:37:05 UTC