This is a big (in terms of scope) issue, but here goes.
I'd like for initial_data.json to come with a complete enough data set that every aspect of TAXII (well, at least TAXII 1.1) can work out of the box. That means, Inbox w/ a Destination Collection Name, Query, etc. I have started an incomplete list of things I'd like to be able to support, and I can update this list if people mention more in the comments:
List of use cases to support out of the box:
[X] Send information to an Inbox with a Destination Collection Name
[ ] Query based on STIX 1.1.1 IDs (Note, this will change to a newer version of STIX at some point)
[X] Poll a Data Collection
[ ] Create, pause, resume, unsubscribe a subscription
[X] Do a successful Collection Information Service
[ ] Have all libtaxii scripts work "out of the box" against the default data set
(Now that I've written the list, I realize this also bleeds over into implementation work in django-taxii-services.)
This is a big (in terms of scope) issue, but here goes.
I'd like for
initial_data.jsonto come with a complete enough data set that every aspect of TAXII (well, at least TAXII 1.1) can work out of the box. That means, Inbox w/ a Destination Collection Name, Query, etc. I have started an incomplete list of things I'd like to be able to support, and I can update this list if people mention more in the comments:List of use cases to support out of the box:
(Now that I've written the list, I realize this also bleeds over into implementation work in django-taxii-services.)
Thank you. -Mark