[caldeveloper-l] FW: Questions on rfc7265

[Vivek Kamath]

Sending message to mailing list based on Cyrus Daboo’s suggestion.  Can someone help?  Based on what Cyrus said, looks like there is a revised json specification in works.  Can someone please let us know how we should proceed?

Thanks much in advance,
Vivek

[cid:image001.png at 01D315C3.F1CF3150]<http://www.ultimatesoftware.com/>

Vivek Kamath
Engineering Team Owner
Virtual, San Diego CA
Mobile: (858) 848-0157
www.ultimatesoftware.com | Follow US: LinkedIn<http://www.linkedin.com/company/ultimate-software> | Twitter<https://twitter.com/UltimateHCM> | People First Blog<http://blog.ultimatesoftware.com/>



From: Vivek Kamath <Vivek_Kamath at ultimatesoftware.com>
Date: Tuesday, August 15, 2017 at 9:44 AM
To: "mozilla at kewis.ch" <mozilla at kewis.ch>, "cyrus at daboo.name" <cyrus at daboo.name>, "douglm at rpi.edu" <douglm at rpi.edu>
Subject: Questions on rfc7265

Hi Everyone,

You guys are listed as authors on this RFC (https://tools.ietf.org/html/rfc7265) therefore sending this question.  We are evaluating to use icalendar components in our application and came across this spec that describes json encoding.  The spec has entire json paload encoded as arrays of arrays.  An example from the spec is as follows based on the rules specificed in section 3.3:

["vcalendar",
     [
       ["calscale", {}, "text", "GREGORIAN"],
       ["prodid", {}, "text", "-//Example Inc.//Example Calendar//EN"],
       ["version", {}, "text", "2.0"]
     ],
     [
       ["vevent",
         [
           ["dtstamp", {}, "date-time", "2008-02-05T19:12:24Z"],
           ["dtstart", {}, "date", "2008-10-06"],
           ["summary", {}, "text", "Planning meeting"],
           ["uid", {}, "text", "4088E990AD89CB3DBB484909"]
         ],
         []
       ]
     ]
   ]


Our needs are quite simple.  We don’t need a very generic encoding mechanism like this.  So we were envisioning something like:
{
  "vcalendar": {
     "calscale": "GREGORIAN",
     "prodid": "-//Example Inc.//Example Calendar//EN",
     "version": "2.0",
     "vevent": [
        {
           "dtstamp": "2008-02-05T19:12:24Z",
           "dtstart": "2008-10-06",
           "summary": "Planning meeting",
          "uid": "4088E990AD89CB3DBB484909"
        }
     ]
  }
}

I think this allows us to simplify the code to understand the event objects in our code.  Is it possible to create a simplified version of the spec with assumed data types and default properties?

Thanks much in advance,
Vivek

[cid:image002.png at 01D315C3.F1CF3150]<http://www.ultimatesoftware.com/>

Vivek Kamath
Engineering Team Owner
Virtual, San Diego CA
Mobile: (858) 848-0157
www.ultimatesoftware.com | Follow US: LinkedIn<http://www.linkedin.com/company/ultimate-software> | Twitter<https://twitter.com/UltimateHCM> | People First Blog<http://blog.ultimatesoftware.com/>



This e-mail message and any attachments to it are intended only for the named recipients and may contain legally privileged and/or confidential information. If you are not one of the intended recipients, do not duplicate or forward this e-mail message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.calconnect.org/pipermail/caldeveloper-l-calconnect.org/attachments/20170815/b8e53721/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 19082 bytes
Desc: image001.png
URL: <http://lists.calconnect.org/pipermail/caldeveloper-l-calconnect.org/attachments/20170815/b8e53721/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 19084 bytes
Desc: image002.png
URL: <http://lists.calconnect.org/pipermail/caldeveloper-l-calconnect.org/attachments/20170815/b8e53721/attachment-0003.png>