Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Understanding how the IDs are handled when the schema has no provenance.

Received: by 10.213.32.15 with SMTP id a15mr971163ebd.14.1331541524601;
        Mon, 12 Mar 2012 01:38:44 -0700 (PDT)
X-BeenThere: json-schema@googlegroups.com
Received: by 10.213.100.201 with SMTP id z9ls2661404ebn.6.gmail; Mon, 12 Mar
 2012 01:38:42 -0700 (PDT)
Received: by 10.213.4.80 with SMTP id 16mr984970ebq.9.1331541522705;
        Mon, 12 Mar 2012 01:38:42 -0700 (PDT)
Received: by 10.213.4.80 with SMTP id 16mr984969ebq.9.1331541522686;
        Mon, 12 Mar 2012 01:38:42 -0700 (PDT)
Return-Path: <fgalie...@gmail.com>
Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182])
        by gmr-mx.google.com with ESMTPS id f5si5925030eeo.2.2012.03.12.01.38.42
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 12 Mar 2012 01:38:42 -0700 (PDT)
Received-SPF: pass (google.com: domain of fgalie...@gmail.com designates 209.85.215.182 as permitted sender) client-ip=209.85.215.182;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of fgalie...@gmail.com designates 209.85.215.182 as permitted sender) smtp.mail=fgalie...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ey0-f182.google.com with SMTP id f13so946106eaa.13
        for <json-schema@googlegroups.com>; Mon, 12 Mar 2012 01:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        bh=ygId2xW/5QvfMW4AP/9eV5yT7wDySZg98IrG3AHcHLI=;
        b=H9U9JPnFRxxz2KYGpgeBXsZLiQkAYl1slSkroekQeOCggIm11f4BxGvW2KENyQz8k3
         q0aoTKZ88TGjhBWU3amYrctS4bk1+z76r4PZJoXZ3zCPCq0dzWcP05IN6DaL0fNzNz25
         2YDniQmsGzpkoMtOqWGtpD7+vpNZY7OOSmB4Wl8u8Zh7HVq60hyAJV3lYwkqITfUYf41
         k9igKF3zL7+0Phx57rZ1DXpXTSoTX0I/XwwralH4LknmmeSqB1a6eQcxLEHUIjpB4VKW
         MTettSZ6R4d/iqnCfRdKGyUneQf2r0DoaCslgfxLRzUbrjHwWgDxVI56f0G7yi6/q73F
         hNwQ==
MIME-Version: 1.0
Received: by 10.14.52.66 with SMTP id d42mr1701838eec.125.1331541522088; Mon,
 12 Mar 2012 01:38:42 -0700 (PDT)
Received: by 10.213.2.78 with HTTP; Mon, 12 Mar 2012 01:38:41 -0700 (PDT)
In-Reply-To: <27779470.1025.1331334784027.JavaMail.geo-discussion-forums@vbtf26>
References: <32890996.4684.1331118544975.JavaMail.geo-discussion-forums@ynlt17>
	<CALcybBDBmVGY93wDrrKi_Z6PingPy0t6i7PK5HS3CMpCXmW...@mail.gmail.com>
	<6532499.5197.1331139245472.JavaMail.geo-discussion-forums@ynlt17>
	<CALcybBD26Un6bbD+3+q2xttyouVOypgjowBkLCSMnbyo0mX...@mail.gmail.com>
	<29936184.10.1331193727447.JavaMail.geo-discussion-forums@vbbp15>
	<CALcybBDD3JNC8UH9iARJ_JWxq2bNvsdw3NgEH0hTe1DScKb...@mail.gmail.com>
	<7207681.21.1331281692236.JavaMail.geo-discussion-forums@vbne13>
	<CALcybBCwGTXicSjYfzUNeeiQMVjw69cnt-oyFAW9vsMriRn...@mail.gmail.com>
	<27779470.1025.1331334784027.JavaMail.geo-discussion-forums@vbtf26>
Date: Mon, 12 Mar 2012 09:38:41 +0100
Message-ID: <CALcybBC=0hf0Tzg1dUZYKBxVnS7NJGxhATGRx-ArdA1W3Rw...@mail.gmail.com>
Subject: Re: [json-schema] Understanding how the IDs are handled when the
 schema has no provenance.
From: Francis Galiegue <fgalie...@gmail.com>
To: json-schema@googlegroups.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 10, 2012 at 00:13, Xample <flavien.vol...@gmail.com> wrote:
[...]
>
> 1. I do not agree again. The rfc specifies the following fallback : id
> relatively to the url where the shema has been got, relatively to the
> environment. This is only a matter of building absolute paths from relati=
ve
> one.The rfc=C2=A0RFC 2396 tells how to do it, you should be able to use t=
he
> java.net.URL by URL url =3D new URL( "http://base.com/url" ,
> "../relativeOne.html");
>
> Normally: new URL( "http://absoluteOne.com" , "http://notARelative.com");
> will give you http://notARelative.com
>

And if the machine names don't exist, this fails. URL does name
resolution. You cannot rely on that.

Please, understand my point of view: I want to keep things _simple_,
it is the best way to kickstart a more widespread use of JSON Schema.
Restricting the values of "id" the way I proposed it makes
implementations easy.

--=20
Francis Galiegue, fgalie...@gmail.com
"It seems obvious [...] that at least some 'business intelligence'
tools invest so much intelligence on the business side that they have
nothing left for generating SQL queries" (St=C3=A9phane Faroult, in "The
Art of SQL", ISBN 0-596-00894-5)