[Standards] XEP-0115 redux

[Peter Saint-Andre]

Kevin Smith wrote:
> On Jan 14, 2008 4:33 PM, Joe Hildebrand <hildjj at gmail.com> wrote:
>>> I'm not sure about the i18n section, it seems better to me to leave
>>> the name in.
>> It reads fine to me.  If you wanted, we might spell out the disco#info
>> request to get the name, and specify that it MUST be cached on a per-
>> node basis.
> 
> Yes, we can always cache it that way to get the friendly name, good
> thinking Batman.

How is this text as a new subsection under Implementation Notes?

******

8.5 Friendly Name

The 'name' attribute of the service discovery <identity/> element 
enables a responding application to specify the "friendly name" for its 
node. However, this attribute is excluded from the hash generation 
method, primarily because it is human-readable text and therefore may be 
provided in different localized versions. As a result, its inclusion 
would needlessly multiply the number of possible hash values and thus 
the time and resources required to validate values of the 'ver' 
attribute. However, a receiving application MAY send a service discovery 
information request to a particularly JID+node combination in order to 
determine the friendly name, then cache the result for that JID+node only.

******

I have moved this from the Internationalization Considerations (and have 
deleted that section) since this seems to be only tangentially related 
to i18n.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/standards/attachments/20080114/91e29191/attachment-0001.bin