IETF Logo Mail Archive

Re: [Json] JSON Schema Language

Pete Cordell <petejson@codalogic.com> Wed, 08 May 2019 13:38 UTC

Return-Path: <petejson@codalogic.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23A88120129 for <json@ietfa.amsl.com>; Wed, 8 May 2019 06:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQTBOJ7lUvuZ for <json@ietfa.amsl.com>; Wed, 8 May 2019 06:38:11 -0700 (PDT)
Received: from ppsa-online.com (ppsa-online.com [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98099120123 for <json@ietf.org>; Wed, 8 May 2019 06:38:10 -0700 (PDT)
Received: (qmail 32203 invoked from network); 8 May 2019 14:36:18 +0100
Received: from host109-157-169-192.range109-157.btcentralplus.com (HELO ?192.168.1.72?) (109.157.169.192) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (AES128-SHA encrypted, authenticated); 8 May 2019 14:36:18 +0100
To: Austin Wright <aaa@bzfx.net>
Cc: json@ietf.org
References: <CAJK=1RjV1uv0eOdtFZ8cKn-FfCwCiGP5r2hOz1UamiM6YV4H1A@mail.gmail.com> <CAHBU6itE8kub1qtdRoW8BqxaOmzMv=vUo1aDeuAr3HX141NUGg@mail.gmail.com> <cfcdd163-36d0-8b98-5f34-84c3e5e774ad@codalogic.com> <46584E26-AE7F-444C-A73C-BBB393BDCBD7@bzfx.net>
From: Pete Cordell <petejson@codalogic.com>
Message-ID: <3864ddba-4c67-2d01-a7e3-2c3a459eae02@codalogic.com>
Date: Wed, 08 May 2019 14:38:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <46584E26-AE7F-444C-A73C-BBB393BDCBD7@bzfx.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/5OnfN20AKeP1z3f58HweGdZwLwU>
Subject: Re: [Json] JSON Schema Language
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2019 13:38:13 -0000

On 07/05/2019 22:50, Austin Wright wrote:
> I still have to spend more time with JCR, but it appears to me JSON Schema implementations could import JCR documents as a JSON Schema with few problems, and it could very well be a superior method of authoring a JSON Schema.
> 
> Would you consider elaborating on this possibility in JCR?

At a guess, the best approach might be to have JCR to JSON Schema (and 
vice versa) translation tools, possibly as a library that can be 
included into other programs rather than as standalone tools in their 
own right.

There will likely be some features that can't be translated. Identifying 
those features could be a useful exercise in converging the technologies.

Pete.
-- 
---------------------------------------------------------------------
Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com
---------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email