From a9a4c46a57da618ea0d16ddfcdea84bc78d6e2be Mon Sep 17 00:00:00 2001
From: "Paul \"LeoNerd\" Evans" <leonerd@leonerd.org.uk>
Date: Wed, 21 Jan 2015 18:26:27 +0000
Subject: [PATCH] Add spec for m.notice (SPEC-18)

---
 specification/10_events.rst | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/specification/10_events.rst b/specification/10_events.rst
index 2597ce82..20dccb6b 100644
--- a/specification/10_events.rst
+++ b/specification/10_events.rst
@@ -330,6 +330,22 @@ outlined below:
   Example:
     ``{ "msgtype": "m.emote", "body": "tries to come up with a witty explanation" }``
 
+``m.notice``
+  Required keys:
+    - ``body`` : "string" - The body of the message.
+  Optional keys:
+    None.
+  Example:
+    ``{ "msgype": "m.notice", "body": "some kind of automated announcement" }``
+
+  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.
+
 ``m.image``
   Required keys:
     - ``url`` : "string" - The URL to the image.