When designing the electronic mortgage standard for Fannie Mae, my goal was to design a flexible container that could travel with the content, protect the content, log its use and render it in multiple views. Of course, I was leveraging my programming experience and encoding the MVC pattern in XML. In my latest book, I refined the concept into this diagram:
Most recently, at the FOSE conference I moderated a panel on Information Sharing. In that panel, I discussed some of the principles of “Information As Product” and compared these XML containers to the packaging and labeling of physical products. A panel member suggested I examine the LEXS standard as an example of such an XML container. I was pleased to see the strong similarity between this work and the electronic mortgage specification (now a MISMO standard called SmartDoc).
I see Information MVC as a key XML technique to enable information products that make particular content relevant to specific consumers. The difference between information and an information product is making information suitable for groups or segments of consumers. Enabling the content to expose a different view based on who is accessing it helps us increase the relevance, privacy and security of our content. For programmers this is probably old news, but for data architects and data architecture it is a new concept. Have you used this concept or seen it used? If so, let me know…
Also, for those interested in Information Products, I just posted the first chapter of my latest book online.
Until next time, see you in the XML trenches. - Mike