Re: Naming advice - Our World in Data
[email protected] ("Stephen Patterson") Tue, 15 Jul 2025 11:13:15 +0100
| Newsgroups | perl.module-authors |
|---|---|
| Message-ID | <[email protected]> |
--0e36f39a8dd4474ab14725530bf79048 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable There are similarly capitalised modules around CPAN, such as Win32::API,= for partly acronymed names, so there's precedence, while still being re= asonably short to type. =20 -- steve On Tue, 15 Jul 2025, at 11:09 AM, Dan wrote: > On Tue, Jul 15, 2025 at 6:05=E2=80=AFAM Boyd Duffee <boyd.duffee@gmail= .com> wrote: >> Hi all, >>=20 >> 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 Per= l API for the "Our World in Data" grapher endpoint at https://ourworldin= data.org >>=20 >> After looking through the maillist archive and given that the python = module for their ETL catalog endpoint is "owid-catalog", I'm thinking th= at WebService::Owid or WebService::OWID are the best names for this modu= le (as mixed caps OWiD is just going to be visually confusing). It's sho= rt and descriptive. >>=20 >> Which would you find less annoying: all caps, ucfirst? Carolingian ma= juscules? >> Suggestions for better names welcome. >>=20 >> Their ETL endpoint is still in beta, but I expect to incorporate that= into the same namespace at a later date. >=20 > WebService::OWID seems perfectly reasonable to me and is how the organ= ization abbreviates itself in the footer of its website. >=20 > -Dan --0e36f39a8dd4474ab14725530bf79048 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><head><title></title></head><body><div>There are si= milarly capitalised modules around CPAN, such as Win32::API, for partly = acronymed names, so there's precedence, while still being reasonably sho= rt to type. </div><div><br></div><div>-- steve<br></div><div><br><= /div><div>On Tue, 15 Jul 2025, at 11:09 AM, Dan wrote:</div><blockquote = type=3D"cite" id=3D"qt" style=3D""><div dir=3D"ltr"><div dir=3D"ltr">On = Tue, Jul 15, 2025 at 6:05=E2=80=AFAM Boyd Duffee <<a href=3D"mailto:b= [email protected]">[email protected]</a>> wrote:</div><div cla= ss=3D"qt-gmail_quote qt-gmail_quote_container"><blockquote class=3D"qt-g= mail_quote" style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;m= argin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-le= ft-color:rgb(204, 204, 204);padding-left:1ex;"><div dir=3D"ltr"><div>Hi = all,</div><div><br></div><div>Having no connection to the project but ju= st goaded into it by there only being a python client to downloading the= ir data, I've written a Perl API for the "Our World in Data" grapher end= point at <a href=3D"https://ourworldindata.org" target=3D"_blank">https:= //ourworldindata.org</a></div><div><br></div><div>After looking through = the maillist archive and given that the python module for their ETL cata= log endpoint is "owid-catalog", I'm thinking that WebService::Owid or We= bService::OWID are the best names for this module (as mixed caps OWiD is= just going to be visually confusing). It's short and descriptive.</div>= <div><br></div><div>Which would you find less annoying: all caps, ucfirs= t? Carolingian majuscules?</div><div>Suggestions for better names welcom= e.</div><div><br></div><div>Their ETL endpoint is still in beta, but I e= xpect to incorporate that into the same namespace at a later date.</div>= </div></blockquote><div><br></div><div>WebService::OWID seems perfectly = reasonable to me and is how the organization abbreviates itself in the f= ooter of its website.</div><div><br></div><div>-Dan</div></div></div></b= lockquote><div><br></div></body></html> --0e36f39a8dd4474ab14725530bf79048--