Difference between revisions of "XEP"
From JaWiki (Jabber/XMPP wiki)
m (→Типы: так понятнее, наверное) |
(→Статусы: ++) |
||
| Line 23: | Line 23: | ||
== Статусы == | == Статусы == | ||
| − | {{xep|0001}} | + | В {{xep|0001}} перечислены следующие статусы (состояния) расширений: |
| − | {{todo}} | + | ; Экспериментальное (Experimental): Расширение любого типа становится ''экпериментальным'' после принятия [[Совет XMPP|Советом XMPP]] и опубликования [[XSF]], но до того, как оно станет ''действующим'' или ''черновиком'' в процессе стандартизации. |
| + | :: {{todo|An Experimental specification is a work in progress and may undergo significant modification before advancing to a status of Draft. While implementation of an Experimental protocol is encouraged in order to determine the feasibility of the proposed solution, it is not recommended for such implementations to be included in the primary release for a software product (as opposed to an experimental branch).}} | ||
| + | ; Предложенное (Proposed): Расширение любого типа является ''предложенным'', пока Совет XMPP решает вопрос об изменении статуса с ''экспериментального'' на ''действующий''. | ||
| + | {{todo| | ||
| + | ; Draft: A Standards Track XEP is in the Draft state after it has undergone extensive discussion and technical review on the Standards list and has been voted forward on the standards track by the XMPP Council. | ||
| + | :: Once an XMPP Extension Protocol has been advanced to a status of Draft, it is expected that the specification will be basis for widespread implementation and for deployment in production environments. As a result of such implementation and deployment experience, the protocol may be subject to modification, including changes that are backwards-incompatible. Although such backwards-incompatible modifications shall be avoided if at all possible, deployment of a Draft protocol in mission-critical application may not be advisable. | ||
| + | ; Final: A Standards Track XEP is in the Final state after it has been in the Draft state for at least 60 days, has been implemented in at least two separate codebases, and has been voted forward on the standards track by the XMPP Council. | ||
| + | :: Once an XMPP Extension Protocol has been advanced to a status of Final, every effort shall be made to limit the scope of modifications; in particular, backwards-incompatible changes shall not be made. However, limited modifications may be made as long as they are optional, backwards-compatible extensions rather than modifications to the core protocol itself. Therefore, a Final protocol is safe for deployment in mission-critical applications. | ||
| + | ; Active: A XEP of any type other than Standards Track is advanced to a status of Active after it has been voted forward from Experimental by the XMPP Council. | ||
| + | ; Deferred: An Experimental XEP of any type is changed to the Deferred state if it has not been updated in six (6) months. | ||
| + | ; Retracted: A XEP of any type is in the Retracted state if the authors have asked the XMPP Extensions Editor to remove the XEP from further consideration in the XSF's standards process. | ||
| + | ; Rejected: A XEP of any type is in the Rejected state if the XMPP Council has deemed it unacceptable and has voted to not move it forward within the standards process. | ||
| + | ; Deprecated: A XEP of any type is in the Deprecated state if the XMPP Council has determined that the protocol defined therein is out of date and that new implementations are no longer encouraged (e.g., because it has been superseded by a more modern protocol). | ||
| + | ; Obsolete: A XEP of any type is changed from Deprecated to Obsolete if the XMPP Council has determined that the protocol defined therein should no longer be implemented or deployed. | ||
| + | }} | ||
== Ссылки == | == Ссылки == | ||
* [http://www.xmpp.org/extensions XMPP Extensions] | * [http://www.xmpp.org/extensions XMPP Extensions] | ||
Revision as of 20:48, 31 March 2009
XMPP extension protocol — расширение протокола XMPP.
Документ «XEP-0001: Расширения протокола XMPP» определяет порядок работы Фонда стандартов XMPP (XMPP Standards Foundation, XSF), утверждённый Советом XMPP (XMPP Council) и/или Советом директоров XSF.
Ранее XEP назывались JEP (Jabber Extension Protocol).
Типы
XEP-0001 определяет пять типов расширений.
Основные, информационные, исторические и шуточные расширения утверждаются Советом XMPP; процедурные расширения могут утверждаться Советом директоров XSF или Советом XMPP.
- Основное расширение (Standards Track)
- Основные расширения определяют одно из следующего:
- Базовый протокол для использования в качестве стандартной составляющей технологии Jabber/XMPP.
- Пакет протоколов, определяющих требования соответствия (например, XEP-0073: Основной пакет протоколов мгновенной передачи сообщений).
- Информационное расширение (Informational)
- Информационные расширения определяют одно из следующего:
- Рекомендации по разработке протоколов (например, XEP-0128: Расширения Service Discovery).
- Способ применения существующего протокола (например, XEP-0126: Невидимость).
- Историческое расширение (Historical)
- Историческое расширение описывает протокол, созданный до установления XSF порядка разработки стандартов, но всё ещё использующийся в сообществе разработчиков Jabber/XMPP. Такое расширение может быть или не быть заменено на основное или преобразовано в основное.
- Шуточное расширение (Humorous)
- Шуточное расширение пытается в шуточной манере определить протокол, который в реальности никогда не будет использоваться. Такие расширения обычно публикуются 1 апреля и автоматически получают статус действующего расширения.
- Процедурное расширение (Procedural)
- Процедурные расширения определяют процесс или действие XSF, включая хартии Специальных групп.
Статусы
В XEP-0001 перечислены следующие статусы (состояния) расширений:
- Экспериментальное (Experimental)
- Расширение любого типа становится экпериментальным после принятия Советом XMPP и опубликования XSF, но до того, как оно станет действующим или черновиком в процессе стандартизации.
- ToDo: An Experimental specification is a work in progress and may undergo significant modification before advancing to a status of Draft. While implementation of an Experimental protocol is encouraged in order to determine the feasibility of the proposed solution, it is not recommended for such implementations to be included in the primary release for a software product (as opposed to an experimental branch).
-
- Предложенное (Proposed)
- Расширение любого типа является предложенным, пока Совет XMPP решает вопрос об изменении статуса с экспериментального на действующий.
ToDo:
- Draft
- A Standards Track XEP is in the Draft state after it has undergone extensive discussion and technical review on the Standards list and has been voted forward on the standards track by the XMPP Council.
- Once an XMPP Extension Protocol has been advanced to a status of Draft, it is expected that the specification will be basis for widespread implementation and for deployment in production environments. As a result of such implementation and deployment experience, the protocol may be subject to modification, including changes that are backwards-incompatible. Although such backwards-incompatible modifications shall be avoided if at all possible, deployment of a Draft protocol in mission-critical application may not be advisable.
- Final
- A Standards Track XEP is in the Final state after it has been in the Draft state for at least 60 days, has been implemented in at least two separate codebases, and has been voted forward on the standards track by the XMPP Council.
- Once an XMPP Extension Protocol has been advanced to a status of Final, every effort shall be made to limit the scope of modifications; in particular, backwards-incompatible changes shall not be made. However, limited modifications may be made as long as they are optional, backwards-compatible extensions rather than modifications to the core protocol itself. Therefore, a Final protocol is safe for deployment in mission-critical applications.
- Active
- A XEP of any type other than Standards Track is advanced to a status of Active after it has been voted forward from Experimental by the XMPP Council.
- Deferred
- An Experimental XEP of any type is changed to the Deferred state if it has not been updated in six (6) months.
- Retracted
- A XEP of any type is in the Retracted state if the authors have asked the XMPP Extensions Editor to remove the XEP from further consideration in the XSF's standards process.
- Rejected
- A XEP of any type is in the Rejected state if the XMPP Council has deemed it unacceptable and has voted to not move it forward within the standards process.
- Deprecated
- A XEP of any type is in the Deprecated state if the XMPP Council has determined that the protocol defined therein is out of date and that new implementations are no longer encouraged (e.g., because it has been superseded by a more modern protocol).
- Obsolete
- A XEP of any type is changed from Deprecated to Obsolete if the XMPP Council has determined that the protocol defined therein should no longer be implemented or deployed.
