(Difference between revisions)

Jump to: navigation, search
m (Reverted edits by ABIDEEN10 (Talk) to last version by Tantek)
Current revision (18:28, 23 July 2014) (view source)
(added issue: Formal deprecation of object-level rel-tag usage)
Line 6: Line 6:
* {{OpenIssue}} 2014-09-23 raised by [[User:TomMorris|tommorris]]
*# '''Formal deprecation of object-level rel-tag usage'''
*#: Given that HTML5 seems to have decided that <var>rel</var>-marked links are document-scoped, and left it to metadata-in-HTML implementations (RDFa, Microdata, Microformats etc.) to work out how scoping works (<var>itemscope</var> in microdata, the <var>about</var>/<var>typeof</var> in old-style RDFa, <var>resource</var> in RDFa Lite 1.1), the use of rel-tag to specifically mark object-level tags will not work. In [[microformats2]] [[h-entry]], the solution that seems to be taking its place is to use the 'category' property which µf2 parsers can parse according to the same parsing rules as any other properties. It would seem reasonable—although rather sad—to deprecate rel-tag.
*#: As the primary use case of rel-tag is to tag blog ''posts'' (or microblog "notes" in the IndieWeb milieu), given the HTML parsing rules as they currently stand, that use case can't be fulfilled using rel-tag anymore. rel-tag can still be used for tagging a ''page''. If a rel-tag link is on a web page, it'll obviously be parsed by a µf2 parser and included in the 'rels' dictionary outputted, but it may be worth deprecating the rel-tag specification as it no longer serves a purpose—the primary use case is better filled using [[h-entry]]'s category property.
* {{OpenIssue}} 2012-04-18 raised by [[User:Rossputin|Ross McDonald]]
* {{OpenIssue}} 2012-04-18 raised by [[User:Rossputin|Ross McDonald]]

Current revision


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


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">
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</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
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 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>
<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, July 23rd, 2014