example fixes

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1650 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-02-04 16:06:06 +00:00
parent bfd0204c0d
commit 4d15d5f0c0
1 changed files with 4 additions and 4 deletions

View File

@ -131,7 +131,7 @@
<tr>
<td>rating</td>
<td>The user's rating of the song or piece, from 1 (lowest) to 10 (highest).</td>
<td>9</td>
<td>8</td>
<td>xs:positiveInteger</td>
</tr>
<tr>
@ -173,7 +173,7 @@
<tune xmlns='http://jabber.org/protocol/tune'>
<artist>Yes</artist>
<length>686</length>
<rating>9</rating>
<rating>8</rating>
<source>Yessongs</source>
<title>Heart of the Sunrise</title>
<track>3</track>
@ -195,7 +195,7 @@
<tune xmlns='http://jabber.org/protocol/tune'>
<artist>Yes</artist>
<length>686</length>
<rating>9</rating>
<rating>8</rating>
<source>Yessongs</source>
<title>Heart of the Sunrise</title>
<track>3</track>
@ -246,7 +246,7 @@
<section1 topic='Implementation Notes' anchor='impl'>
<p>To prevent a large number of updates when a user is skipping through tracks, an implementation SHOULD wait several seconds before publishing new tune information.</p>
<p>If the length is unknown (e.g., the user is listening to a stream), the &lt;length/&gt; element SHOULD NOT be included.</p>
<p>A typical interface for user ratings is to show one to five star icons such as &#9734;&#9734;&#9734;&#9734;&#9734;. If this interface is used, the numbers 2, 4, 6, 8, and 10 should be mapped to one, two, three, four, and five stars respectively, and odd numbers should be mapped to half stars (e.g., the number 9 would be mapped to four-and-a-half stars).</p>
<p>A typical interface for user ratings is to show one to five star icons such as &#9733;&#9733;&#9733;&#9733;. If this interface is used, the numbers 2, 4, 6, 8, and 10 should be mapped to one, two, three, four, and five stars respectively, and odd numbers should be mapped to half stars (e.g., the number 9 would be mapped to four-and-a-half stars).</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>The publication of user tune information is not known to introduce any new security considerations above and beyond those defined in <cite>XEP-0060: Publish-Subscribe</cite>.</p>