airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandeep Panem <sandeep.panem...@gmail.com>
Subject Re: Airavata GSoC 2013 Master Project
Date Wed, 17 Apr 2013 10:32:52 GMT
Instead of an interface which converts json to soap and then sending soap
data to airavata services,we should follow standard data format of json
which is compatible with all browsers and easily understandable and reduces
complexity.


On Wed, Apr 17, 2013 at 2:13 AM, Mattmann, Chris A (398J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> 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 <marpierc@iu.edu>
> Reply-To: "dev@airavata.apache.org" <dev@airavata.apache.org>
> Date: Tuesday, April 16, 2013 1:15 PM
> To: "dev@airavata.apache.org" <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
> >>>
> >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.
> >>
> >>
> >> [1] - https://github.com/garycourt/JSV [2] -
> >> https://github.com/garycourt/JSV/blob/master/README.md#license
> >>
> >-----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=
> >=bQv0
> >-----END PGP SIGNATURE-----
>
>


-- 
-Sandeep Panem

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message