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


Help: OASIS Mailing Lists Help | MarkMail Help

csaf message

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

Subject: Re: [csaf] [CSAF JSON Schema] limits to field lengths

Hi Allan,

I'd be perfectly comfortable with not imposing limits. I raised the issue because:
However, trying to guess at limits is likely a tricky enterprise. I thought it might be worth a discussion - even if we discard it.


On Mon, May 7, 2018 at 8:16 PM, Allan Thomson <athomson@lookingglasscyber.com> wrote:

Eric –


Lower limit -> It depends on the property. 0 (empty string without null) may be a good lower limit. For example, a string property where the value is unassigned may be set to empty string.


Upper limit -> In most cases STIX2 avoided setting an upper limit at all. For certain string enumeration properties the upper limit was set to a reasonably high value for what could be expected in that enumeration. (e.g. 256)



From: <csaf@lists.oasis-open.org> on behalf of Eric Johnson <eric@tibco.com>
Date: Monday, May 7, 2018 at 5:53 PM
To: "csaf@lists.oasis-open.org" <csaf@lists.oasis-open.org>
Subject: [csaf] [CSAF JSON Schema] limits to field lengths


The current specification does not limit the amount of data that goes into properties, such as the document title or the description fields.


The lower limit I put in the JSON schema (for just about everything), is simply a non-empty string - 1 or more characters.


Is that the right lower limit?


What's the upper limit?



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