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 i
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 qua
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
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
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 befor
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
