Thanks Farrukh, now I'm gonna ask something I asked once before but I don't think anyone understood what I was asking (my fault as an ebXML newbie) are there any use-cases, whitepapers, etc. out there about iterative ebXML implementations, by which I mean that standalone components of the whole framework are implemented piece by piece, with appropriate studies done along each step of the implementation flow, until the final step of a full implementation is taken? From what I've read of freebxml it seems to me that this is also a very good use for that project. Sorry if this is a silly question, but I assume that I will be asked to come with recommendations about implementation soon, and I think everyone would be happier if an incremental process was used. -----Oprindelig meddelelse----- Fra: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM] Sendt: 28. juli 2004 13:09 Til: Bryan Rasmussen Cc: ebxml-dev@lists.ebxml.org Emne: Re: [ebxml-dev] ebxml specifications used seperate from ebxml Bryan Rasmussen wrote: >There seems to be a number of ebxml specifications that were designed to be >used seperately from the overarcing ebxml framework, so far I count: > >CPP/CPA >BPSS >ebMS >ebXML core components > >Are there any others that can be used seperately from the whole? > > Add to above the following: ebXML Registry Information Model (ISO 15000 part 3) ebXML Registry Services (ISO 15000 part 4) In summary ebXML Registry standard is completely independent of any other ebXML standard. It is a web service that has a SOAP, REST (HTTP) and ebMS binding, SOAP and REST are required while ebMS is optional. -- Regards, Farrukh
<<attachment: winmail.dat>>