[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Motion to move timestamp, timestamp precision, and custom properties to draft status
Hi everyone,
Thanks to some suggestions by Allan Thompson we have some good language nailed down for timestamp, timestamp precision, and custom properties. Given that, the recent agreement on the working call, and a lack of further comments I’d like to make a motion:
I motion that the STIX SC accept by unanimous consent the timestamp, timestamp precision, and custom properties text contained in the STIX pre-draft specifications and duplicated below, and that the SC allow the STIX editors to move these sections to DRAFT
status. If after a period of 5 business days we don’t hear any substantive (non-editorial) objections we will move it from REVIEW to DRAFT.
Thanks!
John
---
4.8. Timestamp
This section defines the timestamp type. Most discrete timestamps (i.e. not time ranges or relative times) in STIX have a corresponding optional field that indicates the precision of the timestamp, of type timestamp-precision. In cases where the timestamp is metadata about the STIX construct, such as creation and modification times for STIX top-level objects, the timestamp will not have the corresponding precision field. In these cases, the precision is "full". 4.8.1. FormatYYYY-MM-DDTHH:mm:ss.ssssssZ
4.8.2. ExamplesA timestamp known only to a year would look like: { "timestamp": "2016-01-01T00:00:00Z", "timestamp_precision": "year" } A timestamp known only to an hour would look like: { "timestamp": "2016-01-20T12:00:00Z", "timestamp_precision": "hour" } A timestamp known to a second would look like: { "timestamp": "2016-01-20T12:31:12Z" } A timestamp known to 5 digit sub second precision would look like: { "timestamp": "2016-01-20T12:31:12.12345Z" } 4.9. Timestamp Precision
A timestamp-precision represents the precision options for a given timestamp. Its value MUST be one of "year", "month", "day", "hour", "minute", or "full”. <<<<<<<<<SNIP>>>>>>>>>
5.1. Custom Properties
The authors of this specification recognize that there will be cases where certain information exchanges can be improved by adding fields that are not specified nor reserved in this document; these fields are called Custom Properties. This section provides guidance and requirements for how producers can use Custom Properties and how consumers should interpret them in order to extend STIX in an interoperable manner. 5.1.1. Requirements
Any consumer that receives a STIX document with one or more Custom Properties MAY:
The reporting and logging of errors originating from the processing of Custom Properties depends heavily on the technology used to transport the STIX document and is therefore not covered in this specification. Consumers that receive a STIX TLO that contains one or more Custom Properties that are understood MUST process the Custom Properties according to the rules for that Custom Property. Non-Normative: Producers of STIX documents that contain Custom Properties should be well aware of the variability of consumer behavior depending on whether or not the consumer understands the Custom Properties present in a STIX TLO. Rules for processing Custom Properties should be well defined and accessible to any consumer that would be reasonably expected to parse them. 5.1.2. Examples{ ..., "x_acmeinc_scoring": { "impact": "high", "probability": "low" }, ... } |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]