Return-Path: <james@carmanconsulting.com>
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 3412 invoked from network); 18 Sep 2003 13:38:51 -0000
Received: from unknown (HELO bdsn4034.na.pg.com) (192.44.184.18)
  by daedalus.apache.org with SMTP; 18 Sep 2003 13:38:51 -0000
pgSenderHost: bdhp4103.na.pg.com [192.44.184.138]
Received: from bdhp4103.na.pg.com (bdhp4103.na.pg.com [192.44.184.138])
	by bdsn4034.na.pg.com (8.8.8/Switch-3.1.0) with ESMTP id h8IDcqgs027018
	for <commons-dev@jakarta.apache.org>; Thu, 18 Sep 2003 09:38:52 -0400 (EDT)
Received: from NAMRAC2247 ([155.118.182.107])
    by bdhp4103.na.pg.com (8.8.8/8.11.1/v2r56) with SMTP id h8IDcov16124;
 Thu, 18 Sep 2003 09:38:51 -0400 (EDT)
Message-ID: <001401c37dea$300a3360$6bb6769b@NAMRAC2247>
From: james@carmanconsulting.com
To: commons-dev@jakarta.apache.org
References: <011601c37dd9$68a7d2b0$d0020a0a@ALMIGHTYBEAST>
 <oprvo5cjhiwo6mmv@localhost> <3F69AC95.5050306@comcast.net>
 <3F69B4BB.7010502@comcast.net>
Subject: Re: [HiveMind] naming update
Date: Thu, 18 Sep 2003 09:38:47 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

How about <extension service-id=""> ?

----- Original Message ----- 
From: "Harish Krishnaswamy" <hkrishnaswamy@comcast.net>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Sent: Thursday, September 18, 2003 9:35 AM
Subject: Re: [HiveMind] naming update


> And may be even change
> 
> <extend-service service-id=> --> <service for-point-id=>
> 
> I think the same pattern will be helpful learning it easier and 
> remembering it better.
> 
> -Harish
> 
> Harish Krishnaswamy wrote:
> 
> > Absolutely with Christian. For some reason I am not very comfortable 
> > with verbs in the element names!
> >
> > -Harish
> >
> > Christian Essl wrote:
> >
> >> On Thu, 18 Sep 2003 07:38:41 -0400, Howard M. Lewis Ship 
> >> <hlship@comcast.net> wrote:
> >>
> >>> Harish's suggestion:
> >>>
> >>> <service id=> --> <service-point id=>
> >>> <extend-service service-id=> --> <service service-id=>
> >>> <extension-point id=> --> <configuration-point id=>
> >>> <extension point-id=> --> <configuration point-id=>
> >>>
> >>
> >>> Last point was the excessive simularity of <configuration-point 
> >>> id="..."> and <configuration
> >>> point-id="...">.
> >>>
> >>> Perhaps that should be <configuration for-point-id="..."> to help 
> >>> distinguish the two visually?
> >>>
> >>
> >> I think this is all right. So I would say
> >>
> >> <service id=> --> <service-point id=>
> >> <extend-service service-id=> --> <service service-id=>
> >> <extension-point id=> --> <configuration-point id=>
> >> <extension point-id=> --> <configuration for-point-id=> //only change 
> >> to Harish's suggestion
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
> 
>