Hi, With a hat...
This looks good. I like this effort to standardize JSContact profiles across using protocols and the simplifications. -andy On 4/15/25 11:23, Mario Loffredo wrote:
FYI, Robert and I have just published a new version of the document about JSContact profiles. Notably, this version allows JSContact profile designers to make the uid property optional. Please review and provide feedback on calsify. Best, Mario -------- Messaggio Inoltrato -------- Oggetto: [calsify] I-D Action: draft-ietf-calext-jscontact-profiles-00.txt Data: Tue, 15 Apr 2025 06:46:53 -0700 Mittente: [email protected] Rispondi-a: [email protected] A: [email protected] CC: [email protected] Internet-Draft draft-ietf-calext-jscontact-profiles-00.txt is now available. It is a work item of the Calendaring Extensions (CALEXT) WG of the IETF. Title: Protocol-Specific Profiles for JSContact Authors: Robert Stepanek Mario Loffredo Name: draft-ietf-calext-jscontact-profiles-00.txt Pages: 9 Dates: 2025-04-15 Abstract: This document defines JSContact profiles, a named subsets of JSContact elements that are supported in context of a contact data exchange protocol or other use case. It aims to facilitate using JSContact in contexts where supporting all of JSContact semantics is not appropriate. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-calext-jscontact-profiles/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-calext-jscontact-profiles-00.html Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ calsify mailing list -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ rpp 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]
