How would a Headless Calendar Server be built?

Calendarsnack.com and 31events.com are owned by TechVader, A Colorado S Corporation. 1
How Google Calendar Client behaves when
communicating with another
Google Calendar Client
Draft for review
December 5th
, 2021
Greg Hanchin
Arnie Mckinnis
Jonn Jeanneret

Calendarsnack supports 6 Fields for UPDATE from the Outlook or Google Calendar Client.
Any Calendar Invite created with the CalendarSnack service can make the changes to that
particular EVENT and then “SAVE” those changes the Calendar Client interface.
Once the “SAVE” has been completed, we send those changes to the Calendarsnack API for the
processing the UPDATED fields.
If the Calendar Invite has RSVP’s attached to it, we will send out the corresponding UPDATES to
those that have RSVP’D as a YES or MAYBE Status.
The UID is used for the “KEY” to lookup the record, make the changes in the Calendarsnack
workflow and send out the UPDATE Calendar Invitation Changes to the YES, or MAYBE
INVITEE’s of the EVENT.
OUTLOOK GOOGLE
Subject Add Title
Location Add Location
Duration Duration
Starts Starts
Ends Ends
Description Add Description

Proposed DRAFT of CalendarSnack UPDATE Support – V1.1 – NOV 21
1 2 3 4 5
Outlook
Event Fields
UPDATE
SUPPORT
ADVANCE
SEQUENCE
BEHAVIOR in Clients RSVP Status if Already Y or M
Subject Y N Change the Text Keep Current RSVP Status
Location Y N Change the Location Keep Current RSVP Status
Duration Y Y Change the Time Reset to 0, Request new RSVP
Starts Y Y Change the Start Reset to 0, Request new RSVP
Ends Y Y Change the End Reset to 0, Request new RSVP
Description Y N
Change the Add
Description
Keep Current RSVP Status
1 2 3 4 5
Google
Event Fields
UPDATE
SUPPORT
ADVANCE
SEQUENCE
BEHAVIOR in Clients RSVP Status if Already Y or M
Add Title Y N Change the Text Keep Current RSVP Status
Date Y Y Change the Date Reset to 0, Request new RSVP
Time Y Y Change the Time Reset to 0, Request new RSVP
Google
Meet
Y N Add / Subtrack Keep Current RSVP Status
Create
Meeting
Notes
N N / A N/A N/A
Add
Location
Y N Change the Text Keep Current RSVP Status
Notification N N / A N/A N/A
Add
Description
Y N Change the Text Keep Current RSVP Status

How Google Behaves. November, 2021.
A view of a Standard Create and Send of a Calendar Invite between Google Calendar.
Or what we refer to as a GMAIL to GMAIL. Screens 1, 2 and 3.
Below is SEND 1. Sequence is 0 in the ICAL.
As seen in the next 6 SENDS with CANCEL being 7 , Google takes advantage of their ability to
manipulate their Calendar Client Interface for “UPDATES” by INSERTING a Green Bar or Green
Text into the Google Calendar Client interface to give the “INVITEE” a Heads-up on the
CHANGES.
What we attempt to do over the 6 SENDS is show the Organizer SIDE or SEND of the Calendar
Client and the RECEIPTIANT SIDE of the Calendar Invite in the Calendar CLIENT Interfaces.

