[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-taxii] Restrictions on resource names
Lets talk about this on tomorrows call. Mean while, I will update the document with the current language that was used in STIX. I just realized that the language in TAXII is older.
Bret
All,
Previously in the TAXII SC we had talked about and agreed to have some restrictions to the names and lengths of API-Bases and Resource names like "channel names" and "collection names".
In STIX we do not have restrictions for the contents of a "string" property. However, we do have very tight restrictions for property names and custom properties / custom objects.
The current restrictions we have in place and nearly a copy-n-paste from what we do in STIX today, they are:
* An API Base MUST be in ASCII and are limited to characters a–z (lowercase ASCII) and dash (-).* An API Base SHOULD be no longer than 30 ASCII characters in length.* An API Base MUST have a minimum length of three ASCII characters.* An API Base MUST be no longer than 256 ASCII characters in length.
* Resource names MUST be in ASCII and are limited to characters a–z (lowercase ASCII) and underscore (_).* Resource names SHOULD be no longer than 30 ASCII characters in length.* Resource names MUST have a minimum length of three ASCII characters.* Resource names MUST be no longer than 256 ASCII characters in length.
Personally I really like this approach, I believe there to be value in restricting these. I am, however, curious to know if the SC still feels this is the best way to go.
Bret
Dave Cridland
Participate | Collaborate | Innovate
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]