Re: Decoupling between Link and its mediatype, and inputData/outputData

Hi Maxime

Note that he Data Exchange WG is currently gathering Use Case and
Requirements for description and mechanisms of content negotiation by
'profile" and finer grained semantics of data descriptions (e.g. - but not
limited to - schemas).

So what is your Use Case for actually modelling this, vs the information
resource URLs being discovered at run-time via content-negotiation and
redirects?

do you have multiple schema objects or really one schema and a parallel
content-negotiation problem - i.e. get me the schema using JSON vs get me
the XSD?

And how do you handle, for example, the device providing lightweight
information and more detailed graphs - with for example a calibration
history?

In DXWG we are interested in how you might define an "interoperability
profile" of a RDFS schema that might constrain/require for example that
json and XML are available. You can express this with dct:hasFormat
possibly - using SHACL to require that these formats are in fact present in
a desciption?

I am following this looking at how the OGC might support publication of
interoperability profiles of its standards in a consistent way.

Rob Atkinson



On Fri, 22 Sep 2017 at 17:26 Maxime Lefrançois <maxime.lefrancois@emse.fr>
wrote:

> 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 do you suggest to manage this ?
>
> Best,
> Maxime Lefrançois
>