Canonical design

We are in the process of designing canonical documents for sales and purchase orders based on standards like EDI, xCBL, rosettanet ect…
Our canonical document is becoming very big structure. Could you share your knowledge, what is the best approach to design canonical similar to other standard documents (EDI, cXML,xCBL etc).
Big canonical data structure impacts the performance. It is my concern. Whenver we publish canonical document, all the fields may not be utilized.

Thanks,
Brijesh

We were having the same issue. We took the approach to minimize the canonical with only the fields we knew the source side was currently using. If more fields need to be added in the future, they can be added. I’m not sure if this is a best practice, but it helps to minimize the size of the document. We had hundreds of fields that were not being used.

Here is a link to a related thread:

http://www.wmusers.com/wmusers/messages/120/981.shtml?