Quoting the Stix2 Python Library Documentation
"The stix2 library features an interface for pulling and pushing STIX 2 content. This interface consists of [DataStore], [DataSource] and [DataSink] constructs:
a DataSource for pulling STIX 2 content,
a DataSink for pushing STIX 2 content, and
a DataStore for both pulling and pushing."
When we examine the methods in typedb.py, we see that we have many methods on DataSink, and very few on DataSource. We have methods that pull data, incorrectly located on DataSink, which is only for pushing, for example:
get_stix_ids(self)
__retrieve_stix_id(self, stix_id: str)
delete(self, stixid_list: List[str])
We need to:
Reorganise the methods, so methods that require pulling is on the Source, and methods that require pushing on the Sink. the assumption is that the delete() method is on the Source, since it requires pulling the id's
Add the DataStore mixin method, using the filesystem methods as an example
Produce documentation on the high-level methods in the docs directory, interaction sub-directory, python sub directory
Quoting the Stix2 Python Library Documentation "The stix2 library features an interface for pulling and pushing STIX 2 content. This interface consists of [DataStore], [DataSource] and [DataSink] constructs:
When we examine the methods in typedb.py, we see that we have many methods on DataSink, and very few on DataSource. We have methods that pull data, incorrectly located on DataSink, which is only for pushing, for example:
We need to: