[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Tokyo POC choreography - regrep
Hi all, As we are discussing, it would be nice if we all get the configuration and other partner information from a regrep implementation. To that effect, here are my suggestions and queries: 1. Define Information Set - I think P.12 of SJ POC which lists the min required information, is a good starting point. 2. Are we all are getting the partner information we need from an external source - hopefully from a file in XML format ? If so, then we can abstract this functionality and redirect it to a regrep implementation as needed. Also, if we start doing this now, we will also know what information we need from the regrep. 3. It would be good if we can workout some integration at the LA meeting. To that end, I am slowly trying to develop a regrep implementation (which of course, will be finalized after the regrep specs is done). I am looking to work with somebody to start integration, at least at the messaging level and exchanging test documents. So when the regrep is finalized, we can do the real integration. I know that we are still working on the matrix et al. I just want to see if there is anybody whom I can start working together, sharing ideas et al. cheers -----Original Message----- From: David RR Webber [mailto:Gnosis_@compuserve.com] Sent: Friday, September 08, 2000 9:36 PM To: Farrukh Najmi Cc: ebxml-poc@lists.ebxml.org; richard drummond Subject: Re: Tokyo POC choreography - my 2c ;-) Message text written by Farrukh Najmi > While I have the above stated opinion, I want to hear what Krishna, POC team and other teams driving the POC feel regarding this issue. If the decision is to show discovery then together we will make it happen come hell or high water. <<<<<<<<<<<<<<<<<<<<<<< Farrukh, the GUIDE classification layer coupled to the BP definition and a simple set of XML profiles for each company would make a very easy demonstration in Tokyo POC. XML search engines like GoXML can eat this for breakfast - we already have this kind of scenario live over the internet today. You would see the XML, the criteria, the Query interface, and then a resulting HTML menu where you could pick a partner to interact to. If instead you wanted to do this in batch mode from say a TRP module to validate a interface parameter, this would also be possible. I've been holding back from going there however - because I wanted to make the Tokyo POC RegRep side of things as vendor neutral as possible, and based on the spec's to date. This maybe the right moment however to re-visit this if you truely wanted to respond directly to UDDI. Thanks, DW.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC