Jenda Krynicky writes:
> From: Aristotle Pagaltzis <[EMAIL PROTECTED]>
>
> > * Jenda Krynicky <[EMAIL PROTECTED]> [2008-06-14 01:25]:
> >
> > > I don't like XML::Plist. I would not have any idea what kind of
> > > list is it supposed to mean. And I bet there's quite a few others
> > > in the same situation. If it's something Apple specific, let's say
> > > that in the name. Whether it'd be "Apple", "Mac" or "iTunes" I
> > > don't care.
> >
> > If you don´t know what a plist is, you are not part of the target
> > audience for the module in any case. Maybe XML::ApplePlist.
>
> I know I'm not in the targeted audience if it meantions Apple, Mac or
> iTunes, I don't know I'm not if it says just Plist and is in a
> namespace that's inhabited mostly by all kinds of XML parsers,
> general and specific alike.
Quite.
> Which in itself is a problem. I think the specific parsers should
> actually never been included in that namespace. I think the XML::
> namespace should be inhabited by general XML processing modules and by
> formats and technologies that are more or less part of the XML suite
> of standards. DTD, Schema, XSLT, XPath, RSS?, ...
Using XML:: makes sense if the purpose of the module is to do something
with XML ("Hmmm, I've got this XML data -- I know, a plist would be a
good way of handling that").
Whereas if it's purpose is to handle a particular Apple format ("I've
got this plist; how can I deal with that in Perl?"), then that should be
what is emphasized in the name.
Smylers
