Welcome Chris, thank you for serving!
", "time": "2024-03-18T23:31:24Z"}, {"author": "Rajeev RK", "text": "Good Day All
", "time": "2024-03-18T23:32:24Z"}, {"author": "Francesca Palombini", "text": ":clap::clap::clap:
", "time": "2024-03-18T23:32:25Z"}, {"author": "Chris Lemmons", "text": "Dropping this in text, cause it needs no conversation really. (No hats.) There is real value in allowing implementers to use standard time libraries. Minor differences can result in much more expensive errors when engineers try to reimplement the parsers.
", "time": "2024-03-18T23:53:37Z"}, {"author": "Jay Robertson", "text": "Hi Chris, I would note that the time specification is compatible with ISO 8601 Section 4.3.2, so there should be nothing that prevents implementers from using standard time libraries. The specification simply makes the time input a little more restrictive in the interest in simplicity. I would definitely have the same concern if we were inventing a completely original time format, but I don't think that's what we're doing here. Thanks
", "time": "2024-03-19T00:00:09Z"}, {"author": "Chris Lemmons", "text": "Right. But if you use a standard library, you run the risk of accepting improperly formatted input, right?
", "time": "2024-03-19T00:01:09Z"}, {"author": "Chris Lemmons", "text": "Also, you can't use the standard library to generate the times. Otherwise you might wind up with times like 12:59:60 being generated and not accepted.
", "time": "2024-03-19T00:02:21Z"}, {"author": "Jay Robertson", "text": "That is certainly true, as the time would need to go through an additional layer of validation. The choice is between either doing that, or handling the complexities that we're mentioning. If we as a group feel that handling the complexities is the best approach, we can certainly consider that.
", "time": "2024-03-19T00:03:31Z"}, {"author": "Rajeev RK", "text": "+1 for logging draft adoption
", "time": "2024-03-19T00:04:52Z"}, {"author": "Francesca Palombini", "text": "and of course, as always, please make sure it fits within the charter :) (I know Sanjay said it did, just triple checking)
", "time": "2024-03-19T00:05:31Z"}, {"author": "Sanjay Mishra", "text": "@rajev, it will be great if you could review the document and post your comments and support in the cdni mailing list
", "time": "2024-03-19T00:06:41Z"}, {"author": "Rajeev RK", "text": "@Sanjay Will Do on the ML. Have a reviewed it extensively already, as part of the SVTA authoring process.
", "time": "2024-03-19T00:07:57Z"}, {"author": "Rajeev RK", "text": "So here, Labels behave more like a set of Tag rather than a single identifying label
", "time": "2024-03-19T00:21:14Z"}, {"author": "Rajeev RK", "text": "We really miss having a thumbs-up reaction button in meetecho... (Suggestion to the meetecho team)
", "time": "2024-03-19T00:51:57Z"}, {"author": "Ben Rosenblum", "text": ":+1:
", "time": "2024-03-19T01:00:21Z"}, {"author": "Rajeev RK", "text": ":+1:
", "time": "2024-03-19T01:01:33Z"}, {"author": "Jay Robertson", "text": ":+1:
", "time": "2024-03-19T01:02:17Z"}, {"author": "Rajeev RK", "text": "Lead Reviewer ??
", "time": "2024-03-19T01:05:12Z"}, {"author": "Francesca Palombini", "text": "reviews from as many people as possible are great
", "time": "2024-03-19T01:05:19Z"}, {"author": "Francesca Palombini", "text": "thank you all!
", "time": "2024-03-19T01:06:16Z"}, {"author": "Rajeev RK", "text": "Thanks all
", "time": "2024-03-19T01:06:31Z"}, {"author": "Rajeev RK", "text": "and G'Day to you
", "time": "2024-03-19T01:06:38Z"}, {"author": "Francesca Palombini", "text": "meetecho: we are done :)
", "time": "2024-03-19T01:07:03Z"}, {"author": "Lorenzo Miniero", "text": "Thanks Francesca!
", "time": "2024-03-19T01:07:20Z"}]