Canonical Data
Like the exchange of data between Sellers and Suppliers, the exchange of data within the company is vital to successful processing of transactions. This could be the Seller or the Supplier, it doesn’t really matter. As data passes from the processing application, to the external interface. We have a concept that is called a Canonical form of data. Canonical data is the data that is required and essential to completing your business. I have written about this in passing before, but today I want to talk about what goes in it, and what it looks like. (more…)
Tuesday, September 29th, 2009
I have been studying some on the SEF format. SEF stands for Standards Exchange Format. This is a file that defines the EDI standard so that you can use a validation or standard and usage document editor to create nice, and clean specifications for you and your trading partners.
A reader asked me a question, and I want to pass it along: “Do you know of any DOT NET frameworks for working with EDI?”
Whether we are talking about e-commerce or any other movement of data, we will need to capture points of data to ensure proper monitoring and reliability. There is an overall strategy to this, and three types of data points that should be monitored; Points that are convenient. Points that are helpful. And points that are necessary. With these points monitored and the data that passes them recorded and aggregated properly, a reliable and supportable system is created.
The Integration Engineer has been on-line for a whole year now, and I feel like it is time to look back and take stock of what I set out to do here, and what happened to that vision. So today I am departing from my normal task of writing integration tips, tutorials, and experiences and am going to talk about this blog itself.