Re: [Standards] XEP-0292: vCard4 - advance?
> On Jan 19, 2019, at 5:50 PM, Kim Alvefur wrote: > >> On Sun, Jan 20, 2019 at 12:29:43AM +, Philipp Hörist wrote: >> Only thing i would change is this sentence >> >>> When a client stores items at this node, it SHOULD NOT include an >>> ItemID, so that the pubsub service can assign those identifiers. >> >> Maybe i dont understand why this was written but it seems unnecessary >> to me. It should be the implementors choice if it stores the data in a >> way that allows to pull all changes to the vcard since first publish, >> or use a singleton node item id "current". > > This part is about storing custom vcards for your contacts, implying > that you probably want to be able to store as many as you have contacts. > Therefore the singleton "current" method is not appropriate. Using the > contacts bare JID might be a better idea? WFM /psa > > -- > Kim "Zash" Alvefur > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] XEP-0292: vCard4 - advance?
On Sun, Jan 20, 2019 at 12:29:43AM +, Philipp Hörist wrote: > Only thing i would change is this sentence > > > When a client stores items at this node, it SHOULD NOT include an > > ItemID, so that the pubsub service can assign those identifiers. > > Maybe i dont understand why this was written but it seems unnecessary > to me. It should be the implementors choice if it stores the data in a > way that allows to pull all changes to the vcard since first publish, > or use a singleton node item id "current". This part is about storing custom vcards for your contacts, implying that you probably want to be able to store as many as you have contacts. Therefore the singleton "current" method is not appropriate. Using the contacts bare JID might be a better idea? -- Kim "Zash" Alvefur signature.asc Description: PGP signature ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] XEP-0292: vCard4 - advance?
Only thing i would change is this sentence > When a client stores items at this node, it SHOULD NOT include an ItemID, so that the pubsub service can assign those identifiers. Maybe i dont understand why this was written but it seems unnecessary to me. It should be the implementors choice if it stores the data in a way that allows to pull all changes to the vcard since first publish, or use a singleton node item id "current". regards Philipp ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] XEP-0292: vCard4 - advance?
+1. It sure would be great to kill off vcard-temp after all these years. Another benefit: vcard4 is extensible and thus can be used in a wide variety of specialized applications (gaming, IoT, etc.). Peter On 1/19/19 1:44 PM, Kim Alvefur wrote: > Hi, > > I would like to see XEP-0292: vCard4 Over XMPP advanced. Since > popularity and deployment of XEP-0084 appears to be on the rise, much > thanks to XEP-0398, now seems like a good time to dust it off and finish > it. > > One benefit over vcard-temp is improved and configurabel access control, > if XEP-0222 & 0223 are supported. vcard-temp has historically been > completely public, something that may not be clear to users. > > I'm not sure if the IQ based protocol defined is really worth it over > simply storing the vcard4 data per XEP-0222, but it's not hard to > implement or use, so it might be okay. > > The current version of Prosody includes support for XEP-0292 in the form > of a plugin that provides access to the relevant PEP node via the IQ > protocol described as well as an exception that allows such requests to > pass trough MUC. There is also an implementation of XEP-0398 that > translates between vcard-temp and vcard4+xep84. > > > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > signature.asc Description: OpenPGP digital signature ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] XEP-0292: vCard4 - advance?
Hi, I would like to see XEP-0292: vCard4 Over XMPP advanced. Since popularity and deployment of XEP-0084 appears to be on the rise, much thanks to XEP-0398, now seems like a good time to dust it off and finish it. One benefit over vcard-temp is improved and configurabel access control, if XEP-0222 & 0223 are supported. vcard-temp has historically been completely public, something that may not be clear to users. I'm not sure if the IQ based protocol defined is really worth it over simply storing the vcard4 data per XEP-0222, but it's not hard to implement or use, so it might be okay. The current version of Prosody includes support for XEP-0292 in the form of a plugin that provides access to the relevant PEP node via the IQ protocol described as well as an exception that allows such requests to pass trough MUC. There is also an implementation of XEP-0398 that translates between vcard-temp and vcard4+xep84. -- Kim "Zash" Alvefur signature.asc Description: PGP signature ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
