Skip to content

Commit

Permalink
added files new naming
Browse files Browse the repository at this point in the history
  • Loading branch information
@joachimlindborg
joachimlindborg committed Apr 16, 2013
1 parent ca22866 commit 2a7c9ae
Show file tree
Hide file tree
Showing 19 changed files with 24,461 additions and 0 deletions.
152 changes: 152 additions & 0 deletions xep-0000-IoT-BatteryPoweredSensors.html
View file
@@ -0,0 +1,152 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>XEP-xxxx: XEP Template</title>
<link rel="stylesheet" type="text/css" href="xmpp.css">
<link href="prettify.css" type="text/css" rel="stylesheet">
<link rel="shortcut icon" type="image/x-icon" href="favicon.ico"><script type="text/javascript" src="prettify.js"></script><meta name="DC.Title" content="XEP Template">
<meta name="DC.Creator" content="Peter Saint-Andre">
<meta name="DC.Description" content="This specification provides an example of the format for XMPP Extension Protocols (XEPs).">
<meta name="DC.Publisher" content="XMPP Standards Foundation">
<meta name="DC.Contributor" content="XMPP Extensions Editor">
<meta name="DC.Date" content="2001-09-14">
<meta name="DC.Type" content="XMPP Extension Protocol">
<meta name="DC.Format" content="XHTML">
<meta name="DC.Identifier" content="XEP-xxxx">
<meta name="DC.Language" content="en">
<meta name="DC.Rights" content="This XMPP Extension Protocol is copyright (c) 1999 - 2012 by the XMPP Standards Foundation (XSF).">
</head>
<body onload="prettyPrint()">
<h1>XEP-xxxx: XEP Template</h1>
<table>
<tr valign="top">
<td><strong>Abstract:</strong></td>
<td>This specification provides an example of the format for XMPP Extension Protocols (XEPs).</td>
</tr>
<tr valign="top">
<td><strong>Author:</strong></td>
<td>Peter Saint-Andre</td>
</tr>
<tr valign="top">
<td><strong>Copyright:</strong></td>
<td>© 1999 - 2013 XMPP Standards Foundation. <a href="#appendix-legal">SEE LEGAL NOTICES</a>.</td>
</tr>
<tr valign="top">
<td><strong>Status:</strong></td>
<td>ProtoXEP</td>
</tr>
<tr valign="top">
<td><strong>Type:</strong></td>
<td>Standards Track</td>
</tr>
<tr valign="top">
<td><strong>Version:</strong></td>
<td>0.0.1</td>
</tr>
<tr valign="top">
<td><strong>Last Updated:</strong></td>
<td>2001-09-14</td>
</tr>
</table>
<hr>
<p style="color:red">WARNING: This document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards Foundation, and this document is not yet an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at &lt;<a href="http://xmpp.org/extensions/">http://xmpp.org/extensions/</a>&gt; and announced on the &lt;standards@xmpp.org&gt; mailing list.</p>
<hr>
<h2>Table of Contents</h2>
<div class="indent">
<p><br>1. <a href="#intro">Introduction</a><br>2. <a href="#reqs">Requirements</a><br>3. <a href="#glossary">Glossary</a><br>4. <a href="#usecases">Use Cases</a><br>5. <a href="#rules">Business Rules</a><br>6. <a href="#impl">Implementation Notes</a><br>7. <a href="#access">Accessibility Considerations</a><br>8. <a href="#i18n">Internationalization Considerations</a><br>9. <a href="#security">Security Considerations</a><br>10. <a href="#iana">IANA Considerations</a><br>11. <a href="#registrar">XMPP Registrar Considerations</a><br>12. <a href="#schema">XML Schema</a></p>
<p><a href="#appendices">Appendices</a><br>    <a href="#appendix-docinfo">A: Document Information</a><br>    <a href="#appendix-authorinfo">B: Author Information</a><br>    <a href="#appendix-legal">C: Legal Notices</a><br>    <a href="#appendix-xmpp">D: Relation to XMPP</a><br>    <a href="#appendix-discuss">E: Discussion Venue</a><br>    <a href="#appendix-conformance">F: Requirements Conformance</a><br>    <a href="#appendix-notes">G: Notes</a><br>    <a href="#appendix-revs">H: Revision History</a></p>
</div>
<hr>
<h2>1.
<a name="intro">Introduction</a></h2>
<p class="" style="">This is a template for use in writing XMPP Extension Protocol specifications (XEPs). For detailed information about the XSF's standards process and how to write a XEP, refer to "XEP-0001: XMPP Extension Protocols" and "XEP-0143: Guidelines for Authors of XMPP Extension Protocols".</p>
<h2>2.
<a name="reqs">Requirements</a></h2>
<p class="" style="">STRONGLY RECOMMENDED.</p>
<h2>3.
<a name="glossary">Glossary</a></h2>
<p class="" style="">OPTIONAL.</p>
<h2>4.
<a name="usecases">Use Cases</a></h2>
<p class="" style="">STRONGLY RECOMMENDED.</p>
<h2>5.
<a name="rules">Business Rules</a></h2>
<p class="" style="">OPTIONAL.</p>
<h2>6.
<a name="impl">Implementation Notes</a></h2>
<p class="" style="">OPTIONAL.</p>
<h2>7.
<a name="access">Accessibility Considerations</a></h2>
<p class="" style="">OPTIONAL.</p>
<h2>8.
<a name="i18n">Internationalization Considerations</a></h2>
<p class="" style="">OPTIONAL.</p>
<h2>9.
<a name="security">Security Considerations</a></h2>
<p class="" style="">REQUIRED.</p>
<h2>10.
<a name="iana">IANA Considerations</a></h2>
<p class="" style="">REQUIRED.</p>
<h2>11.
<a name="registrar">XMPP Registrar Considerations</a></h2>
<p class="" style="">REQUIRED.</p>
<h2>12.
<a name="schema">XML Schema</a></h2>
<p class="" style="">REQUIRED for protocol specifications.</p>
<hr><a name="appendices"></a><h2>Appendices</h2>
<hr><a name="appendix-docinfo"></a><h3>Appendix A: Document Information</h3>
<p class="indent">
Series: <a href="http://xmpp.org/extensions/">XEP</a><br>
Number: xxxx<br>
Publisher: <a href="/xsf/">XMPP Standards Foundation</a><br>
Status:
<a href="http://xmpp.org/extensions/xep-0001.html#states-ProtoXEP">ProtoXEP</a><br>
Type:
<a href="http://xmpp.org/extensions/xep-0001.html#types-Standards Track">Standards Track</a><br>
Version: 0.0.1<br>
Last Updated: 2001-09-14<br>
Approving Body: <a href="http://xmpp.org/council/">XMPP Council</a><br>Dependencies: XMPP Core, XEP-0001, Etc.<br>
Supersedes: None<br>
Superseded By: None<br>
Short Name: NOT_YET_ASSIGNED<br>
This document in other formats:
<a class="standardsButton" href="http://xmpp.org/extensions/xep-xxxx.xml">XML</a> 
<a class="standardsButton" href="http://xmpp.org/extensions/xep-xxxx.pdf">PDF</a></p>
<hr><a name="appendix-authorinfo"></a><h3>Appendix B: Author Information</h3>
<div class="indent">
<h3>Peter Saint-Andre</h3>
<p class="indent">
Email:
<a href="mailto:stpeter@jabber.org">stpeter@jabber.org</a><br>
JabberID:
<a href="xmpp:stpeter@jabber.org">stpeter@jabber.org</a><br></p>
</div>
<hr><a name="appendix-legal"></a><h3>Appendix C: Legal Notices</h3>
<div class="indent">
<h4>Copyright</h4>This XMPP Extension Protocol is copyright (c) 1999 - 2012 by the XMPP Standards Foundation (XSF).<h4>Permissions</h4>Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.<h4>Disclaimer of Warranty</h4><span style="font-weight: bold">## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##</span><h4>Limitation of Liability</h4>In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.<h4>IPR Conformance</h4>
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at &lt;<a href="http://www.xmpp.org/extensions/ipr-policy.shtml">http://www.xmpp.org/extensions/ipr-policy.shtml</a>&gt; or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).
</div>
<hr><a name="appendix-xmpp"></a><h3>Appendix D: Relation to XMPP</h3>
<p class="indent">The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.</p>
<hr><a name="appendix-discuss"></a><h3>Appendix E: Discussion Venue</h3>
<p class="indent">The primary venue for discussion of XMPP Extension Protocols is the &lt;<a href="http://mail.jabber.org/mailman/listinfo/standards">standards@xmpp.org</a>&gt; discussion list.</p>
<p class="indent">Discussion on other xmpp.org discussion lists might also be appropriate; see &lt;<a href="http://xmpp.org/about/discuss.shtml">http://xmpp.org/about/discuss.shtml</a>&gt; for a complete list.</p>
<p class="indent">Errata can be sent to &lt;<a href="mailto:editor@xmpp.org">editor@xmpp.org</a>&gt;.</p>
<hr><a name="appendix-conformance"></a><h3>Appendix F: Requirements Conformance</h3>
<p class="indent">The following requirements keywords as used in this document are to be interpreted as described in <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a>: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".</p>
<hr><a name="appendix-notes"></a><h3>Appendix G: Notes</h3>
<div class="indent"></div>
<hr><a name="appendix-revs"></a><h3>Appendix H: Revision History</h3>
<p>Note: Older versions of this specification might be available at <a href="http://xmpp.org/extensions/attic/">http://xmpp.org/extensions/attic/</a></p>
<div class="indent">
<h4>Version 0.0.1 (2001-09-14)</h4>
<div class="indent">
<p class="" style="">First draft.</p>
(psa)
</div>
</div>
<hr>
<p>END</p>
</body>
</html>
85 changes: 85 additions & 0 deletions xep-0000-IoT-BatteryPoweredSensors.xml
View file
@@ -0,0 +1,85 @@
<?xml version='1.0' encoding='UTF-8'?>
<!-- TODO: http://xmpp.org/extensions/xep-0160.html -->
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<xep>
<header>
<title>XEP Template</title>
<abstract>This specification provides an example of the format for XMPP Extension Protocols (XEPs).</abstract>
<legal>
<copyright>This XMPP Extension Protocol is copyright (c) 1999 - 2012 by the XMPP Standards Foundation (XSF).</copyright>
<permissions>Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the &quot;Specification&quot;), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.</permissions>
<warranty>## NOTE WELL: This Specification is provided on an &quot;AS IS&quot; BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##</warranty>
<liability>In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.</liability>
<conformance>
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at &lt;<link url='http://www.xmpp.org/extensions/ipr-policy.shtml'>http://www.xmpp.org/extensions/ipr-policy.shtml</link>&gt; or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).
</conformance>
</legal>
<number>xxxx</number>
<status>ProtoXEP</status>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
<dependencies>
<spec>XMPP Core</spec>
<spec>XEP-0001</spec>
<spec>Etc.</spec>
</dependencies>
<supersedes/>
<supersededby/>
<shortname>NOT_YET_ASSIGNED</shortname>
<author>
<firstname>Peter</firstname>
<surname>Saint-Andre</surname>
<email>stpeter@jabber.org</email>
<jid>stpeter@jabber.org</jid>
</author>
<revision>
<version>0.0.1</version>
<date>2001-09-14</date>
<initials>psa</initials>
<remark>
<p>First draft.</p>
</remark>
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
<p>This is a template for use in writing XMPP Extension Protocol specifications (XEPs). For detailed information about the XSF's standards process and how to write a XEP, refer to "XEP-0001: XMPP Extension Protocols" and "XEP-0143: Guidelines for Authors of XMPP Extension Protocols".</p>
</section1>
<section1 topic='Requirements' anchor='reqs'>
<p>STRONGLY RECOMMENDED.</p>
</section1>
<section1 topic='Glossary' anchor='glossary'>
<p>OPTIONAL.</p>
</section1>
<section1 topic='Use Cases' anchor='usecases'>
<p>STRONGLY RECOMMENDED.</p>
</section1>
<section1 topic='Business Rules' anchor='rules'>
<p>OPTIONAL.</p>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>
<p>OPTIONAL.</p>
</section1>
<section1 topic='Accessibility Considerations' anchor='access'>
<p>OPTIONAL.</p>
</section1>
<section1 topic='Internationalization Considerations' anchor='i18n'>
<p>OPTIONAL.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>REQUIRED.</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>REQUIRED.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<p>REQUIRED.</p>
</section1>
<section1 topic='XML Schema' anchor='schema'>
<p>REQUIRED for protocol specifications.</p>
</section1>
</xep>

0 comments on commit 2a7c9ae

Please sign in to comment.