Re: [cti-stix] GeoJSON

To clarify, I think what would be deferred to a later date is re-evaluating whether or not GeoJSON support belongs in STIX at all. As written it sounded as if that was a foregone conclusion that was simply pushed to a later release. I don’t believe that to be the case.

On 6/28/17, 8:05 AM, "Trey Darley" <cti-stix@lists.oasis-open.org on behalf of trey@newcontext.com> wrote:

On 27.06.2017 20:45:48, Wunder, John A. wrote:

> To outline the options:

> Option 1: Include GeoJSON as an optional property alongside the

> other MaxMind-style attributes, including latitude and longitude.

> This creates a bit of “two ways of doing things”, because then you

> can either use GeoJSON to represent a point or you can just use the

> lat/long fields in the core location object.

Slight clarification: on the call we discussed the possibility of

representing lat/long as GeoJSON Points, which *would* eliminate the

"two ways of doing things" problem.

That said, tools which only aimed for MaxMind functionality might not

be capable of processing GeoJSON Polygons. (This might be addressed by

some thoughtful additions to the Interoperability specs.)

John's right about the consensus on the working call: unless some

compelling arguments are brought to the table, most likely we will

defer GeoJSON support to STIX 2.2+.

Cheers,

Trey

++--------------------------------------------------------------------------++

Director of Standards Development, New Context

gpg fingerprint: 3918 9D7E 50F5 088F 823F 018A 831A 270A 6C4F C338

++--------------------------------------------------------------------------++

"When old dreams die, new ones come to take their place. God pity a

one-dream man." --Robert Goddard

cti-stix message