SEND 1 – ICAL DETAILS from ZACKS CLIENT (INVITEE)
Zacks ICAL 1
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20211202T190000Z
DTEND:20211202T200000Z
DTSTAMP:20211124T232922Z
ORGANIZER;CN=greg
Hanchin:mailto:greg@techvader.com
UID:1omp0a57a2f9r14ss03et2778u@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-
PARTICIPANT;PARTSTAT=NEEDS-
ACTION;RSVP=TRUE;CN=zack@techvader.com;X-NUM-
GUESTS=0:mailto:zack@techvader.com
PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=greg Hanchin;X-NUM-
GUESTS=0:mailto:greg@techvader.com
X-MICROSOFT-CDO-OWNERAPPTID:-1499963828
CREATED:20211124T232921Z
DESCRIPTION:Hello, Thanks for liking the
CalenderSnack.nnPlease Save this Date by Accepting the
Invite.nnGregnn-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-nDo
not edit this s ection of the description.nnThis event has
a video call.nJoin: https://m eet.google.com/gsc-pvcr-
sjzn(US) +1 859-545-2041 PIN: 656704971#nnView y
eet.google.com/gsc-pvcr-sjzn(US) +1 859-545-2041 PIN:
656704971#nnView y eet.google.com/gsc-pvcr-sjzn(US)
+1 859-545-2041 PIN: 656704971#nnView y our event at
https://calendar.google.com/calendar/event?action=VIE
W&eid=MW9
tcDBhNTdhMmY5cjE0c3MwM2V0Mjc3OHUgemFja0B0Z
WNodmFkZXIuY29t&tok=MTgjZ3JlZ0B0Z
WNodmFkZXIuY29tYjJlZTIwYjNhYWU4MTM2NTI1ZWIxYzI
3YTE3MDdlMzU2OWYyM2RjOA&ctz=A
WNodmFkZXIuY29tYjJlZTIwYjNhYWU4MTM2NTI1ZWIxYzI
3YTE3MDdlMzU2OWYyM2RjOA&ctz=A
merica%2FDenver&hl=en&es=1.n-
::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20211124T232921Z
LOCATION:We will update you on Details for Zoom Logins
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Saving the Date Request - CalendarSnack
Event
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

In Screen Shot #4 & 5 for SEND #2 - Greg the Organizer removes the GOOGLE MEET option and
does not change any of the other EVENT FIELDS, and Clicks the SAVE BUTTON, which PROMPTS
the Interface into the DARK Box mode and INSERTS the PROMPT BOX with the “Would you like
to SEND update emails to existing Google Calendar GUESTS? Greg types into that TEXT Box a
message to notify the user that he has decided to use a ZOOM Meeting request instead of
GOGGLE MEET.

Zack the Invitee, receives the “UPDATED Invitation with note” in his EMAIL with UPDATED
details as seen below in Screen shot 6 of the Send View #2. Sequence is still 0 in the ICAL.
In this SEND UPDATE message, Zack’s calendar client is decorated GREEN BAR in the Google
Client. NOTE – The RSVP is still LOADED as a YES.
The Data came from Client Screen shot #5 in the previous page

ZACKS ICAL 2 from SEND #2 (INVITEE)
Zacks ICAL 2
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20211202T190000Z
DTEND:20211202T200000Z
DTSTAMP:20211125T134627Z
ORGANIZER;CN=greg Hanchin:mailto:greg@techvader.com
PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=zack@techvader.com;X-
NUM-GUESTS=0:mailto:zack@techvader.com
PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE;CN=greg Hanchin;X-NUM-
CREATED:20211124T232921Z
DESCRIPTION:Hello, Thanks for liking the CalenderSnack.nnPlease Save this
Date by Accepting the Invite.nnGregnn-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-nDo not edit this section of
the description.nnView your event at https://calendar.google.co
m/calendar/event?action=VIEW&eid=MW9tcDBhNTdhMmY5cjE0c3MwM2V0Mjc
3OHUgemFja0B0ZWNodmFkZXIuY29t&tok=MTgjZ3JlZ0B0ZWNodmFkZXIuY29tYjJl
ZTIwYjNhYWU4MTM2NTI1
ZWIxYzI3YTE3MDdlMzU2OWYyM2RjOA&ctz=America%2FDenver&hl=en&es=1.
n-::~:~::~:
~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~: :-
LOCATION:We will update you on Details for Zoom Logins
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Saving the Date Request - CalendarSnack Event
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

