FYI.
Please provide feedback on calsify.
Best,
Mario
-------- Messaggio Inoltrato --------
Oggetto: [calsify] JSContact: make "uid" optional
Data: Wed, 23 Apr 2025 13:14:42 +0200
Mittente: Robert Stepanek <[email protected]>
A: [email protected]
Mario and I want to redefine the JSContact Card "uid" property be
optional. The current JSContact spec (RFC 9553) defines it to be mandatory.
We originally defined the "uid" property to be mandatory to be
consistent with JSCalendar, where it is required, too. It turned out
that this choice makes it unnecessarily complicated for people to start
using JSContact in their protocols, such as RDAP. Making it optional
also better aligns JSContact with vCard, where the UID property also is
optional.
Contrary to our proposal for jscontact-profiles recently, using a
JSContact Profile to make "uid" optional is not a good choice. We want
JSContact profiles to be strict subsets of JSContact elements, which
rules out making mandatory properties optional.
Since this change is backwards-incompatible with RFC 9553, we need to
change the major JSContact version at IANA from "1.0" to "2.0". The
JSContact registry policy for major version changes is Standards Action
(RFC 8126), meaning we will write an I-D and present it to this working
group.
Please let us know on this list if you object to this change.
_______________________________________________
calsify mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
