[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Registry Headers
Mark, Again, The RR spec requires that an algorithmic mapping be followed for the ServiceInterface and Action names. What is the problem that we cannot follow the spec? For your reference the following lines in RR Services v0.8 spec are relavant: 320 321 And Section 3.2 Lets either identify a problem with the spec or not create further confusion with alternatives that violate the spec. If teh spec is not clear it will be more clearer when I send you the sample messages in a teh next 30 minutes. Thanks for your help Mark Hale wrote: > 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?InterfaceId = Object > Query Manager > CPA/BusinessProtocol/BusinessInterface/ServiceInterface/ActionMenu/Action/Re > quest/RequestMessage = GetRootClassificationNodesRequest > > ---------------------------------------------------------- > > Thanks, > > Mark -- Regards, Farrukh
begin:vcard n:Najmi;Farrukh tel;fax:781-442-1610 tel;work:781-442-0703 x-mozilla-html:TRUE url:www.sun.com org:Sun Microsystems;Java Software adr:;;1 Network Drive, MS BUR02-302;Burlington;MA;01803-0902;USA version:2.1 email;internet:najmi@east.sun.com fn:Farrukh S. Najmi end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC