![]() ![]() HCalendar is a simple, open, distributed calendaring and events format, using a 1:1 representation of standard iCalendar ( RFC2445) VEVENT properties and values in semantic HTML or XHTML. HCalendar hCalendar seems the best method I've hit so far for marking up iCalendar entries in HTML, including date/times. It is a lightweight protocol whose primary design goal is to be as simple as possible to implement, focusing more on real world issues with open source applications than on an extremely extensive command set. GroupDAV is a computer protocol used to connect Open Source groupware clients with Open Source groupware servers. Handles far more than the iCalendar data set. I.e., one ECM system could be using iCalendar and another a different specification for tasks, calendar entries, and journal entries, but the two systems could still interoperate if using CMIS as the brokering layer. CMIS treats data as objects and brokers the exchange of the objects between systems. Content Management Interoperability Services Content Management Interoperability Services, Ī recent standard from OASIS that has an incredible amount of adoption already, designed originally for interoperability between Enterprise Content Management (ECM) systems. Marcus Kuhn, A Summary of International Date and time notation. The protocol also supports non-personal calendars, such as calendars for sites or organizations. With this functionality, a user may synchronize his or her own calendar to a CalDAV server, and share it among multiple devices or with other users. Parsing the iCalendar items is necessary, because the server has to support a number of calendaring-specific operations such as doing free-busy time reports and expansion of recurring events. The calendar resources must use iCalendar format, which allows the server to understand and process the data. Therefore the specification requires that CalDAV servers must support "WebDAV Access Control Protocol" ( RFC 3744). The resources and collections can be accessed by one or more users, using standard HTTP and DAV semantics to detect conflicting changes, or to provide locking.įor access control the concept of ACLs are used, so each operation (view, edit, delete etc.) can be denied or granted per user. The architecture of CalDAV (partially inherited from the underlying specifications) organizes the data (events, tasks, free-busy info, notes) in directories (collections), where multiple items (resources) reside. It is developed as an open standard to foster interoperability between software from different implementers. CalDAV is designed for implementation by any collaborative software, client or server, that needs to maintain, access or share collections of events. ![]() In March 2007, the CalDAV specification was described in the RFC 4791. Content Management Interoperability Servicesĭate/Time-Related Specifications Specs that share ISO 8601 formatting in common.ĬalDAV RFC 4791 The CalDAV specification was first published in 2003 as an Internet Draft submitted to the Internet Engineering Task Force ( IETF).See also in the Help file scriptable program commands that can also handle dates and times under the Date Property Commands and Custom Property Commands topics. This branch includes resources for scripts that handle dates and times.
0 Comments
Leave a Reply. |