rubyredrick-ri_cal 0.0.2

data/History.txt

@@ -0,0 +1,3 @@
+== 0.0.1 / 2009-4/26
+
+* Initial public release

data/Manifest.txt

@@ -0,0 +1,122 @@
+History.txt
+Manifest.txt
+README.txt
+Rakefile
+bin/ri_cal
+component_attributes/alarm.yml
+component_attributes/calendar.yml
+component_attributes/component_property_defs.yml
+component_attributes/event.yml
+component_attributes/freebusy.yml
+component_attributes/journal.yml
+component_attributes/timezone.yml
+component_attributes/timezone_period.yml
+component_attributes/todo.yml
+copyrights.txt
+docs/draft-ietf-calsify-2446bis-08.txt
+docs/draft-ietf-calsify-rfc2445bis-09.txt
+docs/incrementers.txt
+docs/rfc2445.pdf
+lib/ri_cal.rb
+lib/ri_cal/component.rb
+lib/ri_cal/component/alarm.rb
+lib/ri_cal/component/calendar.rb
+lib/ri_cal/component/event.rb
+lib/ri_cal/component/freebusy.rb
+lib/ri_cal/component/journal.rb
+lib/ri_cal/component/t_z_info_timezone.rb
+lib/ri_cal/component/timezone.rb
+lib/ri_cal/component/timezone/daylight_period.rb
+lib/ri_cal/component/timezone/standard_period.rb
+lib/ri_cal/component/timezone/timezone_period.rb
+lib/ri_cal/component/todo.rb
+lib/ri_cal/core_extensions.rb
+lib/ri_cal/core_extensions/array.rb
+lib/ri_cal/core_extensions/array/conversions.rb
+lib/ri_cal/core_extensions/date.rb
+lib/ri_cal/core_extensions/date/conversions.rb
+lib/ri_cal/core_extensions/date_time.rb
+lib/ri_cal/core_extensions/date_time/conversions.rb
+lib/ri_cal/core_extensions/object.rb
+lib/ri_cal/core_extensions/object/conversions.rb
+lib/ri_cal/core_extensions/string.rb
+lib/ri_cal/core_extensions/string/conversions.rb
+lib/ri_cal/core_extensions/time.rb
+lib/ri_cal/core_extensions/time/calculations.rb
+lib/ri_cal/core_extensions/time/conversions.rb
+lib/ri_cal/core_extensions/time/week_day_predicates.rb
+lib/ri_cal/invalid_timezone_identifer.rb
+lib/ri_cal/occurrence_enumerator.rb
+lib/ri_cal/parser.rb
+lib/ri_cal/properties/alarm.rb
+lib/ri_cal/properties/calendar.rb
+lib/ri_cal/properties/event.rb
+lib/ri_cal/properties/freebusy.rb
+lib/ri_cal/properties/journal.rb
+lib/ri_cal/properties/timezone.rb
+lib/ri_cal/properties/timezone_period.rb
+lib/ri_cal/properties/todo.rb
+lib/ri_cal/property_value.rb
+lib/ri_cal/property_value/array.rb
+lib/ri_cal/property_value/cal_address.rb
+lib/ri_cal/property_value/date.rb
+lib/ri_cal/property_value/date_time.rb
+lib/ri_cal/property_value/date_time/additive_methods.rb
+lib/ri_cal/property_value/date_time/time_machine.rb
+lib/ri_cal/property_value/date_time/timezone_support.rb
+lib/ri_cal/property_value/duration.rb
+lib/ri_cal/property_value/geo.rb
+lib/ri_cal/property_value/integer.rb
+lib/ri_cal/property_value/occurrence_list.rb
+lib/ri_cal/property_value/period.rb
+lib/ri_cal/property_value/recurrence_rule.rb
+lib/ri_cal/property_value/recurrence_rule/enumeration_support_methods.rb
+lib/ri_cal/property_value/recurrence_rule/enumerator.rb
+lib/ri_cal/property_value/recurrence_rule/initialization_methods.rb
+lib/ri_cal/property_value/recurrence_rule/negative_setpos_enumerator.rb
+lib/ri_cal/property_value/recurrence_rule/numbered_span.rb
+lib/ri_cal/property_value/recurrence_rule/occurence_incrementer.rb
+lib/ri_cal/property_value/recurrence_rule/recurring_day.rb
+lib/ri_cal/property_value/recurrence_rule/recurring_month_day.rb
+lib/ri_cal/property_value/recurrence_rule/recurring_numbered_week.rb
+lib/ri_cal/property_value/recurrence_rule/recurring_year_day.rb
+lib/ri_cal/property_value/recurrence_rule/validations.rb
+lib/ri_cal/property_value/text.rb
+lib/ri_cal/property_value/uri.rb
+lib/ri_cal/property_value/utc_offset.rb
+lib/ri_cal/required_timezones.rb
+lib/ri_cal/time_with_floating_timezone.rb
+ri_cal.gemspec
+sample_ical_files/from_ical_dot_app/test1.ics
+script/console
+script/destroy
+script/generate
+script/txt2html
+spec/ri_cal/component/alarm_spec.rb
+spec/ri_cal/component/calendar_spec.rb
+spec/ri_cal/component/event_spec.rb
+spec/ri_cal/component/freebusy_spec.rb
+spec/ri_cal/component/journal_spec.rb
+spec/ri_cal/component/t_z_info_timezone_spec.rb
+spec/ri_cal/component/timezone_spec.rb
+spec/ri_cal/component/todo_spec.rb
+spec/ri_cal/component_spec.rb
+spec/ri_cal/core_extensions/time/calculations_spec.rb
+spec/ri_cal/core_extensions/time/week_day_predicates_spec.rb
+spec/ri_cal/occurrence_enumerator_spec.rb
+spec/ri_cal/parser_spec.rb
+spec/ri_cal/property_value/date_spec.rb
+spec/ri_cal/property_value/date_time_spec.rb
+spec/ri_cal/property_value/duration_spec.rb
+spec/ri_cal/property_value/period_spec.rb
+spec/ri_cal/property_value/recurrence_rule/recurring_year_day_spec.rb
+spec/ri_cal/property_value/recurrence_rule_spec.rb
+spec/ri_cal/property_value/text_spec.rb
+spec/ri_cal/property_value/utc_offset_spec.rb
+spec/ri_cal/property_value_spec.rb
+spec/ri_cal/required_timezones_spec.rb
+spec/ri_cal_spec.rb
+spec/spec.opts
+spec/spec_helper.rb
+tasks/ri_cal.rake
+tasks/spec.rake

