2006-10-02 18:22:13 -04:00
<?xml version='1.0' encoding='UTF-8'?>
2006-10-03 19:25:20 -04:00
< !DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM "xep.ent">
2006-10-02 18:22:13 -04:00
%ents;
]>
2006-10-03 19:25:20 -04:00
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep >
2006-10-02 18:22:13 -04:00
<header >
<title > Shared Notes</title>
<abstract > A simplistic mechanism for shared notes, modeled after common stickie note applications.</abstract>
&LEGALNOTICE;
<number > 0061</number>
<status > Deferred</status>
<type > Informational</type>
2007-01-14 22:38:19 -05:00
<sig > Standards</sig>
2017-01-01 19:46:56 -05:00
<dependencies > <spec > XMPP Core</spec> </dependencies>
2016-12-26 10:02:53 -05:00
<supersedes />
<supersededby />
2006-10-02 18:22:13 -04:00
<shortname > Not yet assigned</shortname>
<author >
<firstname > Jeremie</firstname>
<surname > Miller</surname>
<email > jer@jabber.org</email>
<jid > jer@jabber.org</jid>
</author>
<revision >
<version > 0.2</version>
<date > 2003-09-30</date>
<initials > psa</initials>
2017-02-14 17:10:01 -05:00
<remark > At the request of the author, changed the status of this document to Deferred pending development of an implementation; also changed the type to Informational.</remark>
2006-10-02 18:22:13 -04:00
</revision>
<revision >
<version > 0.1</version>
<date > 2002-12-06</date>
<initials > jer</initials>
<remark > Initial version.</remark>
</revision>
</header>
<section1 topic= 'Introduction' >
2017-02-14 17:10:01 -05:00
<p > A very simple namespace contaning display hints for the content in a message. Can be used for
2006-10-02 18:22:13 -04:00
person-person collaboration, or by a service managing notes.</p>
</section1>
<section1 topic= 'Message Extension' >
2017-02-14 17:10:01 -05:00
<p > Normal messages are sent, with a sharednote namespace extending them hinting to any supporting client on
how to display the message as a note instead. Any changes to the note within that client should then be sent
back to the sender, either automatically or when the user saves the note (depending on the update element, by
2006-10-02 18:22:13 -04:00
default on a save action by the user).</p>
<example caption= 'An Example Shared Note Message' > < ![CDATA[
<message from= "jer@jabber.org/foo" to= "stpeter@jabber.org/bar" >
<thread > 1X544O</thread>
<subject > Council Votes</subject>
2006-10-03 19:25:20 -04:00
<body > Need votes from bob, tom, and jane yet for XEP-0000</body>
2006-10-02 18:22:13 -04:00
<note xmlns= "http://www.jabber.org/protocol/sharednote" >
<color > #001122</color>
<bgcolor > #221100</bgcolor>
<font > font-name</font>
<x > %left</x>
<y > %top</y>
<z > #</z>
<width > %</width>
<height > %</height>
<update > auto|user</update>
</note>
</message>
2017-02-14 17:08:49 -05:00
]]></example>
2006-10-02 18:22:13 -04:00
2017-02-14 17:10:01 -05:00
<p > Any element not specified in the note should use the last known setting or client defaults, so that when a
2006-10-02 18:22:13 -04:00
change is sent, only the changed elements are returned.</p>
</section1>
<section1 topic= 'Implementation Notes' >
<p > Each thread is a different shared note. Auto updates should use an internal client timer and batch large
changes into chunks, when the user is typing every 5-10 seconds or so. When the user has made changes that
2017-02-14 17:10:01 -05:00
haven't been sent and an update comes in on the same thread the client should prompt the user with the
2006-10-02 18:22:13 -04:00
changes offering to replace or save their changes.</p>
</section1>
2006-10-03 19:25:20 -04:00
</xep>
2006-10-02 18:22:13 -04:00
