From owner-freebsd-current@freebsd.org Fri Nov 20 12:25:13 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 CEA40A32703 for ; Fri, 20 Nov 2015 12:25:13 +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 9F8DC1032; Fri, 20 Nov 2015 12:25:12 +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 tAKCPAI9029970 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Nov 2015 12:25:11 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 - tangent on JSON choices From: David Chisnall In-Reply-To: <20151116210410.7FD2D19E9@freefall.freebsd.org> Date: Fri, 20 Nov 2015 12:25:04 +0000 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20151116210410.7FD2D19E9@freefall.freebsd.org> To: Garance A Drosehn 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: Fri, 20 Nov 2015 12:25:13 -0000 On 16 Nov 2015, at 21:04, Garance A Drosehn wrote: >=20 > First let me say that I wish I had more time to contribute to the = project, > but I seem to be caught in variety of long drawn-out hassles in = real-life. > Otherwise I would already know the answer to this question: >=20 > Is there some specification for what JSON is created by the various = FBSD > utilities? I did not see any discussion of that in the earlier = threads > on this. I don't mean "what is syntatically correct JSON?", I mean = some > kind of guidelines of what property-names would be used across = commands, > and what values should be for those properties. There is not, currently. Until 11.0 is branched, it should be = considered to be in flux, but after that then we are going to provide = backwards compatibility (i.e. you can add fields to the JSON, but you = can=E2=80=99t remove them). Before this point, it would be good to have = some consensus of on what properties should be common and what each = should be providing, and regression tests for the JSON (the XML is = isomorphic to the JSON, so probably doesn=E2=80=99t need testing = separately). If you want to provide a first draft of some recommendations, they would = be very welcome, David