In SEND #3, Screen Shot 7 - Greg the Organizer UPDATES the Location FIELD with a ZOOM URL
and the INSERTS ZOOM into the Description FIELD. Greg does not use the PROMPT TEXT BOX
to send a NOTE this time.
In Screen Shot # 8, Zack the invitee receives SEND #3. The “UPDATED INVITATION:” Notice
stuffed into the Header of the Message as seen in Screen Shot #8. Sequence is still 0 in the
ICAL.

In addition, there is the Green shaded box with the “The Event has been changed” and GREEN
TEXT “Changed:”.

Zack ICAL 3 from SEND #3
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20211202T190000Z
DTEND:20211202T200000Z
DTSTAMP:20211125T144344Z
PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=zack@techvader.com;X-NUM-
PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=greg Hanchin;X-NUM-
CREATED:20211124T232921Z
DESCRIPTION:Hello Attendees! - Updated details of Event with Zoom Data -n nGreg
Hanchin is inviting you to a scheduled Zoom meeting.nnTopic: Greg Hanchin's Personal
Meeting RoomnnJoin Zoom Meetingnhttps://us02web.zoom.u
s/j/3782046740nnMeeting ID: 378 204 6740nOne tap mobilen+13462487799,
,3782046740# US (Houston)n+16699006833,,3782046740# US (San Jose)nnDia l by
your locationn +1 346 248 7799 US (Houston)n +1 669 90 0 6833 US (San Jose)n
+1 253 215 8782 US (Tacoma)n +1 312 6 26 6799 US (Chicago)n +1 646 558 8656
US (New York)n +1 301 715 8592 US (Washington DC)nMeeting ID: 378 204
6740nFind your local num ber: https://us02web.zoom.us/u/kdQwELuSyjnnJoin by
SIPn3782046740@zoomcr ber: https://us02web.zoom.us/u/kdQwELuSyjnnJoin by
SIPn3782046740@zoomcr ber: https://us02web.zoom.us/u/kdQwELuSyjnnJoin by
SIPn3782046740@zoomcr c.comnnJoin by H.323n162.255.37.11 (US
West)n162.255.36.11 (US East)n115.114.131.7 (India Mumbai)n115.114.115.7 (India
Hyderabad)n213.19.144.11 0 (Amsterdam Netherlands)n213.244.140.110
(Germany)n103.122.166.55 (Austr alia Sydney)n103.122.167.55 (Australia
Melbourne)n149.137.40.110 (Singapo re)n64.211.144.160 (Brazil)n149.137.68.253
(Mexico)n69.174.57.160 (Canad a Toronto)n65.39.152.160 (Canada
Vancouver)n207.226.132.110 (Japan Tokyo) n149.137.24.110 (Japan Osaka)nMeeting
ID: 378 204 6740nn-::~:~::~:~:~:~ n149.137.24.110 (Japan Osaka)nMeeting ID: 378
204 6740nn-::~:~::~:~:~:~n149.137.24.110 (Japan Osaka)nMeeting ID: 378 204
6740nn-::~:~::~:~:~:~
:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-nDo not edit this
LOCATION:https://us02web.zoom.us/j/3782046740
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Saving the Date Request - CalendarSnack Event
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

In Screen Shot #9, SEND #4. Greg changed the “Add Title” EVENT Field and SAVED did not Add
anything into the Prompted Text Box option.

In Screen Shot #10 Zack receives SEND #4 – The Calendar Client show UPDATES decorated in
GREEN. This was just an “ADD TITLE” – UPDATE with the TEXT in the Event Field. Sequence is
still 0 in the ICAL.

