W3C home > Mailing lists > Public > www-ws-arch@w3.org > September 2002

Re: Label for Top Node of "triangle diagram"

From: Heather Kreger <kreger@us.ibm.com>
Date: Thu, 26 Sep 2002 19:47:34 -0400
To: www-ws-arch@w3.org, "David Orchard" <dorchard@bea.com>
Message-ID: <OF4B2989BE.3E242863-ON85256C40.00820C04@us.ibm.com>





Hey,
I think Registry or Registries is fine (in a minority I suppose).

I just LOVE " Web Service Registries" - qualified, plural and in a cloud
therefore distributed.

'Registry agencies' is my third place vote

To me, 'Discovery Agency' is biased for 'finding' things and
doesn't represent  interesting publication tecnologies
(like a crawling registry...).

Some other terms I've seen but don't love:
Repository (implies stores local copy rather than pointer to a copy)

Thats why in IBM we settled on 'Registry' .. it was a 'role' name like
requester and provider
and not biased towards either of their uses of it.


Heather Kreger
Web Services Lead Architect
STSM, SWG Emerging Technology
kreger@us.ibm.com
919-543-3211 (t/l 441)  cell:919-496-9572


"David Orchard" <dorchard@bea.com>@w3.org on 09/26/2002 05:26:26 PM

Sent by:    www-ws-arch-request@w3.org


To:    <www-ws-arch@w3.org>
cc:
Subject:    Label for Top Node of "triangle diagram"




This kicks off discussions about what to call the top node in our triangle
diagram.

Some of the terms bandied about (and I list these to support
brainstorming/creative works):
Registry
Registry agency
Discovery Mechanism
Publish/Discover
Advertiser
Search Engine
Metadata store

I looked up in roget's some various synonyms for registry, and I found
catalog(ue for those that write proper english:-), roster, list, roll.  I
looked at discovery and found ascertainment, find, finding, strike.  BTW, I
despise the term metadata in this context.

The way I see it, we can go one of 4 paths:
1) Label it by the function it supports - publish/discover is an example
2) Label it by a term that represent the function it supports - registry is
an example.
3) Same as #2, except we come up with a whole new term.  This has
precedent - RoyF came up with Representations because the trm document
wasn't quite right.
4) Create some modified term based on the previous, like "web service
registry"

I observe that lots of companies and people spent time figuring out these
and other terms.  The chance of us recreating something useful in a timely
manner that is different with what's gone on seems unlikely to me.

I gather that people have heartburn over the term "registry" because it
implies a solution like UDDI.  Is there any prefix that might suffice?   My
personal preference is registry with a prefix like Web Service.

Anyways, let's discuss.  And I'll add in people's suggestions and resend
the
summaries at various points.  I'd prefer to hear what people strongly like
and strongly dislike, so we can get a feel for any consensus, or even
majority of the group.

Cheers,
Dave
Received on Thursday, 26 September 2002 19:53:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:06 GMT