Figure Cal.10 - Entry Characteristics

This section explains the remaining entities that relate directly to CalendarEntry.<br/>CalendarEntries can be categorized to allow for easier sorting and filtering.<br/>We can also attach files to CalendarEntries, which could be items like a document sent out with a meeting request. The attachments may either be in-line or via a URI reference.<br/>To allow for working across different time zones, we need to tag each Calendar Entry TemporalExpression with a time zone. An implementation may decide to make timezone issues invisible to the user by converting all entries on receipt, to the Calendar TimeZone.<br/>Similarly, CalendarEntityTemporalExpressions may be translated from the calendricalSystem that they were created with to the Calendar default.<br/>The CalendarEntry TemporalExpression could be a simple TimePoint or TimePeriod for a non-repeating Entry.<br/>For a repeating Entry, we will need some sort of rule to enable us to specify how long it should repeat for (interval) and how often (frequency).<br/>e.g. we may decide to go to the gym every Wednesday in Summer 2003/4.<br/>So, an entry could be created on 24 Dec 2003 at 5:00pm – 6:30pm. It could be set to repeat weekly, stopping on 17 Mar 2004. As noted before, depending on the complexity required, the RecurrenceRules entity could be implemented using rules or policy engines or simple templates.<br/>