Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 77916200CB3 for ; Mon, 26 Jun 2017 12:00:29 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 75EBA160BDE; Mon, 26 Jun 2017 10:00:29 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BBD7F160BD9 for ; Mon, 26 Jun 2017 12:00:28 +0200 (CEST) Received: (qmail 53933 invoked by uid 500); 26 Jun 2017 10:00:28 -0000 Mailing-List: contact dev-help@asterixdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.apache.org Delivered-To: mailing list dev@asterixdb.apache.org Received: (qmail 53922 invoked by uid 99); 26 Jun 2017 10:00:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jun 2017 10:00:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4F09E182914 for ; Mon, 26 Jun 2017 10:00:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.498 X-Spam-Level: ** X-Spam-Status: No, score=2.498 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id QQCWX2wZSDZe for ; Mon, 26 Jun 2017 10:00:25 +0000 (UTC) Received: from send.cs.ucr.edu (send.cs.ucr.edu [169.235.30.36]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 524435FC57 for ; Mon, 26 Jun 2017 10:00:24 +0000 (UTC) Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com [209.85.220.171]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by send.cs.ucr.edu (Postfix) with ESMTPSA id 42D4221B06 for ; Mon, 26 Jun 2017 03:00:15 -0700 (PDT) Received: by mail-qk0-f171.google.com with SMTP id 16so73420094qkg.2 for ; Mon, 26 Jun 2017 03:00:15 -0700 (PDT) X-Gm-Message-State: AKS2vOwHV25SNYYDA/hqK90I/X+IiECSn/v1qmaz1JN0ayeI6M7Bzfxa xEgbE9Q/uamMw1GqJj9mXD4YWYcHCA== X-Received: by 10.55.114.1 with SMTP id n1mr23163912qkc.123.1498471214602; Mon, 26 Jun 2017 03:00:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.30.164 with HTTP; Mon, 26 Jun 2017 02:59:44 -0700 (PDT) In-Reply-To: References: <05D322EF-1890-44C0-AF67-A8E9A740D1FB@apache.org> From: Ahmed Eldawy Date: Mon, 26 Jun 2017 02:59:44 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: License issue when using esri geometry api To: dev@asterixdb.apache.org Content-Type: multipart/alternative; boundary="94eb2c05a83873deb40552da0441" archived-at: Mon, 26 Jun 2017 10:00:29 -0000 --94eb2c05a83873deb40552da0441 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It seems that (3) would require modifying the open source Esri API library which I don't like. Not only for the overhead of understanding and modifying the code, but also for deviating from the standard library which means we will miss future updates. One of the reasons we chose to use Esri API is the hope that it will be well-maintained in the future. This leaves us with (4). I don't know if it is technically possible to depend on the standard Esri API without using the non-compliant library or not. If this is possible, then we can just use the computational geometry (CG) functionality from the library, and provide our own GeoJSON parser. If this is not possible, then I would rather consider the use of another library, e.g., JTS. Thanks Ahmed On Sun, Jun 25, 2017 at 11:47 AM, Wail Alkowaileet wrote: > I can see from the code that there is a serder steps as such: Asterix > Object (binary) --> JSON (String) --> Esri geometry (Java object) --> Esr= i > geometry (binary). > I think it would be nice if there is a binary-to-binary conversion withou= t > any deserialization (4th option). > > On Sun, Jun 25, 2017 at 6:36 PM, Mike Carey wrote: > > > Agreed that 3 or 4 are what we'll need to do....! (Sigh.) > > > > > > > > On 6/25/17 5:57 AM, Till Westmann wrote: > > > >> Hi Riyafa, > >> > >> I think that the problem is bigger than the failing test. The JSON > >> license itself is not acceptable for inclusion in an Apache artifact > >> [4]. So we cannot use the ESRI API as-is, if we want the GeoJSON > >> functionality be a non-optional part of AsterixDB. > >> > >> Here are a few options I see: > >> 1) Make GeoJSON an optional part of AsterixDB (separate download from = a > >> non-Apache location). > >> 2) Make JSON.org a dependency that is not shipped (i.e. each user woul= d > >> have to download and install those jars separately - and get error > >> messages if the jars are not available). > >> 3) Create a clone/copy of the ESRI API that uses another JSON library. > >> 4) Do all of the parsing independently from the ESRI API. > >> > >> I=E2=80=99m not sure if 1) is a good option as the extensibility in th= is part > >> of the code might not be sufficient to support this option easily. > >> 2) is technically easier, but it involves an unpleasant user > >> experience. > >> Also, I think that both 1) and 2) are not desirable, as GeoJSON should > >> be supported by vanilla AsterixDB. > >> For 3) and 4) we would need to look into the details to see how much > >> work is required for each of those options and if there are other lega= l > >> hurdles. > >> > >> Are there other options? > >> Other thoughts/concerns? > >> > >> Cheers, > >> Till > >> > >> [4] https://www.apache.org/legal/resolved.html#category-x > >> > >> On 25 Jun 2017, at 13:57, Riyafa Abdul Hameed wrote: > >> > >> Dear all, > >>> > >>> I implemented parse_geojon() function[1] using esri-geometry api[2] > which > >>> is apache-2.0 licensed. But this api uses org.json as a dependency. > >>> org.json is licensed under JSON which causes a license issue in the > code > >>> I > >>> have written[3]. What can I do about this issue? > >>> > >>> [1] https://asterix-gerrit.ics.uci.edu/1838 > >>> [2]https://github.com/Esri/geometry-api-java > >>> [3] > >>> https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-integ > >>> ration-tests/3290/ > >>> > >>> Thank you. > >>> Yours sincerely, > >>> Riyafa > >>> > >> > > > > > -- > > *Regards,* > Wail Alkowaileet > --94eb2c05a83873deb40552da0441--