Re: [cti-stix] STIX motion of unanimous consent

Hi everyone,



Since this motion was made last Friday morning ET and we’ve had no objects (some good comments from John Anderson, but no objections) I believe that we can go ahead and accept it as consensus.
  The STIX editors will update the docs to reflect this.



Thanks,

John
From:

<> on behalf of Aharon Chernin <>
Date:  Friday, June 3, 2016 at 7:16 AM
To:  "" <>
Subject:  [cti-stix] STIX motion of unanimous consent



I motion that the STIX SC accept by unanimous consent the Boolean, List, Number, IDs and References, and Object Creator text contained in the STIX pre-draft specifications and
  duplicated below, and that the SC allow the STIX editors to move these sections to CONSENSUS status. If after a period of 5 business days we don’t hear any substantive (non-editorial) objections we will move these sections from REVIEW to CONSENSUS.



  ?3.1.? Boolean

Type Name:

boolean

Status:

Review

MVP
:

Yes



A

boolean
contains a value of either true or false. Properties with this type
  MUST  have a value of
true
or

false  .


The JSON MTI serialization uses the JSON boolean type, which is a literal (unquoted)

true
or

false  .

  ?3.1.1.? Examples

{

 ...

 "is_directional": true,

 ...

}



  3.6.? List

Type Name:

list

Status:

Review

MVP
:

Yes



A

list
contains an ordered sequence of values. When the phrasing “  list
  of type
<type>  ” is used, all values in the list
  MUST  be of the specified type. For instance,
list
of type

number
means that all values of the list must be of the number type. Upper and lower bounds of the
  list – the minimum and maximum number of elements -– may be specified where the list is used. This section does not specify the upper and lower bounds of

list  .


The JSON MTI serialization uses the JSON array type, which is an ordered list of zero or more values.


?3.6.2. Examples

{

 ...

 "observation_refs": [

   "observation--b67d30ff-02ac-498a-92f9-32f845f448cf",

   "observation--c96f4120-2b4b-47c3-b61f-eceaa54bd9c6",

   "observation--787710c9-1988-4a1b-9761-a2de5e19c62f"

 ]

 ...

}



  3.7.? Number

Type Name:

number

Status:

Review

MVP
:

Yes



A

number
contains any number that can be expressed as a real number (e.g., -10, 0, 10, 10.1, 10.123213).
  Each use of
number
specifies the following:


·

The valid range of values;

·

Whether it is limited to integers or not; and

·

The maximum number of decimal places, if non-integer values are permitted.


In the JSON MTI serialization, numbers are represented by the JSON number type.

  ?3.7.1.? Examples

{

 ...

 "count": 8,

 ...

}

  ?6.2.? IDs and References

Status:

Review

MVP
:

Yes



The

id
field uniquely identifies a TLO series. It
  MUST  conform to the
identifier
type.


The STIX language makes use of globally unique identifiers as defined by the

identifier
type for all TLOs. The

identifier
type is also used to define fields that are
  ID references  to other constructs (such as the
created_by_ref
field in all TLOs).
  Resolving
an ID reference is the process of identifying and obtaining the actual object referred by the ID reference field. ID references resolve to an object when the value of the ID reference field (e.g.

created_by_ref
) is an exact match with the

id
field of another object. ID references
  MAY  refer to objects to which  the consumer may not currently have access.


  ?6.3.? Object Creator

Status:

Review

MVP
:

Yes



The

identifier
of the object creator is stored in the

created_by_ref
field, capturing the identity of the creator. The object creator is the entity (e.g. system, organization,
  instance of a tool) that generates the
id
field for a given object.

  Entities that re-publish a TLO from another entity without making any changes to the TLO, and thus maintaining the original

id
,
  are not considered the object creator and  MUST NOT  change the
created_by_ref
field. Entities that accept
  objects and republish them with modifications or omissions  MUST  create a new

id
for the object and update the

created_by_ref
field to reflect their Identity as they will be considered the object creator of the new object.