I completely agree.  Both people who 
know AI and its history, and people who do not,
are likely to look for, or at least notice, AI.
ML will not do that.  
MachineLearning might -- but that is 
not the only possible candidate.
For example to avoid the poor connotations of 
"Data Mining" the ACM named its special interest group
SIGKDD, where KDD stands for Knowledge Discovery in Databases.  

There are many other terms that cover some or most
of this area -- but only AI has 
widespread name recognition.

I agree that adding subcategories below AI can be useful.
But I too would expect AI::ML to be about the language
ML.

 
Hopefully helpfully yours,
Steve
-- 
Steven Tolkin          [EMAIL PROTECTED]      617-563-0516 
Fidelity Investments   82 Devonshire St. V8D     Boston MA 02109
There is nothing so practical as a good theory.  Comments are by me, 
not Fidelity Investments, its subsidiaries or affiliates.

> -----Original Message-----
> From: Mike Lambert [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, April 21, 2002 9:42 PM
> To: Ken Williams
> Cc: Perl-AI
> Subject: Re: An ML:: namespace?
> 
> 
> > Reasons against might be:
> >
> >   1) "ML" isn't nearly as well-known a term as "AI", so casual
> > browsers of CPAN won't find things there as easily.
> >
> >   2) The AI:: namespace already exists and contains some
> > interesting things, and it would be a shame to split the
> > namespace without a good reason.
> 
> 3) There's already a programming language called ML, and this might
> increase confusion. Standard ML, and OCaml are two variants 
> on it. While
> I'm not advocating the creation of a namespace for that 
> language, since
> none exists for other languages, this programming language 
> was the first
> thing that came to mind for a non-ai programmer like myself.
> 
> Perhaps AI::ML::* might be a better namespace? If I we're 
> looking for a
> module that adapts or changes, I would check the AI namespace 
> first. While
> it might be a catch-all, it's a rather descriptive catch-all for these
> types of modules, and you can always subdivide the namespace 
> if it's too
> broad for your tastes.
> 
> 
> Mike Lambert
> A non-ai-programmer lurking on an ai-programmer mailing list. :)
> 

Reply via email to