Re: Module Naming & Relevancy

On 6/9/22 21:02, Brian Erickson wrote:
> I am developing a module for interacting with the United States PACER
> (Public Access to Court Electronic Records) API.  PACER is a US government
> service that provides access to over one billion documents relating to
> cases that were, or are being, tried before US district courts, US court of
> appeals, or US bankruptcy courts.
> 
> https://pacer.uscourts.gov/about-us
> 
> While the PACER API enables relatively easy access to the service, a module
> in CPAN would increase accessibility.  Increasing public access to court
> records could result in unforeseen good.  There are several Python projects
> on GitHub.com for interfacing with PACER.
> 
> Before I started developing this module, I searched CPAN for existing code
> but found nothing relevant.  I've found modules for getting US Census,
> Postal Service, as well as Treasury Department's OFAC (Office of Foreign
> Assets Control) data but nothing related to the judicial system of any
> country.
> 
> Any suggestions for an appropriate package name?  I was thinking perhaps
> Court::US::PACER or USCourt::PACER.
> 
> I appreciate any and all comments.
> 
> -Brian Erickson


It appears that 'WWW' is the appropriate top-level CPAN name for Perl 
distributions that provide programmatic interfaces to web servers:

     https://metacpan.org/search?q=www


(It also appears that those authors stripped the TLDN from the target 
server FQDN when naming their distributions.  That may have seemed okay 
30 years ago, but I would advise against it today.)


'WWW' followed by the reverse fully-qualified domain name of the server 
would make sense to me:

     WWW::Gov::USCourts::PACER


David