From 9640020dc3552ad26818dac6140b07ec2730b087 Mon Sep 17 00:00:00 2001 From: Cyber MacGeddon Date: Mon, 4 Aug 2025 17:17:00 +0100 Subject: [PATCH] Structured data tech spec emerging --- docs/tech-specs/STRUCTURED_DATA.md | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/docs/tech-specs/STRUCTURED_DATA.md b/docs/tech-specs/STRUCTURED_DATA.md index 861a2e92..c5aa838d 100644 --- a/docs/tech-specs/STRUCTURED_DATA.md +++ b/docs/tech-specs/STRUCTURED_DATA.md @@ -138,7 +138,16 @@ This approach allows: ### APIs -[API endpoints and interfaces] +New APIs: +- `POST /api/v1/nlp-to-query` - Convert natural language to structured query +- `POST /api/v1/structured-data/ingest` - Ingest structured data (CSV, JSON, XML) +- `POST /api/v1/structured-data/query` - Execute structured queries +- `GET /api/v1/schemas` - List available schemas +- `GET /api/v1/schemas/{name}` - Get specific schema definition + +Modified APIs: +- Knowledge extraction endpoints - Add structured object output option +- Agent endpoints - Add structured data tool support ### Implementation Details @@ -146,7 +155,7 @@ This approach allows: ## Security Considerations -[Security requirements and considerations] +No extra considerations. ## Performance Considerations @@ -166,8 +175,12 @@ Not specified. ## Open Questions -[Any unresolved questions or decisions to be made] +- Can this be made to work with other store types? We're aiming to use + interfaces which make modules which work with one store applicable to + other stores. ## References -[Related documents and resources] +n/a. + +