Skip to content
Merged
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions planning/work-items/analysis/analysis-data-mapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,12 +48,12 @@ Also known as: Mapping TD elements to messages

2. XML data exchange

- **Who:** Developer with XML data exchange (instead of JSON). In general any other data format which differs from JSON.
- **What:** How to describe the XML format with DataSchemas (TD uses JSON schema means to describe data)
- **Who:** TD designer of a Thing with XML data exchange.
- **What:** Want to describe XML payloads in TDs (TD uses JSON Schema to describe payload data) and automatically validate XML payloads (WoT implementations use JSON Schema to validate payload data)
- Impossible to describe XML data accurately (i.e., there is no 1:1 mapping between JSON schema and XML schema)
- XML and/or JSON in memory while data on the wire (mapping between JSON and XML)
- See discussions in https://github.com/w3c/wot-binding-templates/issues/139
- **Why:** Sometimes the request/response (also of existing solutions) is done in XML. Nevertheless, one wants to describe the data properly in a TD. Moreover, validation should be possible.
- **Why:** Include Things (including in existing solutions) that use XML as payload content type in the WoT

- Sentence: **As a** developer, **I need** to support data exchange other than JSON (e.g., XML).
- Process Stakeholders:
Expand Down
Loading