Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-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 9E82C109E6 for ; Tue, 16 Apr 2013 20:44:01 +0000 (UTC) Received: (qmail 8439 invoked by uid 500); 16 Apr 2013 20:44:01 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 8407 invoked by uid 500); 16 Apr 2013 20:44:01 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 8399 invoked by uid 99); 16 Apr 2013 20:44:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 20:44:01 +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.106] (HELO mail.jpl.nasa.gov) (128.149.139.106) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 20:43:57 +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.3.1/Sentrion-MTA-4.3.1) with ESMTP id r3GKhYbG021547 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO) for ; Tue, 16 Apr 2013 13:43:34 -0700 Received: from AP-EMBX-SP40.RES.AD.JPL ([169.254.7.50]) by ap-ehub-sp01.RES.AD.JPL ([169.254.3.100]) with mapi id 14.02.0342.003; Tue, 16 Apr 2013 13:43:34 -0700 From: "Mattmann, Chris A (398J)" To: "dev@airavata.apache.org" Subject: Re: Airavata GSoC 2013 Master Project Thread-Topic: Airavata GSoC 2013 Master Project Thread-Index: AQHOORT6v4gLYIs4KkyI+b9jtvcdzJjWbXYAgAAM0ICAAA8VAIAABpmAgADMeYCAAcvIAIAAmHcAgAAA2ID//5JvAA== Date: Tue, 16 Apr 2013 20:43:33 +0000 Message-ID: In-Reply-To: <516DB16D.6070508@iu.edu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.2.130206 x-originating-ip: [128.149.137.114] Content-Type: text/plain; charset="us-ascii" Content-ID: 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 Guys, Best way to find out is to email legal-discuss@apache.org. I'll try and look at it either there or here and comment. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Marlon Pierce Reply-To: "dev@airavata.apache.org" Date: Tuesday, April 16, 2013 1:15 PM To: "dev@airavata.apache.org" Subject: Re: Airavata GSoC 2013 Master Project >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >That license doesn't look too bad, but I don't know how strict we need >to be. It is possible that the author, if contacted, will adopt an >Apache or Apache-compatible license. > > >Marlon > > >On 4/16/13 4:12 PM, Subho Banerjee wrote: >>> If we were two pursue JSON for descriptions applications and >>> workflow, we need to explore validations. I wonder if there are >>> any good implementations of the json-schema validation spec - >>> http://tools.ietf.org/pdf/draft-fge-json-schema-validation-00.pdf >>> >>> >>>From >>>=20 >what I know, the best (open and closest to implementing the entire >> spec) validator for JSON schemas is JSV[1]. I am not particularly >> sure if this license[2] is compatible to the Apache license. If it >> is, then using this could be one way to go ahead. However, in the >> case that it is not compatible, then we might have to fork some >> sort of a half baked validator and modify it to suit the needs of >> the project. I will look into this and let you know what I find. >>=20 >>=20 >> [1] - https://github.com/garycourt/JSV [2] - >> https://github.com/garycourt/JSV/blob/master/README.md#license >>=20 >-----BEGIN PGP SIGNATURE----- >Version: GnuPG/MacGPG2 v2.0.18 (Darwin) >Comment: GPGTools - http://gpgtools.org >Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > >iQEcBAEBAgAGBQJRbbFtAAoJEOEgD2XReDo5wRoIAIhK2u0GL+lp2TL6jPJbHJ/U >W+lVr69MAhPdfiMUxqNjHZwJSjn0yU5b310/8rqQ5RMOw6BUHxAaKo3Iinhfq2xf >DPyzhGrawiVuUXvkco6aUI4QmHqXl+7PpXC8Sr0o6FuATDNX7DcOrdlSK6Gp2MXi >BrREBZ4LbY//yue5LkhKkGuz6q7tdBp94AQPrBnbtmTuI81uVBxCLOb0DUxkhOTE >87PgkhyWDyR+2wLwVze2Ng1EaUmADcElhRZvBtLqESFg2LoN4NDIzhBX/XdvxKaf >vlgnmIZS+Uc7ftAijYuQPg4246RJKLDQYFr5Ms3tomu1vt4BHArNuMQdGzoflPs=3D >=3DbQv0 >-----END PGP SIGNATURE-----