moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

1.0 DRAFT 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2189 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-09-03 21:00:22 +00:00
parent 32c39ddeca
commit f04dba046c
1 changed files with 28 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
xep-0231.xml
View File

@ -10,7 +10,7 @@
<abstract>This specification defines an XMPP protocol extension for including or referring to small bits of binary data in an XML stanza.</abstract>
&LEGALNOTICE;
<number>0231</number>
<status>Proposed</status>
<status>Draft</status>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
@ -24,9 +24,18 @@
</dependencies>
<supersedes/>
<supersededby/>
<shortname>NOT_YET_ASSIGNED</shortname>
<shortname>bob</shortname>
<schemaloc>
<url>http://www.xmpp.org/schemas/bob.xsd</url>
</schemaloc>
&stpeter;
&pavlix;
<revision>
<version>1.0</version>
<date>2008-09-03</date>
<initials>psa</initials>
<remark><p>Per a vote of the XMPP Council, advanced status to Draft; concurrently, the XMPP Registrar issued the urn:xmpp:bob namespace.</p></remark>
</revision>
<revision>
<version>0.9</version>
<date>2008-08-16</date>
@ -157,7 +166,7 @@
id='get-data-1'
to='ladymacbeth@shakespeare.lit/castle'
type='get'>
<data xmlns='urn:xmpp:tmp:bob'
<data xmlns='urn:xmpp:bob'
cid='sha1+8f35fef110ffc5df08d579a50083ff9308fb6242@bob.xmpp.org'/>
</iq>
]]></example>
@ -167,7 +176,7 @@
id='get-data-1'
to='doctor@shakespeare.lit/pda'
type='result'>
<data xmlns='urn:xmpp:tmp:bob'
<data xmlns='urn:xmpp:bob'
cid='sha1+8f35fef110ffc5df08d579a50083ff9308fb6242@bob.xmpp.org'/>
max-age='86400'
type='image/png'>
@ -191,7 +200,7 @@
</section2>
<section2 topic='Format of the &lt;data/&gt; Element' anchor='format'>
<p>To exchange binary data, the data is encapsulated as the XML character data of a &lt;data/&gt; element qualified by the 'urn:xmpp:tmp:bob' namespace &NSNOTE;, where the data MUST be encoded as Base64 in accordance with Section 4 of &rfc4648; (note: the Base64 output MUST NOT include whitespace and MUST set the number of pad bits to zero).</p>
<p>To exchange binary data, the data is encapsulated as the XML character data of a &lt;data/&gt; element qualified by the 'urn:xmpp:bob' namespace, where the data MUST be encoded as Base64 in accordance with Section 4 of &rfc4648; (note: the Base64 output MUST NOT include whitespace and MUST set the number of pad bits to zero).</p>
<p>The following attributes are defined for the &lt;data/&gt; element.</p>
<table caption='Attributes of the data Element'>
<tr>
@ -217,7 +226,7 @@
</table>
<p>The following example illustrates the format (line endings are provided for readability only).</p>
<example caption='Data element format'><![CDATA[
<data xmlns='urn:xmpp:tmp:bob'
<data xmlns='urn:xmpp:bob'
cid='sha1+8f35fef110ffc5df08d579a50083ff9308fb6242@bob.xmpp.org'/>
max-age='86400'
type='image/png'>
@ -234,7 +243,7 @@
</section1>
<section1 topic='Determining Support' anchor='support'>
<p>If an entity supports the protocol specified herein, it MUST advertise that fact by returning a feature of "urn:xmpp:tmp:bob" in response to &xep0030; information requests &NSNOTE;.</p>
<p>If an entity supports the protocol specified herein, it MUST advertise that fact by returning a feature of "urn:xmpp:bob" in response to &xep0030; information requests.</p>
<example caption="Service discovery information request"><![CDATA[
<iq from='doctor@shakespeare.lit/pda'
id='disco1'
@ -250,12 +259,12 @@
type='result'>
<query xmlns='http://jabber.org/protocol/disco#info'>
...
<feature var='urn:xmpp:tmp:bob'/>
<feature var='urn:xmpp:bob'/>
...
</query>
</iq>
]]></example>
<p>In order for an application to determine whether an entity supports this protocol, where possible it SHOULD via the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.</p>
<p>In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
@ -268,7 +277,7 @@
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespace shall be "urn:xmpp:tmp:bob"; upon advancement of this specification, the &REGISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;. The namespace 'urn:xmpp:bob' is requested and is thought to be unique per the XMPP Registrar's requirements.</p>
<p>The &REGISTRAR; includes "urn:xmpp:bob" in its registry of protocol namespaces (see &NAMESPACES;).</p>
</section2>
</section1>
@ -278,10 +287,17 @@
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='urn:xmpp:tmp:bob'
xmlns='urn:xmpp:tmp:bob'
targetNamespace='urn:xmpp:bob'
xmlns='urn:xmpp:bob'
elementFormDefault='qualified'>
<xs:annotation>
<xs:documentation>
The protocol documented by this schema is defined in
XEP-0231: http://www.xmpp.org/extensions/xep-0231.html
</xs:documentation>
</xs:annotation>
<xs:element name='data'>
<xs:complexType>
<xs:simpleContent>
@ -294,12 +310,6 @@
</xs:complexType>
</xs:element>
<xs:simpleType name='empty'>
<xs:restriction base='xs:string'>
<xs:enumeration value=''/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
]]></code>
</section1>