data/README.txt

@@ -0,0 +1,271 @@
+== RI_CAL -- a new implementation of RFC2445 in Ruby
+http://rical.rubyforge.org/
+
+    by Rick DeNatale
+== DESCRIPTION:
+
+This is an UNOFFICIAL version.  The public official version will be released on RubyForge.  Github will be used
+for interim versions.  USE THIS VERSION AT YOUR OWN RISK.
+
+A new Ruby implementation of RFC2445 iCalendar.
+
+The existing Ruby iCalendar libraries (e.g. icalendar, vpim) provide for parsing and generating icalendar files,
+but do not support important things like enumerating occurrences of repeating events.
+
+This is a clean-slate implementation of RFC2445.
+
+== FEATURES/PROBLEMS:
+
+* All examples of recurring events in RFC 2445 are handled. RSpec examples are provided for them. 
+
+== SYNOPSIS:
+
+=== Components and properties
+
+An iCalendar calendar comprises subcomponents like Events, Timezones and Todos.  Each component may have
+properties, for example an event has a dtstart property which defines the time (and date) on which the event
+starts.
+
+RiCal components will provide reasonable ruby objects as the values of these properties, and allow the properties
+to be set to ruby objects which are reasonable for the particular property.  For example time properties like dtstart
+can be set to a ruby Time, DateTime or Date object, and will return a DateTime or Date object when queried.
+
+The methods for accessing the properties of each type of component are defined in a module with the same name
+as the component class in the RiCal::properties module.  For example the property accessing methods for 
+RiCal::Component::Event are defined in RiCal::Properties::Event
+
+=== Creating Calendars and Calendar Components
+
+RiCal provides a builder DSL for creating calendars and calendar components. An example
+
+  RiCal.Calendar do
+    event do
+      description "MA-6 First US Manned Spaceflight"
+      dtstart     DateTime.parse("2/20/1962 14:47:39")
+      dtend       DateTime.parse("2/20/1962 19:43:02")
+      location    "Cape Canaveral"
+      add_attendee "john.glenn@nasa.gov"
+      alarm do
+        description "Segment 51"
+      end
+    end
+  end
+  
+This style is for compatibility with the iCalendar and vpim to ease migration.  The downside is that the block is evaluated
+in the context of a different object which cause surprising if the block contains direct instance variable references or
+implicit references to self.  Note that, in this style, one must use 'declarative' method calls like dtstart to set values
+rather than more natural attribute writer methods, like dtstart=
+  
+Alternatively you can pass a block with a single argument, in this case the component being built will be passed as that argument
+
+  RiCal.Calendar do |cal|
+    cal.event do |event|
+      event.description = "MA-6 First US Manned Spaceflight"
+      event.dtstart =  DateTime.parse("2/20/1962 14:47:39")
+      event.dtend = DateTime.parse("2/20/1962 19:43:02")
+      event.location = "Cape Canaveral"
+      event.add_attendee "john.glenn@nasa.gov"
+      event.alarm do
+        description "Segment 51"
+      end
+    end
+  end
+
+As the example shows, the two styles can be mixed, the inner block which builds the alarm uses the first style.
+  
+The blocks are evaluated in the context of an object which builds the calendar or calendar component. method names
+starting with add_ or remove_ are sent to the component, method names which correspond to a property value setter of
+the object being built will cause that setter to be sent to the component with the provided value.
+
+A method corresponding to the name of one of the components sub component will create the sub component and 
+evaluate the block in the context of the new subcomponent.
+
+=== Times, Time zones, and Floating Times
+
+RFC2445 describes three different kinds of DATE-TIME values with respect to time zones:
+
+  1. date-times with a local time. These have no actual time zone, instead they are to be interpreted in the local time zone of the viewer.  These floating times are used for things like the New Years celebration which is observed at local midnight whether you happen to be in Paris, London, or New York.
+
+  2. date-times with UTC time.  An application would either display these with an indication of the time zone, or convert them to the viewer's time zone, perhaps depending on user settings.
+
+  3. date-times with a specified time zone.
+
+RiCal can be given ruby Time, DateTime, or Date objects for the value of properties requiring an 
+iCalendar DATE-TIME value. It can also be given a two element array where the first element is a Time or DateTime,
+and the second is a string representation of the time zone identifier.
+
+Note that a date only DATE-TIME value has no time zone by definition, effectively such values float and describe
+a date as viewed by the user in his/her local time zone.
+
+When a Ruby Time or DateTime instance is used to set properties with with a DATE-TIME value, it needs to determine
+which of the three types it represents.  RiCal is designed to make use of the TimeWithZone support which has been
+part of the ActiveSupport component of Ruby on Rails since Rails 2.2. However it's been carefully designed not
+to require Rails or ActiveSupport, but to dynamically detect the presence of the TimeWithZone support.
+
+When the value of a DATE-TIME property is set to a value, the following processing occurs:
+
+* If the object responds to both the :acts_as_time, and :timezone methods then the result of the timezone method (assumed to be an instance of TZInfoTimezone) is used as a specific local time zone.
+
+* If not then the default time zone id is used.  The normal default timezone id is "UTC". You can set the default by calling ::RiCal::PropertyValue::DateTime.default_tzid = timezone_identifier, where timezone_identifier isa string, or nil.  If you set the default tzid to 'none' or :none, then Times or DateTimes without timezones will be treated as floating times.
+
+Note it is likely that in a future version of RiCal that the default timezone will be set on a Calendar by Calendar
+basis rather than on the DateTime property class.
+
+Also note that time zone identifiers are not standardized by RFC 2445. For an RiCal originated calendar
+time zone identifiers recognized by the TZInfo gem, or the TZInfo implementation provided by ActiveSupport as the case
+may be may be used.  The valid time zone identifiers for a non-RiCal generated calendar imported into RiCalendar
+are determined by the VTIMEZONE compoents within the imported calendar.
+
+If you use a timezone identifer within a calendar which is not defined within the calendar it will detected at the time
+you try to convert a timezone. In this case an InvalidTimezoneIdentifier error will be raised by the conversion method.
+
+To explicitly set a floating time you can use the method #with_floating_timezone on Time or DateTime instances as in
+
+   event.dtstart = Time.parse("1/1/2010 00:00:00").with_floating_timezone
+
+=== Parsing
+
+RiCal can parse icalendar data from either a string or a Ruby io object.
+
+The data may consist of one or more icalendar calendars, or one or more icalendar components (e.g. one or more 
+VEVENT, or VTODO objects.)
+
+In either case the result will be an array of components.
+==== From a string
+	RiCal.parse_string <<ENDCAL
+	BEGIN:VCALENDAR
+	X-WR-TIMEZONE:America/New_York
+	PRODID:-//Apple Inc.//iCal 3.0//EN
+	CALSCALE:GREGORIAN
+	X-WR-CALNAME:test
+	VERSION:2.0
+	X-WR-RELCALID:1884C7F8-BC8E-457F-94AC-297871967D5E
+	X-APPLE-CALENDAR-COLOR:#2CA10B
+	BEGIN:VTIMEZONE
+	TZID:US/Eastern
+	BEGIN:DAYLIGHT
+	TZOFFSETFROM:-0500
+	TZOFFSETTO:-0400
+	DTSTART:20070311T020000
+	RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
+	TZNAME:EDT
+	END:DAYLIGHT
+	BEGIN:STANDARD
+	TZOFFSETFROM:-0400
+	TZOFFSETTO:-0500
+	DTSTART:20071104T020000
+	RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
+	TZNAME:EST
+	END:STANDARD
+	END:VTIMEZONE
+	BEGIN:VEVENT
+	SEQUENCE:5
+	TRANSP:OPAQUE
+	UID:00481E53-9258-4EA7-9F8D-947D3041A3F2
+	DTSTART;TZID=US/Eastern:20090224T090000
+	DTSTAMP:20090225T000908Z
+	SUMMARY:Test Event
+	CREATED:20090225T000839Z
+	DTEND;TZID=US/Eastern:20090224T100000
+	RRULE:FREQ=DAILY;INTERVAL=1;UNTIL=20090228T045959Z
+	END:VEVENT
+	END:VCALENDAR
+	ENDCAL
+
+<b>Beware of the initial whitespace in the above example which is for rdoc formatting.</b> The parser does not strip initial whitespace from lines in the file and will fail.
+
+As already stated the string argument may be a full icalendar format calendar, or just one or more subcomponents, e.g.
+
+RiCal.parse_string("BEGIN:VEVENT\nDTSTART;TZID=US/Eastern:20090224T090000\nSUMMARY:Test Event\nDTEND;TZID=US/Eastern:20090224T100000\nRRULE:FREQ=DAILY;INTERVAL=1;UNTIL=20090228T045959Z\nEND:VEVENT")
+
+==== From an Io
+	File.open("path/to/file", "r") do |file|
+	    components = RiCal.parse(file)
+	end
+
+=== Occurrence Enumeration
+
+Event, Journal, and Todo components can have recurrences which are defined following the RFC 2445 specification.
+A component with recurrences can enumerate those occurrences.
+
+These components have common methods for enumeration which are defined in the RiCal::OccurrenceEnumerator module.
+
+==== Obtaining an array of occurrences
+
+To get an array of occurrences, Use the RiCal::OccurrenceEnumerator#occurrences method:
+
+	event.occurrences
+
+This method may fail with an argument error, if the component has an unbounded recurrence definition. This happens
+when one or more of its RRULES don't have a COUNT, or UNTIL part.  This may be tested by using the RiCal::OccurrenceEnumerator#bounded? method.
+
+In the case of unbounded components, you must either use the :count, or :before options of the RiCal::OccurrenceEnumerator#occurrences method:
+
+	event.occurrences(:count => 10)
+
+or
+
+  event.occurrences(:before => Date.today >> 1)
+
+Alternately, you can use the RiCal::OccurrenceEnumerator#each method,
+or another Enumerable method (RiCal::OccurrenceEnumerator includes Enumerable), and terminate when you wish by breaking out of the block.
+
+	event.each do |event|
+	   break if some_termination_condition
+	   #....
+	end
+
+== REQUIREMENTS:
+
+* RiCal requires that an implementation of TZInfo::Timezone. This requirement may be satisfied by either the TzInfo gem,
+or by a recent(>= 2.2) version of the ActiveSupport gem which is part of Ruby on Rails.
+
+== INSTALL:
+
+=== From RubyForge
+
+    sudo gem install ri_cal
+    
+=== From github
+
+    #TODO: publish to github
+
+==== As a Gem
+
+    #TODO: add the gem source info for github
+    sudo gem install ????? --source http://github.com/????
+   
+==== From source
+
+    1. cd to a directory in which you want to install ri_cal as a subdirectory
+    2. git clone http://github.com/rubyredrick/ri_cal  your_install_subdirectory
+    3. cd your_install_directory
+    4. rake spec
+    5. rake install_gem
+
+
+
+== LICENSE:
+
+(The MIT License)
+
+Copyright (c) 2009 Richard J. DeNatale
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/Rakefile

