Another interesting question from Bill Higgins on the Jazz web UI team, was why in so many conversations with those of us deep in the Foundation the term "triple" seemed to be embedded in the answer to almost any question. The answer is of course that in the Foundation we use RDF considerably as our index format, as the resource format for certain system resources and also of course as our query language (SPARQL). So, it's inevitable that triples, as the core abstraction in the RDF data model, appear a lot in our conversation.
But the more important point, the point Bill was trying to make was, why triples at all, why RDF, why not the SQL data model we used in previous tools? The answer to that question is longer and trickier, but boils down to the fact that we can't define a single data model for all the tools we have today, given the fact that many change on independent schedules, we have acquisitions that bring in new tools all the time and in some domains the resources themselves are not fixed but are constructed/configured by customers. So, how do we develop a single platform for all of these tools? Quite simply we look for a model that is inherently flexible, that allows us to represent information from these tool-specific resources in a common and general way. The answer to that is RDF and therefore there's a lot of us worrying about triples.
So. while maybe not "cosmic", the significance of triples can't be downplayed in the Foundation and you'll find all manner of people writing N-Triples and Turtle in email, documents and the Jazz Foundation wiki.[Read More]