I have to agree with Glen: -1. It's hard enough in general for people to keep track of what the different specifications in this space are supposed to be doing; I don't think that we need to make it hard for them to connect the specification to the implementation as well. (I would also argue against calling it 'Apache Rules' for that same reason.)
-Bill On Mon, 2006-04-17 at 09:08 -0400, Glen Daniels wrote: > Hi folks: > > >> IMO *Apache Commons Policy* is too generic as the brand name of this > >> project I propose *Apache Neethi* as the brand name instead. > >> > >> Neethi -- It is Sinhalese term for rules. Policy is some sense the set > >> of rules which describes nature of the service contract of the web > >> service provider. Hence I think it is a proper term as the brand name > >> for the project. > > Sorry, but -1 from me. I think Apache Commons Policy is a perfect name > for the package, because it says what it is. Case in point - I think > Apache Commons Logging is a great name for that project too. > > Let's leave it clear and simple without forcing people to say "Neethi, > what's that?" (yes I understand that Sinhalese speakers might well be > able to do that, but we've already got quite a few Sinhalese names.... :)) > > --Glen > > P.S. If people are really wanting to change it, I'd suggest "Policy4J" > is a much clearer alternative which works for both english and sinhalese.
