Feature #587
STORY: Define the architecture and use cases of dates, timezones, and event portability
| Status: | New | Start date: | 04/18/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
We'll need to define an architecture and working model for how we want our dates stored, timezones handled, and start+stop times displayed to both anonymous users and logged in users who've set their personal timezone preference.
Also, we need to lay out the RDF plan for sharing this data between Drupal sites in different timezones.