From 4aec6410c2318972240ded2bce5f68706aae18df Mon Sep 17 00:00:00 2001
From: Bryan Newbold <bnewbold@archive.org>
Date: Wed, 12 Feb 2020 20:33:31 -0800
Subject: pdftrio JSON object as top-level in Kafka results

To be same as GROBID results
---
 proposals/20200207_pdftrio.md | 32 ++++++++++++++++----------------
 1 file changed, 16 insertions(+), 16 deletions(-)

(limited to 'proposals')

diff --git a/proposals/20200207_pdftrio.md b/proposals/20200207_pdftrio.md
index 78d2d6c..7ad5142 100644
--- a/proposals/20200207_pdftrio.md
+++ b/proposals/20200207_pdftrio.md
@@ -57,22 +57,22 @@ Basically just like GROBID client for now. Requests, JSON.
 
 Output that goes in Kafka topic:
 
-    pdftrio
-        status
-        status_code
-        ensemble_score
-        bert_score
-        image_score
-        linear_score
-        versions
-            pdftrio_version (string)
-            models_date (string, ISO date)
-            git_rev (string)
-            bert_model (string)
-            image_model (string)
-            linear_model (string)
-        timing (might be added?)
-            ...
+    key (sha1hex)
+    status
+    status_code
+    ensemble_score
+    bert_score
+    image_score
+    linear_score
+    versions
+        pdftrio_version (string)
+        models_date (string, ISO date)
+        git_rev (string)
+        bert_model (string)
+        image_model (string)
+        linear_model (string)
+    timing (might be added?)
+        ...
     file_meta
         sha1hex
         ...
-- 
cgit v1.2.3