rel-tag-issues

(Difference between revisions)

Jump to: navigation, search
(relTag Issues)
Line 25: Line 25:
*# ''Issue H-1: This specification is lacking a user agent conformance section. Does the UA simply crawl the DOM looking for all <html:a> elements with a "rel" attribute that contains a "tag" keyword (after space-separated splitting) and then grab the href="" value? How about relative links? Must they implement xml:base? <html:base>? Other things?
*# ''Issue H-1: This specification is lacking a user agent conformance section. Does the UA simply crawl the DOM looking for all <html:a> elements with a "rel" attribute that contains a "tag" keyword (after space-separated splitting) and then grab the href="" value? How about relative links? Must they implement xml:base? <html:base>? Other things?
*# ''Issue H-2: What's the point? Isn't free-text search more effective than relying on people to remember to put a particular tag?
*# ''Issue H-2: What's the point? Isn't free-text search more effective than relying on people to remember to put a particular tag?
 +
*#* Tags are used for various reasons, including the ability to re-find information later.  Free text search has its own issues, including raising the signal to noise ratio of search results.
* 2006-01-10 raised by Adam Willard
* 2006-01-10 raised by Adam Willard
Line 45: Line 46:
*#*:* yes -- rob yates 18:56, 9 Feb 2006 (EST)
*#*:* yes -- rob yates 18:56, 9 Feb 2006 (EST)
*#* I wanted to do a quick survey to see how many other sites would struggle to easily adopt this format, due to the fact that they don't currently end their tag urls '/<tag-name>'.  While I definately agree that ending with '/<tag-name>' is a best practice, I do feel that their needs to be an option for sites that don't do this, but still want to semantically tag their tags.  Here's some sites that I found that cannot easily adopt reltag without reworking server side logic. There's some pretty big names on this list.
*#* I wanted to do a quick survey to see how many other sites would struggle to easily adopt this format, due to the fact that they don't currently end their tag urls '/<tag-name>'.  While I definately agree that ending with '/<tag-name>' is a best practice, I do feel that their needs to be an option for sites that don't do this, but still want to semantically tag their tags.  Here's some sites that I found that cannot easily adopt reltag without reworking server side logic. There's some pretty big names on this list.
-
*#*:* O'Reilly.com.  See the tags at this url http://www.xml.com/pub/a/2004/11/10/delicious.html
+
*#*:* O'Reilly.com.  See the tags at this url http://www.xml.com/pub/a/2004/11/10/delicious.html note: O'Reilly uses javascript and AJAX to populate the content on page.  This is definitely not standard.
*#*:* Dodgeball.  http://boston.dodgeball.com/tags.php
*#*:* Dodgeball.  http://boston.dodgeball.com/tags.php
*#*:* Any typepad blog.  See for instance the categories here http://ideasinfood.typepad.com/ideas_in_food/
*#*:* Any typepad blog.  See for instance the categories here http://ideasinfood.typepad.com/ideas_in_food/
Line 53: Line 54:
* {{OpenIssue}} 2006-04-06 raised by [[User:Evan|Evan]]
* {{OpenIssue}} 2006-04-06 raised by [[User:Evan|Evan]]
*# ''The scope says 'rel="tag" is specifically designed for "tagging" content, typically web pages (or portions thereof, like blog posts).', but it's not clear how to associate a tag with one portion of a web page and not another. Some common use cases: image galleries, blog posts, yellow-pages directories, hcard directories, del.icio.us-style lists of bookmarks. Does the tag apply to the <a> element's immediate containing element? All containing elements? One possibility I suggest: the tag applies to the '''most immediately enclosing element with an "id" attribute''' (addressable, at least in XHTML, as #idval), or to the entire page if there is no such element. Another possibility is having a '''tagtarget''' class, so that the parent with that class is the object being tagged.''
*# ''The scope says 'rel="tag" is specifically designed for "tagging" content, typically web pages (or portions thereof, like blog posts).', but it's not clear how to associate a tag with one portion of a web page and not another. Some common use cases: image galleries, blog posts, yellow-pages directories, hcard directories, del.icio.us-style lists of bookmarks. Does the tag apply to the <a> element's immediate containing element? All containing elements? One possibility I suggest: the tag applies to the '''most immediately enclosing element with an "id" attribute''' (addressable, at least in XHTML, as #idval), or to the entire page if there is no such element. Another possibility is having a '''tagtarget''' class, so that the parent with that class is the object being tagged.''
 +
