Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ABB02DD2B for ; Thu, 15 Nov 2012 00:23:53 +0000 (UTC) Received: (qmail 48935 invoked by uid 500); 15 Nov 2012 00:23:53 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 48881 invoked by uid 500); 15 Nov 2012 00:23:53 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 48871 invoked by uid 99); 15 Nov 2012 00:23:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 00:23:53 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of himanshu.gahlot86@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-ia0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 00:23:45 +0000 Received: by mail-ia0-f175.google.com with SMTP id z3so674207iad.6 for ; Wed, 14 Nov 2012 16:23:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=Xg47bpbWgt9/SxPf0HsJ+itLm+zn/JtIfy0UnjbXVzk=; b=orglQcBMoAk8wERpZX52rMLPSWUxkUy8q0Sm7IIPRePY8/qf/m6uEefc7S7G7OhDPV Pc85Icmc4nDxi8qvFG8CkPRLkygOQ//3Es5GHL8egLinqYMs3YLB5A0n8FAsSk7rgmaN UWqo5Gvg4GPrmR/DpR/mF2wEdRsKhnRHzQngT7u2YQdD45g2wop/QBsfrsPXrZ0X/het Ud50qp0kf0LYGTS/Pbf3eNmOxb5nLqW28YW/MVzcVVmxQ7+cy+TGzGo9ELDsJmwxEeD3 NuBP//fbQwsWvK9t5XEFfEFqHAfA18maDfbzCjvaWKODXIGBdllWDAdbx7Mn4wD28Z4a xGyQ== Received: by 10.50.183.168 with SMTP id en8mr867357igc.10.1352939004293; Wed, 14 Nov 2012 16:23:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.79.228 with HTTP; Wed, 14 Nov 2012 16:23:03 -0800 (PST) From: Himanshu Gahlot Date: Wed, 14 Nov 2012 16:23:03 -0800 Message-ID: Subject: Should document level annotations inherit from DocumentAnnotation? To: user@uima.apache.org Content-Type: multipart/alternative; boundary=14dae9340c9bc0f26a04ce7da850 X-Virus-Checked: Checked by ClamAV on apache.org --14dae9340c9bc0f26a04ce7da850 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am a little confused about inheriting a document level annotation from uima.jcas.tcas.DocumentAnnotation. I am of the view that a document level annotation may not necessarily have 'begin' and 'end' features. For example, I may want to have a document level annotation such as DocumentCategory which has features such as category1, category2, category3, score1, score2, score3, etc., where categories and scores are the top 3 categories/scores for this document predicted by a document classification algorithm. In such a case, it does not make sense to have 'begin' and 'end' (and even 'coveredText') as features of DocumentCategory, since, the categories do not exist in the document text itself and rather just act like document metadata. Hence, I think it makes more sense to make DocumentCategory inherit from AnnotationBase (which lacks 'begin' and 'end' features) rather than from DocumentAnnotation. But I have not seen people inheriting directly from AnnotationBase. Are there restrictions around not inheriting from DocumentAnnotation or Annotation classes and directly inheriting from AnnotationBase that I should be aware of? Does my understanding of a document level annotation and its proposed lack of 'begin' and 'end' features makes sense? -Himanshu --14dae9340c9bc0f26a04ce7da850--