[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] Timestamp Serialization Question
I would suggest breaking the precision field set of normative statements into separate lines rather than a paragraph. Personally, I find multiple normative statements in a paragraph much harder to read.
It may be useful to add one or two examples in here as well.
From: <cti@lists.oasis-open.org> on behalf of John Wunder <jwunder@mitre.org>
Date: Thursday, January 21, 2016 at 8:56 AM To: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: Re: [cti] Timestamp Serialization Question Here’s what I put together for normative text. I’m just throwing this out there…any and all criticisms or (even better) edits are welcome.
Also we have nowhere to put this now. What should we do to get a CTI Common specification document rolling?
John
---
All discrete timestamps (i.e. not time ranges or relative times) in the CTI specifications are made up of two fields:
the timestamp field itself, containing the time, and an optional field that indicates the precision of the timestamp.
The timestamp field MUST be a valid RFC3339-formatted timestamp. As permitted by RFC3339, any number of decimal fields are permitted in the seconds value. The timestamp itself MUST be represented in the UTC timezone and MUST use the 'Z' designation to indicate this. The optional precision field, if present, MUST be one of "year", "month", "day", "hour", "minute", or "second". The default value is "second", so omitting the field is equivalent to explicitly specifying "second". A value of "second" indicates that the value in the timestamp field is precise to the number of digits in the seconds value. A value of “minute”, “hour”, “day”, “month”, or “year” indicates that the timestamp value is precise to that as a floor. When specifying a precision other than "second", the timestamp field MUST contain zeroes for all fields beyond the specified precision. For example, if the precision field is "month", the timestamp field must contain "00" for the day, hour, minute, and second fields and the fields indicate a time of that day. The timestamp precision field is always nested at the same level as the timestamp field. The key name will be [timestamp_field_name]_precision. For example, if the key of the timestamp field is “created_at”, the key of the precision field is “created_at_precision”.
From: <cti@lists.oasis-open.org> on behalf of "Jordan, Bret" <bret.jordan@bluecoat.com>
Date: Wednesday, January 20, 2016 at 5:08 PM To: Jane on Travel for CTI-TC <jg@ctin.us> Cc: "cti@lists.oasis-open.org" <cti@lists.oasis-open.org> Subject: Re: [cti] Timestamp Serialization Question
Good points... I have asked John Wunder to review the text and clean it up. We hope to get some normative text out to this group tomorrow.
Thanks,
Bret
Bret Jordan CISSP
Director of Security Architecture and Standards | Office of the CTO
Blue Coat Systems
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]