Happy Friday! If these responses are typical of this group, I can tell we like to have fun. :)
I am hoping to avoid an argument about what REST is, because that can become a tug-of-war (or a "tarbaby" as a seasoned coder once told me). Really, if you like your REST to be whatever you want it to be, then go for it!
But, if there is anyone on this list who really likes Fielding Chapter 5, please let me know.
From: email@example.com <firstname.lastname@example.org> on behalf of Jordan, Bret <email@example.com>
Sent: Thursday, September 10, 2015 11:05 AM
To: Trey Darley
Cc: Jason Keirstead; John Anderson; firstname.lastname@example.org
Subject: Re: [cti-taxii] TAXII per Chapter 5 of Fielding
Oh come on...... You do not like writing decision trees in code that go from one ocean to the other? It is so much fun having infinite possibilities. It makes code so fun to maintain.
Bret Jordan CISSP
Director of Security Architecture and Standards | Office of the CTO
Blue Coat Systems
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."
"...near infinite code-paths...This is the very problem we have with TAXII and STIX today - too much complexity."
+100, Jason, I'm having that printed on a t-shirt! ^_^
Senior Security Engineer
Soltra | An FS-ISAC & DTCC Company
My $0.02 - While I really prefer REST principles for APIs, I also think that REST is whatever people want it to be.
There are hardly any (perhaps zero?) high traffic REST APIs in the wild that are purist REST and HATEOAS. The main one that hardly anyone follows is the concept of discoverability -, because it is somewhat idealistic, unnecessary in practice, and just complicates
the API. As a developer I would much rather have a stringent REST spec with documented endpoints that I can consume, than a widely flexable one based on discovery that results in near infinite code-paths.
This is the very problem we have with TAXII and STIX today - too much complexity. We don't need to solve world hunger with this API. My challenge would be this - if simple REST is good enough for Google and Twitter and Facebook and Amazon, why is it not good
enough for TAXII. We can only hope in our wildest dreams that our API gets consumed as much as those APIs do.
Product Architect, Security Intelligence, IBM Security Systems
Without data, all you are is just another person with an opinion - Unknown