Well, I hesitate to speak for the OXCI consortium when some of these architectural decisions have not been finalized by either the OXCI Consortium or Legal XML.
OXCI is intended to be an EFM reference implementation.
As such, it does need API's for interacting with an EFSP, Court Policy, Court CDC, a CMS and a DMS.
It also assumes the existence of a CMS/DMS-unique Adapter that stands between the EFM and the CMS/DMS.
The Adapter handles some of the translation duties, since the OXCI group suspects that to do otherwise would put an unrealistic burden on the EFM, Court Policy and Court CDC.
Some vendors suggested that might be the case during discussion of the last Court Policy version.
I would like to refer any additional questions about OXCI to Greg Arnold, who leads the OXCI Consortium.
