Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
From: Hugues de Mazancourt <hugues@mazancourt.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Ruta conflicts with DKPro typesystem
Date: Tue, 11 Apr 2017 13:47:32 +0200
References: <2485A377-50C7-4649-BDE2-6BC15071081E@mazancourt.com>
 <a903ec01-fd91-4a99-3c13-e38024b3de78@averbis.com>
 <13291E6E-9D08-44E4-A92E-C2C7FAD8720C@mazancourt.com>
 <53d51209-37f1-3349-11f8-a606b2d34a7a@averbis.com>
To: user@uima.apache.org
In-Reply-To: <53d51209-37f1-3349-11f8-a606b2d34a7a@averbis.com>
Message-Id: <BC4FF744-0D4A-42A1-ACFF-9D2624D60EF7@mazancourt.com>
archived-at: Tue, 11 Apr 2017 11:47:49 -0000

>> The advantage over =C2=AB renaming =C2=BB the annotation is that it =
allows to keep syntax highlighting in  Ruta Workbench.
>=20
> Do you mean the highlighting for being a seeding type (bold grey), or
> semantic highlighting for usage in a script?

Simply the bold grey. It helps beginners to know where to find the =
definition of the annotation.

>=20
>=20
>=20
>>=20
>> Your answer raises another question: you wrote=20
>>> If you create the CAS with uimaFIT,
>>> then there are also types that are not imported in you script. Well, =
you
>>> would not even need to import the types in order to use them in your =
script.
>> I did create the CAS with uimaFIT. What kind of types are not =
imported in the script ?
>=20
> It's about what the import statement really do.
>=20
> By default, strictImport is deactivated. Here, the mentions of type
> references are resolved against the type system of the CAS given to =
the
> RutaEngine. This means that the import statements do not matter at =
all.
> They could not change the type system in the CAS anyway during
> processing the CAS. You could write rules using DKPro Core types in =
your
> rules without importing any type system since the DKPro Core types are
> included in the type system of the CAS because you created the CAS =
using
> uimaFIT, and uimaFIT adds the type system with its classpath scanning
> functionality (of course only if the type systems and types.txt are in
> the classpath).
[=E2=80=A6]

That=E2=80=99s perfectly clear, thank you.


=E2=80=94 Hugues