[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Pre-existing Standards for Calendaring, or for specifying schedule
(from the charter) Standards for Calendaring, or for specifying schedule, and interval include but are not limited to: i. iCalendar, also known as RFC 5545 (http://www.ietf.org/rfc/rfc5545.txt). iCalendar describes the base semantics and vocabulary to be delivered. The committee may choose to limit the functionality included to a subset of that offered by iCalendar. ii. hCalendar is a simple, open, distributed calendaring and events format, based on RFC 2445, (http://microformats.org/wiki/hcalendar) suitable for embedding in HTML or XHTML. There are concerns and incompatibilities surrounding the use of HCalendar, though. See http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat-because-of-accessibility-concerns/ iii. HTML 5.0 defines microdata, including a calendar element. include a calendar component (http://www.w3.org/TR/html5/microdata.html#vevent). The vevent is a fork off an earlier version of iCalendar. Currently, we anticipate that HTML 5.0 will instead reference the iCalendar XML specification. iv. Open Building Information Exchange (oBIX) has worked since May 2008 to solve this problem within an OASIS TC. This work is incomplete. (http://lists.oasis-open.org/archives/obix/) v. The Open Knowledge Initiative (OKI) has developed an Open Service Interface Definition (OSID) for Scheduling. The Scheduling OSID provides a means of associating Agents with specific activities (ScheduleItems). This OSID provides a way for an application to integrate or use an external calendaring system, such as an existing Enterprise calendar system. http://www.mirrorservice.org/sites/download.sourceforge.net/pub/sourceforge/o/ok/okiproject/OSID_Scheduling_rel_2_0.pdf vi. CalDAV is a protocol to access server-based shedules and calendars by means of extensions to the the WEBDAV protocol. CalDAV is also referred to as RFC 4791 (http://www.ietf.org/rfc/rfc4791.txt). vii. Microsoft offers the WS-Exchange functions for calendaring. http://msdn.microsoft.com/en-us/library/aa564001(EXCHG.80).aspx viii. Google calendar defines an XML API for calendar activity with growing use in devices such as Android phones. Interoperating with this API is incorporated into the mission of CalConnect. (http://code.google.com/apis/calendar/data/2.0/developers_guide_protocol.html#CreatingSingle). As well as these schedule and interval, the iCalendar format includes a Geo-position element, which has been limited to a point. Several of the use cases for WS-Calendar would benefit from geo-location. Some would benefit more from a point, and some from region or polygon. This suggests that an additional source of IP for WS-Calendar would be at: ix. The Open Geospatial Consortium (OGC) offers standards for the interchange of geospatial data. The OGC is the preferred source for micro-specifications of geospatial data by WS-Calendar. (http://www.opengeospatial.org/) The committee would reach out to the Consortium for advice as to which geospatial standards to use. "Energy and persistence conquer all things." -- Benjamin Franklin
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]