Commit 814ff1fd authored by Thomas Schäfer's avatar Thomas Schäfer

Update affiliation and document move to GitLab

parent a0c6ef1b
......@@ -6,7 +6,7 @@ View the site at https://devguide.calconnect.org
## Background
iCalendar [RFC5545] is a calendaring and scheduling data interchange format designed to promote interoperability between digital calendaring systems. However, calendaring, by its very nature, is complex. Things like recurring events, time zones, multi-party scheduling, and more, all lead to complex scenarios. This complexity is fully exposed in iCalendar, and implementors of digital calendar systems that use it, need to be fully aware of these issues in order to correctly use it.
iCalendar [RFC5545](https://tools.ietf.org/html/rfc5545) is a calendaring and scheduling data interchange format designed to promote interoperability between digital calendaring systems. However, calendaring, by its very nature, is complex. Things like recurring events, time zones, multi-party scheduling, and more, all lead to complex scenarios. This complexity is fully exposed in iCalendar, and implementors of digital calendar systems that use it, need to be fully aware of these issues in order to correctly use it.
Evidence to date has shown that there are a number of key areas that consistently cause problems for implementors. In addition, many implementors are put off by the perceived complexity of iCalendar, instead inventing their own, initially simplistic, calendaring data formats, that eventually fall foul of the same issues iCalendar has already addressed, as more calendaring features are added.
......@@ -47,6 +47,7 @@ We're not developing new protocol elements or APIs, this work is just describing
| October 2017 | improve layout for better reading and navigating |
| November 2017 | adding a section about public available validators for iCal |
| March 2018 | adding layout for FAQ pages |
| January 2020 | move to GitLab and new content |
## DEVGUIDE Mailing List
......@@ -61,6 +62,6 @@ Participation on the DEVGUIDE mailing list will be in accordance with standard C
## Chair
Thomas Schäfer (1&1)
Thomas Schäfer (individual member)
Please contact the Chair for more information or to join this Technical Committee. Participation in this Technical Committee will be in accordance with standard CalConnect practices and procedures.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment