You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These specs are not yet final and will change before publication. There are undoubtably edge cases that are not yet covered. If you find one, please email [jmap@ietf.org](mailto:jmap@ietf.org) or make a pull request on GitHub if you have a proposed fix.
22
+
These specs are not yet final and may change before publication. There are undoubtably edge cases that are not yet covered. If you find one, please email [jmap@ietf.org](mailto:jmap@ietf.org) or make a pull request on GitHub if you have a proposed fix.
22
23
24
+
*[JMAP Contacts](spec-contacts.html)
23
25
*[JMAP Calendars](spec-calendars.html)
24
26
*[JMAP Sharing](spec-sharing.html)
25
-
*[JMAP Contacts](spec-contacts.html)
26
27
*[JMAP Tasks](spec-tasks.html)
27
-
*[JMAP Quotas](spec-quotas.html)
28
28
29
29
## Data formats
30
30
31
31
JMAP was designed in conjunction with new JSON-based file formats for contacts and calendars, which can also be used standalone or in other protocols.
32
32
33
-
JMAP Calendars uses [JSCalendar (RFC 8984)](https://tools.ietf.org/html/rfc8984) as the data format for events.
33
+
JMAP Contacts uses [JSContact (RFC9553)](https://www.rfc-editor.org/rfc/rfc9553.html) as the data format for contacts.
34
34
35
-
JMAP Contacts will use [JSContact (currently under development)](https://datatracker.ietf.org/doc/draft-ietf-jmap-jscontact/) as the data format for contacts.
35
+
JMAP Calendars uses [JSCalendar (RFC 8984)](https://www.rfc-editor.org/rfc/rfc8984.html) as the data format for events.
0 commit comments