- From: Soumya Kanti Datta <Soumya-Kanti.Datta@eurecom.fr>
- Date: Fri, 22 Apr 2016 14:54:49 +0530
- To: Michael Koster <michael.koster@smartthings.com>, "Charpenay, Victor" <victor.charpenay@siemens.com>
- Cc: Public Web of Things IG <public-wot-ig@w3.org>
- Message-ID: <5719EDE1.9010805@eurecom.fr>
Hi Michael, Thanks for the clarification, it answers my question. Soumya Research Engineer, EURECOM, France | +33658194342 | @skdatta2010 | https://sites.google.com/site/skdunfolded | Skype id: soumyakantidatta On 22-04-2016 03:22, Michael Koster wrote: > Resource Directory stores links to resources (could be objects), using > RFC 6690 CoRE Link Format. > > Resource Directory could be used to store Thing Descriptions, as long > as they are serialized to a format compatible with RFC 6690 or one of > it's alternate serializations, for example link-format+json or > link-format+cbor. > > https://tools.ietf.org/html/draft-ietf-core-links-json-04 > > For example, I've attached an example serialization of the TD example > 11 from the Current Practices document sec. 3.2.3.2, which could be > made compatible with CoRE link-format+json processors. > > This currently has 2 issues; first the "@" character isn't allowed in > link header encoding (but could be processed as JSON just fine). Also, > having a map as a link extension value is not representable in link > header encoding, so may need to be string encoded if not represented > in JSON or CBOR. > > Also, "rd-lookup" is an optional function in CoRE RD. An extension > could be a "rd-sparql" service that maps SPARQL queries to uri-query > parameters. > > Best regards, > > Michael > > > > > >> On Apr 21, 2016, at 7:14 AM, Charpenay, Victor >> <victor.charpenay@siemens.com <mailto:victor.charpenay@siemens.com>> >> wrote: >> >> Hi Soumya, >> >> could you give us a link to those guidelines? From what I found, they >> consist in using a CoRE Resource Directory to store objects but it >> seems rather straightforward since LwM2M and IPSO objects are RESTful >> by design. Maybe there is more? >> >> Anyway, isn't the Thingweb Repository an implementation of what you >> are looking for? By the way, the idea of a Thing Repository had been >> questioned (shortly before Nice), since it seems very similar in >> spirit to a Resource Directory. Yet, it provides a SPARQL interface, >> which covers and extends by far the query mechanism of a Resource >> Directory. >> >> Regards, >> Victor >> >> -----Original Message----- >> From: Soumya Kanti Datta [mailto:Soumya-Kanti.Datta@eurecom.fr] >> Sent: Donnerstag, 21. April 2016 11:42 >> To: public-wot-ig@w3.org <mailto:public-wot-ig@w3.org> >> Subject: thing description question >> >> Hi, >> >> With the semantic based TD, how can we use it for automatic >> management of things? If you see IPSO alliance or OMA LwM2M - they >> provide guidelines on how to use CoRE Link Format for TD and utilize >> that for management. >> >> Did someone from TF-TD alrady investigate into this. >> >> Thanks, >> Soumya >> >> -- >> Research Engineer, EURECOM, France | +33658194342 | @skdatta2010 | >> https://sites.google.com/site/skdunfolded | Skype id: soumyakantidatta >> >> >
Received on Friday, 22 April 2016 09:24:34 UTC