Re: Naming advice - Our World in Data

Hi Boyd,

I'd go for WebService::OurWorldInData -- you're not going to type the module name that many times, so I think the longer name is worth it:

    use WebService::OurWorldInData;
    my $owid = WebService::OurWorldInData->new(...);

When it shows up in various places, it will be more obvious what it is.

Just my 2p.

Cheers,
Neil

On 15 Jul 2025 at 11:05 +0100, Boyd Duffee <[email protected]>, wrote:
> Hi all,
>
> Having no connection to the project but just goaded into it by there only being a python client to downloading their data, I've written a Perl API for the "Our World in Data" grapher endpoint at https://ourworldindata.org
>
> After looking through the maillist archive and given that the python module for their ETL catalog endpoint is "owid-catalog", I'm thinking that WebService::Owid or WebService::OWID are the best names for this module (as mixed caps OWiD is just going to be visually confusing). It's short and descriptive.
>
> Which would you find less annoying: all caps, ucfirst? Carolingian majuscules?
> Suggestions for better names welcome.
>
> Their ETL endpoint is still in beta, but I expect to incorporate that into the same namespace at a later date.
>
> thanks,
> --
> Boyd Duffee
> > And if we put 'user fell out window' every time that happened we'd get database normalisation warnings from the helpdesk software. - BOFH: "The trouble with, er, windows installs"
> MAGA is a rehab facility for charlatans and the cancelled
> Trump is a moron whose bankruptcy was bailed out by Putin who is now pulling his strings.