rel-up - Revision history

Prlbr: /* Use cases */ fixed Unicode name for ↑

2018-06-23T13:44:41Z

Use cases: fixed Unicode name for ↑

← Older revision		Revision as of 13:44, 23 June 2018
Line 32:		Line 32:
	This explicit knowledge can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past. In 2018, at least the SeaMonkey, iCab and Lynx browsers support ''rel=up'' natively. Opera did in the past. Add-ons for previous Firefox versions which used ''rel=up'' included Link Widgets by cdn and Stephen Clavering, Site navigation bar by Klaus Bolwin, cmSiteNavigation Toolbar by Christoph A. Mueller. A LinkBar Add-on for Internet Explorer was available. See <nowiki>http://matthias.gutfeldt.ch/translation/LINK/addendum.html</nowiki> for exotic/historical examples.		This explicit knowledge can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past. In 2018, at least the SeaMonkey, iCab and Lynx browsers support ''rel=up'' natively. Opera did in the past. Add-ons for previous Firefox versions which used ''rel=up'' included Link Widgets by cdn and Stephen Clavering, Site navigation bar by Klaus Bolwin, cmSiteNavigation Toolbar by Christoph A. Mueller. A LinkBar Add-on for Internet Explorer was available. See <nowiki>http://matthias.gutfeldt.ch/translation/LINK/addendum.html</nowiki> for exotic/historical examples.

	Assistive technology (does any today?) could communicate better what a link such as the following means, for example by reading "link to ''parent page'', arrow up" instead of just "link, arrow up":		Assistive technology (does any today?) could communicate better what a link such as the following means, for example by reading "link to ''parent page'', upwards arrow" instead of just "link, upwards arrow":

	<source lang=html4strict><a rel='up' href='..'>↑</a></source>		<source lang=html4strict><a rel='up' href='..'>↑</a></source>

Prlbr: /* Use cases */ gave an example how assistive technology could use rel=up (don’t know whether this is done in any software today) and how a "polyfill" could work

2018-06-23T13:41:07Z

Use cases: gave an example how assistive technology could use rel=up (don’t know whether this is done in any software today) and how a "polyfill" could work

← Older revision		Revision as of 13:41, 23 June 2018
Line 32:		Line 32:
	This explicit knowledge can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past. In 2018, at least the SeaMonkey, iCab and Lynx browsers support ''rel=up'' natively. Opera did in the past. Add-ons for previous Firefox versions which used ''rel=up'' included Link Widgets by cdn and Stephen Clavering, Site navigation bar by Klaus Bolwin, cmSiteNavigation Toolbar by Christoph A. Mueller. A LinkBar Add-on for Internet Explorer was available. See <nowiki>http://matthias.gutfeldt.ch/translation/LINK/addendum.html</nowiki> for exotic/historical examples.		This explicit knowledge can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past. In 2018, at least the SeaMonkey, iCab and Lynx browsers support ''rel=up'' natively. Opera did in the past. Add-ons for previous Firefox versions which used ''rel=up'' included Link Widgets by cdn and Stephen Clavering, Site navigation bar by Klaus Bolwin, cmSiteNavigation Toolbar by Christoph A. Mueller. A LinkBar Add-on for Internet Explorer was available. See <nowiki>http://matthias.gutfeldt.ch/translation/LINK/addendum.html</nowiki> for exotic/historical examples.

	Assistive technology (does any today?) could communicate ~~(what should it say?)~~ better what a link such as the following means:		Assistive technology (does any today?) could communicate better what a link such as the following means, for example by reading "link to ''parent page'', arrow up" instead of just "link, arrow up":

	<source lang=html4strict><a rel='up' href='..'>↑</a></source>		<source lang=html4strict><a rel='up' href='..'>↑</a></source>

			In the absence of native support for ''rel=up'' and similar link relations (''next'', ''prev'', …) in assistive technology it’s possible to translate the ''rel'' values to a textual description with the ''aria-label'' attribute automatically using a script.

	Hierarchical information allows for better sitemaps to be generated automatically by web spiders.		Hierarchical information allows for better sitemaps to be generated automatically by web spiders.

Prlbr: /* Use cases */ added specific examples of browsers/extensions which improve navigation with rel=up

2018-06-22T22:50:08Z

