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.
36 lines
735 B
JSON
36 lines
735 B
JSON
{
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"$id": "https://git.eeqj.de/sneak/chat/schema/numerics/482.json",
|
|
"title": "482 ERR_CHANOPRIVSNEEDED",
|
|
"description": "You're not channel operator. RFC 1459 \u00a76.1.",
|
|
"$ref": "../message.json",
|
|
"properties": {
|
|
"command": {
|
|
"const": "482"
|
|
},
|
|
"to": {
|
|
"type": "string"
|
|
},
|
|
"params": {
|
|
"type": "array",
|
|
"items": {
|
|
"type": "string"
|
|
},
|
|
"description": "[channel]."
|
|
},
|
|
"body": {
|
|
"type": "array",
|
|
"items": {
|
|
"type": "string"
|
|
},
|
|
"description": "You're not channel operator",
|
|
"maxItems": 1
|
|
}
|
|
},
|
|
"required": [
|
|
"command",
|
|
"to",
|
|
"params"
|
|
]
|
|
}
|