JSON Schemas & WoT TDs
Budget: €8 – €30 EUR
I need a meticulous hand that revolves around three pillars: crafting well-structured JSON payload files, writing Draft-07 JSON Schemas to validate them, and assembling fully featured Web of Things Thing Descriptions.
Here is what I must hand in:
• A collection of JSON payloads that exercise the full range of data types—strings, numbers, arrays, objects, nested structures—each following a precise filename pattern I will share once we start.
• One Draft-07 JSON Schema for every payload, with definitions, references, and clear validation messages so they can slot straight into automated tests.
• Two complete WoT TDs: one for a robot system, the other for its controller. Each TD has to expose Properties, Actions, and Events, carry multilingual titles/descriptions, include version info, and demonstrate all three security mechanisms (NoSec, Basic Auth, Bearer Token).
I already have a rough outline; what’s missing are the concrete files that pass both manual review and automated validation. If you are comfortable juggling JSON, JSON Schema tooling, and the WoT TD specification (wot-thing-description v1.1), you’ll find everything straightforward once I share the naming conventions and sample data.
Final deliverable set:
1. /payloads/*.json
2. /schemas/*.schema.json
3. /tds/robot.td.json and /tds/controller.td.json, fully resolved and lint-clean
I will test each item with ajv and the official wot-td-tool, so please ensure zero errors or warnings. Let me know your availability and previous experience with similar tasks, and we can get started right away.
Here is what I must hand in:
• A collection of JSON payloads that exercise the full range of data types—strings, numbers, arrays, objects, nested structures—each following a precise filename pattern I will share once we start.
• One Draft-07 JSON Schema for every payload, with definitions, references, and clear validation messages so they can slot straight into automated tests.
• Two complete WoT TDs: one for a robot system, the other for its controller. Each TD has to expose Properties, Actions, and Events, carry multilingual titles/descriptions, include version info, and demonstrate all three security mechanisms (NoSec, Basic Auth, Bearer Token).
I already have a rough outline; what’s missing are the concrete files that pass both manual review and automated validation. If you are comfortable juggling JSON, JSON Schema tooling, and the WoT TD specification (wot-thing-description v1.1), you’ll find everything straightforward once I share the naming conventions and sample data.
Final deliverable set:
1. /payloads/*.json
2. /schemas/*.schema.json
3. /tds/robot.td.json and /tds/controller.td.json, fully resolved and lint-clean
I will test each item with ajv and the official wot-td-tool, so please ensure zero errors or warnings. Let me know your availability and previous experience with similar tasks, and we can get started right away.