schemaorg
schemaorg copied to clipboard
openingHours should have a time zone qualifier
I've written some markup for some LocalBusinesses before, so I've never had to deal with this. However, I have a business that deals with customers all over the world.
Since the documentation makes no mention of time zones, GMT offsets, or the like:
- Should the openingHours attribute be assumed to be in the time zone of the business's defined address or geo-location?
- For edge cases like this -- or, let's say, small local business that are near the border of a time zone -- would it be worthwhile to include a time zone qualifier for this attribute?
I've a client with an interesting scenario. They have local service area businesses across multiple timezones with a central call centre to order those services. This means the opening hours can be related to a timezone different to the location of the business. Being able to supply a timezone would make things easier.
Same for their main Organization that can be contacted from people in multiple timezones.
I am not sure whether I understand the issue, but there has been support for time-zones ever since the original GoodRelations version of the elements, see
http://www.heppnetz.de/ontologies/goodrelations/v1#opens
So you are basically free to indicate any offset from UTC.
If no time-zone suffix is included, the time is given in the local time valid at the gr:Location.
For a time in GMT/UTC, simply add a "Z" following the time:
09:30:10Z.
Alternatively, you can specify an offset from the UTC time by adding a positive or negative time following the time:
09:30:10-09:00
or
09:30:10+09:00.
Best wishes Martin
martin hepp www: http://www.heppnetz.de/
Am 09.01.2022 um 23:57 schrieb Tony McCreath @.***>:
I've a client with an interesting scenario. They have local service area businesses across multiple timezones with a central call centre to order those services. This means the opening hours can be related to a timezone different to the location of the business. Being able to supply a timezone would make things easier.
Same for their main Organization that can be contacted from people in multiple timezones.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.
That's good to know. It's still a bit tricky for places that have daylight savings as the UTC offset changes depending on the time of year. Here in Adelaide Australia it's either +10:30 or +9:30
I am not sure whether I understand the issue, but there has been support for time-zones ever since the original GoodRelations version of the elements, see http://www.heppnetz.de/ontologies/goodrelations/v1#opens So you are basically free to indicate any offset from UTC. If no time-zone suffix is included, the time is given in the local time valid at the gr:Location.
Oh, all right then. There's no mention of time zones, either explicit or implied, in the Schema.org documentation for the openingHours property or schemas such as LocalBusiness. Perhaps a simple text update is all that's needed.
With daylight saving, it is advisable to use explicit offsets from UTC and either update the data or use validFrom/validThrough with two OpeningHoursSpecification entities, one for each period of time (with/without DST).
martin hepp www: http://www.heppnetz.de/
Am 10.01.2022 um 02:35 schrieb Tony McCreath @.***>:
That's good to know. It's still a bit tricky for places that have daylight savings as the UTC offset changes depending on the time of year. Here in Adelaide Australia it's either +10:30 or +9:30
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
Afaik, time-zone support exists only when you use the more advanced pattern with
https://schema.org/openingHoursSpecification
martin hepp www: http://www.heppnetz.de/
Am 10.01.2022 um 02:38 schrieb Colin Cogle @.***>:
I am not sure whether I understand the issue, but there has been support for time-zones ever since the original GoodRelations version of the elements, see http://www.heppnetz.de/ontologies/goodrelations/v1#opens So you are basically free to indicate any offset from UTC. If no time-zone suffix is included, the time is given in the local time valid at the gr:Location.
Oh, all right then. There's no mention of time zones, either explicit or implied, in the Schema.org documentation for the openingHours property or schemas such as LocalBusiness. Perhaps a simple text update is all that's needed.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
Now to work out how to specify "The first Sunday in October" 🤯
This issue is being nudged due to inactivity.