@@ -0,0 +1,31 @@
+#- ©2009 Rick DeNatale
+#- All rights reserved. Refer to the file README.txt for the license
+#
+%w[rubygems rake rake/clean fileutils newgem rubigen].each { |f| require f }
+require File.dirname(__FILE__) + '/lib/ri_cal'
+
+# Generate all the Rake tasks
+# Run 'rake -T' to see list of generated tasks (from gem root directory)
+$hoe = Hoe.new('ri_cal', RiCal::VERSION) do |p|
+  p.developer('author=Rick DeNatale', 'rick.denatale@gmail.com')
+  p.changes              = p.paragraphs_of("History.txt", 0..1).join("\n\n")
+  # p.post_install_message = 'PostInstall.txt' # TODO remove if post-install message not required
+  p.rubyforge_name       = 'rical'
+  # p.extra_deps         = [
+  #   ['tzinfo','>= 2.0.2'],
+  # ]
+  p.extra_dev_deps = [
+    ['newgem', ">= #{::Newgem::VERSION}"]
+  ]
+
+  p.clean_globs |= %w[**/.DS_Store tmp *.log]
+  path = (p.rubyforge_name == p.name) ? p.rubyforge_name : "\#{p.rubyforge_name}/\#{p.name}"
+  p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name}\/?/,''), 'rdoc')
+  p.rsync_args = '-av --delete --ignore-errors'
+end
+
+require 'newgem/tasks' # load /tasks/*.rake
+Dir['tasks/**/*.rake'].each { |t| load t }
+
+# TODO - want other tests/tasks run by default? Add them to the list
+task :default => [:spec]

