You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@opennlp.apache.org by Richard Zowalla <rz...@apache.org> on 2024/10/29 12:22:45 UTC
[DISCUSS] Move "opennlp-brat-annotator" back to sandbox
Hi everyone,
I was looking at removing the Jackson dependencies in the OpenNLP core and noticed that there is "opennlp-brat-annotator" which was moved from the sandbox to the core in OPENNLP-867.
Looking at the name finder resource, it's just a web service that doesn't actually use the model parameter and doesn’t bring much value to the core project.
I even doubt, that anybody is using it.There are no tests.
Therefore, I would like to propose that this component be moved back to the sandbox, as the module does not provide any value (IMHO) as it just bloats our binary distribution.
If anyone actually useds it (from the core project), there is still the possibility to build from sandbox or just copy the related code to their projects.
From my POV, these two classes do not offer much value.
If we want to provide such a web service layer (in the future), we should adhere to Jakarta EE standard and just bundle a WAR application, which can be deployed in any EE application server to serve OpenNLP capabilities via REST.
This could be started via a Maven plugin or in a standalone server context. However, this has some other limitations in terms of resource loading, but if there is interest, we could do that in a separate feature request.
Gruß
Richard
Re: [DISCUSS] Move "opennlp-brat-annotator" back to sandbox
Posted by Richard Zowalla <rz...@apache.org>.
Looks like we reached consensus on moving it. I will put my PRs into ready to review state.
Gruß
Richard
On 2024/10/29 12:22:45 Richard Zowalla wrote:
> Hi everyone,
>
> I was looking at removing the Jackson dependencies in the OpenNLP core and noticed that there is "opennlp-brat-annotator" which was moved from the sandbox to the core in OPENNLP-867.
>
> Looking at the name finder resource, it's just a web service that doesn't actually use the model parameter and doesn’t bring much value to the core project.
> I even doubt, that anybody is using it.There are no tests.
>
> Therefore, I would like to propose that this component be moved back to the sandbox, as the module does not provide any value (IMHO) as it just bloats our binary distribution.
> If anyone actually useds it (from the core project), there is still the possibility to build from sandbox or just copy the related code to their projects.
>
> From my POV, these two classes do not offer much value.
>
> If we want to provide such a web service layer (in the future), we should adhere to Jakarta EE standard and just bundle a WAR application, which can be deployed in any EE application server to serve OpenNLP capabilities via REST.
> This could be started via a Maven plugin or in a standalone server context. However, this has some other limitations in terms of resource loading, but if there is interest, we could do that in a separate feature request.
>
> Gruß
> Richard
Re: [DISCUSS] Move "opennlp-brat-annotator" back to sandbox
Posted by Eric Pugh <ep...@opensourceconnections.com>.
Not a binding voter here, but that is the point of sandboxes right!? Let things mature that maybe aren’t quite ready.
> On Oct 29, 2024, at 8:46 AM, Jeff Zemerick <jz...@apache.org> wrote:
>
> I am +1 to moving it back to the sandbox. It has been a long time since I
> have heard of it being used.
>
> Thanks,
> Jeff
>
> On Tue, Oct 29, 2024 at 8:23 AM Richard Zowalla <rz...@apache.org> wrote:
>
>> Hi everyone,
>>
>> I was looking at removing the Jackson dependencies in the OpenNLP core and
>> noticed that there is "opennlp-brat-annotator" which was moved from the
>> sandbox to the core in OPENNLP-867.
>>
>> Looking at the name finder resource, it's just a web service that doesn't
>> actually use the model parameter and doesn’t bring much value to the core
>> project.
>> I even doubt, that anybody is using it.There are no tests.
>>
>> Therefore, I would like to propose that this component be moved back to
>> the sandbox, as the module does not provide any value (IMHO) as it just
>> bloats our binary distribution.
>> If anyone actually useds it (from the core project), there is still the
>> possibility to build from sandbox or just copy the related code to their
>> projects.
>>
>> From my POV, these two classes do not offer much value.
>>
>> If we want to provide such a web service layer (in the future), we should
>> adhere to Jakarta EE standard and just bundle a WAR application, which can
>> be deployed in any EE application server to serve OpenNLP capabilities via
>> REST.
>> This could be started via a Maven plugin or in a standalone server
>> context. However, this has some other limitations in terms of resource
>> loading, but if there is interest, we could do that in a separate feature
>> request.
>>
>> Gruß
>> Richard
_______________________
Eric Pugh | Founder | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal>
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
Re: [DISCUSS] Move "opennlp-brat-annotator" back to sandbox
Posted by Bruno Kinoshita <br...@gmail.com>.
No objections from me, +1 as well.
On Tue, 29 Oct 2024, 13:53 Martin Wiesner, <ma...@apache.org> wrote:
> Hi all,
>
> In line with Jeff and Richard, I agree to transfer it (back) over to our
> opennlp-sandbox.
> The component in question does not really have great value, it seems.
>
> It shall exist in the sandbox for those people that require an example on
> how to build a web service on top of opennlp-tools.
> Maybe, someone comes along and puts some time and effort into the code
> with tests and better docs.
>
> Best,
> Martin
>
>
> > Am 29.10.2024 um 13:46 schrieb Jeff Zemerick <jz...@apache.org>:
> >
> > I am +1 to moving it back to the sandbox. It has been a long time since I
> > have heard of it being used.
> >
> > Thanks,
> > Jeff
> >
> > On Tue, Oct 29, 2024 at 8:23 AM Richard Zowalla <rz...@apache.org> wrote:
> >
> >> Hi everyone,
> >>
> >> I was looking at removing the Jackson dependencies in the OpenNLP core
> and
> >> noticed that there is "opennlp-brat-annotator" which was moved from the
> >> sandbox to the core in OPENNLP-867.
> >>
> >> Looking at the name finder resource, it's just a web service that
> doesn't
> >> actually use the model parameter and doesn’t bring much value to the
> core
> >> project.
> >> I even doubt, that anybody is using it.There are no tests.
> >>
> >> Therefore, I would like to propose that this component be moved back to
> >> the sandbox, as the module does not provide any value (IMHO) as it just
> >> bloats our binary distribution.
> >> If anyone actually useds it (from the core project), there is still the
> >> possibility to build from sandbox or just copy the related code to their
> >> projects.
> >>
> >> From my POV, these two classes do not offer much value.
> >>
> >> If we want to provide such a web service layer (in the future), we
> should
> >> adhere to Jakarta EE standard and just bundle a WAR application, which
> can
> >> be deployed in any EE application server to serve OpenNLP capabilities
> via
> >> REST.
> >> This could be started via a Maven plugin or in a standalone server
> >> context. However, this has some other limitations in terms of resource
> >> loading, but if there is interest, we could do that in a separate
> feature
> >> request.
> >>
> >> Gruß
> >> Richard
>
>
>
Re: [DISCUSS] Move "opennlp-brat-annotator" back to sandbox
Posted by Richard Zowalla <rz...@apache.org>.
Looking at the related website and the GitHub repo for Brat, it looks like the brat project is dead anyway ...
> Am 29.10.2024 um 13:52 schrieb Martin Wiesner <ma...@apache.org>:
>
> Hi all,
>
> In line with Jeff and Richard, I agree to transfer it (back) over to our opennlp-sandbox.
> The component in question does not really have great value, it seems.
>
> It shall exist in the sandbox for those people that require an example on how to build a web service on top of opennlp-tools.
> Maybe, someone comes along and puts some time and effort into the code with tests and better docs.
>
> Best,
> Martin
>
>
>> Am 29.10.2024 um 13:46 schrieb Jeff Zemerick <jz...@apache.org>:
>>
>> I am +1 to moving it back to the sandbox. It has been a long time since I
>> have heard of it being used.
>>
>> Thanks,
>> Jeff
>>
>> On Tue, Oct 29, 2024 at 8:23 AM Richard Zowalla <rz...@apache.org> wrote:
>>
>>> Hi everyone,
>>>
>>> I was looking at removing the Jackson dependencies in the OpenNLP core and
>>> noticed that there is "opennlp-brat-annotator" which was moved from the
>>> sandbox to the core in OPENNLP-867.
>>>
>>> Looking at the name finder resource, it's just a web service that doesn't
>>> actually use the model parameter and doesn’t bring much value to the core
>>> project.
>>> I even doubt, that anybody is using it.There are no tests.
>>>
>>> Therefore, I would like to propose that this component be moved back to
>>> the sandbox, as the module does not provide any value (IMHO) as it just
>>> bloats our binary distribution.
>>> If anyone actually useds it (from the core project), there is still the
>>> possibility to build from sandbox or just copy the related code to their
>>> projects.
>>>
>>> From my POV, these two classes do not offer much value.
>>>
>>> If we want to provide such a web service layer (in the future), we should
>>> adhere to Jakarta EE standard and just bundle a WAR application, which can
>>> be deployed in any EE application server to serve OpenNLP capabilities via
>>> REST.
>>> This could be started via a Maven plugin or in a standalone server
>>> context. However, this has some other limitations in terms of resource
>>> loading, but if there is interest, we could do that in a separate feature
>>> request.
>>>
>>> Gruß
>>> Richard
>
>
Re: [DISCUSS] Move "opennlp-brat-annotator" back to sandbox
Posted by Martin Wiesner <ma...@apache.org>.
Hi all,
In line with Jeff and Richard, I agree to transfer it (back) over to our opennlp-sandbox.
The component in question does not really have great value, it seems.
It shall exist in the sandbox for those people that require an example on how to build a web service on top of opennlp-tools.
Maybe, someone comes along and puts some time and effort into the code with tests and better docs.
Best,
Martin
> Am 29.10.2024 um 13:46 schrieb Jeff Zemerick <jz...@apache.org>:
>
> I am +1 to moving it back to the sandbox. It has been a long time since I
> have heard of it being used.
>
> Thanks,
> Jeff
>
> On Tue, Oct 29, 2024 at 8:23 AM Richard Zowalla <rz...@apache.org> wrote:
>
>> Hi everyone,
>>
>> I was looking at removing the Jackson dependencies in the OpenNLP core and
>> noticed that there is "opennlp-brat-annotator" which was moved from the
>> sandbox to the core in OPENNLP-867.
>>
>> Looking at the name finder resource, it's just a web service that doesn't
>> actually use the model parameter and doesn’t bring much value to the core
>> project.
>> I even doubt, that anybody is using it.There are no tests.
>>
>> Therefore, I would like to propose that this component be moved back to
>> the sandbox, as the module does not provide any value (IMHO) as it just
>> bloats our binary distribution.
>> If anyone actually useds it (from the core project), there is still the
>> possibility to build from sandbox or just copy the related code to their
>> projects.
>>
>> From my POV, these two classes do not offer much value.
>>
>> If we want to provide such a web service layer (in the future), we should
>> adhere to Jakarta EE standard and just bundle a WAR application, which can
>> be deployed in any EE application server to serve OpenNLP capabilities via
>> REST.
>> This could be started via a Maven plugin or in a standalone server
>> context. However, this has some other limitations in terms of resource
>> loading, but if there is interest, we could do that in a separate feature
>> request.
>>
>> Gruß
>> Richard
Re: [DISCUSS] Move "opennlp-brat-annotator" back to sandbox
Posted by Eric Pugh <ep...@opensourceconnections.com>.
Not a binding voter here, but that is the point of sandboxes right!? Let things mature that maybe aren’t quite ready.
> On Oct 29, 2024, at 8:46 AM, Jeff Zemerick <jz...@apache.org> wrote:
>
> I am +1 to moving it back to the sandbox. It has been a long time since I
> have heard of it being used.
>
> Thanks,
> Jeff
>
> On Tue, Oct 29, 2024 at 8:23 AM Richard Zowalla <rz...@apache.org> wrote:
>
>> Hi everyone,
>>
>> I was looking at removing the Jackson dependencies in the OpenNLP core and
>> noticed that there is "opennlp-brat-annotator" which was moved from the
>> sandbox to the core in OPENNLP-867.
>>
>> Looking at the name finder resource, it's just a web service that doesn't
>> actually use the model parameter and doesn’t bring much value to the core
>> project.
>> I even doubt, that anybody is using it.There are no tests.
>>
>> Therefore, I would like to propose that this component be moved back to
>> the sandbox, as the module does not provide any value (IMHO) as it just
>> bloats our binary distribution.
>> If anyone actually useds it (from the core project), there is still the
>> possibility to build from sandbox or just copy the related code to their
>> projects.
>>
>> From my POV, these two classes do not offer much value.
>>
>> If we want to provide such a web service layer (in the future), we should
>> adhere to Jakarta EE standard and just bundle a WAR application, which can
>> be deployed in any EE application server to serve OpenNLP capabilities via
>> REST.
>> This could be started via a Maven plugin or in a standalone server
>> context. However, this has some other limitations in terms of resource
>> loading, but if there is interest, we could do that in a separate feature
>> request.
>>
>> Gruß
>> Richard
_______________________
Eric Pugh | Founder | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal>
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
Re: [DISCUSS] Move "opennlp-brat-annotator" back to sandbox
Posted by Jeff Zemerick <jz...@apache.org>.
I am +1 to moving it back to the sandbox. It has been a long time since I
have heard of it being used.
Thanks,
Jeff
On Tue, Oct 29, 2024 at 8:23 AM Richard Zowalla <rz...@apache.org> wrote:
> Hi everyone,
>
> I was looking at removing the Jackson dependencies in the OpenNLP core and
> noticed that there is "opennlp-brat-annotator" which was moved from the
> sandbox to the core in OPENNLP-867.
>
> Looking at the name finder resource, it's just a web service that doesn't
> actually use the model parameter and doesn’t bring much value to the core
> project.
> I even doubt, that anybody is using it.There are no tests.
>
> Therefore, I would like to propose that this component be moved back to
> the sandbox, as the module does not provide any value (IMHO) as it just
> bloats our binary distribution.
> If anyone actually useds it (from the core project), there is still the
> possibility to build from sandbox or just copy the related code to their
> projects.
>
> From my POV, these two classes do not offer much value.
>
> If we want to provide such a web service layer (in the future), we should
> adhere to Jakarta EE standard and just bundle a WAR application, which can
> be deployed in any EE application server to serve OpenNLP capabilities via
> REST.
> This could be started via a Maven plugin or in a standalone server
> context. However, this has some other limitations in terms of resource
> loading, but if there is interest, we could do that in a separate feature
> request.
>
> Gruß
> Richard