Zack’s ICAL 4 from SEND#4
Zacks ICAL 4
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20211202T190000Z
DTEND:20211202T200000Z
DTSTAMP:20211125T163214Z
PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=zack@techvader.com;X-
NUM-GUESTS=0:mailto:zack@techvader.com
CREATED:20211124T232921Z
DESCRIPTION:Hello Attendees! - Updated details of Event with Zoom Data -n
nGreg Hanchin is inviting you to a scheduled Zoom meeting.nnTopic: Greg
Hanchin's Personal Meeting RoomnnJoin Zoom
Meetingnhttps://us02web.zoom.u s/j/3782046740nnMeeting ID: 378 204
6740nOne tap mobilen+13462487799, ,3782046740# US
(Houston)n+16699006833,,3782046740# US (San Jose)nnDia l by your
locationn +1 346 248 7799 US (Houston)n +1 669 90 0 6833 US (San
Jose)n +1 253 215 8782 US (Tacoma)n +1 312 6 26 6799 US (Chicago)n
+1 646 558 8656 US (New York)n +1 301 715 8592 US (Washington
DC)nMeeting ID: 378 204 6740nFind your local num ber:
https://us02web.zoom.us/u/kdQwELuSyjnnJoin by SIPn3782046740@zoomcr
ber: https://us02web.zoom.us/u/kdQwELuSyjnnJoin by
SIPn3782046740@zoomcr ber:
https://us02web.zoom.us/u/kdQwELuSyjnnJoin by SIPn3782046740@zoomcr
c.comnnJoin by H.323n162.255.37.11 (US West)n162.255.36.11 (US
East)n115.114.131.7 (India Mumbai)n115.114.115.7 (India
Hyderabad)n213.19.144.11 0 (Amsterdam Netherlands)n213.244.140.110
(Germany)n103.122.166.55 (Austr alia Sydney)n103.122.167.55 (Australia
Melbourne)n149.137.40.110 (Singapo re)n64.211.144.160
(Brazil)n149.137.68.253 (Mexico)n69.174.57.160 (Canad a
Toronto)n65.39.152.160 (Canada Vancouver)n207.226.132.110 (Japan Tokyo)
n149.137.24.110 (Japan Osaka)nMeeting ID: 378 204 6740nn-::~:~::~:~:~:~
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Changed Event Header - CalendarSnack Event
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

In #11 Screen Shot – SEND#5, Greg changes the “Add Title” and Changes the TIME of the EVENT
and SENDS. This prompts a Calendar Receipt Request you will see in the Zack’s Client in #12.
Sequence in the ICAL File moves to 1 from 0 for the FIRST Time in SEND #5.

In #12 Screen Shot - Zack receives the UPDATED invite and ACCEPTS the NEW TIME in SEND #5.
Sequence is changed in ICAL to 1. RSVP Receipt is SENT back to Greg.

