001: package org.columba.calendar.model.api;
002:
003: /**
004: * All iCalendar features Columba is able to handle.
005: * <p>
006: * These are the actually used xml-tags, which are mapped to the corresponding
007: * iCalendar properties.
008: *
009: * @author fdietz
010: */
011: public interface ICALENDAR {
012:
013: public final static String ICALENDAR = "icalendar";
014:
015: /**
016: * Description: A "VEVENT" calendar component is a grouping of component
017: * properties, and possibly including "VALARM" calendar components, that
018: * represents a scheduled amount of time on a calendar. For example, it can
019: * be an activity; such as a one-hour long, department meeting from 8:00 AM
020: * to 9:00 AM, tomorrow. Generally, an event will take up time on an
021: * individual calendar. Hence, the event will appear as an opaque interval
022: * in a search for busy time. Alternately, the event can have its Time
023: * Transparency set to "TRANSPARENT" in order to prevent blocking of the
024: * event in searches for busy time.
025: * <p>
026: * The "VEVENT" is also the calendar component used to specify an
027: * anniversary or daily reminder within a calendar. These events have a DATE
028: * value type for the "DTSTART" property instead of the default data type of
029: * DATE-TIME. If such a "VEVENT" has a "DTEND" property, it MUST be
030: * specified as a DATE value also. The anniversary type of "VEVENT" can span
031: * more than one date (i.e, "DTEND" property value is set to a calendar date
032: * after the "DTSTART" property value).
033: */
034: public final static String VCALENDAR = "vcalendar";
035:
036: /**
037: * Property Name: PRODID
038: *
039: * Purpose: This property specifies the identifier for the product that
040: * created the iCalendar object.
041: *
042: * Value Type: TEXT
043: *
044: * Property Parameters: Non-standard property parameters can be specified on
045: * this property.
046: *
047: * Conformance: The property MUST be specified once in an iCalendar object.
048: *
049: * Description: The vendor of the implementation SHOULD assure that this is
050: * a globally unique identifier; using some technique such as an FPI value,
051: * as defined in [ISO9070].
052: *
053: * This property SHOULD not be used to alter the interpretation of an
054: * iCalendar object beyond the semantics specified in this memo. For
055: * example, it is not to be used to further the understanding of non-
056: * standard properties.
057: */
058: public final static String VCALENDAR_VERSION = "version";
059:
060: /**
061: * Property Name: VERSION
062: *
063: * Purpose: This property specifies the identifier corresponding to the
064: * highest version number or the minimum and maximum range of the iCalendar
065: * specification that is required in order to interpret the iCalendar
066: * object.
067: *
068: * Value Type: TEXT
069: *
070: * Property Parameters: Non-standard property parameters can be specified on
071: * this property.
072: *
073: * Conformance: This property MUST be specified by an iCalendar object, but
074: * MUST only be specified once.
075: */
076: public final static String VCALENDAR_PRODID = "prodid";
077:
078: /**
079: * Property Name: METHOD
080: *
081: * Purpose: This property defines the iCalendar object method associated
082: * with the calendar object.
083: *
084: * Value Type: TEXT
085: *
086: * Property Parameters: Non-standard property parameters can be specified on
087: * this property.
088: *
089: * Conformance: The property can be specified in an iCalendar object.
090: *
091: * Description: When used in a MIME message entity, the value of this
092: * property MUST be the same as the Content-Type "method" parameter value.
093: * This property can only appear once within the iCalendar object. If either
094: * the "METHOD" property or the Content-Type "method" parameter is
095: * specified, then the other MUST also be specified.
096: *
097: * No methods are defined by this specification. This is the subject of
098: * other specifications, such as the iCalendar Transport-independent
099: *
100: * Interoperability Protocol (iTIP) defined by [ITIP].
101: *
102: * If this property is not present in the iCalendar object, then a
103: * scheduling transaction MUST NOT be assumed. In such cases, the iCalendar
104: * object is merely being used to transport a snapshot of some calendar
105: * information; without the intention of conveying a scheduling semantic.
106: */
107: public final static String VCALENDAR_METHOD = "method";
108:
109: public final static String VEVENT = "vevent";
110:
111: /**
112: * Description: A "VTODO" calendar component is a grouping of component
113: * properties and possibly "VALARM" calendar components that represent an
114: * action-item or assignment. For example, it can be used to represent an
115: * item of work assigned to an individual; such as "turn in travel expense
116: * today".
117: * <p>
118: * The "VTODO" calendar component cannot be nested within another calendar
119: * component. However, "VTODO" calendar components can be related to each
120: * other or to a "VTODO" or to a "VJOURNAL" calendar component with the
121: * "RELATED-TO" property.
122: */
123: public final static String VTODO = "vtodo";
124:
125: /**
126: * Property Name: UID
127: *
128: * Purpose: This property defines the persistent, globally unique identifier
129: * for the calendar component.
130: *
131: * Value Type: TEXT
132: *
133: * Property Parameters: Non-standard property parameters can be specified on
134: * this property.
135: *
136: * Conformance: The property MUST be specified in the "VEVENT", "VTODO",
137: * "VJOURNAL" or "VFREEBUSY" calendar components.
138: *
139: * Description: The UID itself MUST be a globally unique identifier. The
140: * generator of the identifier MUST guarantee that the identifier is unique.
141: * There are several algorithms that can be used to accomplish this. The
142: * identifier is RECOMMENDED to be the identical syntax to the [RFC822]
143: * addr-spec. A good method to assure uniqueness is to put the domain name
144: * or a domain literal IP address of the host on which the identifier was
145: * created on the right hand side of the "@", and on the left hand side, put
146: * a combination of the current calendar date and time of day (i.e.,
147: * formatted in as a DATE-TIME value) along with some other currently unique
148: * (perhaps sequential) identifier available on the system (for example, a
149: * process id number). Using a date/time value on the left hand side and a
150: * domain name or domain literal on the right hand side makes it possible to
151: * guarantee uniqueness since no two hosts should be using the same domain
152: * name or IP address at the same time. Though other algorithms will work,
153: * it is RECOMMENDED that the right hand side contain some domain identifier
154: * (either of the host itself or otherwise) such that the generator of the
155: * message identifier can guarantee the uniqueness of the left hand side
156: * within the scope of that domain.
157: *
158: * This is the method for correlating scheduling messages with the
159: * referenced "VEVENT", "VTODO", or "VJOURNAL" calendar component.
160: *
161: * The full range of calendar components specified by a recurrence set is
162: * referenced by referring to just the "UID" property value corresponding to
163: * the calendar component. The "RECURRENCE-ID" property allows the reference
164: * to an individual instance within the recurrence set.
165: *
166: * This property is an important method for group scheduling applications to
167: * match requests with later replies, modifications or deletion requests.
168: * Calendaring and scheduling applications MUST generate this property in
169: * "VEVENT", "VTODO" and "VJOURNAL" calendar components to assure
170: * interoperability with other group scheduling applications. This
171: * identifier is created by the calendar system that generates an iCalendar
172: * object.
173: *
174: * Implementations MUST be able to receive and persist values of at least
175: * 255 characters for this property.
176: */
177: public final static String UID = "uid";
178:
179: /**
180: * Property Name: DTSTAMP
181: *
182: * Purpose: The property indicates the date/time that the instance of the
183: * iCalendar object was created.
184: *
185: * Value Type: DATE-TIME
186: *
187: * Property Parameters: Non-standard property parameters can be specified on
188: * this property.
189: *
190: * Conformance: This property MUST be included in the "VEVENT", "VTODO",
191: * "VJOURNAL" or "VFREEBUSY" calendar components.
192: *
193: * Description: The value MUST be specified in the UTC time format.
194: *
195: * This property is also useful to protocols such as [IMIP] that have
196: * inherent latency issues with the delivery of content. This property will
197: * assist in the proper sequencing of messages containing iCalendar objects.
198: *
199: * This property is different than the "CREATED" and "LAST-MODIFIED"
200: * properties. These two properties are used to specify when the particular
201: * calendar data in the calendar store was created and last modified. This
202: * is different than when the iCalendar object representation of the
203: * calendar service information was created or last modified.
204: */
205: public final static String DTSTAMP = "dtstamp";
206:
207: /**
208: * Property Name: DTSTART
209: *
210: * Purpose: This property specifies when the calendar component begins.
211: *
212: * Value Type: The default value type is DATE-TIME. The time value MUST be
213: * one of the forms defined for the DATE-TIME value type. The value type can
214: * be set to a DATE value type.
215: *
216: * Property Parameters: Non-standard, value data type, time zone identifier
217: * property parameters can be specified on this property.
218: *
219: * Conformance: This property can be specified in the "VEVENT", "VTODO",
220: * "VFREEBUSY", or "VTIMEZONE" calendar components.
221: *
222: * Description: Within the "VEVENT" calendar component, this property
223: * defines the start date and time for the event. The property is REQUIRED
224: * in "VEVENT" calendar components. Events can have a start date/time but no
225: * end date/time. In that case, the event does not take up any time.
226: *
227: * Within the "VFREEBUSY" calendar component, this property defines the
228: * start date and time for the free or busy time information. The time MUST
229: * be specified in UTC time.
230: *
231: * Within the "VTIMEZONE" calendar component, this property defines the
232: * effective start date and time for a time zone specification. This
233: * property is REQUIRED within each STANDARD and DAYLIGHT part included in
234: * "VTIMEZONE" calendar components and MUST be specified as a local
235: * DATE-TIME without the "TZID" property parameter.
236: */
237: public final static String DTSTART = "dtstart";
238:
239: /**
240: * Property Name: DTEND
241: *
242: * Purpose: This property specifies the date and time that a calendar
243: * component ends.
244: *
245: * Value Type: The default value type is DATE-TIME. The value type can be
246: * set to a DATE value type.
247: *
248: * Property Parameters: Non-standard, value data type, time zone identifier
249: * property parameters can be specified on this property.
250: *
251: * Conformance: This property can be specified in "VEVENT" or "VFREEBUSY"
252: * calendar components.
253: *
254: * Description: Within the "VEVENT" calendar component, this property
255: * defines the date and time by which the event ends. The value MUST be
256: * later in time than the value of the "DTSTART" property.
257: *
258: * Within the "VFREEBUSY" calendar component, this property defines the end
259: * date and time for the free or busy time information. The time MUST be
260: * specified in the UTC time format. The value MUST be later in time than
261: * the value of the "DTSTART" property.
262: */
263: public final static String DTEND = "dtend";
264:
265: /**
266: * Property Name: SUMMARY
267: *
268: * Purpose: This property defines a short summary or subject for the
269: * calendar component.
270: *
271: * Value Type: TEXT
272: *
273: * Property Parameters: Non-standard, alternate text representation and
274: * language property parameters can be specified on this property.
275: *
276: * Conformance: The property can be specified in "VEVENT", "VTODO",
277: * "VJOURNAL" or "VALARM" calendar components.
278: *
279: * Description: This property is used in the "VEVENT", "VTODO" and
280: * "VJOURNAL" calendar components to capture a short, one line summary about
281: * the activity or journal entry.
282: *
283: * This property is used in the "VALARM" calendar component to capture the
284: * subject of an EMAIL category of alarm.
285: */
286: public final static String SUMMARY = "summary";
287:
288: /**
289: * Property Name: DESCRIPTION
290: *
291: * Purpose: This property provides a more complete description of the
292: * calendar component, than that provided by the "SUMMARY" property.
293: *
294: * Value Type: TEXT
295: *
296: * Property Parameters: Non-standard, alternate text representation and
297: * language property parameters can be specified on this property.
298: *
299: * Conformance: The property can be specified in the "VEVENT", "VTODO",
300: * "VJOURNAL" or "VALARM" calendar components. The property can be specified
301: * multiple times only within a "VJOURNAL" calendar component.
302: *
303: * Description: This property is used in the "VEVENT" and "VTODO" to capture
304: * lengthy textual decriptions associated with the activity.
305: *
306: * This property is used in the "VJOURNAL" calendar component to capture one
307: * more textual journal entries.
308: *
309: * This property is used in the "VALARM" calendar component to capture the
310: * display text for a DISPLAY category of alarm, to capture the body text
311: * for an EMAIL category of alarm and to capture the argument string for a
312: * PROCEDURE category of alarm.
313: */
314: public final static String DESCRIPTION = "description";
315:
316: /**
317: * Property Name: CLASS
318: *
319: * Purpose: This property defines the access classification for a calendar
320: * component.
321: *
322: * Value Type: TEXT
323: *
324: * Property Parameters: Non-standard property parameters can be specified on
325: * this property.
326: *
327: * Conformance: The property can be specified once in a "VEVENT", "VTODO" or
328: * "VJOURNAL" calendar components.
329: *
330: * Description: An access classification is only one component of the
331: * general security system within a calendar application. It provides a
332: * method of capturing the scope of the access the calendar owner intends
333: * for information within an individual calendar entry. The access
334: * classification of an individual iCalendar component is useful when
335: * measured along with the other security components of a calendar system
336: * (e.g., calendar user authentication, authorization, access rights, access
337: * role, etc.). Hence, the semantics of the individual access
338: * classifications cannot be completely defined by this memo alone.
339: * Additionally, due to the "blind" nature of most exchange processes using
340: * this memo, these access classifications cannot serve as an enforcement
341: * statement for a system receiving an iCalendar object. Rather, they
342: * provide a method for capturing the intention of the calendar owner for
343: * the access to the calendar component.
344: */
345: public final static String CLASS = "class";
346:
347: /**
348: * Property Name: TRANSP
349: *
350: * Purpose: This property defines whether an event is transparent or not to
351: * busy time searches.
352: *
353: * Value Type: TEXT
354: *
355: * Property Parameters: Non-standard property parameters can be specified on
356: * this property.
357: *
358: * Conformance: This property can be specified once in a "VEVENT" calendar
359: * component.
360: *
361: * Description: Time Transparency is the characteristic of an event that
362: * determines whether it appears to consume time on a calendar. Events that
363: * consume actual time for the individual or resource associated with the
364: * calendar SHOULD be recorded as OPAQUE, allowing them to be detected by
365: * free-busy time searches. Other events, which do not take up the
366: * individual's (or resource's) time SHOULD be recorded as TRANSPARENT,
367: * making them invisible to free-busy time searches.
368: */
369: public final static String TRANSP = "transp";
370:
371: /**
372: * Property Name: CATEGORIES
373: *
374: * Purpose: This property defines the categories for a calendar component.
375: *
376: * Value Type: TEXT
377: *
378: * Property Parameters: Non-standard and language property parameters can be
379: * specified on this property.
380: *
381: * Conformance: The property can be specified within "VEVENT", "VTODO" or
382: * "VJOURNAL" calendar components.
383: *
384: * Description: This property is used to specify categories or subtypes of
385: * the calendar component. The categories are useful in searching for a
386: * calendar component of a particular type and category. Within the
387: * "VEVENT", "VTODO" or "VJOURNAL" calendar components, more than one
388: * category can be specified as a list of categories separated by the COMMA
389: * character (US-ASCII decimal 44).
390: */
391: public final static String CATEGORIES = "categories";
392: public final static String ITEM = "item";
393: /**
394: * Property Name: RRULE
395: *
396: * Purpose: This property defines a rule or repeating pattern for recurring
397: * events, to-dos, or time zone definitions.
398: *
399: * Value Type: RECUR
400: *
401: * Property Parameters: Non-standard property parameters can be specified on
402: * this property.
403: *
404: * Conformance: This property can be specified one or more times in
405: * recurring "VEVENT", "VTODO" and "VJOURNAL" calendar components. It can
406: * also be specified once in each STANDARD or DAYLIGHT sub-component of the
407: * "VTIMEZONE" calendar component.
408: *
409: * Description: The recurrence rule, if specified, is used in computing the
410: * recurrence set. The recurrence set is the complete set of recurrence
411: * instances for a calendar component. The recurrence set is generated by
412: * considering the initial "DTSTART" property along with the "RRULE",
413: * "RDATE", "EXDATE" and "EXRULE" properties contained within the iCalendar
414: * object. The "DTSTART" property defines the first instance in the
415: * recurrence set. Multiple instances of the "RRULE" and "EXRULE" properties
416: * can also be specified to define more sophisticated recurrence sets. The
417: * final recurrence set is generated by gathering all of the start
418: * date/times generated by any of the specified "RRULE" and "RDATE"
419: * properties, and excluding any start date/times which fall within the
420: * union of start date/times generated by any specified "EXRULE" and
421: * "EXDATE" properties. This implies that start date/times within exclusion
422: * related properties (i.e., "EXDATE" and "EXRULE") take precedence over
423: * those specified by inclusion properties (i.e., "RDATE" and "RRULE").
424: * Where duplicate instances are generated by the "RRULE" and "RDATE"
425: * properties, only one recurrence is considered. Duplicate instances are
426: * ignored.
427: *
428: * The "DTSTART" and "DTEND" property pair or "DTSTART" and "DURATION"
429: * property pair, specified within the iCalendar object defines the first
430: * instance of the recurrence. When used with a recurrence rule, the
431: * "DTSTART" and "DTEND" properties MUST be specified in local time and the
432: * appropriate set of "VTIMEZONE" calendar components MUST be included. For
433: * detail on the usage of the "VTIMEZONE" calendar component, see the
434: * "VTIMEZONE" calendar component definition.
435: *
436: * Any duration associated with the iCalendar object applies to all members
437: * of the generated recurrence set. Any modified duration for specific
438: * recurrences MUST be explicitly specified using the "RDATE" property.
439: */
440: public final static String RRULE = "rrule";
441:
442: /**
443: * Property Name: ORGANIZER
444: *
445: * Purpose: The property defines the organizer for a calendar component.
446: *
447: * Value Type: CAL-ADDRESS
448: *
449: * Property Parameters: Non-standard, language, common name, directory entry
450: * reference, sent by property parameters can be specified on this property.
451: *
452: * Conformance: This property MUST be specified in an iCalendar object that
453: * specifies a group scheduled calendar entity. This property MUST be
454: * specified in an iCalendar object that specifies the publication of a
455: * calendar user's busy time. This property MUST NOT be specified in an
456: * iCalendar object that specifies only a time zone definition or that
457: * defines calendar entities that are not group scheduled entities, but are
458: * entities only on a single user's calendar.
459: *
460: * Description: The property is specified within the "VEVENT", "VTODO",
461: * "VJOURNAL calendar components to specify the organizer of a group
462: * scheduled calendar entity. The property is specified within the
463: * "VFREEBUSY" calendar component to specify the calendar user requesting
464: * the free or busy time. When publishing a "VFREEBUSY" calendar component,
465: * the property is used to specify the calendar that the published busy time
466: * came from.
467: *
468: * The property has the property parameters CN, for specifying the common or
469: * display name associated with the "Organizer", DIR, for specifying a
470: * pointer to the directory information associated with the "Organizer",
471: * SENT-BY, for specifying another calendar user that is acting on behalf of
472: * the "Organizer". The non-standard parameters may also be specified on
473: * this property. If the LANGUAGE property parameter is specified, the
474: * identified language applies to the CN parameter value.
475: */
476: public final static String ORGANIZER = "organizer";
477:
478: /**
479: * Property Name: ATTENDEE
480: *
481: * Purpose: The property defines an "Attendee" within a calendar component.
482: *
483: * Value Type: CAL-ADDRESS
484: *
485: * Property Parameters: Non-standard, language, calendar user type, group or
486: * list membership, participation role, participation status, RSVP
487: * expectation, delegatee, delegator, sent by, common name or directory
488: * entry reference property parameters can be specified on this property.
489: *
490: * Conformance: This property MUST be specified in an iCalendar object that
491: * specifies a group scheduled calendar entity. This property MUST NOT be
492: * specified in an iCalendar object when publishing the calendar information
493: * (e.g., NOT in an iCalendar object that specifies the publication of a
494: * calendar user's busy time, event, to-do or journal). This property is not
495: * specified in an iCalendar object that specifies only a time zone
496: * definition or that defines calendar entities that are not group scheduled
497: * entities, but are entities only on a single user's calendar.
498: *
499: * Description: The property MUST only be specified within calendar
500: * components to specify participants, non-participants and the chair of a
501: * group scheduled calendar entity. The property is specified within an
502: * "EMAIL" category of the "VALARM" calendar component to specify an email
503: * address that is to receive the email type of iCalendar alarm.
504: *
505: * The property parameter CN is for the common or displayable name
506: * associated with the calendar address; ROLE, for the intended role that
507: * the attendee will have in the calendar component; PARTSTAT, for the
508: * status of the attendee's participation; RSVP, for indicating whether the
509: * favor of a reply is requested; CUTYPE, to indicate the type of calendar
510: * user; MEMBER, to indicate the groups that the attendee belongs to;
511: * DELEGATED-TO, to indicate the calendar users that the original request
512: * was delegated to; and DELEGATED-FROM, to indicate whom the request was
513: * delegated from; SENT-BY, to indicate whom is acting on behalf of the
514: * ATTENDEE; and DIR, to indicate the URI that points to the directory
515: * information corresponding to the attendee. These property parameters can
516: * be specified on an "ATTENDEE" property in either a "VEVENT", "VTODO" or
517: * "VJOURNAL" calendar component. They MUST not be specified in an
518: * "ATTENDEE" property in a "VFREEBUSY" or "VALARM" calendar component. If
519: * the LANGUAGE property parameter is specified, the identified language
520: * applies to the CN parameter.
521: *
522: * A recipient delegated a request MUST inherit the RSVP and ROLE values
523: * from the attendee that delegated the request to them.
524: *
525: * Multiple attendees can be specified by including multiple "ATTENDEE"
526: * properties within the calendar component.
527: */
528: public final static String ATTENDEE = "attendee";
529:
530: /**
531: * Property Name: URL
532: *
533: * Purpose: This property defines a Uniform Resource Locator (URL)
534: * associated with the iCalendar object.
535: *
536: * Value Type: URI
537: *
538: * Property Parameters: Non-standard property parameters can be specified on
539: * this property.
540: *
541: * Conformance: This property can be specified once in the "VEVENT",
542: * "VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
543: *
544: * Description: This property may be used in a calendar component to convey
545: * a location where a more dynamic rendition of the calendar information
546: * associated with the calendar component can be found. This memo does not
547: * attempt to standardize the form of the URI, nor the format of the
548: * resource pointed to by the property value. If the URL property and
549: * Content-Location MIME header are both specified, they MUST point to the
550: * same resource.
551: */
552: public final static String URL = "url";
553:
554: /**
555: * Property Name: FREEBUSY
556: *
557: * Purpose: The property defines one or more free or busy time intervals.
558: *
559: * Value Type: PERIOD. The date and time values MUST be in an UTC time
560: * format.
561: *
562: * Property Parameters: Non-standard or free/busy time type property
563: * parameters can be specified on this property.
564: *
565: * Conformance: The property can be specified in a "VFREEBUSY" calendar
566: * component.
567: *
568: * Property Parameter: "FBTYPE" and non-standard parameters can be specified
569: * on this property.
570: *
571: * Description: These time periods can be specified as either a start and
572: * end date-time or a start date-time and duration. The date and time MUST
573: * be a UTC time format.
574: *
575: * "FREEBUSY" properties within the "VFREEBUSY" calendar component SHOULD be
576: * sorted in ascending order, based on start time and then end time, with
577: * the earliest periods first.
578: *
579: * The "FREEBUSY" property can specify more than one value, separated by the
580: * COMMA character (US-ASCII decimal 44). In such cases, the "FREEBUSY"
581: * property values SHOULD all be of the same "FBTYPE" property parameter
582: * type (e.g., all values of a particular "FBTYPE" listed together in a
583: * single property).
584: */
585: public final static String FREEBUSY = "freebusy";
586:
587: /**
588: * Property Name: PRIORITY
589: *
590: * Purpose: The property defines the relative priority for a calendar
591: * component.
592: *
593: * Value Type: INTEGER
594: *
595: * Property Parameters: Non-standard property parameters can be specified on
596: * this property.
597: *
598: * Conformance: The property can be specified in a "VEVENT" or "VTODO"
599: * calendar component.
600: *
601: * Description: The priority is specified as an integer in the range zero to
602: * nine. A value of zero (US-ASCII decimal 48) specifies an undefined
603: * priority. A value of one (US-ASCII decimal 49) is the highest priority. A
604: * value of two (US-ASCII decimal 50) is the second highest priority.
605: * Subsequent numbers specify a decreasing ordinal priority. A value of nine
606: * (US-ASCII decimal 58) is the lowest priority.
607: *
608: * A CUA with a three-level priority scheme of "HIGH", "MEDIUM" and "LOW" is
609: * mapped into this property such that a property value in the range of one
610: * (US-ASCII decimal 49) to four (US-ASCII decimal 52) specifies "HIGH"
611: * priority. A value of five (US-ASCII decimal 53) is the normal or "MEDIUM"
612: * priority. A value in the range of six (US- ASCII decimal 54) to nine
613: * (US-ASCII decimal 58) is "LOW" priority.
614: *
615: * A CUA with a priority schema of "A1", "A2", "A3", "B1", "B2", ..., "C3"
616: * is mapped into this property such that a property value of one (US-ASCII
617: * decimal 49) specifies "A1", a property value of two (US- ASCII decimal
618: * 50) specifies "A2", a property value of three (US-ASCII decimal 51)
619: * specifies "A3", and so forth up to a property value of 9 (US-ASCII
620: * decimal 58) specifies "C3".
621: *
622: * Other integer values are reserved for future use.
623: *
624: * Within a "VEVENT" calendar component, this property specifies a priority
625: * for the event. This property may be useful when more than one event is
626: * scheduled for a given time period.
627: *
628: * Within a "VTODO" calendar component, this property specified a priority
629: * for the to-do. This property is useful in prioritizing multiple action
630: * items for a given time period.
631: */
632: public final static String PRIORITY = "priority";
633:
634: /**
635: * Property Name: ATTACH
636: *
637: * Purpose: The property provides the capability to associate a document
638: * object with a calendar component.
639: *
640: * Value Type: The default value type for this property is URI. The value
641: * type can also be set to BINARY to indicate inline binary encoded content
642: * information.
643: *
644: * Property Parameters: Non-standard, inline encoding, format type and value
645: * data type property parameters can be specified on this property.
646: *
647: * Conformance: The property can be specified in a "VEVENT", "VTODO",
648: * "VJOURNAL" or "VALARM" calendar components.
649: *
650: * Description: The property can be specified within "VEVENT", "VTODO",
651: * "VJOURNAL", or "VALARM" calendar components. This property can be
652: * specified multiple times within an iCalendar object.
653: */
654: public final static String ATTACH = "attach";
655:
656: /**
657: * Property Name: LOCATION
658: *
659: * Purpose: The property defines the intended venue for the activity defined
660: * by a calendar component.
661: *
662: * Value Type: TEXT
663: *
664: * Property Parameters: Non-standard, alternate text representation and
665: * language property parameters can be specified on this property.
666: *
667: * Conformance: This property can be specified in "VEVENT" or "VTODO"
668: * calendar component.
669: *
670: * Description: Specific venues such as conference or meeting rooms may be
671: * explicitly specified using this property. An alternate representation may
672: * be specified that is a URI that points to directory information with more
673: * structured specification of the location. For example, the alternate
674: * representation may specify either an LDAP URI pointing to an LDAP server
675: * entry or a CID URI pointing to a MIME body part containing a vCard
676: * [RFC2426] for the location.
677: */
678: public final static String LOCATION = "location";
679:
680: public final static String X_COLUMBA_CALENDAR = "x-columba-calendar";
681:
682: }
|