On 10 April 2015 at 13:01, Dave Cridland wrote:
> On 9 April 2015 at 23:24, Ben Langfeld wrote:
>
>>
>> On 9 April 2015 at 16:58, Florian Schmaus wrote:
>>
>>> On 09.04.2015 18:59, Ben Langfeld wrote:
>>> > Florian, my concerns with your approach are twofold:
>>> >
>>> > 1. It is complicated an
On 09.04.2015 18:59, Ben Langfeld wrote:
> Florian, my concerns with your approach are twofold:
>
> 1. It is complicated and is not markup in the sense that is used by XML,
> HTML, SSML, etc. Being abstracted means a complicated association step.
Yep, it's more complicated then just adding anothe
Florian, my concerns with your approach are twofold:
1. It is complicated and is not markup in the sense that is used by XML,
HTML, SSML, etc. Being abstracted means a complicated association step.
2. It does not accurately correlate. Imagine this example:
Hi Joe Bloggs. How are you? Oh, and
On 09.04.2015 06:10, Mel Adamaitis wrote:
> Problem:
>
> In an XMPP IM client we are working on, it is necessary for mentions of
> other users (for alerting, highlighting) to be based on a normalised
> user identity, but displayed in a denormalized human-readable format.
> Additionally, for a part
On 9 Apr 2015, at 09:24, Dave Cridland wrote:
> Adding a (private) disco feature and checking for it in caps would be better.
> Then, by all means, add custom attributes and markup.
+1
/K
On 9 April 2015 at 08:27, Kevin Smith wrote:
> 1) I’m not sure that adding data-* to XEP-0071 would aid interoperability,
> as the use of the data-* needs to be understood by both ends (e.g. in your
> case it isn’t enough for xep71 to just say ‘you can use data-*’, because a
> third-party client
On 9 Apr 2015, at 05:10, Mel Adamaitis wrote:
>
> Problem:
> In an XMPP IM client we are working on, it is necessary for mentions of other
> users (for alerting, highlighting) to be based on a normalised user identity,
> but displayed in a denormalized human-readable format. Additionally, for
Problem:
In an XMPP IM client we are working on, it is necessary for mentions of
other users (for alerting, highlighting) to be based on a normalised user
identity, but displayed in a denormalized human-readable format.
Additionally, for a particular denormalized identity, there may be any
number
