mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-28 04:02:20 -05:00
Some aesthetic changes.
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3530 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
parent
0dd8696879
commit
88da694266
12
index.shtml
12
index.shtml
@ -9,7 +9,7 @@
|
|||||||
|
|
||||||
<p>XMPP is the Extensible Messaging and Presence Protocol, a set of open <a href='/tech/'>technologies</a> for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.</p>
|
<p>XMPP is the Extensible Messaging and Presence Protocol, a set of open <a href='/tech/'>technologies</a> for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.</p>
|
||||||
<p>The <a href='/xsf/'>XMPP Standards Foundation</a> (XSF) develops extensions to <a href="/">XMPP</a> through a standards process centered around XMPP Extension Protocols (XEPs). The <a href="xep-0001.html">process</a> is managed by the <a href="editor.shtml">XMPP Extensions Editor</a> and involves intensive discussion on the <a href="http://mail.jabber.org/mailman/listinfo/standards/">Standards mailing list</a>, formal review and <a href="/council/votes.shtml">voting</a> by the <a href="/council/">XMPP Council</a>, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal <a href="ipr-policy.shtml">IPR Policy</a> for wide implementation. Submissions are <a href='submit.shtml'>welcome</a> (see also the <a href="/extensions/inbox/">"inbox"</a>). All XEPs and related files are under <a href="/xsf/sourcecontrol.shtml">source control</a>, <a href="/extensions/attic/">old versions</a> are available, and IETF-style <a href="/extensions/refs/">XML reference files</a> are provided.</p>
|
<p>The <a href='/xsf/'>XMPP Standards Foundation</a> (XSF) develops extensions to <a href="/">XMPP</a> through a standards process centered around XMPP Extension Protocols (XEPs). The <a href="xep-0001.html">process</a> is managed by the <a href="editor.shtml">XMPP Extensions Editor</a> and involves intensive discussion on the <a href="http://mail.jabber.org/mailman/listinfo/standards/">Standards mailing list</a>, formal review and <a href="/council/votes.shtml">voting</a> by the <a href="/council/">XMPP Council</a>, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal <a href="ipr-policy.shtml">IPR Policy</a> for wide implementation. Submissions are <a href='submit.shtml'>welcome</a> (see also the <a href="/extensions/inbox/">"inbox"</a>). All XEPs and related files are under <a href="/xsf/sourcecontrol.shtml">source control</a>, <a href="/extensions/attic/">old versions</a> are available, and IETF-style <a href="/extensions/refs/">XML reference files</a> are provided.</p>
|
||||||
<p>This page lists approved XMPP extensions as well as proposals that are under active consideration. Good places for developers to start are the <a href='xep-0242.html'>client compliance</a> and <a href='xep-0243.html'>server compliance</a> definitions, as well as the <a href='/tech/'>technology overview pages</a>.</p>
|
<p>This page lists approved XMPP extensions as well as proposals that are under active consideration. A <a href="all.shtml">list of all XEPs</a> (including retracted, rejected, deprecated, and obsolete XEPs) is also available. Good places for developers to start are the <a href='xep-0242.html'>client compliance</a> and <a href='xep-0243.html'>server compliance</a> definitions, as well as the <a href='/tech/'>technology overview pages</a>.</p>
|
||||||
<p class="jsSupport" style="display: none;"><em>Note: The following table is sortable, just click on the headers (click twice to reverse the sort order).</em></p>
|
<p class="jsSupport" style="display: none;"><em>Note: The following table is sortable, just click on the headers (click twice to reverse the sort order).</em></p>
|
||||||
<p class="jsSupport" style="display: none;"><em>Note: You can change show/hide the various types of XEPs by checking/unchecking the checkboxes below.</em></p>
|
<p class="jsSupport" style="display: none;"><em>Note: You can change show/hide the various types of XEPs by checking/unchecking the checkboxes below.</em></p>
|
||||||
<form>
|
<form>
|
||||||
@ -18,20 +18,20 @@
|
|||||||
$("p#status-selector > input").click(function(event){
|
$("p#status-selector > input").click(function(event){
|
||||||
var xep_status = $(this).attr("name");
|
var xep_status = $(this).attr("name");
|
||||||
if (this.checked) {
|
if (this.checked) {
|
||||||
$(".XEP-" + xep_status).css("display", "");
|
$(".XEP-" + xep_status).fadeIn("normal");
|
||||||
} else {
|
} else {
|
||||||
$(".XEP-" + xep_status).css("display", "none");
|
$(".XEP-" + xep_status).fadeOut("normal");
|
||||||
}
|
}
|
||||||
});
|
});
|
||||||
jQuery.each($("p#status-selector > input"), function() {
|
jQuery.each($("p#status-selector > input"), function() {
|
||||||
var xep_status = $(this).attr("name");
|
var xep_status = $(this).attr("name");
|
||||||
if (this.checked) {
|
if (this.checked) {
|
||||||
$(".XEP-" + xep_status).css("display", "");
|
$(".XEP-" + xep_status).show();
|
||||||
} else {
|
} else {
|
||||||
$(".XEP-" + xep_status).css("display", "none");
|
$(".XEP-" + xep_status).hide();
|
||||||
}
|
}
|
||||||
});
|
});
|
||||||
$(".jsSupport").css("display", "");
|
$(".jsSupport").fadeIn("normal");
|
||||||
});
|
});
|
||||||
</script>
|
</script>
|
||||||
<p id="status-selector" class="jsSupport" style="display: none;">
|
<p id="status-selector" class="jsSupport" style="display: none;">
|
||||||
|
Loading…
Reference in New Issue
Block a user