The Knowledge Warehouse project implementation was a steep learning curve for all involved. S1000D is not just about XML and being an XML expert does not automatically make you an S1000D expert. S1000D is built on decades of experience in maintaining documentation for complex civil aviation and military systems and because of this, it is a robust and complex system in itself. It has also been designed to meet a very broad spectrum of requirements and it is for this reason that the specification is a bulky and intimidating document.

Perhaps the key to getting the most out of S1000D is in chapter 1.4.1 of the specification[[7]] where it talks about tailoring for a specific project or organisation. I think this is a very helpful way to think about it, especially if you take the analogy of a tailor a little further. We all know that tailors cut cloth and sew the pieces together to create a bespoke item of clothing for the customer. Before getting out the scissors though, the tailor asks what the customer is looking for and then proceeds to take a series of measurements to ensure the finished article is exactly what is requested and that it fits perfectly. The application of S1000D business rules are the way to understand your customer's requirements and get the measurements of your project. With these measurements you can then tailor the specification to fit, leaving out all the parts that aren't relevant. Furthermore, business rules give you the thread to sew the different components of your project together and hold them together securely in the long term.