Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Suggested change for Dictionary - Common Data Type #35

Closed
emmanvg opened this issue Oct 20, 2017 · 5 comments
Closed

Suggested change for Dictionary - Common Data Type #35

emmanvg opened this issue Oct 20, 2017 · 5 comments
Labels
Status: Closed Done STIX: Core Target: STIX-2.1
Projects
STIX 2.1
Milestone
2.1-wd01

Comments

@emmanvg
Copy link

emmanvg commented Oct 20, 2017 •
edited

While writing tests to support the LanguageContent object I found myself with a problem using the contents dictionary. I saw RFC5646 supports language tags longer than 2 characters, but the STIX specs mandate 3 or more for keys in a dictionary. The examples found in the document use language tags that are too short. Will this mean that producers need to provide a more specific language tag?

Affects: Section 2.2 Dictionary

Should there be an exception to this MUST requirement or remove the requirement completely?
@emmanvg
Copy link
Author

emmanvg commented Oct 20, 2017

dictionary

@JasonKeirstead
Copy link

I don't know the history behind that MUST requirement, but I'd suggest it simply be removed.

@jordan2175 jordan2175 added the F2F label Jan 31, 2018
@jordan2175
Copy link

jordan2175 commented Feb 13, 2018 •
edited

We talked about this on the working call on 2018-01-13 and the consensus on the call was to remove the phrase "MUST have a minimum length of 3 ASCII characters".

The people that voted for this to be remove were: Bret Jordan, Trey Darley, Allan Thomson, Mark Davidson, Chris Ricard, Sean Barnum, Rich Struse, Paul Patrick

Abstain: Sarah Kelley

There were 12 people on the call.

@skelley1
Copy link

Point of clarification, this issue was discussed on the working call on Feb 13, 2018, NOT January 13.

@treyka
Copy link

treyka commented Mar 5, 2018

The call for objections ended COB 02 March with no objections received to the TC mailing list. The change has been made in suggesting mode in STIX 2.1, Part 1 with a comment noting that it closes this Github issue. QED, we are closing this issue.

@treyka treyka closed this as completed Mar 5, 2018
@johnwunder johnwunder added this to the STIX 2.1 CSD01 milestone Apr 25, 2018
@johnwunder johnwunder added this to Done in STIX 2.1 Apr 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Closed Done STIX: Core Target: STIX-2.1
Projects
STIX 2.1
  
Done
Milestone
2.1-wd01
Development

No branches or pull requests
6 participants
@johnwunder @treyka @JasonKeirstead @emmanvg @jordan2175 @skelley1