[Standards] multiple <forwarded/> elements in a stanza (XEP 297)

Kurt Zeilenga kurt.zeilenga at isode.com
Wed Nov 12 14:46:53 UTC 2014


> On Nov 12, 2014, at 5:57 AM, Florian Schmaus <flo at geekplace.eu> wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> On 12.11.2014 14:27, Kurt Zeilenga wrote:
>> The language of XEP 297 does not preclude a stanza from containing
>> as direct children multiple <forwarded/> elements,
> 
> The XML Schema (XEP-297 § 8) states "<xs:element name='forwarded'>"
> and http://www.w3schools.com/schema/el_element.asp says the default
> for maxOccurs (and minOccurs) is 1.

As I recall, minOccurs and maxOccurs cannot be specified and are not used when the parent of the <element/> is a <schema/> element because the number of occurs is controlled by the schema allowing the element to be present.

— Kurt


> 
> I have no strong opinion in changing this, but please remember to
> update the schema accordingly. This wouldn't be the first case where
> the wording diverges from the scheme [1].
> 
> While looking at the scheme, I wonder why it's
> 
>        <xs:choice minOccurs='0' maxOccurs='1'>
>          <xs:choice>
>            <xs:element ref='client:message'/>
>            <xs:element ref='client:presence'/>
>            <xs:element ref='client:iq'/>
>          </xs:choice>
>          <xs:choice>
>            <xs:element ref='server:message'/>
>            <xs:element ref='server:presence'/>
>            <xs:element ref='server:iq'/>
>          </xs:choice>
>        </xs:choice>
> 
> and not
> 
>          <xs:choice>
>            <xs:element ref='client:message'/>
>            <xs:element ref='client:presence'/>
>            <xs:element ref='client:iq'/>
>            <xs:element ref='server:message'/>
>            <xs:element ref='server:presence'/>
>            <xs:element ref='server:iq'/>
>          </xs:choice>
> 
> That is: Why is minOccurs=0 and not 1? And why is there a nested
> xs:choice?
> 
> Florian
> 
> 1: http://mail.jabber.org/pipermail/standards/2014-October/029266.html
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQF8BAEBCgBmBQJUY2dlXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMzU3QjAxODY1QjI1MDNDMTg0NTNEMjA4
> Q0FDMkE5Njc4NTQ4RTM1AAoJEIysKpZ4VI41qQwH+wQNZzHXgkfhnys95FV/wFQc
> PadetBLWrE7xUwgbs+Zi5HELSXVD5P3b2Kf1NcrqcXXH/4UbaiQB+nNHFaHQFf1d
> fjLzFA9q7MdRpxf5GOchm+jvmvsKdjw+JRnXvYV1o87FqkslsZIxFTBlFCx34myn
> HO+jzjNk9kBvSNyMsYkrhIVuZqjM1O4HIgxioUeeVGV/AxC92c2MVwT2pfn1n5wC
> BtRLgouEF9t8zdc0BEV32pTOFZx90hwAlE5XDjq8EfOs1HYXr1SdiPU3tUf86Jek
> RQa/kOkWH1lN2GDQEd/U08md+GBsDQISBiYEgCXAq4FSGamXJDP/s/WuqhPdIto=
> =ehj1
> -----END PGP SIGNATURE-----




More information about the Standards mailing list