Maciek Niedzielski wrote:
Peter Saint-Andre wrote:A question: should this clientinfo extension include the software name, or do we assume that is provided properly in the service discovery identity? If the latter, I'll make that clear in the extension spec. (It seems preferable to have the same information in only one place!)BTW I think it is unclear (at least for some people) what should be given as a 'name' in <identity category='client' type='pc'/>.
Probably because XEP-0030 doesn't really say. :)
I don't remember the details, but some time ago people complained that Psi puts 'Psi' as a name, not user's nick.
Well, we do have XEP-0172 for nicknames.I think that the service discovery name is the name for the software (e.g., "Psi") or service (e.g., "jabber.org bytestreams proxy"). But that's not a well-defined rule.
So if we want to read client's name from <identity/> element, it should be noted (maybe in disco registry) what the name should be.
Agreed. Or in the registry entry for that category+type.
And now about the original question: We could have optional field which - if present - would override client/pc identity name.
Yes, I think so too.
Also for implementation notes: if we continue reading client name from <identity/>, there should be probably a reminder that there may be multiple <identity/> elements, but we are only interested in client/pc here (and this may be not always the first element)
Correct. Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