*# In most sites that support tagging, the association is done visually.  There isn't any semantic markup that would tie the tag to the "id" attribute of the content being tagged.  XML has "ref-id" attribute, which can be used.  Not sure if it should be made part of the rel-tag standard though.  [[User:Bloritsch|Bloritsch]] 18:26, 17 July 2009 (UTC)
* {{OpenIssue}} 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
* {{OpenIssue}} 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
Line 68: Line 70:
[...]
[...]
</nowiki></pre>
</nowiki></pre>
 +
 +
*# Isn't this a major departure from how tags are used across different sites?  When I click on a tag link, I expect to see other content that applies that tag. [[User:Bloritsch|Bloritsch]] 18:26, 17 July 2009 (UTC)
* {{OpenIssue}} 2006-11-25 raised by [[User:AndyMabbett|Andy Mabbett]]
* {{OpenIssue}} 2006-11-25 raised by [[User:AndyMabbett|Andy Mabbett]]
Line 74: Line 78:
* {{OpenIssue}} 2006-11-26 raised by [[User:AndyMabbett|Andy Mabbett]]
* {{OpenIssue}} 2006-11-26 raised by [[User:AndyMabbett|Andy Mabbett]]
*#There is a danger of encouraging users to breach [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-meaningful-links WCAG 1.0 priority 2 guideline 13.6] "'''Clearly identify the target of each link'''". If a page has a link thus <code><a href="http://www.bbc.co.uk">BBC</a></code>, tagging it with a link thus <code><a href="http://www.example.com/BBC" rel="tag">BBC</a></code> will result in two links on the page, both labelled "BBC", with different targets.
*#There is a danger of encouraging users to breach [http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-meaningful-links WCAG 1.0 priority 2 guideline 13.6] "'''Clearly identify the target of each link'''". If a page has a link thus <code><a href="http://www.bbc.co.uk">BBC</a></code>, tagging it with a link thus <code><a href="http://www.example.com/BBC" rel="tag">BBC</a></code> will result in two links on the page, both labelled "BBC", with different targets.
 +
*#Typically tags are kept in one location on a screen so that visually they have a context--this provides disambiguation for seeing users.  However, this practice does not address usability for people dependent on screen readers.[[User:Bloritsch|Bloritsch]] 18:26, 17 July 2009 (UTC)
*{{OpenIssue}} 2007-01-01 raised Jan 2006 by Ben Buchanan as [http://weblog.200ok.com.au/2006/01/limitations-of-rel-microformat.html limitations of rel="tag" microformat]
*{{OpenIssue}} 2007-01-01 raised Jan 2006 by Ben Buchanan as [http://weblog.200ok.com.au/2006/01/limitations-of-rel-microformat.html limitations of rel="tag" microformat]

Revision as of 18:26, 17 July 2009

Contents

relTag Issues

These are externally raised issues about rel-tag with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Tantek

Issues

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>
There should be another way to specify the human-readable tagname.
20070110 AB123YZ postcode:uk=AB123YZ upcoming:id=123456 upcoming:event=19876 upcoming:venue=14567 url=example.com geocoded geotagged geo:lat=52.3456 geo:lon=-1.2345
Is any work being done, to document such tag "schema"? Andy Mabbett 12:43, 10 Jan 2007 (PST)
Isn't that several different tags? I.e. "20070110", "AB123YZ", "postcode:uk=AB123YZ" .... At least this is how a site like Flickr would decipher it. The rel-tag standard handles each one separately, although the "machine tags" (as Flickr calls them) have the same issues as the i18n issue above. Bloritsch 18:00, 17 July 2009 (UTC)
<ul class="navbar">
<li><a href="#whisky" rel="tag">Whisky</a></li>
<li><a href="#wine" rel="tag">Wine</a></li>
</ul>
[...]
<h2 id="whisky">"Whisky</h2>
[...]
<h2 id="wine">"Wine</h2>
[...]

Need reformatting

These issues were mistakenly added to the rel-tag-faq and should have been put here in the first place. They need to be reformatted as issues.

Are tags case sensitive?

Multi-word tags

Related pages

The rel-tag specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

rel-tag-issues was last modified: Wednesday, December 31st, 1969

Views