I am asking what would be gained by having
<link rel="conversation" href="xmpp://foo"
label="Chat about foo" />
that it could not just as readily infer from
<link rel="related" href="xmpp://foo"
label="Chat about foo" />
seeing as the critical bit of information for the machine seems
to be conveyed by the `xmpp:` part in both cases and the critical
bit of information for the user would be conveyed by the label in
both cases.
It seems to me that having to parse the URI to decide whether or not such a link is usable by the program reading it is fairly poor design decision.
From a machine POV, how would you differentiate those:
<link rel="related" href="xmpp://foo"
label="Chat about foo" />
<link rel="related" href="xmpp://bar"
label="Monitor bar" />
The second might not even interest the user per-se, it might just be
targetted at auto discovery or what have you. You could make the URI
more explicit probably but why refusing the use of the rel attribute in
such case anyway?
I'm trying hard to understand your reluctance by gauging how that would hurt any out of band context but I'm unsure it's the right battle.
- Sylvain