From owner-freebsd-current@freebsd.org Mon Nov 16 21:04:10 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 8B229A30AF9 for ; Mon, 16 Nov 2015 21:04:10 +0000 (UTC) (envelope-from gad@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8107B1DA9 for ; Mon, 16 Nov 2015 21:04:10 +0000 (UTC) (envelope-from gad@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 858) id 7FD2D19E9; Mon, 16 Nov 2015 21:04:10 +0000 (UTC) To: freebsd-current@freebsd.org Subject: libXO-ification - tangent on JSON choices Message-Id: <20151116210410.7FD2D19E9@freefall.freebsd.org> Date: Mon, 16 Nov 2015 21:04:10 +0000 (UTC) From: gad@freebsd.org (Garance A Drosehn) 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: Mon, 16 Nov 2015 21:04:10 -0000 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: 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. I came across the following project while watching a series of videos on youtube. I think I started out watching something about Clojure, or ruby, or d-lang, and ended up at this: http://jsonapi.org/ http://jsonapi.org/format/ And I must admit I haven't even taken the time to read the whole spec, but what I did read seemed interesting. It doesn't cover much, so I'd expect a spec for freebsd command outputs would need to be more detailed. Is there such a spec already written up, at least in a rough outline? -- Garance Alistair Drosehn = drosih@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA