Naming advice - Our World in Data

2025-07-15 Thread Boyd Duffee
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 pytho

Re: Naming advice - Our World in Data

2025-07-15 Thread Boyd Duffee
Thanks for the feedback. It helps to see someone else write it out to see what looks good. I think I'll go with the longer name and start getting WebService::OurWorldInData ready to upload. Oh, and it's Neil's WebService::HackerNews that I stole most of the API code from, having decided to try out

Re: Naming advice - Our World in Data

2025-07-15 Thread Dan
On Tue, Jul 15, 2025 at 6:05 AM Boyd Duffee 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 > > Af

Re: Naming advice - Our World in Data

2025-07-15 Thread Neil Bowers
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 obviou

Re: Naming advice - Our World in Data

2025-07-15 Thread Stephen Patterson
There are similarly capitalised modules around CPAN, such as Win32::API, for partly acronymed names, so there's precedence, while still being reasonably short to type. -- steve On Tue, 15 Jul 2025, at 11:09 AM, Dan wrote: > On Tue, Jul 15, 2025 at 6:05 AM Boyd Duffee wrote: >> Hi all, >> >>