[CalendarServer-changes] [5030] CalendarServer/trunk/doc/Extensions

[source_changes at macosforge.org]

Revision: 5030
          http://trac.macosforge.org/projects/calendarserver/changeset/5030
Author:   cdaboo at apple.com
Date:     2010-02-03 09:01:02 -0800 (Wed, 03 Feb 2010)
Log Message:
-----------
Reference oops.

Modified Paths:
--------------
    CalendarServer/trunk/doc/Extensions/caldav-privateevents.txt
    CalendarServer/trunk/doc/Extensions/caldav-privateevents.xml

Modified: CalendarServer/trunk/doc/Extensions/caldav-privateevents.txt
===================================================================
--- CalendarServer/trunk/doc/Extensions/caldav-privateevents.txt	2010-02-03 16:55:57 UTC (rev 5029)
+++ CalendarServer/trunk/doc/Extensions/caldav-privateevents.txt	2010-02-03 17:01:02 UTC (rev 5030)
@@ -46,7 +46,7 @@
    7.  Normative References . . . . . . . . . . . . . . . . . . . . . 11
    Appendix A.  Acknowledgments . . . . . . . . . . . . . . . . . . . 12
    Appendix B.  Change History  . . . . . . . . . . . . . . . . . . . 12
-   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
+   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
 
 
 
@@ -60,7 +60,7 @@
 1.  Introduction
 
    Internet calendaring and scheduling standards are defined by
-   iCalendar [RFC5445] and iTIP [RFC5446].  The CalDAV [RFC4791]
+   iCalendar [RFC5545] and iTIP [RFC5546].  The CalDAV [RFC4791]
    standard defines a way to access calendar data stored on a server.
    CalDAV uses WebDAV ACLs [RFC3744] to allow a calendar user to grant
    rights to other users to see the calendar data stored on the server.
@@ -627,11 +627,13 @@
               "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791,
               March 2007.
 
-   [RFC5445]  Watson, M., "Basic Forward Error Correction (FEC)
-              Schemes", RFC 5445, March 2009.
+   [RFC5545]  Desruisseaux, B., "Internet Calendaring and Scheduling
+              Core Object Specification (iCalendar)", RFC 5545,
+              September 2009.
 
-   [RFC5446]  Korhonen, J. and U. Nilsson, "Service Selection for Mobile
-              IPv4", RFC 5446, February 2009.
+   [RFC5546]  Daboo, C., "iCalendar Transport-Independent
+              Interoperability Protocol (iTIP)", RFC 5546,
+              December 2009.
 
 
 Appendix A.  Acknowledgments
@@ -666,8 +668,6 @@
 
 
 
-
-
 Daboo                                                          [Page 12]
 
                    CalDAV Private Calendar Components      February 2010

Modified: CalendarServer/trunk/doc/Extensions/caldav-privateevents.xml
===================================================================
--- CalendarServer/trunk/doc/Extensions/caldav-privateevents.xml	2010-02-03 16:55:57 UTC (rev 5029)
+++ CalendarServer/trunk/doc/Extensions/caldav-privateevents.xml	2010-02-03 17:01:02 UTC (rev 5030)
@@ -3,8 +3,8 @@
 <!ENTITY rfc2119 PUBLIC '' 'bibxml/reference.RFC.2119.xml'>
 <!ENTITY rfc3744 PUBLIC '' 'bibxml/reference.RFC.3744.xml'>
 <!ENTITY rfc4791 PUBLIC '' 'bibxml/reference.RFC.4791.xml'>
-<!ENTITY rfc5445 PUBLIC '' 'bibxml/reference.RFC.5445.xml'>
-<!ENTITY rfc5446 PUBLIC '' 'bibxml/reference.RFC.5446.xml'>
+<!ENTITY rfc5545 PUBLIC '' 'bibxml/reference.RFC.5545.xml'>
+<!ENTITY rfc5546 PUBLIC '' 'bibxml/reference.RFC.5546.xml'>
 <!ENTITY I-D.desruisseaux-caldav-sched PUBLIC '' 'bibxml3/reference.I-D.desruisseaux-caldav-sched.xml'>
 ]> 
 <?rfc toc="yes"?>
@@ -46,7 +46,7 @@
     <middle>
         <section title='Introduction'>
             <t>
-                Internet calendaring and scheduling standards are defined by <xref target="RFC5445">iCalendar</xref> and <xref target="RFC5446">iTIP</xref>. The <xref target="RFC4791">CalDAV</xref> standard defines a way to access calendar data stored on a server. CalDAV uses <xref target="RFC3744">WebDAV ACLs</xref> to allow a calendar user to grant rights to other users to see the calendar data stored on the server. This is an "all or nothing" behavior, i.e. if another user is granted the DAV:read privilege to a calendar component, then that user can read all the calendar data in the calendar resource stored on the server.
+                Internet calendaring and scheduling standards are defined by <xref target="RFC5545">iCalendar</xref> and <xref target="RFC5546">iTIP</xref>. The <xref target="RFC4791">CalDAV</xref> standard defines a way to access calendar data stored on a server. CalDAV uses <xref target="RFC3744">WebDAV ACLs</xref> to allow a calendar user to grant rights to other users to see the calendar data stored on the server. This is an "all or nothing" behavior, i.e. if another user is granted the DAV:read privilege to a calendar component, then that user can read all the calendar data in the calendar resource stored on the server.
             </t>
             <t>
                 It is often the case that a calendar user wants to give "restricted" access to portions of the calendar data. e.g., allow another calendar user to see only the start and end times of an event, but not other information (such as summary, description, location, attendee list etc). There is currently no way to do that with CalDAV.
@@ -531,8 +531,8 @@
             &rfc2119;
             &rfc3744;
             &rfc4791;
-            &rfc5445;
-            &rfc5446;
+            &rfc5545;
+            &rfc5546;
             &I-D.desruisseaux-caldav-sched; 
         </references>
 <!--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20100203/2aa8173e/attachment.html>