[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Registry Headers
With respect to the ebXML Headers required to interact with RegRep, we need to finalize on the header info. I think that the suggestion that I made earlier went on a long-winded tangent. Please permit to back up and see if we can reach consensus. Step 1: The header looks the following where and we are trying to reach consensus on --A-- and --B-- <ebXMLHeader> <Header> <TPAInfo> <TPAId context = "POC"> CPA/CPAInfo/CPAName </TPAId> <ConversationId context = “POC uid@requester-domain [from request message] </ConversationId> <ServiceInterface> --A-- </ServiceInterface> <Action> --B-- </Action> </TPAInfo> </Header> ... </ebXMLHeader> Step 2: I propose the values of A & B should be: --A-- == Object Query Manager Note: This is only one of several service interfaces --B-- == GetRootClassificationNodesRequest Note: This is only one of several actions within the interface Step 3: I suggested the locations of A & B in the cpp-cpa DTD in the e-mail sent earlier. Please do not use the locations in the header. Rather I thought I would tell you exactly where you can find the values of A & B in the DTD: --A-- == CPA/BusinessProtocol/BusinessInterface/ServiceInterface?InterfaceId --B-- == CPA/BusinessProtocol/BusinessInterface/ServiceInterface/ActionMenu/Action/Re quest/RequestMessage Thanks, Mark > -----Original Message----- > From: Mark Hale [mailto:hale@ajubasolutions.com] > Sent: Friday, October 27, 2000 3:12 PM > To: ebXML-poc > Subject: Registry Headers > > > JP raised a good point. First, I would like to add some > background. JP is > referring to the ebXML headers for messages going to the RegRep > and not the > CPA itself. There are two things that must be considered, the CPP/CPA and > the header. Though we now have the CPA DTD from Marty, the TPAInfo in the > headers are not fully aligned (to prove it TPAInfo ceases to exist in the > DTD). In fact, a proposal hit the thread today to align the two. > > IMHO, I would like to augment JP's proposal from earlier and suggest the > following (I've inserted the full element locations in a RegRep > CPA into the > ebXML Header sample): > > ---------------------------------------------------------- > <ebXMLHeader> > <Header> > <TPAInfo> > <TPAId context = "POC"> > CPA/CPAInfo/CPAName > </TPAId> > <ConversationId context = “ItemAlignment"> > uid@requester-domain [from request message] > </ConversationId> > <ServiceInterface> > > CPA/BusinessProtocol/BusinessInterface/ServiceInterface?InterfaceId > </ServiceInterface> > <Action> > > CPA/BusinessProtocol/BusinessInterface/ServiceInterface/ActionMenu > /Action/Re > quest/RequestMessage > </Action> > </TPAInfo> > </Header> > ... > </ebXMLHeader> > ---------------------------------------------------------- > Example Data: > > CPA/BusinessProtocol/BusinessInterface/ServiceInterface?InterfaceI > d = Object > Query Manager > CPA/BusinessProtocol/BusinessInterface/ServiceInterface/ActionMenu > /Action/Re > quest/RequestMessage = GetRootClassificationNodesRequest > > ---------------------------------------------------------- > > > Thanks, > > Mark > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC