From d0cb9a40191783a5e932e622c986c396f4a1564a Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Fri, 27 Dec 2013 16:47:49 +0100 Subject: [PATCH] Clarification of the example appendix --- i-d/pdns-qof.xml | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/i-d/pdns-qof.xml b/i-d/pdns-qof.xml index ff0c2ee..d52794f 100644 --- a/i-d/pdns-qof.xml +++ b/i-d/pdns-qof.xml @@ -172,18 +172,8 @@ The document does not describe the protocol (e.g. WHOIS The formatting of the answer follows the JSON format. The order of the fields is not significant for the same resource type. That means, the same name tuple plus timing information identifies a unique answer per server. The intent of this output format is to be easily parsable by scripts. Each JSON object is expressed on a single line to be processed by the client line-by-line. Every implementation MUST support the JSON output format. - -
-
A sample output using the JSON format:
-
+ Examples of JSON output are in the appendix. +
Formal grammar as defined in ABNF