mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-04-24 11:44:08 +02:00
7f81501762
Rename "schema/v1/core" to "schema/v1/core-event-schema". Add self-referential symlinks to schema/v1/core-event-schema The python json schema libraries expect that relative references are relative to the file they are in. The node json schema libraries expect that relateive references are relative to the first file loaded. To support both kinds we reference the core event schema using "core-event-schema/event.json". We then symlink the core-event-schema directory to both the location of the file refering to "event.json" so that it will work in python and to the location of the top level file so that it will work in node.
30 lines
1.2 KiB
Plaintext
30 lines
1.2 KiB
Plaintext
{
|
|
"$schema": "http://json-schema.org/draft-04/schema#",
|
|
"type": "object",
|
|
"title": "NoticeMessage",
|
|
"description": "A m.notice message should be considered similar to a plain m.text message except that clients should visually distinguish it in some way. It is intended to be used by automated clients, such as bots, bridges, and other entities, rather than humans. Additionally, such automated agents which watch a room for messages and respond to them ought to ignore m.notice messages. This helps to prevent infinite-loop situations where two automated clients continuously exchange messages, as each responds to the other.",
|
|
"allOf": [{
|
|
"$ref": "core-event-schema/room_event.json"
|
|
}],
|
|
"properties": {
|
|
"content": {
|
|
"type": "object",
|
|
"properties": {
|
|
"msgtype": {
|
|
"type": "string",
|
|
"enum": ["m.notice"]
|
|
},
|
|
"body": {
|
|
"type": "string",
|
|
"description": "The notice text to send."
|
|
}
|
|
},
|
|
"required": ["msgtype", "body"]
|
|
},
|
|
"type": {
|
|
"type": "string",
|
|
"enum": ["m.room.message"]
|
|
}
|
|
}
|
|
}
|