Return-Path: X-Original-To: apmail-oodt-dev-archive@www.apache.org Delivered-To: apmail-oodt-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 09695CDEA for ; Fri, 11 May 2012 05:02:19 +0000 (UTC) Received: (qmail 58842 invoked by uid 500); 11 May 2012 05:02:18 -0000 Delivered-To: apmail-oodt-dev-archive@oodt.apache.org Received: (qmail 58746 invoked by uid 500); 11 May 2012 05:02:18 -0000 Mailing-List: contact dev-help@oodt.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@oodt.apache.org Delivered-To: mailing list dev@oodt.apache.org Received: (qmail 58727 invoked by uid 99); 11 May 2012 05:02:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2012 05:02:17 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [128.149.139.109] (HELO mail.jpl.nasa.gov) (128.149.139.109) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2012 05:02:11 +0000 Received: from mail.jpl.nasa.gov (ap-ehub-sp01.jpl.nasa.gov [128.149.137.148]) by smtp.jpl.nasa.gov (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q4B51nFc026302 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO) for ; Thu, 10 May 2012 22:01:50 -0700 Received: from AP-EMBX-SP40.RES.AD.JPL ([169.254.7.245]) by ap-ehub-sp01.RES.AD.JPL ([169.254.3.250]) with mapi id 14.02.0298.004; Thu, 10 May 2012 22:01:49 -0700 From: "Mattmann, Chris A (388J)" To: "" Subject: Re: OODT-402 progress update Thread-Topic: OODT-402 progress update Thread-Index: Ac0UI+/XXrAvu2W5RxutgA9aeNkg1gPvqYuAAAY7UYAANUoqAAAxVquAAnMJ3oAAAJG8gAACV+uA Date: Fri, 11 May 2012 05:01:48 +0000 Message-ID: References: <59B44093-B866-46D3-A695-BAEA63936D1F@jpl.nasa.gov> <169E811D-B826-4202-AE04-CCB6CC8931AF@jpl.nasa.gov> <5939FAFE-AD08-4CEA-8EAD-A4F3772B5E21@jpl.nasa.gov> <544A4548-059C-4AC9-A011-F66F25E25A66@jpl.nasa.gov> <69B62BE6-9EFB-4794-9B00-DAB718CD1E3E@jpl.nasa.gov> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.149.137.113] Content-Type: text/plain; charset="us-ascii" Content-ID: <814FF70B9A9AA6439DDC6F8D237D7929@ad.jpl> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Source-Sender: chris.a.mattmann@jpl.nasa.gov X-AUTH: Authorized X-Virus-Checked: Checked by ClamAV on apache.org Hey Ross, Either one would be +1 for me -- if you make it easily configurable, and ch= angeable, that would be even better! Cheers, Chris On May 10, 2012, at 8:54 PM, Ross Laidlaw wrote: > ... or maybe it could be: xmlns:cas=3D"http://oodt.apache.org/components/cas"> >=20 >=20 > On 11 May 2012 04:38, Ross Laidlaw wrote: >> Hi Chris, >>=20 >> I noticed the following commented code in the rssconf.xml file for the >> fmprod webapp: >>=20 >> >> >>=20 >>=20 >> Since the work on OODT-402 is based on that file, would it be ok if I >> include an update for the URI in the patch? Would the following be >> correct? >>=20 >> >>=20 >>=20 >> I'd also like to use the updated URI for the georss-config.xml as well. >>=20 >>=20 >> Ross >>=20 >>=20 >>=20 >> On 28 April 2012 17:24, Mattmann, Chris A (388J) >> wrote: >>> Anytime, Ross! >>>=20 >>> Cheers, >>> Chris >>>=20 >>> On Apr 27, 2012, at 9:51 AM, Ross Laidlaw wrote: >>>=20 >>>> Hi Chris! >>>>=20 >>>> Thanks for responding so quickly and for the guidance. I'll set up >>>> the JIRA issues and add some specific info and questions to each item. >>>>=20 >>>> Ross >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> On 26 April 2012 16:25, Mattmann, Chris A (388J) >>>> wrote: >>>>> Hi Ross, >>>>>=20 >>>>> No problem at all! Read on below and keep the questions coming! >>>>>=20 >>>>> On Apr 26, 2012, at 5:27 AM, Ross Laidlaw wrote: >>>>>=20 >>>>>> Hi Chris, >>>>>>=20 >>>>>> I'm planning my next steps for working on OODT-402. The first task = is >>>>>> to create a default GeoRSS config in the File Manager RSS service. = Do >>>>>> you have a preference for where this file should be stored and >>>>>> accessed? >>>>>=20 >>>>> Yep. I think we should ship it with the File Manager inside of: >>>>>=20 >>>>> http://svn.apache.org/repos/asf/oodt/trunk/webapp/fmprod/src/main/res= ources/georss-config.xml >>>>>=20 >>>>>> As a first step, in the demo that I set up recently I used >>>>>> the default 'rssconfig.xml' file for the fmprod webapp and followed >>>>>> your comments to add latitude and longitude tags to this. >>>>>>=20 >>>>>=20 >>>>> Yep in the georss-config.xml I would copy through the default RSS and= config >>>>> and then just expose lat/lon with the comments/documentation. >>>>>=20 >>>>> This could be a JIRA issue in itself. >>>>>=20 >>>>>> For the 'LocationAwareProduct' definition, I was wondering if we cou= ld >>>>>> make this a virtual type that could then be inherited by concrete >>>>>> vendor types. >>>>>=20 >>>>> +1, this sounds like a good strategy, and I would do it as a full >>>>> specced product-types.xml, elements.xml and product-type-element-map.= xml >>>>> combination. A home for it could be: >>>>>=20 >>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources= /examples/geo >>>>>=20 >>>>> As part of this, we should move the current contents of: >>>>>=20 >>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources= /examples/ >>>>>=20 >>>>> To: >>>>>=20 >>>>> http://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/resources= /examples/core >>>>>=20 >>>>> This would be 2 separate JIRA issues (for default geo policy, and the= n a separate >>>>> to move core, and make sure assembly.xml still works, and the unit te= sts, etc.) >>>>>=20 >>>>>>=20 >>>>>> Just a few questions and thoughts to get going! Apologies if I'm of= f track... >>>>>=20 >>>>> HTH and rock on! >>>>>=20 >>>>> Cheers, >>>>> Chris >>>>>=20 >>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>> Chris Mattmann, Ph.D. >>>>> Senior Computer Scientist >>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>>>> Office: 171-266B, Mailstop: 171-246 >>>>> Email: chris.a.mattmann@nasa.gov >>>>> WWW: http://sunset.usc.edu/~mattmann/ >>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>> Adjunct Assistant Professor, Computer Science Department >>>>> University of Southern California, Los Angeles, CA 90089 USA >>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>=20 >>>=20 >>>=20 >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> Chris Mattmann, Ph.D. >>> Senior Computer Scientist >>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>> Office: 171-266B, Mailstop: 171-246 >>> Email: chris.a.mattmann@nasa.gov >>> WWW: http://sunset.usc.edu/~mattmann/ >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> Adjunct Assistant Professor, Computer Science Department >>> University of Southern California, Los Angeles, CA 90089 USA >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>=20 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattmann@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++