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: <a43e982c-38a2-d82d-f6f5-682b612c8d87@averbis.com>
References: <CAA3ojm8AHXBGkf9BAk1=jdG-yiDah7OqpLQfwrJvBCxYLp0Ezg@mail.gmail.com>
 <a43e982c-38a2-d82d-f6f5-682b612c8d87@averbis.com>
From: =?UTF-8?Q?Jos=C3=A9_Vicente_Moyano_Murillo?= <moyanoj@aia.es>
Date: Wed, 22 Feb 2017 09:24:37 +0100
Message-ID: <CAA3ojm-9ifJJMjvZWqWiP=AseieqEuUmx2U2wkb3VRg__zO9CA@mail.gmail.com>
Subject: Re: Using RUTA
To: user@uima.apache.org
Content-Type: multipart/alternative; boundary=001a114f4b3c2eed0e05491a3a99
archived-at: Wed, 22 Feb 2017 08:24:53 -0000

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

Thank you very much Peter. Your advice was amazing.

We tried the first option using Conjunct rules and as you said it does 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"Norse Mytho=
logy"}"
      %
              Attribute{Attribute.name=3D=3D"author", Attribute.ct=3D=3D"Ne=
il
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"Norse Mytho=
logy"}"
      %
               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.com>:

> Hi,
>
>
> I'd normally say that you need the conjunt rules construct to specify 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 than 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 Gaiman"->
> 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"-> fa=3Dt=
rue};
>     Document{ft,fa -> NeilsBook};
> }
>
>
> If the order of the attributes is known, you can avoid the AND check 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 t=
o
> > 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 featur=
e
> "
> > *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: "Nors=
e
> > 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: "Ne=
il
> > 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: "Neve=
r
> > 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
> >
>
>

--001a114f4b3c2eed0e05491a3a99--