From owner-freebsd-current@freebsd.org Sun Nov 15 19:26:05 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9C44A30A69 for ; Sun, 15 Nov 2015 19:26:05 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E49B18DD; Sun, 15 Nov 2015 19:26:04 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.0.7] (cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id tAFJPsMi093738 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Nov 2015 19:25:57 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61] claimed to be [192.168.0.7] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? From: David Chisnall In-Reply-To: <6506.1447614741@chaos> Date: Sun, 15 Nov 2015 19:25:45 +0000 Cc: Garrett Cooper , Andrey Chernov , Adrian Chadd , Dan Partelly , freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <702A1341-FB0C-41FA-AB95-F84858A7B3A4@rdsor.ro> <5648C60B.6060205@freebsd.org> <6EDFB74B-2206-46E7-85F7-8DE05FB6D325@gmail.com> <6506.1447614741@chaos> To: "Simon J. Gerraty" X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 19:26:05 -0000 On 15 Nov 2015, at 19:12, Simon J. Gerraty wrote: >=20 > Garrett Cooper wrote: >> We lack a [dtd/json] spec for tools, so programming for xo'ification >> doesn't seems like the best idea in the world to me from a end-user >> sysadmin/developer perspective. >=20 > A dtd etc is good for sure, and we (Juniper) do have them, as well as > ui-police to help ensure things go smoothly - even that doesn't catch > everything. At the GSoC Mentor Summit, someone from GitHub pointed me at a tool[1] = for generating schemas from JSON (which can then be refined manually) = and can be used for validating that the schema is still respected in = newer versions. I hope to integrate something like this into our = regression test suite before 11. For the people complaining that there are no command-line tools for = filtering JSON in shell scripts, I=E2=80=99d suggest that they look at = JQ[2]. I=E2=80=99m not sure if it=E2=80=99s worth bringing it into = base, but being able to install it easily (textproc/jq, no dependencies) = from ports suddenly makes a load of stuff trivial with shell scripts = that were either incredibly hard or impossible prior to libxo. David [1] https://github.com/perenecabuto/json_schema_generator [2] https://stedolan.github.io/jq/