ZACKS ICAL 5 from SEND#5
Zacks ICAL 5
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20211202T210000Z
DTEND:20211202T220000Z
DTSTAMP:20211125T171236Z
CREATED:20211124T232921Z
DESCRIPTION:Hello Attendees! - Updated details of Event with Zoom Data -
n nGreg Hanchin is inviting you to a scheduled Zoom meeting.nnTopic:
Greg Hanchin's Personal Meeting RoomnnJoin Zoom
Meetingnhttps://us02web.zoom.u s/j/3782046740nnMeeting ID: 378
204 6740nOne tap mobilen+13462487799, ,3782046740# US
(Houston)n+16699006833,,3782046740# US (San Jose)nnDia l by your
locationn +1 346 248 7799 US (Houston)n +1 669 90 0 6833 US
(San Jose)n +1 253 215 8782 US (Tacoma)n +1 312 6 26 6799 US
(Chicago)n +1 646 558 8656 US (New York)n +1 301 715 8592 US
(Washington DC)nMeeting ID: 378 204 6740nFind your local num ber:
https://us02web.zoom.us/u/kdQwELuSyjnnJoin by
SIPn3782046740@zoomcr c.comnnJoin by H.323n162.255.37.11 (US
West)n162.255.36.11 (US East)n115.114.131.7 (India
Mumbai)n115.114.115.7 (India Hyderabad)n213.19.144.11 0
(Amsterdam Netherlands)n213.244.140.110 (Germany)n103.122.166.55
(Austr alia Sydney)n103.122.167.55 (Australia
Melbourne)n149.137.40.110 (Singapo re)n64.211.144.160
(Brazil)n149.137.68.253 (Mexico)n69.174.57.160 (Canad a
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Changed Time Header - CalendarSnack Event
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

In Screen Shot #13 for SEND#6 - Greg UPDATES the Add Title, DATE and the Add Description
EVENT Fields. SEQUENCE in ICAL Files is MOVED to 2 from 1, prompting a Calendar Receipt for
the EVENT – or setting the EVENT back to ZERO.

In #14 Screen Shot of SEND #6 of Zack Client. RSVP is NOT GREEN. Zack ACCEPTS the RSVP’s -
YES. SEND’s a RSVP Notification Receipt back to Greg of YES or “Accepted” is SEEN in Greg the
Organizer Client. SEQUENCE 2 is seen in the ICAL.

ZACK’s ICAL #6 of SEND #6
Zacks ICAL 6
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20211217T210000Z
DTEND:20211217T220000Z
DTSTAMP:20211125T182400Z
PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=greg
Hanchin;X-NUM-GUESTS=0:mailto:greg@techvader.com
CREATED:20211124T232921Z
DESCRIPTION:Hello Attendees! - Updated details of Event with
Zoom Data - Greg Hanchin is inviting you to a scheduled
Zoom meeting. Topic : Greg Hanchin's Personal Meeting
Room Join Zoom Meeting <a href=
"https://us02web.zoom.us/j/3782046740">https://us02web.zoo
m.us/j/3782046740 </a>nn-
::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
:~:~:~:~:~:~::~:~::-nDo not edit this section of the
description.nnView your event at
https://calendar.google.com/calendar/event?action=VIEW&eid=
MW9tcDBhNTdhMmY5cjE0c3MwM2V0Mjc3OHUgemFja0B0ZW
NodmFkZXIuY29t&tok=MTgjZ3JlZ0B0ZWNodmFkZXIuY29tYjJlZTI
wYjNhYWU4MTM2NTI1ZWIxYzI3YTE3MDdlMzU2OWYyM2RjOA
&ctz= America%2FDenver&hl=en&es=1.n-
::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:CalendarSnack Event
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

In Screen Shot #15 and SEND of #6 Greg DELETES the Calendar Invite off of his calendar,
prompting a response box that asks him if he want to send out notifications to the Google
Calendar Guests. He clicks YES. SEQUENCE IS MOVED to #3.

In Screen Shot #16 of SEND #6 in Zack’s Inbox is the CANCELED Notification from Greg the
Organizer.
The “PEACH Colored BAR” notification is “This Event has been canceled and removed from your
calendar”.

ZACK ICAL # 7 – from SEND 7 – The CANCELATION
Zacks ICAL 7
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VEVENT
DTSTART:20211217T210000Z
DTEND:20211217T220000Z
DTSTAMP:20211125T190956Z
ACTION;CN=zack@techvader.com;X-NUM-
PARTICIPANT;PARTSTAT=ACCEPTED;CN=greg
HATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-
PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=gr
eg.hanchin@techdata.com;X-NUM-
CREATED:20211124T232921Z
DESCRIPTION:Hello Attendees! - Updated details of Event with
Zoom Data - Greg Hanchin is inviting you to a
scheduled Zoom meeting. Topic : Greg Hanchin's
Personal Meeting Room Join Zoom Meeting <a
href=
"https://us02web.zoom.us/j/3782046740">https://us02web.z
oom.us/j/3782046740 </a>
SEQUENCE:3
STATUS:CANCELLED
SUMMARY:CalendarSnack Event
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

How would a Headless Calendar Server be built?

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (13)

Ähnlich wie How would a Headless Calendar Server be built?

Ähnlich wie How would a Headless Calendar Server be built? (10)

Mehr von 31events.com

Mehr von 31events.com (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

How would a Headless Calendar Server be built?