summaryrefslogtreecommitdiff
path: root/design-data
diff options
context:
space:
mode:
authorAllen Winter <allen.winter@kdab.com>2022-04-28 17:25:20 -0400
committerAllen Winter <allen.winter@kdab.com>2022-04-28 17:25:20 -0400
commite9c1b56aadc077a5316e2009e64863717faf4997 (patch)
tree175156612e6ab4a3380589db6234d176c8ee991c /design-data
parent130a2634f459bc86b5d92d13082ef8d3b807181d (diff)
downloadlibical-git-e9c1b56aadc077a5316e2009e64863717faf4997.tar.gz
design-data/properties.csv - remove dupe entry for "NAME"
There were 2 NAME properties: * CAP Properties","RFC 4324 Section 2.1.2", NAME - used to add locale-specific descs to components. * Properties for iCalendar","RFC 7986 Section 5", NAME - specifies the name of the calendar. Now we have 1 property that can have either context but uses the same enum value (151). RFCs shouldn't use the same identifier string to describe two different contexts.
Diffstat (limited to 'design-data')
-rw-r--r--design-data/properties.csv6
1 files changed, 3 insertions, 3 deletions
diff --git a/design-data/properties.csv b/design-data/properties.csv
index 7217a582..7f019653 100644
--- a/design-data/properties.csv
+++ b/design-data/properties.csv
@@ -80,7 +80,7 @@
"MAX-COMPONENT-SIZE","44","INTEGER","INTEGER"
"MINDATE","49","DATE-TIME","DATE-TIME"
"MULTIPART","50","TEXT","TEXT"
-"NAME","51","TEXT","TEXT"
+"NAME","115","TEXT","TEXT"
"OWNER","53","TEXT","TEXT"
"PERMISSION","55","TEXT","TEXT"
"QUERY","58","QUERY","QUERY"
@@ -142,7 +142,7 @@
"TASK-MODE","114","TASKMODE","TASKMODE"
"#New Properties for iCalendar","RFC 7986 Section 5",
-"NAME","115","TEXT","TEXT"
+#"NAME","115","TEXT","TEXT" (conflicts with NAME from rfc4324#section-2.1.2)
"REFRESH-INTERVAL","116","DURATION","NO"
"SOURCE","117","URI","NO"
"COLOR","118","TEXT","TEXT"
@@ -156,7 +156,7 @@
"PATCH-DELETE","124","TEXT","TEXT"
"PATCH-PARAMETER","125","TEXT","TEXT"
-"#Event Publication Extensions Properies","RFC 9073 Section 6",
+"#Event Publication Extensions Properties","RFC 9073 Section 6",
"LOCATION-TYPE","127","TEXT","TEXT",is_multivalued
"PARTICIPANT-TYPE","128","PARTICIPANTTYPE","PARTICIPANTTYPE"
"RESOURCE-TYPE","129","RESOURCETYPE","RESOURCETYPE"