[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti-users] Towards a better understanding of JSON-LD (Was: MTI Binding)
So here’s my understanding:
We will define an OASIS work product that describes the STIX high-level data model. This work product will be some form of UML and/or RDF. So at that point, we’ve defined the high-level data model.
The community has (unofficially) decided that in the interest of best interoperability between tools we need to define a single serialization format as “mandatory to implement” (MTI). All tools implementing STIX would implement this format. This
would also be codified as an OASIS work product.
Whether we have other OASIS work products for other serialization formats is up for debate, but I do think there’s some sense that the fewer of these we officially standardize the better (again, for best interoperability).
So let’s say we choose JSON / JSONSchema as the MTI format. We would have two OASIS work products:
- The high-level model
- A binding of that high-level model, describing what it looks like when serialized to JSON along with JSONSchema to automatically validate it.
Tools claiming that they participate in STIX-based exchanges would be required to implement the JSON serialization format. They could also implement any other serialization formats they want (RDF-style STIX transfers, CSV, IODEF, Thrift, etc).
Data exchange of those formats just wouldn’t be called a “STIX information exchanges” unless we also developed and published an OASIS work product standardizing them as such.
Although, now that I think of it, I’m wondering if an RDF-style exchange (JSON-LD, RDF/XML, RDF/Turtle) would be considered STIX-based just because it natively conforms to the high-level model (assuming the high-level model is RDF). I don’t know!
If it did, those tools would also need to implement the MTI serialization but could also call the RDF exchange “STIX-based".
John
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]