Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4FD4FD10A for ; Tue, 3 Jul 2012 03:23:39 +0000 (UTC) Received: (qmail 7548 invoked by uid 500); 3 Jul 2012 03:23:38 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 7356 invoked by uid 500); 3 Jul 2012 03:23:38 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 7296 invoked by uid 99); 3 Jul 2012 03:23:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2012 03:23:36 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of damjan.jov@gmail.com designates 209.85.216.43 as permitted sender) Received: from [209.85.216.43] (HELO mail-qa0-f43.google.com) (209.85.216.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2012 03:23:30 +0000 Received: by qadb33 with SMTP id b33so2575270qad.9 for ; Mon, 02 Jul 2012 20:23:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=ZeAn1W3z8LobtHsVbPUAn8XXYCuCwxiQBzFp/dbASx0=; b=yjvAgka+rWd65aUxxJ9eRu1/VbR+1Y8Rx0gD8/iD55BXHwxOhVLPthko3fMJTsln8Z mnvLnlIt92SKdVHrZqYKHY5k3lkb9oO/U4HerrnU3PJjFGLeOdPiTPMM5B0H6vAzcaYO q6wl9c4k1oMNOtPdz0MR93JT3zhQqm9cYc/6WMPJ88X66opJKRC0W8iFEP95MJKiy6YV LQktpILDjeDvWyCcFdB1sr1w4KJMTdfIRRj/XZa1UlCLcKIcH39LIwbvrcRi86cExbNa UnEY6AhQRg5lXC4nW1g6qdO6AK2ips4KL66Wkitaua5D0YBKa8f+UHj9A4s6RZpz38W7 D76Q== Received: by 10.229.137.147 with SMTP id w19mr3757304qct.44.1341285789326; Mon, 02 Jul 2012 20:23:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.240.12 with HTTP; Mon, 2 Jul 2012 20:22:49 -0700 (PDT) In-Reply-To: <4FF213A5.3090600@wellfleetsoftware.com> References: <4FF213A5.3090600@wellfleetsoftware.com> From: Damjan Jovanovic Date: Tue, 3 Jul 2012 05:22:49 +0200 Message-ID: Subject: Re: [IMAGING] TagInfo and distinction between TagName and FieldName To: Commons Developers List Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jul 2, 2012 at 11:33 PM, Farrukh Najmi wrote: > > Hi Guys, > > I am new to the project so forgive me if the answer is obvious... > > I am working with latest svn bits and the > org.apache.commons.imaging.formats.tiff.taginfos.TagInfo class seems to only > support the TagName column of Table 3 TIFF Rev. 6.0 Attribute Information > Used in Exif in the Exif spec . I need > access to FieldName as it seems more suitable as a human-friendly identifier > for the tag. > > I think it would be ideal if TagInfo supports both TagName and FieldName. > What does the dev team think? If there are not many -1s then I will file in > RFE in JIRA. > > Thanks for your input. > > -- > Regards, > Farrukh > > Web: http://www.wellfleetsoftware.com > Hi Farrukh The TIFF6 specification Appendix A only has a "TagName", which is similar to Exif 2.2's "FieldName". Other TIFF tag specifications (DNG, TIFFPM6, RFC 2301) also only give a name and a description. Maybe what we need is: Use TagInfo's "name" field for the name taken verbatim from those specs (eg. use "ImageWidth" instead of "Image Width") Add a "description" field to TagInfo with a long description (eg. "Image width, the number of columns in the image") What do you think? Regards Damjan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org