Lists Home |
Date Index |
David Jacobs wrote:
> Our thinking is that web services should be an integral part of the
> web. This means that if someone puts a pointer to a service on their
> web page it should be easy to exploit that information. In the days
> before Google, when performing keyword searches you would often have
> to page through hundreds of results to find what you wanted. Current
> registry efforts feel like they have the same scaleability problem.
> They work ok for now because the offerings are so paltry but if there
> were many, finding the one you want could prove time consuming. We
> wanted to leverage Google's PageRank(tm) reputation system to see if
> we could avoid that problem from the start.
I believe that the ebXML Registry with its HTTP interface meets your
thinking above. A Service description may be registered with an ebXML
Registry and get all the benefits of being validated, cataloged and be
query able. The actual description may be in the ebXML Registry's
repository or may be elsewhere. The URL to the Service description can
be embedded in any web page.
My experience with google is that you still have to page through
hundreds of entries. It is just that it is better than the old days.
What is really needed is an ability to do semantic queries to find what
you are looking for more precisely. ebXML Registry supports advanced
query capabilities that make it possible to define more precisely what
you are looking for/
> How do federated queries work? I'm not sure I understand the
> mechanism that registries discover each other to pass queries.
Federation is nothing more than a collection of registries that have a
common purpose. Someone needs to track the Federation and its
membership. This is called Federation metadata and it can reside in any
ebXML Registry (usually one of the members but does not have to be). A
client issues a federated query to any federation member without
needing to know of or specify the members. The federation member
dispatches the query as a parallel distributed query across all
reachable Federation members and then awaits the responses. It then
joins the responses in a unified response and return it to the client.
Partial results are handled as warnings.