Microformats Wiki - User contributions [en]

sitemap-brainstorming

2012-04-23T20:50:56Z

Rossputin:

<entry-title>Sitemap Brainstorming</entry-title>

Per the microformats [[process]] this page documents attempts to brainstorm a sitemap and related mechanisms microformat.

'''Note''' : We define 'site mapping' as the process of generating a particular sitemap flavour, like sitemap.xml or an HTML sitemap, or something related like an HTML5 cache manifest.

'''Note''' : Here we are attempting to derive a simple mechanism, lowest common denominator and driven by a top level HTML nav mechanism. We are not considering crawlers etc just yet. It is possible that later when/if we look at crawlers we may need to encode some kind of order information (for now this is explicitly defined in the order the author defined the link elements).

== Brainstorming solution 1 ==
=== Content and class values ===
* h-sitemap required
** wraps a sitemap block
* u-url, required
** every link element we want included in a generated artifact must be annotated with this
* p-priority-x, optional
** only pertinent to sitemap.xml
** p-priority-0-0 = 0.0, p-priority-0.1 = 0.1 ... p-priority-1-0 = 1.0
** if the author fails to specify a priority it is sane to assume a machine may generate the default of 0.5 as per the sitemaps.org protocol
* p-change-x, optional
** only pertinent to sitemap.xml
** we can lift the possible values directly out of the sitemaps.org protocol (p-change-always|p-change-hourly...)

'''Note''' : We ignore 'lastmod' for now (again only pertinent to sitemap.xml)

=== Examples ===
==== Simple HTML sitemap or cache manifest example ====
<pre><nowiki>
<ul class="h-sitemap">
<li>
<a class="u-url" href="http://www.site.tld/">Home</a>
</li>
<li>
<a class="u-url" href="http://www.site.tld/section1/">Section 1</a>
</li>
</ul>
</nowiki></pre>

==== sitemap.xml example with changefreq specified ====
<pre><nowiki>
<ul class="h-sitemap">
<li>
<a class="u-url p-change-daily" href="http://www.site.tld/">Home</a>
</li>
<li>
<a class="u-url p-change-weekly" href="http://www.site.tld/section1/">Section 1</a>
</li>
</ul>
</nowiki></pre>

==== sitemap.xml example with changefreq and priority specified ====
<pre><nowiki>
<ul class="h-sitemap">
<li>
<a class="u-url p-change-daily p-priority-1-0" href="http://www.site.tld/">Home</a>
</li>
<li>
<a class="u-url p-change-weekly p-priority-0-8" href="http://www.site.tld/section1/">Section 1</a>
</li>
</ul>
</nowiki></pre>

==== sitemap.xml example where nav mechanism is structured differently ====
<pre><nowiki>
<div class="h-sitemap">
<a class="u-url p-change-weekly p-priority-0-6" href="/section1">Section 1</a>
<span>.</span>
<a class="u-url p-change-monthly p-priority-0-4" href="/section2">Section 2</a>
</div>
</nowiki></pre>

sitemap

2012-04-23T19:21:21Z

Rossputin:

<entry-title>Sitemap</entry-title>

