moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00
Code Issues Releases Wiki Activity

0.11

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1094 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-07-25 23:55:02 +00:00
parent a2826ebd4a
commit 67e4aacb8a
1 changed files with 6 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
xep-0084.xml
View File

@ -28,6 +28,12 @@
&pgmillard; &pgmillard;
&temas; &temas;
&xvirge; &xvirge;
<revision>
<version>0.11</version>
<date>2007-07-25</date>
<initials>psa</initials>
<remark><p>Removed image size requirements.</p></remark>
</revision>
<revision> <revision>
<version>0.10</version> <version>0.10</version>
<date>2007-06-18</date> <date>2007-06-18</date>
@ -431,17 +437,6 @@
<p>The contact then MAY subscribe to the metadata node following the protocol specified in <cite>XEP-0060</cite>. However, the contact SHOULD NOT subscribe to the data node (instead, it SHOULD simply retrieve items from that node when needed, as described above).</p> <p>The contact then MAY subscribe to the metadata node following the protocol specified in <cite>XEP-0060</cite>. However, the contact SHOULD NOT subscribe to the data node (instead, it SHOULD simply retrieve items from that node when needed, as described above).</p>
</section2> </section2>
</section1> </section1>
<section1 topic='Business Rules' anchor='bizrules'>
<section2 topic='Image Requirements' anchor='bizrules-images'>
<p>The following restrictions apply to the image:</p>
<ol>
<li>The image height and width SHOULD be between thirty-two (32) and ninety-six (96) pixels.</li>
<li>The suggested size is sixty-four (64) pixels high and sixty-four (64) pixels wide.</li>
<li>The image SHOULD be square.</li>
<li>The image SHOULD use less than eight (8) kilobytes of data.</li>
</ol>
</section2>
</section1>
<section1 topic='Implementation Notes' anchor='impl'> <section1 topic='Implementation Notes' anchor='impl'>
<section2 topic='Multiple Resources' anchor='impl-resources'> <section2 topic='Multiple Resources' anchor='impl-resources'>
<p>If a user has multiple online resources at the same time, each resource MAY publish a different avatar. The PEP service SHOULD include the replyto address of the publishing resource as shown above in order to facilitate differentiation between per-resource avatars.</p> <p>If a user has multiple online resources at the same time, each resource MAY publish a different avatar. The PEP service SHOULD include the replyto address of the publishing resource as shown above in order to facilitate differentiation between per-resource avatars.</p>