[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: CPA and overrides
I believe it makes sense to have the CPAid optional, and load any needed information into the header, as David B points out. I think the CPAid should called ConfigInfo with a "type" like Partyid and be ORed with a structure containing the needed header data. Fundamentally, all we are talking about is by-reference or by-value with some additional process concerns for initial messages or bootstrap, which may not even need to be spec'd. The issue to me is not *if* it makes sense to have it either by-ref or by-value, but *what* header data is needed. That is what may not be able to be settled in time. This also is well in line with breaking dependency between components in ebXML. Scott Hinkelman, Senior Software Engineer XML Industry Enablement IBM e-business Standards Strategy 512-823-8097 (TL 793-8097) (Cell: 512-940-0519) srh@us.ibm.com, Fax: 512-838-1074
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC