Re: [cti-stix] field names

["Jordan, Bret" <bret.jordan@bluecoat.com>]

That is a good catch.  And let's please catch things like this and fix them while we can.

Bret

Sent from my Commodore 64

On Jun 29, 2016, at 7:19 PM, Allan Thomson <athomson@lookingglasscyber.com> wrote:

I would prefer consistency as Bret suggests but I would also suggest that all terms should be in the same tense.

 

Start / End are not the same as creat-ED and modif-ED are.

 

So they should be start-ED and end-ED.

 

Started

Ended

Published

Created

Modified

 

allan

 

From: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org> on behalf of Terry MacDonald <terry.macdonald@cosive.com>
Date: Wednesday, June 29, 2016 at 3:03 PM
To: "Jordan, Bret" <bret.jordan@bluecoat.com>
Cc: "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org>
Subject: Re: [cti-stix] field names

 

I would like the names to stay the same as they are. I think that start and end are very clear and describe their purpose well. I believe that clarity should win over consistency in this case, as those field names are very obvious to anyone consuming or producing the STIX.

Cheers
Terry MacDonald
Cosive

On 30/06/2016 06:08, "Jordan, Bret" <bret.jordan@bluecoat.com> wrote:

In the following TLOs we have defined the following timestamp fields

 

In Observations we have "start" and "end"

In Report we have "published"

In Indicator we have "start" an "end"

 

In the TLO Common Properties we have 2 fields:

"created_time"

"modified_time"

 

I am guessing  we should probably have some consistency...  Perhaps we should change the TLO Common Properties fields to be just "created" and "modified"  

 

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."