 |
 |
On Wed, Jun 8, 2011 at 3:08 PM, Nate Vack <[log in to unmask]> wrote: > On Wed, Jun 8, 2011 at 1:45 PM, Brice Stacey <[log in to unmask]> wrote: > > You can't necessarily say "We 8:00-2:00" because your closing hour could > be after your opening hour on the next day and it would be ambiguous. E.g. > Opening at 2am and closing the next day at 4am. > > Hm, good point. > > > Ideally, if working with times with date granularity you should honor > that choice and say "We 8:00-24:00" and "Th 0:00-2:00". Then, when creating > human readable formats you always check tomorrow in the event today's > closing time is midnight. > > And there's nothing in the spec, as far as I can tell, that says you can't > do something like: > > <time itemprop="openingHours" datetime="Th 0:00-2:00">Thursday: Open until > 2:00 AM</time> > <time itemprop="openingHours" datetime="Th 8:00-20:00">Reopens from 8:00 AM > until 8:00 PM</time> > Good Relations explicitly allows (and requires) multiple openingHours entities in this situation. There are some important potential semantic differences between two contiguous time intervals, and a single temporally continuous time interval. If there are semantics attached to Closing, then even though there may be no point of time in between the Closing and the Opening, there has none-the-less been a ClosingEvent. This may affect statistics, fines, or even more significantly wages (when I worked at the Technion, the union contract had overtime rates kick in after 8hrs worked on a given workday. Since as a systems programmer I would often get stuck working past midnight, this would show as up as clocking out at 26:00 hrs....) Male, Female, or Mule<http://ontolog.cim3.net/forum/ontology-summit/2011-01/msg00060.html> ? Simon