Design Rationale

Design Choices

See this page for general implementation advice

Flexibility

• There are multiple ways to encode the same data into STIX Solution: implementations should handle a the full range of potential input and create well-formatted output

• STIX can be extended, meaning that incoming data may be in an unfamiliar format Solution: Users may communicate a Profile to negotiate the type of STIX format that they support and will produce

Versioning

see page

Data Markings

• We use a list of XPaths to mark specific elements, because of TODO

Language Choice

• We use XML, because TODO

Implementation

• Rather than storing XML data in a persistent database, we suggest that developers parse STIX data and store it in their a database-specific manner. Python scripts along with database-specific queries may be used to export STIX content on demand.