OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cti-users message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [EXT] [cti-users] ScalaStix library


Ringo,


Can you please submit this to the cti-comments public comment list?


Thanks

Bret



From: cti-users@lists.oasis-open.org <cti-users@lists.oasis-open.org> on behalf of ringo <ringowathelet@gmail.com>
Sent: Thursday, May 18, 2017 11:54:27 PM
To: cti-users@lists.oasis-open.org
Subject: [EXT] [cti-users] ScalaStix library
 
From the specs (2.0 and 2.1)
"A STIX Object MAY have any number of Custom Properties."
for example:
{
...,
"x_acme_org_confidence": 10,
"x_acme_org_scoring": {
"impact": "high",
"probability": "low"
},
...
}

I've been thinking of implementing this in my scala library, however
it is turning into a mess to have unknown key names.

I would prefer have a dedicated area/object, say "x_custom", such as:
{
...,
"x_custom": {
"x_acme_org_confidence": 10,
"x_acme_org_scoring": {
"impact": "high",
"probability": "low"
},
...
}
}

Would this scheme of putting all custom properties into such "object" be a break from the specs?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]