So my rule was ‘tomorrow’ begins at 6am or sunrise.

‘Course that was in college, so to be fair, I think 5am or sunrise works, even though it lacks a certain ring to it.

05:00-11:30 Morning
11:30-01:30 Lunch
01:30-05:30 Afternoon
05:30-09:00 Evening
09:00-01:30 Night
01:30-05:00 Wee Hours

The thinking behind Lunch is that in the events domain, it’s an important peg on which to hang things.

A curator will, of course, be able to define Gweep Standard Time. The mechanism to do so will be only mildly gweepy, involving some Delicious tags.

Note, though, that you wouldn’t want to impose GST on a whole geographic community, which would include many non-gweeps.

That implies either or both of:

1. Users can request a GST overlay on a geographic aggregation.

2. The aggregation is topical, like http://calagator.org/, in which case GST might be an appropriate community norm.

It’s all doable. But I’m not sure any of this advances the real goal of this project, which is to encourage non-gweeps to understand and apply the principles of:

- syndication
- tagging
- structured data
- pub/sub
- aggregation

From that point of view, the choices that Stamen made with the Oakland time vocabulary are instructive. In my interview with Eric Rodenbeck, he pointed out that the day/night/swingshift terminology was chosen because that’s how the police themselves think about the domain.

The purpose of the site is to help citizens and police share a common understanding of how crimes are defined in the neighborhood.

I would likewise want to help event promoters and event goers share a common understanding of how public events are defined in a community.

06-10 Morning
10-14 Midday
14-18 Afternoon
18-22 Evening
22-02 Gweepning
02-06 Oh-my-god-what-are-we-doing-up-this-late-ning

http://everything2.com/title/gweep%2520standard%2520time

Since you appear to be breaking time into “normal” periods, I’d suggest “night” should be 9 PM to 1 AM, and 1 AM to 5 AM be “late night” or “early morning.”