Data-ICal
view release on metacpan or search on metacpan
$calendar->as_string;DESCRIPTIONA Data::ICal object represents a"VCALENDAR"object asdefinedin theiCalendar protocol (RFC 2445, MIME type"text/calendar"), as implementedin many popular calendaring programs such as Apple's iCal.Each Data::ICal object is a collection of"entries", which are objectsof a subclass of Data::ICal::Entry. The types of entriesdefinedbyiCalendar (which refers to them as"components") include events, to-doitems, journal entries, free/busytimeindicators, andtimezonedescriptors; in addition, events and to-doitems can containalarmentries. (Currently, Data::ICal only implements to-doitems and events.)Data::ICal is a subclass of Data::ICal::Entry; see its manpageformoremethods applicable to Data::ICal.METHODSnew [data=>$data, ] [filename=>$file], [vcal10=>$bool]Creates a new Data::ICal object.
doc/rfc2445.txt view on Meta::CPAN
This memo is formatted as a registrationfora MIME media type per[RFC 2048]. However, theformatin this memo is equally applicableThe proposed media type value is'text/calendar'. This string wouldlabel a media type containing calendaring and scheduling informationencoded as text characters formatted in a manner outlined below.This MIME media type provides a standard content typeforcapturingcalendar event, to-doand journal entry information. It also can beused to convey free/busytimeinformation. The content type issuitable as a MIME message entity that can be transferred over MIMEbased email systems, using HTTP or some other Internet transport. InDawson & Stenerson Standards Track [Page 1]
doc/rfc2445.txt view on Meta::CPAN
In order to avoid confusionwiththis referenced work, this memo isto be known as the iCalendar specification.This memo defines theformatforspecifying iCalendar object methods.An iCalendar object method is a set of usage constraintsfortheiCalendar object. For example, these methods might define schedulingmessages that request an event be scheduled, reply to an eventrequest,senda cancellation noticeforan event, modify or replacethe definition of an event, provide a counter proposalforanoriginal event request, delegate an event request to anotherindividual, request free or busytime, reply to a free or busytimerequest, or provide similar scheduling messagesfora to-doorjournal entry calendar component. The iCalendar Transport-indendentInteroperability Protocol (iTIP)definedin [ITIP] is one suchscheduling protocol.Table of Contents1 Introduction.....................................................52 Basic Grammar and Conventions....................................62.1 Formatting Conventions .......................................7
doc/rfc2445.txt view on Meta::CPAN
unwired transport such as infrared might also be used.The memo also providesforthe definition of iCalendar object methodsthat willmapthis content type to a set of messagesforsupportingcalendaring and scheduling operations such as requesting, replyingto, modifying, and canceling meetings or appointments, to-dos andjournal entries. The iCalendar object methods can be used to defineother calendaring and scheduling operations such a requestingforandreplyingwithfree/busytimedata. Such a scheduling protocol isdefinedin the iCalendar Transport-independent InteroperabilityProtocol (iTIP)definedin [ITIP].The memo also includes a formal grammarforthe content type based onthe Internet ABNFdefinedin [RFC 2234]. This ABNF is requiredforthe implementation of parsers and to serve as the definitivereferencewhenambiguities or questions arise in interpreting thedescriptive prose definition of the memo.2 Basic Grammar and Conventions
doc/rfc2445.txt view on Meta::CPAN
Dawson & Stenerson Standards Track [Page 11]RFC 2445 iCalendar November 1998The file extension of"ifb"is to be used to designate a filecontaining free or busytimeinformation consistentwiththis MIMEcontent type.Macintosh file type codes: The file type code of"iCal"is to be usedin Apple MacIntosh operatingsystemenvironments to designate a filecontaining calendaring and scheduling information consistentwiththis MIME media type.The file type code of"iFBf"is to be used in Apple MacIntoshoperatingsystemenvironments to designate a file containing free orbusytimeinformation consistentwiththis MIME media type.3.11 ContactforFurther Information:Frank Dawson6544 Battleford DriveRaleigh, NC 27613-3502919-676-9515 (Telephone)919-676-9564 (Data/Facsimile)Frank_Dawson@Lotus.com (Internet Mail)
doc/rfc2445.txt view on Meta::CPAN
the following notation:parameter = altrepparam ; Alternate text representation/ cnparam ; Common name/ cutypeparam ; Calendar user type/ delfromparam ; Delegator/ deltoparam ; Delegatee/ dirparam ; Directory entry/ encodingparam ; Inline encoding/ fmttypeparam ; Format type/ fbtypeparam ; Free/busytimetype/ languageparam ; Languagefortext/ memberparam ; Group or list membership/ partstatparam ; Participation status/ rangeparam ; Recurrence identifier range/ trigrelparam ; Alarm trigger relationship/ reltypeparam ; Relationship type/ roleparam ; Participation role/ rsvpparam ; RSVP expectation/ sentbyparam ; Sent by/ tzidparam ; Reference totimezone object
doc/rfc2445.txt view on Meta::CPAN
Example:ATTACH;FMTTYPE=application/binary:ftp://domain.com/pub/docs/agenda.doc4.2.9 Free/Busy Time TypeParameter Name: FBTYPEPurpose: To specify the free or busytimetype.Format Definition: The property parameter isdefinedby the followingnotation:fbtypeparam ="FBTYPE""="("FREE"/"BUSY"/"BUSY-UNAVAILABLE"/"BUSY-TENTATIVE"/ x-name; Some experimental iCalendar data type./ iana-token)Dawson & Stenerson Standards Track [Page 23]RFC 2445 iCalendar November 1998; Some other IANA registered iCalendar data type.Description: The parameter specifies the free or busytimetype. Thevalue FREE indicates that thetimeinterval is freeforscheduling.The value BUSY indicates that thetimeinterval is busy because oneor more events have been scheduledforthat interval. The valueBUSY-UNAVAILABLE indicates that thetimeinterval is busy and thatthe interval can not be scheduled. The value BUSY-TENTATIVE indicatesthat thetimeinterval is busy because one or more events have beententatively scheduledforthat interval. If not specified on aproperty that allows this parameter, thedefaultis BUSY.Example: The following is an example of this parameter on a FREEBUSYproperty.FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z4.2.10 Language
doc/rfc2445.txt view on Meta::CPAN
The datewithlocaltimeform is simply a date-timevalue that doesnot contain the UTC designator nor does it reference atimezone. Forexample, the following represents Janurary 18, 1998, at 11 PM:DTSTART:19980118T230000Date-timevaluesof this type are said to be"floating"and are notbound to anytimezone in particular. They are used to represent thesame hour, minute, and second value regardless of whichtimezone iscurrently being observed. For example, an event can bedefinedthatindicates that an individual will be busy from 11:00 AM to 1:00 PMevery day,nomatter whichtimezone the person is in. In thesecases, alocaltimecan be specified. The recipient of an iCalendarobjectwitha property value consisting of alocaltime, without anyrelativetimezone information, SHOULD interpret the value as beingfixed to whatevertimezone the ATTENDEE is in at anygivenmoment.This means that two ATTENDEEs, in differenttimezones, receiving thesame event definition as a floatingtime, may be participating in theevent at different actualtimes. FloatingtimeSHOULD only be usedwhere that is the reasonable behavior.
doc/rfc2445.txt view on Meta::CPAN
Dawson & Stenerson Standards Track [Page 47]RFC 2445 iCalendar November 1998Timevaluesof this type are said to be"floating"and are not boundto anytimezone in particular. They are used to represent the samehour, minute, and second value regardless of whichtimezone iscurrently being observed. For example, an event can bedefinedthatindicates that an individual will be busy from 11:00 AM to 1:00 PMevery day,nomatter whichtimezone the person is in. In thesecases, alocaltimecan be specified. The recipient of an iCalendarobjectwitha property value consisting of alocaltime, without anyrelativetimezone information, SHOULD interpret the value as beingfixed to whatevertimezone the ATTENDEE is in at anygivenmoment.This means that two ATTENDEEs may participate in the same event atdifferent UTCtimes; floatingtimeSHOULD only be used where that isreasonable behavior.In most cases, a fixedtimeis desired. To properly communicate a
doc/rfc2445.txt view on Meta::CPAN
as DtStart;TzID=US-Eastern:19980714T120000.4.6 Calendar ComponentsThe body of the iCalendar object consists of a sequence of calendarproperties and one or more calendar components. The calendarproperties are attributes that apply to the calendar as a whole. Thecalendar components are collections of properties that express aparticular calendar semantic. For example, the calendar component canspecify an event, a to-do, a journal entry,timezone information, orfree/busytimeinformation, or analarm.The body of the iCalendar object isdefinedby the followingnotation:icalbody = calprops componentcalprops = 2*(;'prodid'and'version'are both REQUIRED,; but MUST NOT occur more than once
doc/rfc2445.txt view on Meta::CPAN
Dawson & Stenerson Standards Track [Page 51]RFC 2445 iCalendar November 1998)component = 1*(eventc / todoc / journalc / freebusyc // timezonec / iana-comp / x-comp)iana-comp ="BEGIN"":"iana-token CRLF1*contentline"END"":"iana-token CRLFx-comp ="BEGIN"":"x-name CRLF1*contentline"END"":"x-name CRLFAn iCalendar object MUST include the"PRODID"and"VERSION"calendarproperties. In addition, it MUST include at least one calendarcomponent. Special forms of iCalendar objects are possible to publishjust busytime(i.e., only a"VFREEBUSY"calendar component) ortimezone (i.e., only a"VTIMEZONE"calendar component) information. Inaddition, a complex iCalendar object is possible that is used tocapture a complete snapshot of the contents of a calendar (e.g.,composite of many different calendar components). More commonly, aniCalendar object will consist of just a single"VEVENT","VTODO"or"VJOURNAL"calendar component.4.6.1 Event ComponentComponent Name:"VEVENT"
doc/rfc2445.txt view on Meta::CPAN
resources / rdate / rrule / x-prop)Description: A"VEVENT"calendar component is a grouping of componentproperties, and possibly including"VALARM"calendar components, thatrepresents a scheduled amount oftimeon a calendar. For example, itcan be an activity; such as a one-hour long, department meeting from8:00 AM to 9:00 AM, tomorrow. Generally, an event will take uptimeon an individual calendar. Hence, the event will appear as an opaqueinterval in a searchforbusytime. Alternately, the event can haveits Time Transparency set to"TRANSPARENT"in order to preventblocking of the event in searchesforbusytime.The"VEVENT"is also the calendar component used to specify ananniversary or daily reminder within a calendar. These events have aDATE value typeforthe"DTSTART"property instead of thedefaultdata type of DATE-TIME. If such a"VEVENT"hasa"DTEND"property, itMUST be specified as a DATE value also. The anniversary type of"VEVENT"can span more than one date (i.e,"DTEND"property value isset to a calendar dateafterthe"DTSTART"property value).The"DTSTART"propertyfora"VEVENT"specifies the inclusive start
doc/rfc2445.txt view on Meta::CPAN
RFC 2445 iCalendar November 1998The"VEVENT"calendar component cannot be nested within anothercalendar component. However,"VEVENT"calendar components can berelated toeachother or to a"VTODO"or to a"VJOURNAL"calendarcomponentwiththe"RELATED-TO"property.Example: The following is an example of the"VEVENT"calendarcomponent used to represent a meeting that will also be opaque tosearchesforbusytime:BEGIN:VEVENTUID:19970901T130000Z-123401@host.comDTSTAMP:19970901T1300ZDTSTART:19970903T163000ZDTEND:19970903T190000ZSUMMARY:Annual Employee ReviewCLASS:PRIVATECATEGORIES:BUSINESS,HUMAN RESOURCESEND:VEVENTThe following is an example of the"VEVENT"calendar component usedto represent a reminder that will not be opaque, but rathertransparent, to searchesforbusytime:BEGIN:VEVENTUID:19970901T130000Z-123402@host.comDTSTAMP:19970901T1300ZDTSTART:19970401T163000ZDTEND:19970402T010000ZSUMMARY:Laurel is in sensitivity awareness class.CLASS:PUBLICCATEGORIES:BUSINESS,HUMAN RESOURCESTRANSP:TRANSPARENTEND:VEVENTThe following is an example of the"VEVENT"calendar component usedto represent an anniversary that will occur annually. Since it takesupnotime, it will not appear as opaque in a searchforbusytime;nomatter what the value of the"TRANSP"property indicates:BEGIN:VEVENTUID:19970901T130000Z-123403@host.comDTSTAMP:19970901T1300ZDTSTART:19971102SUMMARY:Our Blissful AnniversaryCLASS:CONFIDENTIALCATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASIONRRULE:FREQ=YEARLY
doc/rfc2445.txt view on Meta::CPAN
property is used to specify the calendar date that the journal entryis associatedwith. Generally, it will have a DATE value data type,but it can also be used to specify a DATE-TIME value data type.Examples of a journal entry include a daily record of a legislativebody or a journal entry of individual telephone contactsforthe dayor an ordered list of accomplishmentsforthe day. The"VJOURNAL"calendar component can also be used to associate a documentwithacalendar date.The"VJOURNAL"calendar component does not take uptimeon acalendar. Hence, it does not play a role in free or busytimesearches - - it is as though ithasatimetransparency value ofTRANSPARENT. It is transparent to any such searches.The"VJOURNAL"calendar component cannot be nested within anothercalendar component. However,"VJOURNAL"calendar components can berelated toeachother or to a"VEVENT"or to a"VTODO"calendarcomponent,withthe"RELATED-TO"property.Example: The following is an example of the"VJOURNAL"calendarcomponent:
doc/rfc2445.txt view on Meta::CPAN
Dawson & Stenerson Standards Track [Page 57]RFC 2445 iCalendar November 19984.6.4 Free/Busy ComponentComponent Name: VFREEBUSYPurpose: Provide a grouping of component properties that describeeither a requestforfree/busytime, describe a response to a requestforfree/busytimeor describe a published set of busytime.Formal Definition: A"VFREEBUSY"calendar component isdefinedby thefollowing notation:freebusyc ="BEGIN"":""VFREEBUSY"CRLFfbprop"END"":""VFREEBUSY"CRLFfbprop = *(; the following are optional,; but MUST NOT occur more than oncecontact / dtstart / dtend / duration / dtstamp /organizer / uid / url /; the following are optional,; and MAY occur more than onceattendee / comment / freebusy / rstatus / x-prop)Description: A"VFREEBUSY"calendar component is a grouping ofcomponent properties that represents either a requestfor, a reply toa requestforfree or busytimeinformation or a published set ofbusytimeinformation.When used to request free/busytimeinformation, the"ATTENDEE"property specifies the calendar users whose free/busytimeis beingrequested; the"ORGANIZER"property specifies the calendar user whois requesting the free/busytime; the"DTSTART"and"DTEND"properties specify the window oftimeforwhich the free/busytimeisbeing requested; the"UID"and"DTSTAMP"properties are specified toassist in proper sequencing of multiple free/busytimerequests.When used to reply to a requestforfree/busytime, the"ATTENDEE"property specifies the calendar user responding to the free/busytimerequest; the"ORGANIZER"property specifies the calendar user thatoriginally requested the free/busytime; the"FREEBUSY"propertyspecifies the free/busytimeinformation (ifitexists); and theDawson & Stenerson Standards Track [Page 58]RFC 2445 iCalendar November 1998"UID"and"DTSTAMP"properties are specified to assist in propersequencing of multiple free/busytimereplies.When used to publish busytime, the"ORGANIZER"property specifiesthe calendar user associatedwiththe published busytime; the"DTSTART"and"DTEND"properties specify an inclusivetimewindowthat surrounds the busytimeinformation; the"FREEBUSY"propertyspecifies the published busytimeinformation; and the"DTSTAMP"property specifies the date/timethat iCalendar object was created.The"VFREEBUSY"calendar component cannot be nested within anothercalendar component. Multiple"VFREEBUSY"calendar components can bespecified within an iCalendar object. This permits the grouping ofFree/Busy information into logical collections, such as monthlygroups of busytimeinformation.object methods involving requestsforfreetime, requestsforbusytime, requestsforboth free and busy, and the associated replies.Free/Busy information is representedwiththe"FREEBUSY"property.This property provides a terse representation oftimeperiods. One ormore"FREEBUSY"properties can be specified in the"VFREEBUSY"calendar component.When present in a"VFREEBUSY"calendar component, the"DTSTART"and"DTEND"properties SHOULD be specified prior to any"FREEBUSY"properties. In a freetimerequest, these properties can be used incombinationwiththe"DURATION"property to represent a requestforaduration of freetimewithin a specified window oftime.The recurrence properties ("RRULE","EXRULE","RDATE","EXDATE") arenot permitted within a"VFREEBUSY"calendar component. Any recurringevents are resolved into their individual busytimeperiods using the"FREEBUSY"property.Example: The following is an example of a"VFREEBUSY"calendarcomponent used to request free or busytimeinformation:BEGIN:VFREEBUSYORGANIZER:MAILTO:jane_doe@host1.comATTENDEE:MAILTO:john_public@host2.comDTSTART:19971015T050000ZDTEND:19971016T050000ZDTSTAMP:19970901T083000ZEND:VFREEBUSYDawson & Stenerson Standards Track [Page 59]RFC 2445 iCalendar November 1998The following is an example of a"VFREEBUSY"calendar component usedto reply to the requestwithbusytimeinformation:BEGIN:VFREEBUSYORGANIZER:MAILTO:jane_doe@host1.comATTENDEE:MAILTO:john_public@host2.comDTSTAMP:19970901T100000ZFREEBUSY;VALUE=PERIOD:19971015T050000Z/PT8H30M,19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30MCOMMENT:This iCalendar file contains busytimeinformationforthenextthree months.END:VFREEBUSYThe following is an example of a"VFREEBUSY"calendar component usedto publish busytimeinformation.BEGIN:VFREEBUSYORGANIZER:jsmith@host.comDTSTART:19980313T141711ZDTEND:19980410T141711ZFREEBUSY:19980314T233000Z/19980315T003000ZFREEBUSY:19980316T153000Z/19980316T163000ZFREEBUSY:19980318T030000Z/19980318T040000ZEND:VFREEBUSY4.6.5 Time Zone ComponentComponent Name: VTIMEZONEPurpose: Provide a grouping of component properties that defines atimezone.Formal Definition: A"VTIMEZONE"calendar component isdefinedby the
doc/rfc2445.txt view on Meta::CPAN
identifier property parameters can be specified on this property.Conformance: This property can be specified in"VEVENT"or"VFREEBUSY"calendar components.Description: Within the"VEVENT"calendar component, this propertydefines the date andtimeby which the event ends. The value MUST belater intimethan the value of the"DTSTART"property.Within the"VFREEBUSY"calendar component, this property defines theend date andtimeforthe free or busytimeinformation. ThetimeMUST be specified in the UTCtimeformat. The value MUST be later intimethan the value of the"DTSTART"property.Format Definition: The property isdefinedby the following notation:dtend ="DTEND"dtendparam":"dtendval CRLFdtendparam = *(; the following are optional,
doc/rfc2445.txt view on Meta::CPAN
Conformance: This property can be specified in the"VEVENT","VTODO","VFREEBUSY", or"VTIMEZONE"calendar components.Description: Within the"VEVENT"calendar component, this propertydefines the start date andtimeforthe event. The property isREQUIRED in"VEVENT"calendar components. Events can have a startdate/timebutnoend date/time. In that case, the event does not takeup anytime.Within the"VFREEBUSY"calendar component, this property defines thestart date andtimeforthe free or busytimeinformation. ThetimeMUST be specified in UTCtime.Within the"VTIMEZONE"calendar component, this property defines theeffective start date andtimeforatimezone specification. Thisproperty is REQUIRED withineachSTANDARD and DAYLIGHT part includedin"VTIMEZONE"calendar components and MUST be specified as alocalDATE-TIME without the"TZID"property parameter.Format Definition: The property isdefinedby the following notation:
doc/rfc2445.txt view on Meta::CPAN
The following is an example of this property that specifies aninterval oftimeof 15 minutes.DURATION:PT15M4.8.2.6 Free/Busy TimeProperty Name: FREEBUSYPurpose: The property defines one or more free or busytimeintervals.Value Type: PERIOD. The date andtimevaluesMUST be in an UTCtimeformat.Property Parameters: Non-standard or free/busytimetype propertyparameters can be specified on this property.Conformance: The property can be specified in a"VFREEBUSY"calendarcomponent.Property Parameter:"FBTYPE"and non-standard parameters can bespecified on this property.Description: Thesetimeperiods can be specified as either a startand end date-timeor a start date-timeand duration. The date and
doc/rfc2445.txt view on Meta::CPAN
Dawson & Stenerson Standards Track [Page 95]RFC 2445 iCalendar November 1998Format Definition: The property isdefinedby the following notation:freebusy ="FREEBUSY"fbparam":"fbvalueCRLFfbparam = *(; the following is optional,; but MUST NOT occur more than once(";"fbtypeparam) /; the following is optional,; and MAY occur more than once
doc/rfc2445.txt view on Meta::CPAN
FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1HFREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H,19970308T230000Z/19970309T000000Z4.8.2.7 Time TransparencyProperty Name: TRANSPPurpose: This property defines whether an event is transparent or notto busytimesearches.Value Type: TEXTProperty Parameters: Non-standard property parameters can bespecified on this property.Conformance: This property can be specified once in a"VEVENT"calendar component.Description: Time Transparency is the characteristic of an event that
doc/rfc2445.txt view on Meta::CPAN
that consume actualtimeforthe individual or resource associatedDawson & Stenerson Standards Track [Page 96]RFC 2445 iCalendar November 1998withthe calendar SHOULD be recorded as OPAQUE, allowing them to bedetected by free-busytimesearches. Other events, whichdonot takeup the individual's (or resource's)timeSHOULD be recorded asTRANSPARENT, making them invisible to free-busytimesearches.Format Definition: The property is specified by the followingnotation:transp ="TRANSP"tranparam":"transvalue CRLFtranparam = *(";"xparam)transvalue ="OPAQUE";Blocks or opaque on busytimesearches./"TRANSPARENT";Transparent on busytimesearches.;Default value is OPAQUEExample: The following is an example of this propertyforan eventthat is transparent or does not block on free/busytimesearches:TRANSP:TRANSPARENTThe following is an example of this propertyforan event that isopaque or blocks on free/busytimesearches:TRANSP:OPAQUE4.8.3 Time Zone Component PropertiesThe following properties specifytimezone information in calendarcomponents.4.8.3.1 Time Zone Identifier
doc/rfc2445.txt view on Meta::CPAN
Property Parameters: Non-standard, language, calendar user type,group or list membership, participation role, participation status,RSVP expectation, delegatee, delegator, sent by, common name ordirectory entry reference property parameters can be specified onthis property.Conformance: This property MUST be specified in an iCalendar objectthat specifies a group scheduled calendar entity. This property MUSTNOT be specified in an iCalendar objectwhenpublishing the calendarinformation (e.g., NOT in an iCalendar object that specifies thepublication of a calendar user's busytime, event, to-door journal).This property is not specified in an iCalendar object that specifiesonly atimezone definition or that defines calendar entities thatare not group scheduled entities, but are entities only on a singleuser's calendar.Description: The property MUST only be specified within calendarcomponents to specify participants, non-participants and the chair ofa group scheduled calendar entity. The property is specified withinan"EMAIL"category of the"VALARM"calendar component to specify anemail address that is to receive the email type of iCalendaralarm.
doc/rfc2445.txt view on Meta::CPAN
Value Type: CAL-ADDRESSProperty Parameters: Non-standard, language, common name, directoryentry reference, sent by property parameters can be specified on thisproperty.Conformance: This property MUST be specified in an iCalendar objectthat specifies a group scheduled calendar entity. This property MUSTbe specified in an iCalendar object that specifies the publication ofa calendar user's busytime. This property MUST NOT be specified inan iCalendar object that specifies only atimezone definition orthat defines calendar entities that are not group scheduled entities,but are entities only on a single user's calendar.Description: The property is specified within the"VEVENT","VTODO","VJOURNAL calendar components to specify the organizer of a groupscheduled calendar entity. The property is specified within the"VFREEBUSY"calendar component to specify the calendar userrequesting the free or busytime. When publishing a"VFREEBUSY"calendar component, the property is used to specify the calendar thatthe published busytimecame from.The propertyhasthe property parameters CN,forspecifying thecommon or display name associatedwiththe"Organizer", DIR,forspecifying a pointer to the directory information associatedwiththe"Organizer", SENT-BY,forspecifying another calendar user that isacting on behalf of the"Organizer". The non-standard parameters mayalso be specified on this property. If the LANGUAGE propertyparameter is specified, the identified language applies to the CNparameter value.
doc/rfc2445.txt view on Meta::CPAN
The COMMA and SEMICOLON separator characters in the property valueare BACKSLASH character escaped because they appear in a text value.REQUEST-STATUS:2.0;SuccessREQUEST-STATUS:3.1;Invalid property value;DTSTART:96-Apr-01REQUEST-STATUS:2.8; Success\, repeating event ignored. Scheduledas a single event.;RRULE:FREQ=WEEKLY\;INTERVAL=2REQUEST-STATUS:4.1;Event conflict. Date/timeis busy.REQUEST-STATUS:3.7;Invalid calendar user;ATTENDEE:MAILTO:jsmith@host.com5 iCalendar Object ExamplesThe following examples are provided as an informational source ofillustrative iCalendar objects consistentwiththis content type.The following example specifies a three-day conference that begins at
doc/rfc2445.txt view on Meta::CPAN
Participants: John Smith, Jane Doe, Jim Dandy\n-It wasdecided that the requirements need to be signed off byproduct marketing.\n-Project processes were accepted.\n-Project schedule needs to accountforscheduled holidaysand employee vacationtime. CheckwithHRforspecificdates.\n-New schedule will be distributed by Friday.\n-Next weeks meeting is cancelled. No meetinguntil3/23.END:VJOURNALEND:VCALENDARThe following is an example of published busytimeinformation. TheiCalendar object might be placed in the network resourcewww.host.com/calendar/busytime/jsmith.ifb.BEGIN:VCALENDARVERSION:2.0PRODID:-//RDU Software//NONSGML HandCal//ENBEGIN:VFREEBUSYDawson & Stenerson Standards Track [Page 139]RFC 2445 iCalendar November 1998ORGANIZER:MAILTO:jsmith@host.comDTSTART:19980313T141711ZDTEND:19980410T141711ZFREEBUSY:19980314T233000Z/19980315T003000ZFREEBUSY:19980316T153000Z/19980316T163000ZFREEBUSY:19980318T030000Z/19980318T040000ZEND:VFREEBUSYEND:VCALENDAR6 Recommended PracticesThese recommended practices should be followed in order to assureconsistent handling of the following casesforan iCalendar object.1. Content lines longer than 75 octets SHOULD be folded.2. A calendar entrywitha"DTSTART"property butno"DTEND"property does not take up anytime. It is intended to representan event that is associatedwithagivencalendar date andtimeof day, such as an anniversary. Since the event does not take upanytime, it MUST NOT be used to record busytimenomatter whatthe valueforthe"TRANSP"property.3. When the"DTSTART"and"DTEND",for"VEVENT","VJOURNAL"and"VFREEBUSY"calendar components, and"DTSTART"and"DUE",for"VTODO"calendar components, have the same value data type (e.g.,DATE-TIME), they SHOULD specifyvaluesin the sametimeformat(e.g., UTCtimeformat).4. When the combination of the"RRULE"and"RDATE"properties on aniCalendar object produces multiple instances having the same
lib/Data/ICal.pm view on Meta::CPAN
=head1 DESCRIPTIONA L<Data::ICal> object represents a C<VCALENDAR> object as defined in theiCalendar protocol (RFC 2445, MIME type "text/calendar"), as implemented in manypopular calendaring programs such as Apple's iCal.Each L<Data::ICal> object is a collection of "entries", which are objects of asubclass of L<Data::ICal::Entry>. The types of entries defined by iCalendar(which refers to them as "components") include events, to-do items, journalentries, free/busy time indicators, and time zone descriptors; in addition,events and to-do items can contain alarm entries. (Currently, L<Data::ICal>only implements to-do items and events.)L<Data::ICal> is a subclass of L<Data::ICal::Entry>; see its manpage for moremethods applicable to L<Data::ICal>.=head1 METHODS=cut
lib/Data/ICal/Entry.pm view on Meta::CPAN
$output.=$self->footer(%args);return$output;}=head2 add_entry $entryAdds an entry to this entry. (According to the standard, this shouldonly be called on either a to-do or event entry with an alarm entry,or on a calendar entry (L<Data::ICal>) with a to-do, event, journal,timezone, or free/busy entry.)Returns true if the entry was successfully added, and false otherwise(perhaps because you tried to add an entry of an invalid type, butthis check hasn't been implemented yet).=cutsubadd_entry {my$self=shift;my$entry=shift;
lib/Data/ICal/Entry.pm view on Meta::CPAN
@_);return'END:'.$self->ical_entry_type .$args{crlf};}# mapping of event types to class (under the Data::Ical::Event namespace)my%_generic= (vevent=>'Event',vtodo=>'Todo',vjournal=>'Journal',vfreebusy=>'FreeBusy',vtimezone=>'TimeZone',standard=>'TimeZone::Standard',daylight=>'TimeZone::Daylight',);=head2 parse_objectTranslate a L<Text::vFile::asData> sub object into the appropriateL<Data::iCal::Event> subtype.
lib/Data/ICal/Entry/FreeBusy.pm view on Meta::CPAN
usewarnings;usestrict;packageData::ICal::Entry::FreeBusy;=head1 NAMEData::ICal::Entry::FreeBusy - Represents blocks of free and busy time in an iCalendar file=head1 SYNOPSISmy $vfreebusy = Data::ICal::Entry::FreeBusy->new();$vfreebusy->add_properties(organizer => 'MAILTO:jsmith@host.com',# Dat*e*::ICal is not a typo herefreebusy => Date::ICal->new( epoch => ... )->ical . '/' . Date::ICal->new( epoch => ... )->ical,);$calendar->add_entry($vfreebusy);=head1 DESCRIPTIONA L<Data::ICal::Entry::FreeBusy> object represents a request forinformation about free and busy time or a reponse to such a request,in an iCalendar file. (Note that the iCalendar RFC refers to entriesas "components".) It is a subclass of L<Data::ICal::Entry> andaccepts all of its methods.=head1 METHODS=cut=head2 ical_entry_type
lib/Data/ICal/Entry/FreeBusy.pm view on Meta::CPAN
=cutsub mandatory_unique_properties {my $self = shift;return $self->rfc_strict ? ("uid") : ()}=head2 optional_unique_propertiesAccording to the iCalendar standard, the following properties may bespecified at most one time for a free/busy entry:contact dtstart dtend duration dtstamporganizer uid url=cutsuboptional_unique_properties {my$self=shift;my@ret=qw(contact dtstart dtend duration dtstamporganizer url);push@ret,"uid"unless$self->rfc_strict;return@ret;}=head2 optional_repeatable_propertiesAccording to the iCalendar standard, the following properties may bespecified any number of times for free/busy entry:attendee comment freebusy request-status=cutsuboptional_repeatable_properties {qw(attendee comment freebusy request-status);}=head1 AUTHORBest Practical Solutions, LLC E<lt>modules@bestpractical.comE<gt>=head1 LICENCE AND COPYRIGHTCopyright (c) 2005 - 2020, Best Practical Solutions, LLC. All rights reserved.
( run in 0.368 second using v1.01-cache-2.11-cpan-454fe037f31 )