Re: Module Naming & Relevancy
On 11/06/2022 09:21, Neil Bowers wrote: I’d go with WebService::PACER – WebService is *one* of the standard namespaces on CPAN for this sort of module :-) You could slip a USCourt in the middle, but I don’t think that’s necessary – better to keep things simple. It's not *necessary* but it is the polite and reasonable thing to do. I'm sure it's not the only web service out there called Pacer, and if there is another then Brian's isn't any more important than they are. -- David Cantrell
Re: Module Naming & Relevancy
I think if PACER is unambiguous (there's no other Web service named PACER) then further qualification shouldn't be needed. If PACER is a single standard that could be used for multiple services other than the US courts (other countries were to implement the same service with the same api) then qualification would be at the other end... WebService::PACER::USCourt (for example). But PACER could be a term that is eventually overloaded when someone else names their own unrelated Web service PACER. While only a slim possibility I don't think forwardly ensuring unambiguous module naming wouldn't be a bad idea. Just my 2c worth. :) On Sat, Jun 11, 2022, 10:01 Tim Ka wrote: > Is it specific to `UsCourt`? Could there be later a `MexicoCourt`? > > On Sat, Jun 11, 2022, 10:22 Neil Bowers wrote: > >> Hi Brian, >> >> I’d go with WebService::PACER – WebService is *one* of the standard >> namespaces on CPAN for this sort of module :-) >> >> You could slip a USCourt in the middle, but I don’t think that’s >> necessary – better to keep things simple. >> >> Cheers, >> Neil >> >
Re: Module Naming & Relevancy
Is it specific to `UsCourt`? Could there be later a `MexicoCourt`? On Sat, Jun 11, 2022, 10:22 Neil Bowers wrote: > Hi Brian, > > I’d go with WebService::PACER – WebService is *one* of the standard > namespaces on CPAN for this sort of module :-) > > You could slip a USCourt in the middle, but I don’t think that’s necessary > – better to keep things simple. > > Cheers, > Neil >
Re: Module Naming & Relevancy
Hi Brian, I’d go with WebService::PACER – WebService is *one* of the standard namespaces on CPAN for this sort of module :-) You could slip a USCourt in the middle, but I don’t think that’s necessary – better to keep things simple. Cheers, Neil
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
