Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
MIME-Version: 1.0
In-Reply-To: <55b16bd5-5652-6fe3-dfb9-b2c27c2a37dd@averbis.com>
References: <CAA3ojm8AHXBGkf9BAk1=jdG-yiDah7OqpLQfwrJvBCxYLp0Ezg@mail.gmail.com>
 <a43e982c-38a2-d82d-f6f5-682b612c8d87@averbis.com> <CAA3ojm-9ifJJMjvZWqWiP=AseieqEuUmx2U2wkb3VRg__zO9CA@mail.gmail.com>
 <64dc83e5-e21f-bc71-7668-899338f86d2d@averbis.com> <78958a00-8a4b-bb1a-f35e-744ea20a6aae@averbis.com>
 <CAA3ojm8fvJyvdLb0tr_EK=p81gzmwDzizFR7hKhjOSw+3jfvXg@mail.gmail.com>
 <CAA3ojm_E2WXEiZinW3uSz=k2CQgCJuo7BcwA2d_P=e=s6kjhNA@mail.gmail.com> <55b16bd5-5652-6fe3-dfb9-b2c27c2a37dd@averbis.com>
From: =?UTF-8?Q?Jos=C3=A9_Vicente_Moyano_Murillo?= <moyanoj@aia.es>
Date: Thu, 23 Feb 2017 13:47:31 +0100
Message-ID: <CAA3ojm8ta9yvmfNd5z6dX-h5Vr3pp1k-W+HjXXqYDOxL3jzJOg@mail.gmail.com>
Subject: Re: Using RUTA
To: user@uima.apache.org
Content-Type: multipart/alternative; boundary=94eb2c0e773e3e347d05493204b3
archived-at: Thu, 23 Feb 2017 12:48:47 -0000

--94eb2c0e773e3e347d05493204b3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

ruta-core.jar it's enough.

It will be fantastic if i could access the snapshot repository.

2017-02-23 13:03 GMT+01:00 Peter Kl=C3=BCgl <peter.kluegl@averbis.com>:

