W3C home > Mailing lists > Public > public-wot-wg@w3.org > September 2017

Decoupling between Link and its mediatype, and inputData/outputData

From: Maxime Lefrançois <maxime.lefrancois@emse.fr>
Date: Fri, 22 Sep 2017 13:11:59 +0000
Message-ID: <CALsPASV+9TM+9rRpakMb8cfQcjSoX_KJsePqzCO_CKTTpT909A@mail.gmail.com>
To: public-wot-wg@w3.org
Dear all,

The decoupling between Link and its mediatype, and inputData/outputData,
makes me having some trouble trying to model the following situation:

Suppose a device exposes the same information in xml or json, using
content-negotiation, at http://192.168.0.10/property
- the xml version has a canonical URL http://192.168.0.10/property.xml (see
also Content-Location)
- the json version has a canonical URL http://192.168.0.10/property.json

I'd like to model this situation with a single device, a single
td:Property, three td:Link, and only two td:DataSchema objects.

How would you suggest to manage this ?

Best,
Maxime Lefrançois
Received on Friday, 22 September 2017 13:12:35 UTC

This archive was generated by hypermail 2.3.1 : Friday, 22 September 2017 13:12:36 UTC