legalxml-courtfiling — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [legalxml-courtfiling] Groups - Component Issue resolution conference call added
MHonArc v2.5.0b2 -->legalxml-courtfiling message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [legalxml-courtfiling] Groups - Component Issue resolution conference call added
- From: "Cusick, James" <[email protected]>
- To: <[email protected]>,<[email protected]>
- Date: Sun, 27 Feb 2005 12:56:53 -0500
Folks, I would just like to state my preference in resolving this. I would prefer not to see any use of the term component or a substitute. I would prefer that the standard define the functionalities of a generic filing system and an interface (API) to that system. The decomposition of the system into components is a step for the implementer to take not something for the standard to define. I would like to see the standard talk about a filer (or filing client) and a filing system (or server). I can imagine a scenario where diverse filing clients talk to diverse filing systems which may implement the standard interfaces in diverse ways. It may be necessary to discuss a CMS as well. This might be seen as another client or a cooperating server. With these three entities I think a useful standard could be described. Additionally, it might be useful to describe the interface to a payment system (another server). Looking forward to the discussion. Regards, james
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]