| Internet-Draft | Calendar Dev Resources | February 2018 |
| Murchison | Expires 7 August 2018 | [Page] |
This memo lists specifications and resources available to developers of calendaring and scheduling applications.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 7 August 2018.¶
Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document came about via discussions at CalConnect - the Calendaring and Scheduling Consortium. Thanks in particular to Mike Douglass.¶
This memo lists standards and resources available to developers of calendaring and scheduling applications.¶
This list SHOULD NOT be considered exhaustive, but SHOULD be sufficient as a starting point for developers new to calendaring and scheduling.¶
The documents in the following sections define the standards for calendaring and scheduling data formats and protocols.¶
The following documents outline guidelines and best practices for developing interoperable calendar and scheduling applications.¶
There are no security considerations related to this memo.¶
- date:
- type: updated
edition: calext-00
amend:
- description: |
Added Murchison as editor.
Updated HTTP references to RFC7230 and RFC7231.
Updated Prefer header field references to RFC7240.
Added Implementation Status section.
Minor editorial changes.¶