Title Normative Text on Lengths Proposal
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
Ballot Options Ballot has closed
[ ] No, there should be no normative text describing length limits.
[ ] Yes, the spec should have normative text describing length limits for some fields.
Opening Date Mon, Jun 13 2016 12:00 pm EDT
Closing Date Mon, Jun 20 2016 12:00 pm EDT
Ballot has closed.

Referenced Items

Name Type Date Actions

02942: Normative Text on Lengths Proposal

Document (Archive)

2016-06-20