Re: Current summary of Label for Top Node of "triangle diagram"

Dave,

Here's an updated table with my votes(s) clarified:

Preferences:
Web Services Registry : DaveO, Heather, EricN, Joel, ChrisF, DaveH#3, MarkJ#2
Discover Mechanism: Igor
Discovery Agency: ChrisF#2, MarkJ#1
Advertising and Discovery Services/Mechanisms: DaveH#1
Services Description and Discovery: DaveH#2, Mike Champion
the Web: DavidB

Really don't like:
* Registry: DavidB
the Web: Many people


Also, +1 on not liking "the Web".

--mark

Mark Jones
AT&T

	From www-ws-arch-request@w3.org Wed Oct  2 16:31 EDT 2002
	X-UIDL: O6&"!inX"!l_Y"!@2H!!
	Delivered-To: jones@research.att.com
	X-Authentication-Warning: mail-pink.research.att.com: postfixfilter set sender to www-ws-arch-request@w3.org using -f
	Resent-Date: Wed, 2 Oct 2002 16:31:24 -0400 (EDT)
	Resent-Message-Id: <200210022031.g92KVOL05073@frink.w3.org>
	From: "David Orchard" <dorchard@bea.com>
	To: <www-ws-arch@w3.org>
	Date: Wed, 2 Oct 2002 13:21:39 -0700
	MIME-Version: 1.0
	Content-Transfer-Encoding: 7bit
	X-Priority: 3 (Normal)
	X-MSMail-Priority: Normal
	Importance: Normal
	X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
	Subject: Current summary of Label for Top Node of "triangle diagram"
	Resent-From: www-ws-arch@w3.org
	X-Mailing-List: <www-ws-arch@w3.org> archive/latest/2824
	X-Loop: www-ws-arch@w3.org
	Resent-Sender: www-ws-arch-request@w3.org
	List-Id: <www-ws-arch.w3.org>
	List-Help: <http://www.w3.org/Mail/>
	List-Unsubscribe: <mailto:www-ws-arch-request@w3.org?subject=unsubscribe>
	X-Spam-Status: No, hits=-3.1 required=5.0 tests=IN_REP_TO,MAY_BE_FORGED version=2.20


	After a week of spirited debate, I've gone through and summarized as best I
	can the leanings of people.

	Preferences:
	Web Services Registry : DaveO, Heather, EricN, Joel, ChrisF, DaveH#3( he
	preferred Services Registry for his 3rd choice but it seemed to fit in
	here), maybe Mark Jones - he +1 to a message from Heather.
	Discover Mechanism: Igor
	Discovery Agency: ChrisF#2
	Advertising and Discovery Services/Mechanisms: DaveH#1
	Services Description and Discovery: DaveH#2, Mike Champion
	the Web: DavidB

	Really don't like:
	* Registry: DavidB
	the Web: Many people

	Seems that the use of Registry is ok for the most number of people but it
	also has an objection.

	I'm not sure quite how to get to consensus on this issue.  I have a feeling
	if we get to consensus, we'll be left with a term that nobody likes, but
	that nobody hates.  Which I don't think would serve any of our communities.
	Or we could do the usual standards thing and union them so that everybody
	gets their feature in: Web Services Description, Discovery and Advertising
	Registries, Agencies and Mechanisms on the Web ;-)

	To be blunt, it looks to me like Registry with a prefix of some kind is the
	one that satisfies the most with only annoying a few.  Again, not the best
	solution.

	Maybe what we could do is adopt (WS|S|{}) Registry, and then as early as
	possible show that google is an example of this.

	Personally, I'd really like to move on from this issue - time to market
	cough.  This is one term, and we've got dozens more as well as relationships
	to define.

	Cheers,
	Dave

	> -----Original Message-----
	> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
	> Behalf Of David Orchard
	> Sent: Thursday, September 26, 2002 2:26 PM
	> To: www-ws-arch@w3.org
	> 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, 3 October 2002 10:05:44 UTC