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

In dcat:PeriodOfTime, add new properties time:hasBeggining, time:hasEnd #84

Closed
NatasaSofou opened this issue Sep 12, 2019 · 6 comments
Closed

Comments

@NatasaSofou
Copy link
Contributor

NatasaSofou commented Sep 12, 2019

In dct:PeriodOfTime, add new properties:

  • time:hasBeginning: Beginning of a period or interval
  • time:hasEnd: End of a period or interval

The values of time:hasBeggining and time:hasEnd are time:Instant for whose position several options are available ( times that do not use the conventional Gregorian calendar, geological and archeological periods, and times given as numeric positions on a time-line.)

@NatasaSofou NatasaSofou added release:majorsemantic dcat 2 Issues related to new release of DCAT labels Sep 12, 2019
@akuckartz
Copy link

Typo: hasBeggining -> hasBeginning

@NatasaSofou
Copy link
Contributor Author

Proposed resolution: In class dct:PeriodOfTime, add optional properties time:hasBeginning, time:hasEnd

@init-dcat-ap-de
Copy link

Now the Typo "hasBegginnig" is in the diagram of the Spec V2.0.0. of 03/10/2019

image

@init-dcat-ap-de
Copy link

What happens if the data includes dcat:startDate AND time:hasBeginning and they are different?

Also: #83 (comment)

@bertvannuffelen
Copy link
Contributor

This would be unfortunately ;-).

I think here the Open Data Portals should play a role at the point they recieve the master record of the dataset description. Harvesting Open Data Portals can only flag it and provide feedback.
By chosing for recommending dcat:startDate over time:hasBeginning the vocabulary time will be less used in the practice, unless no alternative is possible.

@bertvannuffelen
Copy link
Contributor

typos resolved

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

No branches or pull requests

4 participants