> [AddressableURISchemes] should only be used when the connection is offline.
> When it is connected the addressable URI schemes should be retrieved from the
> Requests.RequestableChannelClasses's TargetURIScheme fixed-property instead.

That'll only work if Conn.I.Addressing is undrafted, which it hasn't been yet. Perhaps delete this bit and reinstate it in the Conn.I.Addressing branch, or prefix with "After Conn.I.Addressing.DRAFT becomes stable, ..."?

The Gabble implementation in Bug #32692 looks good enough to unblock undrafting this.

Revisiting this: Comment #1 (broken cross-reference) still stands, unless I review Conn.I.Addressing (which I'll do in a moment) and decide it's already ready.

For use for Facebook IDs in XMPP (the current motivating use-case), x-facebook-id should be added, with an example (if your JID is "-12345@chat.facebook.com" then your x-facebook-id is "12345").

(In reply to comment #2)
> For use for Facebook IDs in XMPP (the current motivating use-case),
> x-facebook-id should be added, with an example (if your JID is
> "-12345@chat.facebook.com" then your x-facebook-id is "12345").

Alternatively, if there are Facebook developer docs you can link to (some sort of glossary or "basic concepts" or something), do that.

Is "Facebook ID" or "ID" the terminology that Facebook itself uses (e.g. in app APIs)? If not, the vCard field name should probably change to be more like the terminology that FB uses.

(In reply to comment #3)
> (In reply to comment #2)
> > For use for Facebook IDs in XMPP (the current motivating use-case),
> > x-facebook-id should be added, with an example (if your JID is
> > "-12345@chat.facebook.com" then your x-facebook-id is "12345").
> 
> Alternatively, if there are Facebook developer docs you can link to (some sort
> of glossary or "basic concepts" or something), do that.
There is http://developers.facebook.com/docs/chat/, but I guess it's better to not link it as it may confuse more than help.

> Is "Facebook ID" or "ID" the terminology that Facebook itself uses (e.g. in app
> APIs)? If not, the vCard field name should probably change to be more like the
> terminology that FB uses.
They refer to facebook ID several times in the link above, so I guess we are fine in using this.

Branch updated with x-facebook-id added to the list of known vcard fields. URL updated.

Ship it, assuming the broken link in Comment #1 doesn't break the build. Conn.I.Addressing will catch up soon enough...

(In reply to comment #5)
> Ship it, assuming the broken link in Comment #1 doesn't break the build.
> Conn.I.Addressing will catch up soon enough...

Changes merged upstream. I removed the broken link in Comment #1 on patch a9e7212 that should be reverted once Chan.I.Addressing is undrafted. Comment added to bug #42918.

Marking as fixed.