Re: Module Naming & Relevancy

--000000000000195fa705e12af5f4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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 <[email protected]> wrote:

> Is it specific to `UsCourt`? Could there be later a `MexicoCourt`?
>
> On Sat, Jun 11, 2022, 10:22 Neil Bowers <[email protected]> wrote:
>
>> Hi Brian,
>>
>> I=E2=80=99d go with WebService::PACER =E2=80=93 WebService is *one* of t=
he standard
>> namespaces on CPAN for this sort of module :-)
>>
>> You could slip a USCourt in the middle, but I don=E2=80=99t think that=
=E2=80=99s
>> necessary =E2=80=93 better to keep things simple.
>>
>> Cheers,
>> Neil
>>
>

--000000000000195fa705e12af5f4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto"></div>I think if PACER is unambiguous (=
there&#39;s no other Web service named PACER) then further qualification sh=
ouldn&#39;t be needed.=C2=A0<div dir=3D"auto"><br></div><div dir=3D"auto">I=
f 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 wit=
h the same api) then qualification would be at the other end... WebService:=
:PACER::USCourt (for example).=C2=A0<div dir=3D"auto"><br></div><div dir=3D=
"auto">But PACER could be a term that is eventually overloaded when someone=
 else names their own unrelated Web service PACER. While only a slim possib=
ility I don&#39;t think forwardly ensuring unambiguous module naming wouldn=
&#39;t be a bad idea.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Ju=
st my 2c worth. :)=C2=A0</div><div dir=3D"auto"><br><div dir=3D"auto"><br><=
div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr" class=3D"gmail_attr=
">On Sat, Jun 11, 2022, 10:01 Tim Ka &lt;<a href=3D"mailto:tim.potapov@gmai=
l.com" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">tim.potap=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"auto">Is it specific to `UsCourt`? Could there be later a `MexicoCourt=
`?</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">On Sat, Jun 11, 2022, 10:22 Neil Bowers &lt;<a href=3D"mailto:neilb@neilb=
.org" rel=3D"noreferrer noreferrer noreferrer noreferrer" target=3D"_blank"=
>[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<div>
<div name=3D"messageBodySection">
<div dir=3D"auto">Hi Brian,<br>
<br>
I=E2=80=99d go with WebService::PACER =E2=80=93=C2=A0WebService is *one* of=
 the standard namespaces on CPAN for this sort of module :-)<br>
<br>
You could slip a USCourt in the middle, but I don=E2=80=99t think that=E2=
=80=99s necessary =E2=80=93=C2=A0better to keep things simple.<br>
<br>
Cheers,<br>
Neil<br></div>
</div>
</div>

</blockquote></div>
</blockquote></div></div></div></div></div>

--000000000000195fa705e12af5f4--