On 2020/09/17, Maxime Buquet wrote: > This change to PubSub has been met with some ““resistance”” by the > prosody team because the proposed value “max” is not a number and > doesn't fit the way they currently handle things with XEP-0122 (Data > Forms Validation), setting this value to “integer”. > > While this is more restrictive than what PubSub mandates (text-single), > it does indeed make sense to have a “maximum number of items” be > restricted to an int (not discussing which particular type of int, if > there is). And while it's certainly not impossible for them to handle > this “max” value, that would mean going through various hoops with 0122 > to get this right.
After a chat on xsf@, we agreed on another way forward, which is to declare a (integer-or-max or similar) type to be used with 0122. So I'll retract the PR and try to tackle this instead. Concerning the specification of this type, I'm a bit annoyed conceptually because 0122 allows stuff like <range/>, but a range applied to a union type doesn't really make sense / isn't defined. Even if it does seem obvious that it's gonna be applied to the only integer type in the union, what does that mean when a union has more than one of the same type that accepts ranges. I was looking for union with variants somewhere in XML -- so I can say to which variant apply <range/> -- but that doesn't seem to be defined. Suggestions? As a workaround, whether I end up modifying 0060 or creating a new document, I'll specify that <range/> applies to the integer value of this type. Happy Hacking! -- Maxime “pep” Buquet
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
