moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 15:18:51 -05:00
Code Issues Releases Wiki Activity

0.6

Browse Source
This commit is contained in:
Peter Saint-Andre 2012-05-29 20:29:24 -06:00
parent a14395f4be
commit 473b989328
1 changed files with 58 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

65
xep-0268.xml
View File

@ -1,6 +1,8 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
<!ENTITY ADDITION "&lt;AdditionalData/&gt;">
<!ENTITY JID "&lt;jid/&gt;">
%ents;
]>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
@ -41,6 +43,12 @@
</author>
&stpeter;
&mwild;
<revision>
<version>0.6</version>
<date>2012-05-29</date>
<initials>psa</initials>
<remark><p>Aligned document with the IETF guidelines for defining extensions to IODEF; defined several more IODEF NodeRole categories; added schema for the JID element; noted that the JID element might be moved to a separate specification.</p></remark>
</revision>
<revision>
<version>0.5</version>
<date>2012-05-16</date>
@ -313,8 +321,33 @@
<p>If the recipient is able to process the report, it MUST return an &IQ; stanza of type "result"; if not, it MUST return an &IQ; stanza of type "error" (error handling will be defined in a future version of this specification).</p>
</section1>
<section1 topic='Definition of IODEF Extensions' anchor='iodef'>
<p>This document defines the following IODEF extensions, described in accordance with the guidelines in &miletemplate;.</p>
<section2 topic='Contact' anchor='iodef-contact'>
<p>This specification defines an extended Contact role of "chatroom", i.e., a new enumerated value for the Contact@role attribute. This value specifies a text conference where discussion of the incident can take place, e.g., an IRC channel or an XMPP &xep0045; room. Since there are many different chatroom technologies, the address of the chatroom shall be specified as the child of an &ADDITION; element. For XMPP chatrooms, the address is the XML character data of a &JID; element qualified by the 'urn:xmpp:jid:0' namespace.</p>
<p>Note: Definition of the &JID; element might be moved to a separate specification.</p>
</section2>
<section2 topic='Address' anchor='iodef-address'>
<p>This specification defines an extended Address category of "xmpp", i.e., a new enumerated value for the Address@category attribute. This value specifies the JabberID of a network entity, in conformance with &rfc6122; or its successor.</p>
</section2>
<section2 topic='NodeRole' anchor='iodef-noderole'>
<p>This specification defines several extended NodeRole categories, i.e., new enumerated values for the NodeRole@category attribute:</p>
<ul>
<li>"xmpp" -- the network role of an XMPP service or core router as defined by &rfc6120; and &rfc6121;</li>
<li>"xmpp-bytestreams" -- the network role of an XMPP SOCKS5 byestreams service as defined by &xep0065;</li>
<li>"xmpp-muc" -- the network role of an XMPP multi-user chat service as defined by <cite>XEP-0045</cite></li>
<li>"xmpp-pubsub" -- the network role of an XMPP pubsub service as defined by &xep0060;</li>
</ul>
</section2>
<section2 topic='AdditionalData' anchor='iodef-additionaldata'>
<p>This specification defines an AdditionalData element of &JID; qualified by the 'urn:xmpp:jid:0' namespace. The XML character data of this element is a JabberID (i.e., an XMPP address) that conforms to RFC 6122 or its successor.</p>
<p>Note: Definition of the &JID; element might be moved to a separate specification.</p>
</section2>
</section1>
<section1 topic='Internationalization Considerations' anchor='i18n'>
<p>The &lt;jid/&gt; element qualified by the 'urn:xmpp:incident:2' namespace is a "JID slot" as described in &rfc6122bis;.</p>
<p>The &JID; element qualified by the 'urn:xmpp:incident:2' namespace is a "JID slot" as described in &rfc6122bis;.</p>
<p>Note: Definition of the &JID; element might be moved to a separate specification.</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
@ -331,7 +364,7 @@
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document might require interaction with &IANA; to register various IODEF extension attributes.</p>
<p>This document might require interaction with &IANA; to register various IODEF extensions, in accordance with <cite>draft-ietf-mile-template</cite>.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='reg'>
@ -339,16 +372,19 @@
<p>This specification defines the following XML namespace:</p>
<ul>
<li>urn:xmpp:incident:2</li>
<li>urn:xmpp:jid:0</li>
</ul>
<p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
<p>Note: Registration of the 'urn:xmpp:jid:0' namespace might be moved to a separate specification.</p>
</section2>
<section2 topic='Protocol Versioning' anchor='registrar-versioning'>
&NSVER;
</section2>
</section1>
<section1 topic='XML Schema' anchor='schema'>
<code><![CDATA[
<section1 topic='XML Schemas' anchor='schemas'>
<section2 topic='Incident Namespace' anchor='schemas-incident'>
<code><![CDATA[
<?xml version='1.0' encoding='UTF-8'?>
<xs:schema
@ -359,8 +395,6 @@
<xs:import namespace='urn:ietf:params:xml:ns:iodef-1.0'/>
<xs:element name='jid' type='xs:string'/>
<xs:element name='inquiry' type='IODEFContainerType'/>
<xs:element name='report' type='IODEFContainerType'/>
<xs:element name='request' type='IODEFContainerType'/>
@ -373,7 +407,24 @@
</xs:complexType>
</xs:schema>
]]></code>
]]></code>
</section2>
<section2 topic='JID Namespace' anchor='schemas-jid'>
<p>Note: This schema and associated text might be moved to a separate specification.</p>
<code><![CDATA[
<?xml version='1.0' encoding='UTF-8'?>
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='urn:xmpp:jid:0'
xmlns='urn:xmpp:jid:0'
elementFormDefault='qualified'>
<xs:element name='jid' type='xs:string'/>
</xs:schema>
]]></code>
</section2>
</section1>
</xep>