While developing an application that processes entities stored as PointOfInterest, we noticed that there is currently no standard field for storing the operating hours of a POI.
Our application focuses on displaying relevant information about each POI — and one particularly useful piece of information is its schedule (i.e., when it’s open to the public).
For example: https://explore.porto.pt/pois/5cd04b45f979e000018e5ac3
At the moment, we are using a custom field called Calendar to store this information, but we believe it would be more appropriate and interoperable to adopt a standard field such as openingHours — similar to what is already used in the Event data model.
Would it be possible to include an optional openingHours field in the PointOfInterest data model?
Thanks! :)
While developing an application that processes entities stored as PointOfInterest, we noticed that there is currently no standard field for storing the operating hours of a POI.
Our application focuses on displaying relevant information about each POI — and one particularly useful piece of information is its schedule (i.e., when it’s open to the public).
For example: https://explore.porto.pt/pois/5cd04b45f979e000018e5ac3
At the moment, we are using a custom field called Calendar to store this information, but we believe it would be more appropriate and interoperable to adopt a standard field such as openingHours — similar to what is already used in the Event data model.
Would it be possible to include an optional openingHours field in the PointOfInterest data model?
Thanks! :)