Document:
02942: Normative Text on Lengths Proposal

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Alexander Foley on 2016-06-20 4:03 pm UTC

Publication Type

None at this time.

Group / Folder

OASIS Cyber Threat Intelligence (CTI) TC / System Ballot Results

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

476

Download Agreement

None at this time.

Description

NOTE: The purpose of this ballot is to develop consensus for STIX on an issue that has been discussed on the list in the "Unicode, strings and STIX" thread. This is a non-binding ballot that can be reversed at any time in the future by simple majority vote of the TC. Elaboration: ============ On May 31, John-Mark Gurney raised questions related to whether or not we were going to determine the specific length of fields in the STIX specification. His original post is here: https://lists.oasis-open.org/archives/cti-stix/201605/msg00174.html There was a vibrant debate for the next few days, and there seems to be general consensus that we should specify some normative text, even if it is SHOULD, for the length of fields. If the results of this ballot yield a YES vote, there will be additional questions to follow (such as whether lengths should be mandatory or advisory) but for now, please help us decide whether we should specify limits at all. To consider the discussion in the entire thread, please use this link to the MarkMail archives of the cti-stix list: http://markmail.org/search/?q=Unicode%2C+strings+and+STIX&q=list%3Aorg.oasis-open.lists.cti-stix