Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Received-SPF: pass (nike.apache.org: domain of eaepstein@gmail.com designates
 74.125.82.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=HH/vxzT3qe0ZbWDotdp8A0Zpb3kOTEc/TnvWORxUb64qvofGbLOPzb9foMPJtMO4+4
         HGfzJ7rNOh27d0vh0CzgSsXRbv39yv6UVPoCoGINufkgn9ZFT92WKigoAMjbRMep//Pu
         FS63lygJCGj4ckDRlyRxkCRb/Rq1bL8ZwTseI=
MIME-Version: 1.0
In-Reply-To: <loom.20100428T083846-715@post.gmane.org>
References: <loom.20100426T105447-208@post.gmane.org>
	 <4BD5836A.50603@schor.com> <loom.20100426T143907-932@post.gmane.org>
	 <o2zcd6edfd31004270717k6e0b16ffifae3e9f21bcf22e4@mail.gmail.com>
	 <4BD6FBD5.1090900@gmx.de>
	 <y2ocd6edfd31004271258n9a43a3cbyd05c19ee623fb829@mail.gmail.com>
	 <loom.20100428T083846-715@post.gmane.org>
Date: Wed, 28 Apr 2010 07:51:15 -0400
Message-ID: <j2zcd6edfd31004280451i8b049e4dk673f034689a6877f@mail.gmail.com>
Subject: Re: Restrictions on sofa data array
From: Eddie Epstein <eaepstein@gmail.com>
To: user@uima.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It did occur to me after that the string array may not be supported, but
this could be considered a lack of imagination in the original implementati=
on
rather than any fundamental design limitation :)

The changes to allow use of a string array for Sofa data would not be much.
Additional work probably needed for delta-CAS serialization used with remot=
e
UIMA AS service replies.

Regards,
Eddie

On Wed, Apr 28, 2010 at 3:00 AM, Klaus Rothenh=E4usler <rothenha@gmail.com>=
 wrote:
> Eddie Epstein <eaepstein@...> writes:
>
>>
>> On Tue, Apr 27, 2010 at 10:59 AM, Thilo Goetz <twgoetz@...> wrote:
>> > My understanding is that he wants the tokens as primitives,
>> > not the characters. =A0Annotation offsets could then be token
>> > offsets, not character offsets. =A0That's perfectly reasonable
>> > for some tasks. =A0We usually create annotations with the start
>> > offset being the start of some token, and the end offset the
>> > end of some token. =A0Then it's hard to find the tokens that
>> > are "covered" by the annotation, which is why we have
>> > subiterators, which are not super efficient. =A0And so on.
>> > I like the idea, but I have no idea how compatible it is with
>> > UIMA's idea of views and sofas.
>>
>> A StringArrayFS can be used as Sofa data.
>
> Are you sure? The documentation explicitly denies that
> (http://uima.apache.org/downloads/releaseDocs/2.3.0-incubating/
> docs/html/tutorials_and_users_guides/
> tutorials_and_users_guides.html#ugr.tug.aas.setting_accessing_sofa_data):
>
> [...]
> aCas.setSofaDataArray(feature_structure_primitive_array,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mime_type_string);
> [...]
> Feature Structure primitive arrays are all the UIMA Array types except
> arrays of Feature Structures, Strings, and Booleans. Typically, these
> are arrays of bytes, but can be other types, such as floats, longs,
> etc.
> [...]
>
> And as far as I can see in the implementation for
> setLocalSofaData(FeatureStructure aFS) in SofaFSImpl.java this
> restriction is endorsed through following lines (77-92):
> [...]
> Type type =3D aFS.getType();
> if (!type.isArray()) {
> =A0 CASRuntimeException e =3D new CASRuntimeException(...);
> =A0 throw e;
> }
> if ( =A0 !type.getName().equals(CAS.TYPE_NAME_BYTE_ARRAY)
> =A0 =A0&& !type.getName().equals(CAS.TYPE_NAME_DOUBLE_ARRAY)
> =A0 =A0&& !type.getName().equals(CAS.TYPE_NAME_FLOAT_ARRAY)
> =A0 =A0&& !type.getName().equals(CAS.TYPE_NAME_INTEGER_ARRAY)
> =A0 =A0&& !type.getName().equals(CAS.TYPE_NAME_LONG_ARRAY)
> =A0 =A0&& !type.getName().equals(CAS.TYPE_NAME_SHORT_ARRAY)) {
> =A0 CASRuntimeException e =3D new CASRuntimeException(
> =A0 =A0 CASRuntimeException.INAPPROP_TYPE,
> =A0 =A0 new String[] {
> =A0 =A0 "Byte/Float/Integer/Short/String/Long/Double Array",
> =A0 =A0 type.getName() });
> =A0 throw e;
> }
> [...]
>
> Even though the exception message suggests differently.
>
> Am I missing something?
>
> Regards
> --Klaus
>
>