diff --git a/xep-0061.xml b/xep-0061.xml index 86195183..82dd132f 100644 --- a/xep-0061.xml +++ b/xep-0061.xml @@ -13,7 +13,7 @@ Deferred Informational Standards - XMPP Core + XMPP Core Not yet assigned diff --git a/xep-0062.xml b/xep-0062.xml index ff8aa423..bd390ec2 100644 --- a/xep-0062.xml +++ b/xep-0062.xml @@ -16,7 +16,10 @@ Deferred Informational Standards - XMPP Core, XEP-0030 + + XMPP Core + XEP-0030 + Not yet assigned @@ -30,7 +33,7 @@ 0.2 2003-09-30 psa - At the request of the author, changed the status of this document to Deferred pending development of an implementation; also changed the type to Informational. + At the request of the author, changed the status of this document to Deferred pending development of an implementation; also changed the type to Informational. 0.1 @@ -90,7 +93,6 @@

A rule is processed by applying its condition to the packet. If the condition is true, then the action is taken. The "description" attribute is provided so a rule generator can assign a meaningful and user-readable description of a rule.

A ruleset is be expressed in XML like so:

- @@ -108,7 +110,7 @@ ]]> -

A ruleset is processed by applying each rule to the packet, one at a time. Processing of the ruleset stops after the first matching rule is found and its action taken, unless the "continue" attribute is found on the matched rule, in which case the remaining rules get processed as though the current rule did not match. If no rules match, packet processing continues as though no rules were specified.

+

A ruleset is processed by applying each rule to the packet, one at a time. Processing of the ruleset stops after the first matching rule is found and its action taken, unless the "continue" attribute is found on the matched rule, in which case the remaining rules get processed as though the current rule did not match. If no rules match, packet processing continues as though no rules were specified.

If the <condition/> element contains no condition expression, then the rule matches all packets.

@@ -136,7 +138,7 @@

The above example is equivalent to "conditionexpr1 AND conditionexpr2 AND (conditionexpr3 OR conditionexpr4)".

No such aggregation exists for actions - only a single action expression may be included within an <action/> element.

- + diff --git a/xep-0063.xml b/xep-0063.xml index 5d7d0767..d536ada4 100644 --- a/xep-0063.xml +++ b/xep-0063.xml @@ -16,7 +16,7 @@ Deferred Informational Standards - XEP-0062 + XEP-0062 Not yet assigned diff --git a/xep-0064.xml b/xep-0064.xml index 06b18008..ebd722c6 100644 --- a/xep-0064.xml +++ b/xep-0064.xml @@ -16,7 +16,7 @@ Deferred Informational Standards - XEP-0062 + XEP-0062 Not yet assigned diff --git a/xep-0067.xml b/xep-0067.xml index 2dabc1eb..d251dd76 100644 --- a/xep-0067.xml +++ b/xep-0067.xml @@ -5,42 +5,43 @@ ]> -
-Stock Data Transmission -This document specifies a data format for stock data distribution in the Jabber community. -&LEGALNOTICE; -0067 -Deferred -Standards Track -Standards -XEP-0060 - -Ulrich -Staudinger -chicago5@gmx.de -uls@jabber.org - - -0.3 -2003-07-19 -uls -Added transmission in messages - - -0.2 -2003-01-26 -uls -Added ISO-8601 time scheme, added symbols, fixed typos. - - - -0.1 -2003-01-12 -uls -Initial Release - - -
+
+ Stock Data Transmission + This document specifies a data format for stock data distribution in the Jabber community. + &LEGALNOTICE; + 0067 + Deferred + Standards Track + Standards + XEP-0060 + + + NOT_YET_ASSIGNED + + Ulrich + Staudinger + chicago5@gmx.de + uls@jabber.org + + + 0.3 + 2003-07-19 + uls + Added transmission in messages + + + 0.2 + 2003-01-26 + uls + Added ISO-8601 time scheme, added symbols, fixed typos. + + + 0.1 + 2003-01-12 + uls + Initial Release + +

diff --git a/xep-0069.xml b/xep-0069.xml index 3cee553e..20cffeec 100644 --- a/xep-0069.xml +++ b/xep-0069.xml @@ -13,6 +13,10 @@ Deferred SIG Formation None + + + + N/A &stpeter; 0.1 diff --git a/xep-0074.xml b/xep-0074.xml index 66a433bc..4545c4e2 100644 --- a/xep-0074.xml +++ b/xep-0074.xml @@ -13,11 +13,10 @@ Retracted Standards Track Standards - XEP-0030 + XEP-0030 sac - Not yet assigned Justin Kirby diff --git a/xep-0075.xml b/xep-0075.xml index 93b33b73..76b46b73 100644 --- a/xep-0075.xml +++ b/xep-0075.xml @@ -18,8 +18,8 @@ Standards Track Standards - + N/A Evan diff --git a/xep-0087.xml b/xep-0087.xml index aa70d929..3243f4b7 100644 --- a/xep-0087.xml +++ b/xep-0087.xml @@ -13,9 +13,9 @@ Retracted Standards Track Standards - XEP-0030 + XEP-0030 - XEP-0095 + XEP-0095 si Thomas diff --git a/xep-0097.xml b/xep-0097.xml index 1e804592..a47594d7 100644 --- a/xep-0097.xml +++ b/xep-0097.xml @@ -8,12 +8,12 @@

iCal Envelope A simple mechanism to transport iCal data over the jabber protocol - &LEGALNOTICE; + &LEGALNOTICE; 0097 Deferred Standards Track Standards - XEP-0030 + XEP-0030 ice @@ -31,7 +31,7 @@
-

This will be the first, in a series (hopefully), of specifications which will define how to utilize GroupWare over jabber. While GroupWare is extremely broad subject, this document will focus on iCaliCalendar http://www.ietf.org/html.charters/calsch-charter.html. Since iCal is a defined standard which is transport-agnostic, all this document will do is define how iCal will be transported over Jabber.

+

This will be the first, in a series (hopefully), of specifications which will define how to utilize GroupWare over jabber. While GroupWare is extremely broad subject, this document will focus on iCaliCalendar http://www.ietf.org/html.charters/calsch-charter.html. Since iCal is a defined standard which is transport-agnostic, all this document will do is define how iCal will be transported over Jabber.

What this document will cover:

  • Sending iCal data
    • @@ -40,20 +40,16 @@

    Before sending iCal messages to a jabber entity, a disco query should be performed in order to discover whether or not that entity supports iCal Envelopes.

    - - - - ]]> - +]]>

    If the jabber entity supports iCal Envelopes, then it MUST respond with http://jabber.org/protocol/gw/ical as a feature.

    - - - - ]]> - +]]>

    To send iCal, all that needs to be done is wrap the iCal data in a ical element. All iCal data sent MUST be in the ical element in the http://jabber.org/protocol/gw/ical namespace. The CDATA section is optional and is used here simply to make it readable.

    -

    Other than wrapping iCal in XML, the data itself MUST follow the ietf 2445 RFC2445 RFC http://www.ietf.org/rfc/rfc2445.txt

    - - Other than wrapping iCal in XML, the data itself MUST follow the ietf 2445 RFC2445 RFC http://www.ietf.org/rfc/rfc2445.txt

    + Protocol gathering every Tuesday at 22:00 UTC @@ -98,9 +91,7 @@ END:VEVENT END:VCALENDAR - - ]]> - +]]>

    As a convenience for users which do not have ical support the sender may want to place human readable information in the <body/> for the receiver to read.