[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: rel="discuss"



2008/5/8 Peter Saint-Andre <stpeter@xxxxxxxxxx>:
In the Jabber community we've been looking at defining links to, say, a
chat room where a post could be discussed. Therefore we've been thinking
about defining rel="discuss". The value of such a link could point to an
XMPP-based or SIP-based groupchat room, an IRC channel, an email
discussion list, a web forum, or other such venue. Does this seem
reasonable?
 
Pretty much : "discuss" seems a good umbrella term, I'd imagine it being a better choice than say "chat" or "comment".

Might there be any constraints on/expectations about what it *could* point to?

Also noting the spec:
[[
 The value of "rel" MUST be a string that is non-empty and matches
   either the "isegment-nz-nc" or the "IRI" production in [RFC3987].
]]
http://tools.ietf.org/html/rfc4287#page-21
4.2.7.2.

Is there any advantage in it being a registered string, as opposed to a (HTTP dereferenceable) IRI?

Apart from minor syntax convenience, I can only really see disadvantages in the shortstring+registry approach - an extra level of indirection, the political stuff, latency if things need changing. With a HTTP URI and appropriate Web representation, it's one step and in your hands. Yeah, I've heard arguments why some level of centralization is desirable for some things, but for keywords like this I'm not convinced...only my 0.02 euro.

Cheers,
Danny.

--
http://dannyayers.com
~
http://blogs.talis.com/nodalities/this_weeks_semantic_web/