Return-Path: <hlship@comcast.net>
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 11646 invoked from network); 18 Sep 2003 15:19:46 -0000
Received: from unknown (HELO sccrmhc11.comcast.net) (204.127.202.55)
  by daedalus.apache.org with SMTP; 18 Sep 2003 15:19:46 -0000
Received: from almightybeast (unknown[65.114.188.240])
          by comcast.net (sccrmhc11) with SMTP
          id <2003091815194801100c8lace>
          (Authid: hlship);
          Thu, 18 Sep 2003 15:19:49 +0000
From: "Howard M. Lewis Ship" <hlship@comcast.net>
To: "'Jakarta Commons Developers List'" <commons-dev@jakarta.apache.org>
Subject: RE: [HiveMind] naming update
Date: Thu, 18 Sep 2003 11:19:41 -0400
Message-ID: <013901c37df8$48a721e0$d0020a0a@ALMIGHTYBEAST>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <000701c37df7$b2c95940$6bb6769b@NAMRAC2247>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Yeah ... the verb'ed attribute name is awkward.

The underlying problem is the simularity between:
<configuration-point id="..."> and
<configuration point-id="...">

Option A:
<configuration-point id="...">
<contribution point-id="...">

Option B:
<configuration-point id="...">
<contribution id="...">

(Don't like this one; are we defining a contribution or making a contribution?)

Option C:
<define-configuration-point id="...">
<configuration point-id="...">

(Kinda like this one ... but then should it be <define-service>?)

Other options?

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com

> -----Original Message-----
> From: james@carmanconsulting.com [mailto:james@carmanconsulting.com] 
> Sent: Thursday, September 18, 2003 11:16 AM
> To: commons-dev@jakarta.apache.org
> Subject: Re: [HiveMind] naming update
> 
> 
> I don't know if I'd put the "for" in there, but I like the 
> "implementation" idea....
> 
> <implementation service-id="yaddayaddayadda">
> 
> ----- Original Message ----- 
> From: "Howard M. Lewis Ship" <hlship@comcast.net>
> To: "'Jakarta Commons Developers List'" 
> <commons-dev@jakarta.apache.org>
> Sent: Thursday, September 18, 2003 11:00 AM
> Subject: RE: [HiveMind] naming update
> 
> 
> > Current consensus:
> >
> > <service id=> --> <service-point id=>
> > <extend-service service-id=> --> <service for-service-id=> 
> > <extension-point id=> --> <configuration-point id=> <extension 
> > point-id=> --> <configuration for-point-id=>
> >
> > ... but consider:
> >
> > <extend-service service-id=> --> <implementation for-service-id=>
> >
> > --
> > Howard M. Lewis Ship
> > Creator, Tapestry: Java Web Components 
> > http://jakarta.apache.org/tapestry
> > http://jakarta.apache.org/commons/sandbox/hivemind/
> > http://javatapestry.blogspot.com
> >
> > > -----Original Message-----
> > > From: Howard M. Lewis Ship [mailto:hlship@comcast.net]
> > > Sent: Thursday, September 18, 2003 7:39 AM
> > > To: Jakarta Commons Developers List
> > > Subject: [HiveMind] naming update
> > >
> > >
> > > 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=>
> > >
> > > Everyone seems pretty keen on this.
> > >
> > > I have minor reservations about <service> not quite 
> capturing what 
> > > the element does.  I agree that <extend-service> has some 
> unwanted 
> > > connotations.  <provide-service> perhaps? At one time it was 
> > > <contribute-service>.
> > >
> > > 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? An earlier version was 
> > > <contribute-configuration> but damn thats long.
> > >
> > > Alternately, here's my suggestion:
> > >
> > > <service> --> <define-service-point>
> > > <extend-service> --> <service>
> > > <extension-point> --> <define-configuration-point> 
> <extension> --> 
> > > <configuration>
> > >
> > >
> > >
> > >
> > > --
> > > Howard M. Lewis Ship
> > > Creator, Tapestry: Java Web Components 
> > > http://jakarta.apache.org/tapestry
> > >
> > http://jakarta.apache.org/commons/sandbox/hivemind/
> > http://javatapestry.blogspot.com
> >
> >
> > 
> ---------------------------------------------------------------------
> > 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
>