MISP
/
misp-rfc
mirror of https://github.com/MISP/misp-rfc
2
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #1 from MISP/Rafiot-patch-1 

Clarification of date vs timestamp
pull/6/head
Alexandre Dulaunoy 2016-10-03 11:00:35 +02:00 committed by GitHub
parent f4034924b5 48aa6c49de
commit 1247d572bd
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
misp-core-format/raw.md
View File

@ -127,13 +127,13 @@ threat_level_id is represented as a JSON string. threat_level_id SHALL be presen
#### date #### date
date represents a reference date to the event in year-month-date format. For a more precise time reference, the timestamp key is used. date represents a reference date to the event in ISO 8601 format (date only: YYYY-MM-DD). This date corresponds to the date the event occured, which may be in the past.
date is represented as a JSON string. date is represented as a JSON string.
#### timestamp #### timestamp
timestamp represents a reference time when the event was created. timestamp is expressed in seconds (decimal) since 1st of January 1970 (Unix timestamp). The time zone MUST be UTC. timestamp represents a reference time when the event was created, or last updated. timestamp is expressed in seconds (decimal) since 1st of January 1970 (Unix timestamp). The time zone MUST be UTC.
timestamp is represented as a JSON string. timestamp MUST be present. timestamp is represented as a JSON string. timestamp MUST be present.