Use cases: added specific examples of browsers/extensions which improve navigation with rel=up

← Older revision		Revision as of 22:50, 22 June 2018
Line 30:		Line 30:
	* in software documentation a page about a class and its parent class		* in software documentation a page about a class and its parent class

	This explicit knowledge can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past ~~(specific~~ examples ~~of each?)~~.		This explicit knowledge can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past. In 2018, at least the SeaMonkey, iCab and Lynx browsers support ''rel=up'' natively. Opera did in the past. Add-ons for previous Firefox versions which used ''rel=up'' included Link Widgets by cdn and Stephen Clavering, Site navigation bar by Klaus Bolwin, cmSiteNavigation Toolbar by Christoph A. Mueller. A LinkBar Add-on for Internet Explorer was available. See <nowiki>http://matthias.gutfeldt.ch/translation/LINK/addendum.html</nowiki> for exotic/historical examples.

	Assistive technology (does any today?) could communicate (what should it say?) better what a link such as the following means:		Assistive technology (does any today?) could communicate (what should it say?) better what a link such as the following means:

Tantek: a few parentheticals, standards discussion

2018-06-20T22:18:58Z

a few parentheticals, standards discussion

← Older revision		Revision as of 22:18, 20 June 2018
Line 23:		Line 23:
	== Use cases ==		== Use cases ==

	Authors can make a hierarchical relationship ~~machine-readable~~, for example between		Authors can make a hierarchical relationship discoverable, for example between

	* a single photo page and a gallery overview page		* a single photo page and a gallery overview page
Line 30:		Line 30:
	* in software documentation a page about a class and its parent class		* in software documentation a page about a class and its parent class

	This can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past. Assistive technology could communicate better what a link such as the following means:		This explicit knowledge can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past (specific examples of each?).

			Assistive technology (does any today?) could communicate (what should it say?) better what a link such as the following means:

	<source lang=html4strict><a rel='up' href='..'>↑</a></source>		<source lang=html4strict><a rel='up' href='..'>↑</a></source>

	Hierarchical information allows for better sitemaps to be generated automatically by web spiders.		Hierarchical information allows for better sitemaps to be generated automatically by web spiders.
			* Web spiders tend to prefer an explicit [[sitemap]] for that use-case. [[User:Tantek\|Tantek]] 22:18, 20 June 2018 (UTC)

	== Standards ==		== Standards ==
