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

Point and period of date-time #634

Open
csarven opened this issue Jul 4, 2015 · 6 comments
Open

Point and period of date-time #634

csarven opened this issue Jul 4, 2015 · 6 comments
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

Comments

@csarven
Copy link

csarven commented Jul 4, 2015

Request: A generic way to indicate point (e.g., instant) and period (e.g., intervals, reference, calendar) of date-time. AFAICT, these fall outside of the current use date-time start/end* or *published/modified etc. Point and period should be separate properties (in contrast to dcterms:date for example).

@csarven
Copy link
Author

csarven commented Jul 4, 2015

This addition will be particularly useful in order to declare temporal dimensions in statistical data. I suspect that there will need to be some usage in any case with https://github.com/w3c/csvw

@csarven
Copy link
Author

csarven commented Jul 4, 2015

What already exists:

  • http://reference.data.gov.uk/id/{gregorian-interval, gregorian-instant, year, month, day, hour, quarter}
  • http://reference.data.gov.uk/def/intervals
  • http://www.w3.org/2006/time
  • ...

@csarven
Copy link
Author

csarven commented Sep 23, 2015

An example of a point in time is when an event takes place on a given day without specifying the time. It is possible to infer this if both startDate and endDate have the same value, however, I think a single property e.g., schema:date would be simpler i.e., an equivalent to dcterms:date.

@mfhepp
Copy link
Contributor

mfhepp commented Oct 14, 2015

If you implement that, I recommend to use the same pattern as in value/minValue/maxValue and price/minPrice/maxPrice, i.e. to make

schema:date rdfs:subPropertyOf schema:startDate and schema:endDate.

By that, a one-day event will also have the proper startDate and endDate values.

Note that the respective axioms (from GoodRelations) are currently missing in schema.org because I forgot to submit the pull-request, but they will come asap.


martin hepp http://www.heppnetz.de
mhepp@computer.org @mfhepp

On 23 Sep 2015, at 14:35, Sarven Capadisli notifications@github.com wrote:

An example of a point in time is when an event takes place on a given day without specifying the time. It is possible to infer this if both startDate and endDate have the same value, however, I think a single property e.g., schema:date would be simpler e.g., an equivalent to dcterms:date.


Reply to this email directly or view it on GitHub.

@github-actions
Copy link

This issue is being tagged as Stale due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Aug 16, 2020
@VladimirAlexiev
Copy link

VladimirAlexiev commented Feb 26, 2021

@csarven @mfhepp

  1. I raised a similar issue in Proposal for representing Aggregate Statistical Data #2291: observationDate vs reference period
  2. https://schema.org/PropertyValue has value, minValue, maxValue. Doesn't this fulfill your need?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Projects
None yet
Development

No branches or pull requests

3 participants