> Hi,
>
>
> what do you need? Only ruta-core.jar or also the Eclipse plugins/update
> site?
>
> I will prepare a new RC for the next release soon.
>
> There should be snapshot artifacts built by jenkins in the snapshot
> repository. I am out-of-office today so do not have the link right now. (=
If
> you want to build it yourself, the svn source repo can be accessed by
> anyone)
>
>
> Best,
>
>
> Peter
>
>
>
>
> Am 23.02.2017 um 08:06 schrieb Jos=C3=A9 Vicente Moyano Murillo:
>
>> Hi Peter, good morning.
>>
>> Have we any opportunity to get a fixed version? I mean a snapshot or an
>> access to the repo.
>>
>> Regards
>>
>> 2017-02-22 10:38 GMT+01:00 Jos=C3=A9 Vicente Moyano Murillo <moyanoj@aia=
.es>:
>>
>> you're right
>>>
>>> % is performing some kind of "or".
>>>
>>> So we will wait for the new release.
>>>
>>> Many thanks
>>>
>>> 2017-02-22 9:54 GMT+01:00 Peter Kl=C3=BCgl <peter.kluegl@averbis.com>:
>>>
>>> I actually wonder why your rules work. I am quite sure that they match
>>>> too often, i. e. they match also if only one of the conjunct rule
>>>> elements match.
>>>>
>>>> You can simply try that by using a wrong string in the check like "NG"
>>>> instead of "Neil Gaiman"
>>>>
>>>> Anyways, the problem will be fixed in a few minutes and will be part o=
f
>>>> the next release.
>>>>
>>>>
>>>> Best,
>>>>
>>>>
>>>> Peter
>>>>
>>>>
>>>> Am 22.02.2017 um 09:38 schrieb Peter Kl=C3=BCgl:
>>>>
>>>>> Thanks. Maybe its just a bug in 2.5.0 I already fixed. I'll investiga=
te
>>>>>
>>>> it.
>>>>
>>>>>
>>>>> Am 22.02.2017 um 09:24 schrieb Jos=C3=A9 Vicente Moyano Murillo:
>>>>>
>>>>>> Thank you very much Peter. Your advice was amazing.
>>>>>>
>>>>>> We tried the first option using Conjunct rules and as you said it do=
es
>>>>>>
>>>>> not
>>>>
>>>>> work with version 2.5.0. But we change a little your example and it
>>>>>>
>>>>> works
>>>>
>>>>> perfectly witn 2.4.0 and 2.5.0
>>>>>>
>>>>>> We use theses examples with success:
>>>>>>
>>>>>> DECLARE Annotation RuleDetection;
>>>>>>   Book{ -> CREATE(NeilsBook) } <- {
>>>>>>        Attribute{Attribute.name=3D=3D"title", Attribute.ct=3D=3D"Nor=
se
>>>>>>
>>>>> Mythology"}"
>>>>
>>>>>        %
>>>>>>                Attribute{Attribute.name=3D=3D"author",
>>>>>> Attribute.ct=3D=3D"Neil
>>>>>> Gaiman"};"
>>>>>>   };
>>>>>>
>>>>>>
>>>>>> DECLARE Annotation RuleDetection;
>>>>>>   Book{ -> CREATE(NeilsBook) } <- {
>>>>>>         Attribute{FEATURE("name","title"), FEATURE("ct", "Norse
>>>>>>
>>>>> Mythology")}"
>>>>
>>>>>        %
>>>>>>                 Attribute{FEATURE("name","author"), FEATURE("ct",
>>>>>> "Neil
>>>>>> Gaiman")};
>>>>>>   };
>>>>>>
>>>>>> DECLARE Annotation RuleDetection;
>>>>>>   Book{ -> CREATE(NeilsBook) } <- {
>>>>>>        Attribute{Attribute.name=3D=3D"title", Attribute.ct=3D=3D"Nor=
se
>>>>>>
>>>>> Mythology"}"
>>>>
>>>>>        %
>>>>>>                 Attribute{FEATURE("name","author"), FEATURE("ct",
>>>>>> "Neil
>>>>>> Gaiman")};
>>>>>>   };
>>>>>>
>>>>>>
>>>>>> May be the problem is with when we use Identifiers:
>>>>>>     a1:Attribute and  a2:Attribute
>>>>>>
>>>>>> In any case thank you very much for your help.
>>>>>>
>>>>>>
>>>>>> 2017-02-21 17:46 GMT+01:00 Peter Kl=C3=BCgl <peter.kluegl@averbis.co=
m>:
>>>>>>
>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>> I'd normally say that you need the conjunt rules construct to speci=
fy
>>>>>>>
>>>>>> an
>>>>
>>>>> AND between two rule element independent of the position:
>>>>>>>
>>>>>>>
>>>>>>> Book{-> NeilsBook}<-{
>>>>>>>      a1:Attribute{a1.name=3D=3D"title", a1.ct=3D=3D"Norse Mythology=
"}
>>>>>>>      % a2:Attribute{a2.name=3D=3D"author", a2.ct=3D=3D"Neil Gaiman"=
};
>>>>>>>      };
>>>>>>>
>>>>>>>
>>>>>>> However, I just noted that there is a problem with conjunct rules. =
I
>>>>>>> haven't used it in a long time and the test coverage much lower tha=
n
>>>>>>>
>>>>>> the
>>>>
>>>>> other constructs. I'll create a ticket for it and fix it.
>>>>>>>
>>>>>>>
>>>>>>> Without conjunct rules, you need some boolean variables for cheking
>>>>>>>
>>>>>> the
>>>>
>>>>> AND, which looks all but declarative:
>>>>>>>
>>>>>>>
>>>>>>> BOOLEAN ft, fa;
>>>>>>> FOREACH(book) Book{}{
>>>>>>>      book{-> ft =3D false, fa =3D false};
>>>>>>>      book->{a1:Attribute{a1.name=3D=3D"title", a1.ct=3D=3D"Norse
>>>>>>> Mythology"->
>>>>>>> ft=3Dtrue};};
>>>>>>>      book->{a2:Attribute{a2.name=3D=3D"author", a2.ct=3D=3D"Neil Ga=
iman"->
>>>>>>> fa=3Dtrue};};
>>>>>>>      book{ft,fa -> NeilsBook};
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>> ... or with a BLOCK...
>>>>>>>
>>>>>>>
>>>>>>> BLOCK(book) Book{}{
>>>>>>>      Document{-> ft =3D false, fa =3D false};
>>>>>>>      a1:Attribute{a1.name=3D=3D"title", a1.ct=3D=3D"Norse Mythology=
"->
>>>>>>>
>>>>>> ft=3Dtrue};
>>>>
>>>>>      a2:Attribute{a2.name=3D=3D"author", a2.ct=3D=3D"Neil Gaiman"-> f=
a=3Dtrue};
>>>>>>>      Document{ft,fa -> NeilsBook};
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>> If the order of the attributes is known, you can avoid the AND chec=
k
>>>>>>>
>>>>>> and
>>>>
>>>>> just specify a sequential constraint:
>>>>>>>
>>>>>>>
>>>>>>> Book{-> NeilsBook}<-{
>>>>>>>      a1:Attribute{a1.name=3D=3D"title", a1.ct=3D=3D"Norse Mythology=
"}
>>>>>>>      # a2:Attribute{a2.name=3D=3D"author", a2.ct=3D=3D"Neil Gaiman"=
};
>>>>>>>      };
>>>>>>>
>>>>>>>
>>>>>>> If you need to check on the complete title with the URL, you can
>>>>>>>
>>>>>> replace
>>>>
>>>>> the coveredText comparison with a REGEXP condition.
>>>>>>>
>>>>>>>
>>>>>>> (tested with UIMA Ruta 2.5.0)
>>>>>>>
>>>>>>>
>>>>>>> Best,
>>>>>>>
>>>>>>>
>>>>>>> Peter
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 21.02.2017 um 13:58 schrieb Jos=C3=A9 Vicente Moyano Murillo:
>>>>>>>
>>>>>>>> Hello everyone
>>>>>>>>
>>>>>>>> I'm planning to use RUTA to create some annotations. But i'm not
>>>>>>>>
>>>>>>> able to
>>>>
>>>>> accomplish my objective.
>>>>>>>>
>>>>>>>> This is my case right now:
>>>>>>>>
>>>>>>>> I have a text annotated with some annotations "*Book*".
>>>>>>>>
>>>>>>>> Under "*Book*" annotation i have a few annotations "*Attribute*"
>>>>>>>> that
>>>>>>>> stores some information about the book. Each "*Attribute*" has a
>>>>>>>>
>>>>>>> feature
>>>>
>>>>> "
>>>>>>>
>>>>>>>> *name*" and a feature "*parent*" to its parent (one "*Book*"
>>>>>>>>
>>>>>>> annotation).
>>>>
>>>>> And example could be a text with 2 "*Book*" annotations:
>>>>>>>>
>>>>>>>> "*Book*" annotation number 1 with 3 nested attributes
>>>>>>>> 1.- *Attribute* with name feature equals "title" -> covered text:
>>>>>>>>
>>>>>>> "Norse
>>>>
>>>>> Mythology
>>>>>>>> <http://www.barnesandnoble.com/w/norse-mythology-neil-
>>>>>>>>
>>>>>>> gaiman/1124023596;jsessionid=3DFD1D8F9690602616CA59B38CFE9290
>>>>>>> 06.prodny_store02-atgap08?ean=3D9780393609097>
>>>>>>>
>>>>>>>> "
>>>>>>>> 2.- *Attribute* with name feature equals "author" ->  covered text=
:
>>>>>>>>
>>>>>>> "Neil
>>>>
>>>>> Gaiman"
>>>>>>>> 3.- *Attribute* with name feature equals "language" - > covered
>>>>>>>> text:
>>>>>>>> "English"
>>>>>>>>
>>>>>>>>
>>>>>>>> "*Book*" annotation number 2 with 3 nested attributes
>>>>>>>> 1.- *Attribute* with name feature equals "title" -> covered text:
>>>>>>>>
>>>>>>> "Never
>>>>
>>>>> Never
>>>>>>>> <http://www.barnesandnoble.com/w/never-never-james-patterson
>>>>>>>>
>>>>>>> /1123863634;
>>>>
>>>>> jsessionid=3DFD1D8F9690602616CA59B38CFE929006.prodny_store02-
>>>>>>>
>>>>>> atgap08?ean=3D
>>>>
>>>>> 9780316433174>
>>>>>>>
>>>>>>>> "
>>>>>>>> 2.- *Attribute* with name feature equals "author" ->  covered text=
:
>>>>>>>>
>>>>>>> "James
>>>>>>>
>>>>>>>> Patterson"
>>>>>>>> 3.- *Attribute* with name feature equals "language" - > covered
>>>>>>>> text:
>>>>>>>> "English"
>>>>>>>>
>>>>>>>> I need to respect this schema but i have this question:
>>>>>>>> It is possible to create and annotation over a book for a given
>>>>>>>>
>>>>>>> author
>>>>
>>>>> name
>>>>>>>
>>>>>>>> and a given title name?
>>>>>>>>
>>>>>>>> Thank's in advance
>>>>>>>>
>>>>>>>>
>>>>
>

--94eb2c0e773e3e347d05493204b3--