Line 43:		Line 46:
	* XHTML vocabulary (<nowiki>https://www.w3.org/1999/xhtml/vocab#up</nowiki>)		* XHTML vocabulary (<nowiki>https://www.w3.org/1999/xhtml/vocab#up</nowiki>)
	** and hence XHTML+RDFa Initial Context (<nowiki>https://www.w3.org/2011/rdfa-context/xhtml-rdfa-1.1</nowiki>)		** and hence XHTML+RDFa Initial Context (<nowiki>https://www.w3.org/2011/rdfa-context/xhtml-rdfa-1.1</nowiki>)

			<div class="discussion">
			* This is good reason to reserve the rel value of "up", but insufficient to make it a standard, since those registries do not require use-cases or implementation, both of which are essential to having a useful standard. - [[User:Tantek\|Tantek]] 22:18, 20 June 2018 (UTC)
			</div>

	== History ==		== History ==

Prlbr: added possible use cases

2018-06-20T15:13:40Z

added possible use cases

← Older revision		Revision as of 15:13, 20 June 2018
Line 20:		Line 20:

	''next'' and ''prev'' relate to documents on the same hierarchy level while ''up'' moves one level up.		''next'' and ''prev'' relate to documents on the same hierarchy level while ''up'' moves one level up.

			== Use cases ==

			Authors can make a hierarchical relationship machine-readable, for example between

			* a single photo page and a gallery overview page
			* a forum thread and a forum
			* the archive page for a single month in a blog and the archive page for the whole year
			* in software documentation a page about a class and its parent class

			This can improve navigation for users of navigation bars, either browser extension or built-in. Multiple such bars exist and existed in the past. Assistive technology could communicate better what a link such as the following means:

			<source lang=html4strict><a rel='up' href='..'>↑</a></source>

			Hierarchical information allows for better sitemaps to be generated automatically by web spiders.

	== Standards ==		== Standards ==

Prlbr: added some historical notes (the wiki doesn’t let me post external links, so I put the URLs into tags)

2018-06-20T14:38:11Z

added some historical notes (the wiki doesn’t let me post external links, so I put the URLs into <nowiki> tags)

@@ Line 28: / Line 28: @@
 * XHTML vocabulary (<nowiki>https://www.w3.org/1999/xhtml/vocab#up</nowiki>)
 ** and hence XHTML+RDFa Initial Context (<nowiki>https://www.w3.org/2011/rdfa-context/xhtml-rdfa-1.1</nowiki>)
 == Implementations ==

Prlbr: added standards that define rel=up and an implementation (the wiki doesn’t let me post an external link, so I put the URL into tags)

2018-06-20T14:28:02Z

added standards that define rel=up and an implementation (the wiki doesn’t let me post an external link, so I put the URL into <nowiki> tags)

← Older revision		Revision as of 14:28, 20 June 2018
Line 20:		Line 20:

	''next'' and ''prev'' relate to documents on the same hierarchy level while ''up'' moves one level up.		''next'' and ''prev'' relate to documents on the same hierarchy level while ''up'' moves one level up.

			== Standards ==

			The link relation ''up'' is recognized in standards:

			* IANA link relations registry (<nowiki>https://www.iana.org/assignments/link-relations/link-relations.xhtml</nowiki>)
			* XHTML vocabulary (<nowiki>https://www.w3.org/1999/xhtml/vocab#up</nowiki>)
			** and hence XHTML+RDFa Initial Context (<nowiki>https://www.w3.org/2011/rdfa-context/xhtml-rdfa-1.1</nowiki>)

	== Implementations ==		== Implementations ==
Line 26:		Line 34:
	* https://chrome.google.com/webstore/detail/cgddacggfmoggigikjjcogdodjiplibe		* https://chrome.google.com/webstore/detail/cgddacggfmoggigikjjcogdodjiplibe
	* http://www.seamonkey-project.org/		* http://www.seamonkey-project.org/
			* <nowiki>https://www.drupal.org/project/rel_links</nowiki>

	== See Also ==		== See Also ==

Prlbr: added short description, example (the wiki doesn’t let me post an external link, so I put the URL into tags)

2018-06-20T14:19:40Z

added short description, example (the wiki doesn’t let me post an external link, so I put the URL into <nowiki> tags)

← Older revision		Revision as of 14:19, 20 June 2018
Line 1:		Line 1:
	{{stub}}		{{stub}}

			== Description ==

			Refers to a parent document in a hierarchy of documents.

			== Example ==

			A page (<nowiki>https://prlbr.de/galerie/14/am-pranger/</nowiki>) in a photo gallery showcases a photo. The page defines multiple link relations which refer to the

			* '''next''' page which contains the next photo from the gallery
			* '''prev'''ious page from the gallery
			* parent page using '''up''', which shows previews of many photos as thumbnails including the current one and includes links to their corresponding pages.

			<source lang=html4strict>
			<link rel='next' href='/galerie/14/mustergatte/'>
			<link rel='prev' href='/galerie/14/linie-1/'>
			<link rel='up' href='/galerie/seite-6'>
			</source>

			''next'' and ''prev'' relate to documents on the same hierarchy level while ''up'' moves one level up.

	== Implementations ==		== Implementations ==

Henke37: a browser that supports it by default?! crazy, right?

2016-09-16T14:12:04Z

a browser that supports it by default?! crazy, right?

← Older revision		Revision as of 14:12, 16 September 2016
Line 5:		Line 5:
	* https://addons.mozilla.org/en-US/firefox/addon/link-widgets/		* https://addons.mozilla.org/en-US/firefox/addon/link-widgets/
	* https://chrome.google.com/webstore/detail/cgddacggfmoggigikjjcogdodjiplibe		* https://chrome.google.com/webstore/detail/cgddacggfmoggigikjjcogdodjiplibe
			* http://www.seamonkey-project.org/

	== See Also ==		== See Also ==

Tantek: couple more see alsos

2011-08-13T00:20:46Z

couple more see alsos

← Older revision		Revision as of 00:20, 13 August 2011
Line 9:		Line 9:

	* [[rel-next]]		* [[rel-next]]
			* [[rel-faq]]
			* [[existing-rel-values]]