Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DCAT - temporal resolution #776

Merged
merged 6 commits into from
Feb 28, 2019
Merged

DCAT - temporal resolution #776

merged 6 commits into from
Feb 28, 2019

Conversation

dr-shorthair
Copy link
Contributor

Add dcat:temporalResolution as discussed in #84

@agbeltran
Copy link
Member

@agbeltran
Copy link
Member

I think it would be helpful to expand the description below the example to explain what we are representing with dct:temporal and dcat:temporalResolution.

In the section describing the property, there is a type dct:temporalResolution instead of dcat:temporalResolution.

@agbeltran
Copy link
Member

Following the discussion in #84, should we also add a comment referring to DQV for more complex cases?

@davebrowning davebrowning merged commit bd2c504 into gh-pages Feb 28, 2019
@davebrowning davebrowning deleted the dcat-issue84-tres-simon branch February 28, 2019 09:40
@davebrowning
Copy link
Contributor

As per meeting minutes https://www.w3.org/2019/02/27-dxwgdcat-minutes#x12

@init-dcat-ap-de
Copy link

The definition is
"Minimum time period resolvable in the dataset."
The usage note is
"If the dataset is a time-series this should correspond to the spacing of items in the series. For other kinds of dataset, this property will usually indicate the smallest time difference between items in the dataset."

So the definition changes according to the use case. How do I describe the frequency of the time-series and the resolution of the dataset?
How do I know whether "temporal resolution" is the frequency of a time-series or the resolution?

@makxdekkers
Copy link
Contributor

Good point. The mention of a time-series is a bit iffy, as we have already said we need to treat that issue more fundamentally in future work.
Could we just simplify the usage note to:
"This property will usually indicate the smallest time difference between items in the dataset."
I think this simplified statement could also be seen as including 'spacing of items'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants