ab70f889a6
Message bodies are always arrays of strings (text lines) or objects (structured data like PUBKEY). Never raw strings. This enables: - Multiline messages without escape sequences - Deterministic JSON canonicalization (RFC 8785 JCS) for signing - Structured data where needed Update all schemas: body fields use array type with string items. Update message.json envelope: body is oneOf[array, object], id is UUID. Update README: message envelope table, examples, and canonicalization docs. Update schema/README.md: field types, examples with array bodies.
22 lines
685 B
JSON
22 lines
685 B
JSON
{
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"$id": "https://git.eeqj.de/sneak/chat/schema/commands/PONG.json",
|
|
"title": "PONG",
|
|
"description": "Keepalive response. S2C or S2S. RFC 1459 §4.6.3.",
|
|
"$ref": "../message.json",
|
|
"properties": {
|
|
"command": { "const": "PONG" },
|
|
"from": { "type": "string", "description": "Responding server name." },
|
|
"body": {
|
|
"type": "array",
|
|
"items": { "type": "string" },
|
|
"description": "Echoed token from PING (single-element array).",
|
|
"maxItems": 1
|
|
}
|
|
},
|
|
"required": ["command"],
|
|
"examples": [
|
|
{ "command": "PONG", "from": "server.example.com", "body": ["1707580000"] }
|
|
]
|
|
}
|