Ryan King wrote:
Requiring authors to add markup in order to make rel-tag's scope
explicit makes it hard to publish the data and doesn't solve any
real problem.
Hijacking a thread to mention another rel-tag oddity:
Requiring a restful URL for rel-tag (though the ideal solution) is
expecting a lot more of a µf author than requiring authors to add a
bit of markup.
Ideal:
<a rel="tag" href="/tags/tagName">text</a>
Practical alternative for some cases (using title value):
<a rel="tag" title="tagName" href="/
theOtherDevelopersHideouslyComplexUrl.extension?
queryJunk=tagName">text</a>
If the ugly URL isn't enough of an explanation, consider that front-
end developers make up a majority of the converts in the area of web
standards. It is not unthinkable that a front-end developer would
want to implement rel-tag even when the server-side developer is
unwilling to implement a restful URL. There ought to be a markup
fallback.
I didn't see this address on any of the rel-tag wiki pages other that
the tagName-as-linkText solution with which I also disagree. Wanted
to mention it here for feedback.
Wot say you?
James
PS. Intro will come later.
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
