W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > February 2019

Re: [dxwg] Summary statistics [RSS] (#84)

From: Andrea Perego via GitHub <sysbot+gh@w3.org>
Date: Mon, 18 Feb 2019 23:53:16 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-464925023-1550533995-sysbot+gh@w3.org>
@smrgeoinfo wrote:

> One issue with dqv is that in some engineering situations, resolution and precision are different.

Yes, the wording of the relevant section in DQV does not make this distinction, but the formal definition of the resolution in the examples does not bind the notion of resolution with the one of precision.

> Is there a problem with using schema:Distance as the value for SpatialResolutionAsDistance, and schema:Duration for TemporalResolutionAsDuration?

Maybe `schema:Duration` can work, as it is using a standard syntax encoding, but `schema:Distance` uses a literal where value and a code for unit of measurement are separated by a space. Besides the problem of ensuring that codes for units of measurement are used consistently, this value is not machine-actionable. E.g., I won't be able to make a query to get the datasets using a spatial resolution with a distance less than 100 m.

Besides this, IMO, re-using Schema.org properties may lead to the issues mentioned in https://github.com/w3c/dxwg/issues/85#issuecomment-457961545 (in that case in relation to `schema:startDate` and `schema:endDate`).

-- 
GitHub Notification of comment by andrea-perego
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/84#issuecomment-464925023 using your GitHub account
Received on Monday, 18 February 2019 23:53:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:13 UTC