data/bin/ri_cal

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby
+
+require File.expand_path(
+    File.join(File.dirname(__FILE__), %w[.. lib rfc2445]))
+
+# Put your code here
+
+# EOF

data/component_attributes/alarm.yml

@@ -0,0 +1,10 @@
+- action
+- description
+- trigger
+- duration
+- repeat
+- summary
+- attendee:
+    multi: *
+- attach:
+    multi: *

data/component_attributes/calendar.yml

@@ -0,0 +1,4 @@
+- calscale
+- method
+- prodid
+- version

data/component_attributes/component_property_defs.yml

@@ -0,0 +1,180 @@
+calscale:
+    purpose: This property defines the calendar scale used for the calendar information specified in the calendar object.
+    constant_value: GREGORIAN
+    rfc_ref: "4.7.1 p 73"
+method:
+    purpose: This property defines the iCalendar object method associated with the calendar object
+    ruby_name: icalendar_method
+    rfc_ref: "4.7.2 p 74-75"
+prodid:
+    purpose: This property specifies the identifier for the product that created the iCalendar object.
+    required: true
+    default_value: '-//com.denhaven2/NONSGML ri_cal gem//EN'
+    rfc_ref: '4.7.3 pp 75-76'    
+version:
+    purpose: This property specifies the identifier corresponding to thehighest version number or the minimum and maximum range of the iCalendar specification that is required in order to interpret the iCalendar object.
+    constant_value: '2.0'
+    rfc_ref: '4.7.4 pp 76-77'    
+attach:
+    purpose: The property provides the capability to associate a document object with a calendar component.
+    type: Uri
+    rfc_ref: '4.8.1.1 pp 77-78'
+categories:
+    purpose: This property defines the categories for a calendar component.
+    type: Array
+    array_type: Text
+    rfc_ref: '4.8.1.2 pp 78-79'
+class:
+    ruby_name: security_class
+    purpose: This property defines the access classification for a calendar component.
+    rfc_ref: '4.8.1.3 pp 79-80'   
+comment:
+    purpose: This property specifies non-processing information intended to provide a comment to the calendar user.
+    rfc_ref: '4.8.1.4 pp 80-81'
+description:
+    purpose: This property provides a more complete description of the calendar component, than that provided by the "SUMMARY" property.
+    rfc_ref: '4.8.1.5 pp 81-82'
+geo:
+    purpose: This property specifies information related to the global position for the activity specified by a calendar component.
+    type: Geo
+    rfc_ref: '4.8.1.6 pp 82-83'
+location:
+    purpose: This property defines the intended venue for the activity defined by a calendar component.
+    rfc_ref: '4.8.1.7 pp 84'
+percent-complete:
+    purpose: This property is used by an assignee or delegatee of a to-do to convey the percent completion of a to-do to the Organizer.
+    type: Integer
+    rfc_ref: '4.8.1.8 pp 85'
+priority:
+    type: Integer
+    purpose: This property defines the relative priority for a calendar component.
+    rfc_ref: '4.8.1.9 pp 85-87'
+resources:
+    purpose: This property defines the equipment or resources anticipated for an activity specified by a calendar entity.
+    type: 'Array'
+    rfc_ref: '4.8.1.10 pp 87-88'
+status:
+    purpose: This property defines a short summary or subject for the calendar component.
+    rfc_ref: '4.8.1.11 pp 80-89'
+summary:
+    purpose: This property defines a short summary or subject for the calendar component.
+    rfc_ref: '4.8.1.12 pp 89-90'
+completed:
+    purpose: This property specifies the date and time that a to-do was actually completed.
+    type: DateTime
+    type_constraint: must_be_utc
+    rfc_ref: '4.8.2.1 pp 90-91'
+dtend:
+    purpose: This property specifies the date and time that a calendar component ends.
+    type: date_time_or_date
+    rfc_ref: '4.8.2.2 pp 91-92'
+due:
+    purpose: This property defines the date and time that a to-do is expected to be completed.
+    type: date_time_or_date
+    rfc_ref: '4.8.2.3 pp 92-93'
+dtstart: 
+    purpose: This property specifies when the calendar component begins.
+    type: date_time_or_date
+    rfc_ref: '4.8.2.4 pp 93-94'
+duration:
+    purpose: This property specifies a positive duration of time.
+    type: Duration
+    rfc_ref: '4.8.2.5 pp 94-95'
+freebusy:
+    purpose: This property defines one or more free or busy time intervals.
+    type: Period
+    type_constraint: must_be_utc
+    rfc_ref: '4.8.2.6 pp 95-96'
+transp:
+    purpose: This property defines whether an event is transparent or not to busy time searches.
+    rfc_ref: '4.8.2.7 pp 96-97'
+tzid:
+    purpose: This property specifies the text value that uniquely indentifies the "VTIMEZONE" calendar component.
+    rfc_ref: '4.8.3.1 pp 97-98'
+tzname:
+    purpose: This property specifies the customary designation for a time zone description.
+    rfc_ref: '4.8.3.2 p 99'
+tzoffsetfrom:
+    purpose: This property specifies the offset which is in use prior to this time zone observance
+    type: UtcOffset
+    rfc_ref: '4.8.3.3 pp 99-100'
+tzoffsetto:
+    purpose: This property specifies the offset which is in use in this time zone observance
+    type: UtcOffset
+    rfc_ref: '4.8.3.4 pp 100-101'
+tzurl:
+    purpose: The TZURL provies a means for a VTIMEZONE component to point to a network location that can be used to retrieve an up-to_date version of itself.
+    type: Uri
+    rfc_ref: '4.8.3.4 p 101'    
+attendee:
+    purpose: The property defines an 'Attendee' within a calendar component.
+    type: CalAddress
+    rfc_ref: '4.8.4.1 pp 102-104'   
+contact:
+    purpose: The property is used to represent contact information oralternately a reference to contact information associated with the calendar component.
+    rfc_ref: '4.8.4.2 pp 104-106'   
+organizer:
+    purpose: The property defines the organizer for a calendar component.
+    type: CalAddress
+    rfc_ref: '4.8.4.3 pp 106-107'   
+recurrence-id:
+    purpose: This property is used in conjunction with the "UID" and "SEQUENCE" property to identify a specific instance of a recurring "VEVENT", "VTODO" or "VJOURNAL" calendar component. The property value is the effective value of the "DTSTART" property of the recurrence instance.
+    type: date_time_or_date
+    rfc_ref: '4.8.4.4 pp 107-109'   
+related-to:
+    purpose: The property is used to represent a relationship or reference between one calendar component and another.
+    rfc_ref: '4.8.4.5 pp 109-110'   
+url:
+    purpose: This property defines a Uniform Resource Locator (URL) associated with the iCalendar object.
+    type: Uri
+    rfc_ref: '4.8.4.6 pp 110-111'   
+uid:
+    purpose: This property defines the persistent, globally unique identifier for the calendar component.
+    rfc_ref: '4.8.4.7 pp 111-112'   
+exdate:
+    purpose: This property defines the list of date/time exceptions for a recurring calendar component.
+    type: 'OccurrenceList'
+    rfc_ref: '4.8.5.1 pp 112-114'   
+exrule:
+    purpose: This property defines a rule or repeating pattern for an exception to a recurrence set.
+    type: 'RecurrenceRule'
+    rfc_ref: '4.8.5.2 pp 114-125'   
+rdate:
+    purpose: This property defines the list of date/times for a recurring calendar component.
+    type: 'OccurrenceList'
+    rfc_ref: '4.8.5.3 pp 115-117'   
+rrule:
+    purpose: This property defines a rule or repeating pattern for recurring events, to-dos, or time zone definitions.
+    type: 'RecurrenceRule'
+    rfc_ref: '4.8.5.4 pp 117-125'
+action:
+    purpose: This property defines the action to be invoked when an alarm is triggered
+    rfc_ref: '4.8.6.1 p 126'
+repeat:
+    purpose: This property defines the number of times the alarm should be repeated, after the initial trigger.
+    type: Integer
+    rfc_ref: '4.8.6.2 p 126-127'
+trigger:
+    purpose: This property specifies when an alarm will trigger.
+    type: duration_or_utc_date_time
+    rfc_ref: '4.8.6.3 p 127-129'
+created:
+    purpose: This property specifies the date and time that the calendar information was created by teh calendar user agent in the calendar store.
+    type: DateTime
+    rfc_ref: '4.8.7.1 pp 129-130'   
+dtstamp:
+    purpose: This property indicates the date/time that the instance of the iCalendar object was created.
+    type: DateTime
+    auto_set: to_ical
+    rfc_ref: '4.8.7.2 pp 130-131'   
+last-modified:
+    purpose: This property specifies the date and time that the information associated with the calendar component was last revised in teh calendar store.
+    type: DateTime
+    rfc_ref: '4.8.7.3 p 131'   
+sequence:
+    purpose: This property defines the revision sequence number of the calendar component within a sequence of revisions.
+    type: Integer
+    auto_set: sequence_modifiers
+    rfc_ref: '4.8.7.4 pp 131-133'   
+request-status:
+    rfc_ref: '4.8.8.2 pp 134-136'   

data/component_attributes/event.yml

@@ -0,0 +1,45 @@
+- class
+- created
+- description
+- dtstart 
+- geo
+- last-modified
+- location
+- organizer
+- priority
+- dtstamp
+- sequence
+- status
+- summary
+- transp
+- uid
+- url
+- recurrence-id
+- dtend:
+    conflicts_with: duration
+- duration:
+    conflicts_with: dtend
+- attach:
+    multi: *
+- attendee:
+    multi: *
+- categories:
+    multi: *
+- comment:
+    multi: *
+- contact:
+    multi: *
+- exdate:
+    multi: *
+- rdate:
+    multi: *
+- exrule:
+    multi: *
+- request-status:
+    multi: *
+- related-to:
+    multi: *
+- resources:
+    multi: *
+- rrule:
+    multi: *