==Authors==
[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

== Problem ==
Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML navigation constructs by specifying a minimal amount of semantic information.

There is currently no way to encode in a machine readable way which navigation link elements pointing to locations in a site should be considered for inclusion in a sitemap.xml, cache manifest or related artifact, additionally information is not currently available which would enable specification of priority weighting or frequency of change.

Currently accurate sitemap.xml files, HTML sitemaps and cache manifests are written manually, or created by supplying information generator services/sites. This is rather disconnected from our sites, and not always as accurate as we would like.

== Use Cases ==
Examples of what could be generated if we had such information:
* sitemap.xml
* HTML sitemap for usability/accessibility
* HTML5 cache manifest

Countless sites contain HTML navigation constructs which already detail all/most of the information required to build an HTML sitemap or cache manifest, and parts of the information required to build a sitemap.xml file.

Typically these constructs leverage link elements which conveniently expose an 'href' attribute. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.xml.

Useful metadata could be generated by machines or browser plugins with both leveraging a simple microformat.

== Proposal ==
Per the microformats [[process]]:

* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

sitemap

2012-04-23T19:14:37Z

Rossputin:

<entry-title>Sitemap</entry-title>

==Authors==
[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

== Problem ==
Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML navigation constructs by specifying a minimal amount of semantic information. There is currently no way to encode in a machine readable way which navigation link elements pointing to locations in a site should be considered for inclusion in a sitemap.xml, cache manifest or related artifact, additionally information is not currently available which would enable specification of priority weighting or frequency of change.

Examples of what could be generated if we had such information:
* sitemap.xml
* HTML sitemap for usability/accessibility
* HTML5 cache manifest

Countless sites contain HTML navigation constructs which already detail all/most of the information required to build an HTML sitemap or cache manifest, and parts of the information required to build a sitemap.xml file.

Typically these constructs leverage link elements which conveniently expose an 'href' attribute. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.xml.

Currently the alternative is to either write a site map manually, or supply information to a generator (the said data being disconnected from your site).

Useful metadata could be generated by machines or browser plugins with both leveraging a simple microformat.

== Proposal ==
Per the microformats [[process]]:

* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

sitemap-brainstorming

2012-04-23T19:04:31Z

Rossputin:

<entry-title>Sitemap Brainstorming</entry-title>

Per the microformats [[process]] this page documents attempts to brainstorm a sitemap and related mechanisms microformat.

'''Note''' : We define 'site mapping' as the process of generating a particular sitemap flavour, like sitemap.xml or an HTML sitemap, or something related like an HTML5 cache manifest.

'''Note''' : Here we are attempting to derive a simple mechanism, lowest common denominator and driven by a top level HTML nav mechanism. We are not considering crawlers etc just yet. It is possible that later when/if we look at crawlers we may need to encode some kind of order information (for now this is explicitly defined in the order the author defined the link elements).

== Brainstorming solution 1 ==
=== Content and class values ===
* mapmf (shorthand for map microformat), required
** mapmf can be used to declare a link element as something the author wants considered when site mapping occurs
** mapmf would be required to generate all the different sitemap and related mechanisms, HTML sitemap, sitemap.xml and cache manifest
* priority, optional
** priority is only pertinent to sitemap.xml
** a first iteration for defining possible values could be (p0|p1|p2|p3|p4|p5|p6|p7|p8|p9|one)
** p0 = 0.0, p1 = 0.1, one = 1.0
** if the author fails to specify a priority it is sane to assume a machine may generate the default of 0.5 as per the sitemaps.org protocol
* changefreq, optional
** changefreq is only pertinent to sitemap.xml
** we can lift the possible values directly out of the sitemaps.org protocol (always|hourly|daily|weekly|monthly|yearly|never)

'''Note''' : We ignore 'lastmod' for now (again only pertinent to sitemap.xml)

=== Examples ===
==== Simple HTML sitemap or cache manifest example ====
<pre><nowiki>
<ul>
<li>
<a href="http://www.site.tld/" class="mapmf">Home</a>
</li>
<li>
<a href="http://www.site.tld/section1/" class="mapmf">Section 1</a>
</li>
</ul>
</nowiki></pre>

==== sitemap.xml example with changefreq specified ====
<pre><nowiki>
<ul>
<li>
<a href="http://www.site.tld/" class="mapmf daily">Home</a>
</li>
<li>
<a href="http://www.site.tld/section1/" class="mapmf weekly">Section 1</a>
</li>
</ul>
</nowiki></pre>

==== sitemap.xml example with changefreq and priority specified ====
<pre><nowiki>
<ul>
<li>
<a href="http://www.site.tld/" class="mapmf daily one">Home</a>
</li>
<li>
<a href="http://www.site.tld/section1/" class="mapmf weekly p8">Section 1</a>
</li>
</ul>
</nowiki></pre>

sitemap-issues

2012-04-23T17:56:19Z

Rossputin:

<entry-title>Sitemap Issues</entry-title>

Per the microformats [[process]] this page tracks issues raised against the different elements of the sitemap microformat investigation.

__TOC__

== Issues ==

=== brainstorming ===

==== brainstorming solution 1 ====
* {{OpenIssue}} 2012-04-23 raised by [[User:Tantek|Tantek]]
*# ''Uses class names for data (i.e. values like daily weekly monthly).''
*#* Normally that kind of information is user-visible on a page, with micro formats used to put markup around it.
*#* Currently we have no counter proposal (at least not one that would not require adding significant extra markup), and the values are specifically from the sitemap protocol.

sitemap-issues

2012-04-23T17:51:18Z

Rossputin:

sitemap-issues

2012-04-23T17:50:34Z

Rossputin: New page: <entry-title>Sitemap Issues<entry-title> Per the microformats process this page tracks issues raised against the different elements of the sitemap microformat investigation. == Issue...

<entry-title>Sitemap Issues<entry-title>

Per the microformats [[process]] this page tracks issues raised against the different elements of the sitemap microformat investigation.

== Issues ==
=== brainstorming ===

sitemap-formats

2012-04-23T17:31:02Z

Rossputin: New page: <entry-title>Sitemap Formats</entry-title> Per the microformats process this page documents existing formats we may choose to leverage. == sitemaps.org protocol == The [http://www.si...

<entry-title>Sitemap Formats</entry-title>

Per the microformats [[process]] this page documents existing formats we may choose to leverage.

== sitemaps.org protocol ==
The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.

sitemap

2012-04-23T17:29:34Z

Rossputin:

<entry-title>Sitemap</entry-title>

==Authors==
[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

== Problem ==
Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML by specifying a minimal amount of semantic information.

Examples that could be generated:
* sitemap.xml
* HTML sitemap for usability/accessibility
* HTML5 cache manifest

Countless sites contain HTML navigation constructs which already detail all/most of the information required to build an HTML sitemap or cache manifest, and parts of the information required to build a sitemap.xml file.

Typically these constructs leverage link elements which conveniently expose an 'href' attribute. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.xml.

Currently the alternative is to either write a site map manually, or supply information to a generator (the said data being disconnected from your site).

Useful metadata could be generated by machines or browser plugins with both leveraging a simple microformat.

== Proposal ==
Per the microformats [[process]]:

* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

sitemap-brainstorming

2012-04-21T15:45:07Z

Rossputin: New page: <entry-title>Sitemap Brainstorming</entry-title> Per the microformats process this page documents attempts to brainstorm a sitemap and related mechanisms microformat. '''Note''' : We...

<entry-title>Sitemap Brainstorming</entry-title>

Per the microformats [[process]] this page documents attempts to brainstorm a sitemap and related mechanisms microformat.

'''Note''' : We define 'site mapping' as the process of generating a particular sitemap flavour, like sitemap.xml or an HTML sitemap, or something related like an HTML5 cache manifest.

'''Note''' : Here we are attempting to derive a simple mechanism, lowest common denominator and driven by a top level HTML nav mechanism. We are not considering crawlers etc just yet. It is possible that later when/if we look at crawlers we may need to encode some kind of order information (for now this is explicitly defined in the order the author defined the link elements).

== Content and class values ==
* mapmf (shorthand for map microformat), required
** mapmf can be used to declare a link element as something the author wants considered when site mapping occurs
** mapmf would be required to generate all the different sitemap and related mechanisms, HTML sitemap, sitemap.xml and cache manifest
* priority, optional
** priority is only pertinent to sitemap.xml
** a first iteration for defining possible values could be (p0|p1|p2|p3|p4|p5|p6|p7|p8|p9|one)
** p0 = 0.0, p1 = 0.1, one = 1.0
** if the author fails to specify a priority it is sane to assume a machine may generate the default of 0.5 as per the sitemaps.org protocol
* changefreq, optional
** changefreq is only pertinent to sitemap.xml
** we can lift the possible values directly out of the sitemaps.org protocol (always|hourly|daily|weekly|monthly|yearly|never)

'''Note''' : We ignore 'lastmod' for now (again only pertinent to sitemap.xml)

== Examples ==
=== Simple HTML sitemap or cache manifest example ===
<pre><nowiki>
<ul>
<li>
<a href="http://www.site.tld/" class="mapmf">Home</a>
</li>
<li>
<a href="http://www.site.tld/section1/" class="mapmf">Section 1</a>
</li>
</ul>
</nowiki></pre>

=== sitemap.xml example with changefreq specified ===
<pre><nowiki>
<ul>
<li>
<a href="http://www.site.tld/" class="mapmf daily">Home</a>
</li>
<li>
<a href="http://www.site.tld/section1/" class="mapmf weekly">Section 1</a>
</li>
</ul>
</nowiki></pre>

=== sitemap.xml example with changefreq and priority specified ===
<pre><nowiki>
<ul>
<li>
<a href="http://www.site.tld/" class="mapmf daily one">Home</a>
</li>
<li>
<a href="http://www.site.tld/section1/" class="mapmf weekly p8">Section 1</a>
</li>
</ul>
</nowiki></pre>

sitemap

2012-04-21T14:58:55Z

Rossputin:

<entry-title>Sitemap</entry-title>

==Authors==
[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

== Problem ==
Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML by specifying a minimal amount of semantic information.

Examples that could be generated:
* sitemap.xml
* HTML sitemap for usability/accessibility
* HTML5 cache manifest

Countless sites contain HTML navigation constructs which already detail all/most of the information required to build an HTML sitemap or cache manifest, and parts of the information required to build a sitemap.xml file.

Typically these constructs leverage link elements which conveniently expose an 'href' attribute. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.xml.

Currently the alternative is to either write a site map manually, or supply information to a generator (the said data being disconnected from your site).

Useful metadata could be generated by machines or browser plugins with both leveraging a simple microformat.

== Existing standards ==
The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.

== Proposal ==
Per the microformats [[process]]:

* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

sitemap-examples

2012-04-20T16:38:58Z

Rossputin:

<entry-title>Sitemap Examples</entry-title>

Per the microformats [[process]] this page documents common examples of HTML navigation mechanisms out of which we may want to construct a sitemap.xml.

== HTML navigation mechanism examples ==
There would be no difference here really between websites and webapps, both use HTML elements for nav in the same way.

=== bbc.co.uk ===
As per any decent POSH citizen the BBC's website uses a simple list element for navigation. The BBC admirably use very standard attributes.

<pre><nowiki>
<ul id="blq-nav-main">
<li id="blq-nav-news">
<a href="http://www.bbc.co.uk/news/">News</a>
</li>
...
</ul>
</nowiki></pre>

=== apple.com ===
Apple use the same construct.

<pre><nowiki>
<ul id="globalnav" role="navigation">
<li id="gn_store">
<a href="http://store.apple.com/uk"><span>Store</span></a>
</li>
...
</ul>
</nowiki></pre>

=== instapaper.com ===
Subjectively not so semantic in terms of markup.

<pre><nowiki>
<div id="userpanel">
<a href="/extras">Extras</a>
<span>.</span>
...
</div>
</nowiki></pre>

== Existing practices and patterns ==
While the semantic markup differs slightly between these different example mechanisms, and many others, a common theme is the use of the link element. We have always used the same for our own sites.

== Proposal ==
** [[sitemap-formats]]
** [[sitemap-brainstorming]]
** [[sitemap-issues]]

sitemap-examples

2012-04-20T14:18:31Z

Rossputin:

<entry-title>Sitemap Examples</entry-title>

Per the microformats [[process]] this page documents common examples of HTML navigation mechanisms out of which we may want to construct a sitemap.xml.

== HTML navigation mechanism examples ==

There would be no difference here really between websites and webapps, both use HTML elements for nav in the same way.

=== bbc.co.uk ===

As per any decent POSH citizen the BBC's website uses a simple list element for navigation. The BBC admirably use very standard attributes.

<pre><nowiki>
<ul id="blq-nav-main">
<li id="blq-nav-news">
<a href="http://www.bbc.co.uk/news/">News</a>
</li>
...
</ul>
</nowiki></pre>

=== apple.com ===

Apple use the same construct.

<pre><nowiki>
<ul id="globalnav" role="navigation">
<li id="gn_store">
<a href="http://store.apple.com/uk"><span>Store</span></a>
</li>
...
</ul>
</nowiki></pre>

=== instapaper.com ===

Subjectively not so semantic in terms of markup.

<pre><nowiki>
<div id="userpanel">
<a href="/extras">Extras</a>
<span>.</span>
...
</div>
</nowiki></pre>

sitemap-examples

2012-04-20T14:15:13Z

Rossputin:

<entry-title>Sitemap Examples</entry-title>

Per the microformats [[process]] this page documents common examples of HTML navigation mechanisms out of which we may want to construct a sitemap.xml.

== HTML navigation mechanism examples ==

There would be no difference here really between websites and webapps, both use HTML elements for nav in the same way.

=== BBC ===

As per any decent POSH citizen the BBC's website uses a simple list element for navigation. The BBC admirably use very standard attributes.

<pre><nowiki>
<ul id="blq-nav-main">
<li id="blq-nav-news">
<a href="http://www.bbc.co.uk/news/">News</a>
</li>
...
</ul>
</nowiki></pre>

=== Apple ===

Apple use the same construct.

<pre><nowiki>
<ul id="globalnav" role="navigation">
<li id="gn_store">
<a href="http://store.apple.com/uk"><span>Store</span></a>
</li>
...
</ul>
</nowiki></pre>

=== Instapaper ===

Subjectively not so semantic in terms of markup.

<pre><nowiki>
<div id="userpanel">
<a href="/extras">Extras</a>
<span>.</span>
...
</div>
</nowiki></pre>

sitemap-examples

2012-04-20T13:37:41Z

Rossputin: New page: <entry-title>Sitemap Examples</entry-title> Per the microformats process this page documents common examples of HTML navigation mechanisms out of which we may want to construct a site...

sitemap

2012-04-20T11:57:01Z

Rossputin:

<entry-title>Sitemap</entry-title>

==Authors==
[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

== Problem ==
Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

Countless sites contain HTML navigation constructs which already detail parts of the information required to build a sitemap file. Typically these constructs leverage link elements which conveniently expose an 'href' attribute. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a site map.

Currently the alternative is to either write a site map manually, or supply information to a generator (the said data being disconnected from your site).

== Existing standards ==
The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.

Per the microformats [[process]]:

* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

sitemap

2012-04-20T11:52:55Z

Rossputin:

<entry-title>Sitemap</entry-title>

==Authors==
[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

Countless sites contain HTML navigation constructs which already detail parts of the information required to build a sitemap file. Typically these constructs leverage link elements which conveniently expose an 'href' attribute. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a site map.

Currently the alternative is to either write a site map manually, or supply information to a generator (the said data being disconnected from your site).

The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.

Per the microformats [[process]]:

* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

sitemap

2012-04-20T11:50:54Z

Rossputin:

<entry-title>Sitemap</entry-title>

Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

Countless sites contain HTML navigation constructs which already detail parts of the information required to build a sitemap file. Typically these constructs leverage link elements which conveniently expose an 'href' attribute. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a site map.

Currently the alternative is to either write a site map manually, or supply information to a generator (the said data being disconnected from your site).

The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.

Per the microformats [[process]]:

* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

sitemap

2012-04-19T20:32:59Z

Rossputin:

sitemap

2012-04-19T20:20:44Z

Rossputin:

<entry-title>Sitemap</entry-title>

Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

Per the microformats [[process]]:

* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

sitemap

2012-04-19T20:06:16Z

Rossputin: New page: <entry-title>Sitemap</entry-title> Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information. Per the microformats [[proces...

<entry-title>Sitemap</entry-title>

Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

Per the microformats [[process]]:

* [[sitemap-problem]]
* [[sitemap-examples]]
* [[sitemap-formats]]
* [[sitemap-brainstorming]]
* [[sitemap-issues]]

rel-tag-issues

2012-04-18T18:57:05Z

Rossputin: /* Issues */

= 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. — [http://tantek.com/log/ Tantek]

== Issues ==

{{issues-format}}

* {{OpenIssue}} 2012-04-18 raised by [[User:Rossputin|Ross McDonald]]
*# At the time of writing rel-tag is catagorised as stable, but has a sub-heading 'Draft Specification 2005-01-10'.

* {{OpenIssue}} 2009-12-27 raised by [[User:GagaPete|Sebastian Joseph]]
*# I have a problem with this specification. It requires the tags to be links, but isn't it possible to select tags without linking them? In my opinion tags are not anything different than visible keywords. So it should be allowed to use any html elements as tags, too. I would prefer the usage of a wrapper, for example with class ''page-tags''. Then the text content of the wrapped elements with class ''tag'' should be used as tags for this page. If a Image if used as tag, then the implementations should use the alt-text of this element. The element with class ''page-tags'' should only appear once at a page.

* {{OpenIssue}} 2007-03-28 raised by [[User:JamesCraig|James Craig]]
*# [[internationalization|Internationalization]] (i18n) issue with restful tag spaces. Restful tag spaces cannot be used with non-western characters unless escaped in unicode, which renders a restful tag space quite pointless. For example:
*#*A Japanese Katakana tag ピフ would have to be <nowiki>http://example.com/tags/%E3%83%94%E3%83%95/</nowiki>
*#*A Hindi Devanagri tag चट would have to be <nowiki>http://example.com/tags/%E0%A4%9A%E0%A4%9F/</nowiki>
::There should be another way to specify the human-readable tagname.
*#*One possible solution is to provide a "romaji" or transliteration of the characters to the Latin alphabet. It would be a bit troublesome for pictographic alphabets such as kanji, but it would work well for Russian, Katakana, Hiragana, and similar phonetic alphabets. This i18n issue is a problem for URLs in general, a more fundamental issue that has to be fixed. The URL spec was created before UTF existed. (NOTE: index names for tags can be different from the raw tag, as demonstrated by Flickr). [[User:Bloritsch|Bloritsch]] 19:19, 23 July 2009 (UTC)

* {{OpenIssue}} 2007-01-10 raised by [[User:AndyMabbett|Andy Mabbett]]
*# I recently received an e-mail circular, asking that images and blog posts about a particular event be tagged in the style:

::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"? [[User:AndyMabbett|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. [[User:Bloritsch|Bloritsch]] 18:00, 17 July 2009 (UTC)

* {{OpenIssue}} 2005-06-21 raised by Hixie
*# ''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?
*#* 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
*# ''Issue 1: Somewhat confused. Please either fix or elaborate the difference in the URLs in the Tag Spaces area -> is it /tag/ or /tags/ or /wiki/. Is this URI changeable or is this just showing other implementations. If this is the case I am confused on the implementation. Should /wiki/ only show tagged content of wiki? Should URIs be constructed as /definition/ /blog/ etc... to return those items? Or is it just returning pages and the webmaster just decided on /wiki/ or /tag/ or /applicationdir/?''
*#* ACCEPTED FAQ - We need to make this an FAQ entry. --[[User:RyanKing|RyanKing]] 14:46, 25 Jan 2006 (PST) (@TODO)
*# ''Issue 2: More information on actually implementing a tag space would be helpful. I wrote a tagging system on our intranet and we run IIS. So I had to install URLrewrite (ISAPI) to create the URI /tag/tagname. We horrible Microsoft people aren't as lucky to have Mod Rewrite.''
*#* REJECTED IRRELEVANT - Implementing a tagspace is well outside the bounds of the rel-tag specification. --[[User:RyanKing|RyanKing]] 14:46, 25 Jan 2006 (PST)

* 2006-02-09 raised by JonathanFeinberg
*# ''Issue 1: It's bizarre to have the tag be denoted by the URL. The content of the '''a''' tag is a perfectly suitable place to '''contain''' the tag.''
*#* REJECTED, IGNORES ESTABLISHED PRACTICE. Flickr and del.icio.us and other tagging sites established the defacto standard of having the tag term be denoted by the last segment in the URL. [[rel-tag]] was designed to leverage that existing behavior. Theoretical arguments about suitability are irrelevant in the fact of overwhelming existing practice.
*# ''Issue 2: There's no way to distinguish between an individual user's notion of a tag and a global tag (i.e., Fred's java tag versus all things tagged with java.''
*#* REJECTED UNTRUE. ACCEPTED FAQ. Tag spaces (see [[rel-tag]] specification) are used for distinguishing, e.g. Flickr does this with photos from one user with a tag, vs. photos from all users with a tag. [[to-do]] - add this to the the [[rel-tag-faq]].
*# ''Issue 3: It's not reasonable to restrict the host's REST implementation according to this spec's rather limited idea of a "good" tag URL. The idea of tags as query parameters is rejected without justification, for example. Query parameters are a perfectly legitimate means of denoting state.''
*#* REJECTED, IGNORES ESTABLISHED PRACTICE. Flickr and del.icio.us and other tagging sites established the defacto standard of having the tag term be denoted by the last segment in the URL and thus defined what makes a "good" tag URL. [[rel-tag]] has codified this good practice.

* 2006-02-09 raised by Robert Yates
*# ''Issue 1: So I work alongside Jonathan at Lotus / IBM and we have several systems in development each with their own tag implementations. All of them have their own pages that are dedicated to listing the things within them that have been tagged by a given tag. Some of these systems use a url notation that ends in /tag but many (the majority) do not. We are looking to have a standard way that these systems can sematically tag their tags and relTag looked very promising. However, given that some of the systems produce tag urls that do not end in /tag we are a little stuck. It would be extremely hard and somewhat impracticle to get all these groups to ensure that their tag urls end in /tag. Are you at all considering another approach. We'd love to use relTag within our products, but at the moment we can't. Looking for some help / guidance.''
*#* Clarification: By '/tag' do you mean '/<tag-name>'? --[[User:RyanKing|RyanKing]] 15:21, 9 Feb 2006 (PST)
*#*:* 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.
*#*:* 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
*#*:* Any typepad blog. See for instance the categories here http://ideasinfood.typepad.com/ideas_in_food/
*#*:* Eventful. http://eventful.com/
*#*:* WordPress blogs, default permalink structure (http://example.com/?cat=N). Pretty permalinks (http://example.com/category/<tagname>) are supported through various methods, but cannot be enabled by default due to technical variances in web servers and setups. The rigidity of the spec has set a high technical barrier to entry. Even if the category name were put into the URL, it would have to be in the querystring for default WordPress setups, which isn't supported in the spec. A querystring fallback (?tag=<tagname>) would enable many more systems to use rel-tag. --[[User:MarkJaquith|MarkJaquith]] 15:39, 20 Oct 2006 (PDT)

* {{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.''
*# 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]]
*# Why not ''also'' allow tagging on within-page links (i.e. after "#" as well as after "/")? Then, if I have a page with sub-sections, each of those could be a tag, according to their ID:

<pre><nowiki>
<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>
[...]
</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]]
*#Caution should be advised when recommending Wikipedia as a name-space. For example, an article about Birmingham, Alabama, tagged with a link to http://en.wikipedia.org/wiki/Birmingham would link to an article about Birmingham, England. Similarly, a tag using http://wikitravel.org/en/Newcastle will link to a disambiguation page.

* {{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.
*#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]
*#Summary: Under the current draft, tags and relevant tagspaces are potentially hard to create; and it's still easy to abuse the system. Humans can still be tricked and so can the machines. It's a great spec if you happen to have a compliant directory structure, but if your site doesn't match then you either recreate your entire system... or, more likely, you sadly advise the client that tags aren't happening.

* {{OpenIssue}} 2007-02-03 raised by [[User:Evan|Evan]]
*#There may be value in adopting, supporting or commenting on the [http://www.flickr.com/groups/api/discuss/72157594497877875/ machine tags] format in use at [http://flickr.com/ Flickr]. Machine tags (also called [http://geobloggers.com/archives/2007/01/24/offtopic-ish-flickr-ramps-up-triple-tag-support/ triple tags]) are a structured tag format with the syntax "''namespace'':''property''=''value''". Examples: "geo:city=Portland". It's not clear how machine tags interact with other microformats ("geo:long=..." and "geo:lat=..." are two commonly-used examples, which clearly overlaps with [[geo]]), whether other sites and services will support machine tags, and how to include them here.

== 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?===
*Are tags case sensitive? Is "Dog" the same tag as "dog" and "DOG"?

===Multi-word tags===
*How should a multi-word tag be made? For instance, if using Wikipedia as a name space, a page about a Black Redstart (a bird) would be tagged '''Black_Redstart''', with an underscore [http://en.wikipedia.org/wiki/Black_Redstart]. Is there any way of aliasing alternatives ("BlackRedstart", "Black-Redstart", etc.)? Is any particular format preferable?

==Related pages==
{{rel-tag-related-pages}}

User:Rossputin

2012-04-18T18:49:55Z

Rossputin: About Me

Geek, software architect, Open Source committer, [http://www.bheap.co.uk company] co-founder and director, Jiu Jitsu fan, wine taster and father.