cti-taxii — archive

[Jason Keirstead]

I should be more clear... This is in the 2.0 spec. The 2.1 spec does not have this "problem", it has UUIDs everywhere. Which implies that some of the examples in the 2.0 spec, are not valid in 2.1 - Jason Keirstead Lead Architect - IBM.Security www.ibm.com/security "Things may come to those who wait, but only the things left by those who hustle." - Unknown __________________ I have found errata in the TAXII spec The TAXII spec defines the ID of the collection resource to be of type "identifier", which, at the start of the document, is defined as having to be a UUID. However, numerous examples throughout the specification show a collection ID having a common string name such as "my-collection". Is it allowed for a TAXII collection to have a common name as an ID? Or do they all have to be UUIDS This has ramifications for people wanting to create special read-only or write-only collections that serve as things like an Inbox. - Jason Keirstead Lead Architect - IBM.Security www.ibm.com/security "Things may come to those who wait, but only the things left by those who hustle." - Unknown