mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-05 03:04:11 +01: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.3 KiB
Plaintext
30 lines
1.3 KiB
Plaintext
{
|
|
"$schema": "http://json-schema.org/draft-04/schema#",
|
|
"type": "object",
|
|
"title": "Redaction",
|
|
"description": "Events can be redacted by either room or server admins. Redacting an event means that all keys not required by the protocol are stripped off, allowing admins to remove offensive or illegal content that may have been attached to any event. This cannot be undone, allowing server owners to physically delete the offending data. There is also a concept of a moderator hiding a message event, which can be undone, but cannot be applied to state events. The event that has been redacted is specified in the ``redacts`` event level key.",
|
|
"allOf": [{
|
|
"$ref": "core-event-schema/room_event.json"
|
|
}],
|
|
"properties": {
|
|
"content": {
|
|
"type": "object",
|
|
"properties": {
|
|
"reason": {
|
|
"type": "string",
|
|
"description": "The reason for the redaction, if any."
|
|
}
|
|
}
|
|
},
|
|
"redacts": {
|
|
"type": "string",
|
|
"description": "The event ID that was redacted."
|
|
},
|
|
"type": {
|
|
"type": "string",
|
|
"enum": ["m.room.redaction"]
|
|
}
|
|
},
|
|
"required": ["redacts"]
|
|
}
|