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
Comments
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 |
What already exists:
|
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 |
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
|
This issue is being tagged as Stale due to inactivity. |
|
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).The text was updated successfully, but these errors were encountered: