moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2025-02-07 02:40:22 -05:00
Code Issues Releases Wiki Activity

XEP-0412: introduce 'Category' and 'Level' dimensions

Browse Source
This commit is contained in:
Georg Lukas 2019-03-25 19:07:34 +01:00
parent 97104b2bb3
commit d4117e6099
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
xep-0412.xml
View File

@ -92,13 +92,20 @@
This document specifies compliance levels for XMPP clients and servers; it This document specifies compliance levels for XMPP clients and servers; it
is hoped that this document will advance the state of the art, and provide is hoped that this document will advance the state of the art, and provide
guidance and eventual certification to XMPP client and server authors. guidance and eventual certification to XMPP client and server authors.
</p>
<p>
This document defines <strong>Categories</strong> based on
typical use cases (Core, Web, IM, Mobile) and <strong>Levels</strong>
(Core, Advanced) based on functionality in the respective category.
</p>
<p>
Unless explicitly noted, support for the listed specifications is REQUIRED Unless explicitly noted, support for the listed specifications is REQUIRED
for compliance purposes. for compliance purposes.
A feature is considered supported if all comma separated feature providers A feature is considered supported if all comma separated feature providers
listed in the "Providers" column are implemented (unless otherwise noted). listed in the "Providers" column are implemented (unless otherwise noted).
</p> </p>
</section1> </section1>
<section1 topic='Compliance Levels' anchor='levels'> <section1 topic='Compliance Categories' anchor='categories'>
<section2 topic='Core Compliance Suite' anchor='core'> <section2 topic='Core Compliance Suite' anchor='core'>
<table caption='XMPP Core Compliance Levels'> <table caption='XMPP Core Compliance Levels'>
<tr> <tr>
@ -170,7 +177,7 @@
<section2 topic='Web Compliance Suite' anchor='web'> <section2 topic='Web Compliance Suite' anchor='web'>
<p> <p>
To be considered XMPP web compliant, all features from the core To be considered XMPP web compliant, all features from the core
compliance suite must be met, as well as all features in this suite. compliance category must be met, as well as all features in this suite.
</p> </p>
<table caption='XMPP Web Compliance Levels'> <table caption='XMPP Web Compliance Levels'>
<tr> <tr>
@ -194,7 +201,7 @@
<section2 topic='IM Compliance Suite' anchor='im'> <section2 topic='IM Compliance Suite' anchor='im'>
<p> <p>
To be considered XMPP IM compliant, all features from the core To be considered XMPP IM compliant, all features from the core
compliance suite must be met, as well as all features in this suite. compliance category must be met, as well as all features in this suite.
</p> </p>
<table caption='XMPP IM Compliance Levels'> <table caption='XMPP IM Compliance Levels'>
<tr> <tr>
@ -338,7 +345,7 @@
<section2 topic='Mobile Compliance Suite' anchor='mobile'> <section2 topic='Mobile Compliance Suite' anchor='mobile'>
<p> <p>
To be considered XMPP mobile compliant, all features from the core To be considered XMPP mobile compliant, all features from the core
compliance suite must be met, as well as all features in this suite. compliance category must be met, as well as all features in this suite.
</p> </p>
<table caption='XMPP Mobile Compliance Levels'> <table caption='XMPP Mobile Compliance Levels'>
<tr> <tr>