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

XEP-0350 Data Forms Geoloation Element: approved by XMPP Council 

--HG--
rename : extensions/inbox/geoloc-dataform.xml => extensions/xep-0350.xml
This commit is contained in:
Matthew A. Miller 2014-07-03 08:55:26 -06:00
parent 9c36a074aa
commit 312588a298
2 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
inbox/geoloc-dataform.xml → xep-0350.xml
View File

@ -9,8 +9,8 @@
<title>Data Forms Geolocation Element</title>
<abstract>This specification defines an XMPP protocol extension for including geolocation data in XEP-0004 data forms.</abstract>
&LEGALNOTICE;
<number>xxxx</number>
<status>ProtoXEP</status>
<number>0350</number>
<status>Experimental</status>
<type>Standards Track</type>
<sig>Standards</sig>
<dependencies>
@ -31,6 +31,14 @@
<email>laukner@gmail.com</email>
<jid>laukner@jabber.org</jid>
</author>
<revision>
<version>0.1</version>
<date>2014-07-03</date>
<initials>editor (mam)</initials>
<remark>
<p>Initial published version approved by the XMPP Council.</p>
</remark>
</revision>
<revision>
<version>0.0.3</version>
<date>2014-06-28</date>
@ -85,7 +93,7 @@
</x>]]></example>
</section1>
<section1 topic='Allow Receiver to Valdidate Geolocation Data' anchor='validation'>
<p>All elements associated with location fields MUST be qualified by the 'http://jabber.org/protocol/geoloc' namespace. The use of namespace prefixes is RECOMMENDED for large forms, to reduce the data size. To maintain the highest level of compatibility, implementations sending the form using prefixes SHOULD use the namespace prefix "geo:", and SHOULD declare the namespace prefix mapping in the ancestor &gt;x xmlns='jabber:x:data'/&lt; element:</p>
<p>All elements associated with location fields MUST be qualified by the 'http://jabber.org/protocol/geoloc' namespace. The use of namespace prefixes is RECOMMENDED for large forms, to reduce the data size. To maintain the highest level of compatibility, implementations sending the form using prefixes SHOULD use the namespace prefix "geo:", and SHOULD declare the namespace prefix mapping in the ancestor &lt;x xmlns='jabber:x:data'/&gt; element:</p>
<p>The following example is provided only for the purpose of illustration; consult the specifications for using protocols (e.g. XEP-0080, XEP-0122) to see canonical examples.</p>
<example caption='Validation of Geolocation Data'><![CDATA[<x xmlns='jabber:x:data'
xmlns:geo= http://jabber.org/protocol/geoloc'

1
xep.ent
View File

@ -1328,3 +1328,4 @@ IANA Service Location Protocol, Version 2 (SLPv2) Templates</link></span> <note>
<!ENTITY xep0347 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0347.html'>Internet of Things - Discovery (XEP-0347)</link></span> <note>XEP-0347: Internet of Things - Discovery &lt;<link url='http://xmpp.org/extensions/xep-0347.html'>http://xmpp.org/extensions/xep-0347.html</link>&gt;.</note>" >
<!ENTITY xep0348 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0348.html'>Signing Forms (XEP-0348)</link></span> <note>XEP-0348: Signing Forms &lt;<link url='http://xmpp.org/extensions/xep-0348.html'>http://xmpp.org/extensions/xep-0348.html</link>&gt;.</note>" >
<!ENTITY xep0349 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0349.html'>Rayo Clustering (XEP-0349)</link></span> <note>XEP-0349: Rayo Clustering &lt;<link url='http://xmpp.org/extensions/xep-0349.html'>http://xmpp.org/extensions/xep-0349.html</link>&gt;.</note>" >
<!ENTITY xep0349 "<span class='ref'><link url='http://xmpp.org/extensions/xep-0350.html'>Data Forms Geolocation Element (XEP-0350)</link></span> <note>XEP-0350: Data Forms Geolocation Element &lt;<link url='http://xmpp.org/extensions/xep-0330.html'>http://xmpp.org/extensions/xep-0350.html</link>&gt;.</note>" >