[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ebxml-dev] Registry Usage Models
Hi Folks, Now that I have an ebXML v2.0 registry installed, are there models available of how to use it. I am still struggling with the big picture. We want to base our development on and therefore store OAGIS 8.0 *.xsd files in the registry. We also want to store *.xml instance files and eventually we will put together some CPP, CPA, and BPSS. And of course there will be some miscellaneous stuff in the registry as well. Plus the entries in the registry may be URIs. I was speaking with Michael Rowell at the OAG and with the correct resources he can see providing a URI for accessing the BODs. What happens when the data at these URLs changes? I know a lot of questions and no answers. Brian Aingworth Lockheed Martin Systems Integration 607-751-2071 brian.aingworth@lmco.com -----Original Message----- From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM] Sent: Tuesday, August 06, 2002 5:14 PM To: Aingworth, Brian Cc: 'Nikola' Subject: Re: Hey What's Up? Brian, Thanks for the update. Let us know how you find GoXML's registry and its compliance with ebXML Registry V2 specs. "Aingworth, Brian" wrote: > Hey guys, > We have decided to take a closer look at XML Global's GoXML product. Thanks > for all your help and I hope we can continue to share information. Lisa > Carnahan has GoXML, but last I spoke with her, it had not been installed. > We've had our GoXML installed for several weeks and are now looking ahead as > to the possibilities it may provide us. > > Stay in Touch > > Brian > > -----Original Message----- > From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM] > Sent: Monday, July 22, 2002 11:40 AM > To: Aingworth, Brian > Cc: 'Nikola' > Subject: Re: UDDI vs ebXML > > Brian, > > Just came back from vacation and digging our from email and phone mail. > Please > see comments inline below: > > "Aingworth, Brian" wrote: > > > Hey where did you guys go? or is this answered out in the newsgroup? > > Brian > > > > Nikola, Farrukh, > > > > Can either of you help me out here? I made the following statement about > > UDDI and received the following response. Are UDDI and RIM/RSS different, > > are they suppose to work together or am I to choose one technology/product > > over another? I thought UDDI and ebXML were different technologies and > that > > UDDI would be used to locate ebXML registries. > > > > Brian: I believe that UDDI is a Directory Service and not > a > > MetaData Registry. > > UDDI is a metadata registry only and does not include repository function. > ebXML is a registry and repository. > > > > > > > Response: As I had UDDI presented to me it incorporated > the > > look-up function and the registry function. Basically you would look-up > > publicly via yellow, white, or green pages companies that do business in > > your area of interest. Then once you publicly find those companies there > > would be contact information allowing you to access secure registries > > maintained based on UDDI but secured within individual enterprises. These > > secure internal registries would use UDDI to perform B2B operations. What > > part of this am I off on? > > UDDI includes basic publish/lookup function. It provides ability to lookup > via > fixed SOAP queries. ebXML Registry supports complete ad hoc query capability > using XML and SQL query syntaxes. The differences between the two are many. > I > will summarize to say that ebXML is more flexible and extensible while UDDI > is > designed for a narrow set of use cases (publish/lookup of businesses and > services). ebXML is designed as a more general puprose registry.b > > > > > > > Brian Aingworth > > Lockheed Martin Systems Integration > > 607-751-2071 > > brian.aingworth@lmco.com > > <<Aingworth, Brian.vcf>> > > -- > Regards, > Farrukh -- Regards, Farrukh
Attachment:
Aingworth, Brian.vcf
Description: Binary data
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC