oops.

52.md

@@ -35,9 +35,6 @@ The list of tags are as follows:
 * `t` (optional, repeated) hashtag to categorize calendar event
 * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc.
 
-The following tags are deprecated:
-* `name` name of the calendar event. Use only if `title` is not available.
-
 ```json
 {
   "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
@@ -49,6 +46,8 @@ The following tags are deprecated:
     ["d", "<UUID>"],
 
     ["title", "<title of calendar event>"],
+    ["image", "<image url>"],
+    ["banner", "<image url>"],
 
     // Dates
     ["start", "<YYYY-MM-DD>"],
@@ -96,9 +95,6 @@ The list of tags are as follows:
 * `t` (optional, repeated) hashtag to categorize calendar event
 * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc.
 
-The following tags are deprecated:
-* `name` name of the calendar event. Use only if `title` is not available.
-
 ```json
 {
   "id": <32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>,
@@ -110,6 +106,8 @@ The following tags are deprecated:
     ["d", "<UUID>"],
 
     ["title", "<title of calendar event>"],
+    ["image", "<image url>"],
+    ["banner", "<image url>"],
 
     // Timestamps
     ["start", "<Unix timestamp in seconds>"],
@@ -210,13 +208,7 @@ The list of tags are as follows:
 }
 ```
 
-## Unsolved Limitations
+## Recurring Calendar Events
-
-* No private events
-
-## Intentionally Unsupported Scenarios
-
-### Recurring Calendar Events
 
 Recurring calendar events come with a lot of complexity, making it difficult for software and humans to deal with. This complexity includes time zone differences between invitees, daylight savings, leap years, multiple calendar systems, one-off changes in schedule or other metadata, etc.