rel-registry - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:32:07Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:32, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~rel registry~~</entry-title>~~		{{DISPLAYTITLE:rel registry}}

	The microformats wiki has the closest thing to a real-world rel value registry of [[link-relation-types\|link relation types]] (or link types).		The microformats wiki has the closest thing to a real-world rel value registry of [[link-relation-types\|link relation types]] (or link types).

Tantek: link types is what HTML4 called them

2011-09-20T15:07:14Z

link types is what HTML4 called them

← Older revision		Revision as of 15:07, 20 September 2011
Line 1:		Line 1:
	<entry-title>rel registry</entry-title>		<entry-title>rel registry</entry-title>

	The microformats wiki has the closest thing to a real-world rel value registry of [[link-relation-types\|link relation types]].		The microformats wiki has the closest thing to a real-world rel value registry of [[link-relation-types\|link relation types]] (or link types).

	We have the most comprehensive documentation of [[existing-rel-values]] currently which performs quite well as a rel registry, perhaps even better than any other "official" attempts at rel registries (AKA link relation registry or link relations list) out there.		We have the most comprehensive documentation of [[existing-rel-values]] currently which performs quite well as a rel registry, perhaps even better than any other "official" attempts at rel registries (AKA link relation registry or link relations list) out there.

Tantek: link relation types

2011-09-20T15:06:43Z

link relation types

← Older revision		Revision as of 15:06, 20 September 2011
Line 1:		Line 1:
	<entry-title>rel registry</entry-title>		<entry-title>rel registry</entry-title>

	The microformats wiki has the closest thing to a real-world rel value registry.		The microformats wiki has the closest thing to a real-world rel value registry of [[link-relation-types\|link relation types]].

	We have the most comprehensive documentation of [[existing-rel-values]] currently which performs quite well as a rel registry, perhaps even better than any other "official" attempts at rel registries (AKA link relation registry or link relations list) out there.		We have the most comprehensive documentation of [[existing-rel-values]] currently which performs quite well as a rel registry, perhaps even better than any other "official" attempts at rel registries (AKA link relation registry or link relations list) out there.

SamB: /* How does the microformats rel registry compare to RFC and W3C options */

2011-06-06T23:01:31Z

How does the microformats rel registry compare to RFC and W3C options

← Older revision		Revision as of 23:01, 6 June 2011
Line 66:		Line 66:
	''Q: How does the microformats rel registry compare to RFC and W3C options?''		''Q: How does the microformats rel registry compare to RFC and W3C options?''

	A: The W3C doesn't currently have a rel registry. The closest thing to a W3C rel registry is the HTML4.01 Recommendation (which defines several rel values), and the HTML5 Working Draft. The latter is only edited/updated by a single editor, and thus all "registrations" must be committed by one individual. Such "registrations" are simultaneously published by the WHATWG in their "HTML" specification which ~~are~~ available under the MIT license.		A: The W3C doesn't currently have a rel registry. The closest thing to a W3C rel registry is the HTML4.01 Recommendation (which defines several rel values), and the HTML5 Working Draft. The latter is only edited/updated by a single editor, and thus all "registrations" must be committed by one individual. Such "registrations" are simultaneously published by the WHATWG in their "HTML" specification (see http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#linkTypes) which is available under the MIT license.

			Also note that the WHATWG spec presently [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#other-link-types states]:

			<blockquote>
			<dfn id="concept-rel-extensions" title="concept-rel-extensions">Extensions to the predefined set of link types</dfn> may be registered in the [http://microformats.org/wiki/existing-rel-values Microformats wiki existing-rel-values page].
			</blockquote>

	In comparison, the RFC/IETF/IANA method which appears to be at this URL:		In comparison, the RFC/IETF/IANA method which appears to be at this URL:
Line 79:		Line 85:

	# microformats has the most liberal (least private) availability as public domain		# microformats has the most liberal (least private) availability as public domain
	# W3C HTML5 (via WHATWG's "HTML") has the ~~effective~~ as liberal MIT license		# W3C HTML5 (via WHATWG's "HTML") has the effectively as liberal MIT license
	# RFC/IETF/IANA has no obvious license and thus it is unclear.		# RFC/IETF/IANA has no obvious license and thus it is unclear.

Tantek: /* new rel values */ more detail on jump starting a new rel value to make it easier / simpler

2011-04-02T17:12:48Z

new rel values: more detail on jump starting a new rel value to make it easier / simpler

← Older revision		Revision as of 17:12, 2 April 2011
Line 19:		Line 19:

	== new rel values ==		== new rel values ==
	If you wish to develop a new rel value, please follow the microformats [[process]]. ~~Feel~~ free to add ~~possible~~ rel ~~values~~ to the ~~brainstorms~~ section, but be sure to follow-up quickly with a page for the rel value itself explaining it in more detail, ~~as well as~~ email the microformats-new [[mailing-list]].		If you wish to develop a new rel value, please follow the microformats [[process]].

			While you're following the [[process]], feel free to add your new rel value to the [[existing-rel-values#brainstorming\|brainstorming section]] to indicate your interest and work in progress, but be sure to follow-up quickly with:
			* a page for the rel value itself clearly documenting it as a ''brainstorm proposal'', and explaining it in more detail, including documentation sections per the [[process]] (real world end user use cases, examples of content in the wild that would benefit, previous attempts at such a rel value or related format)
			* email to the microformats-new [[mailing-list]] stating your interest in developing the rel value
			* [[IRC]] (or email) asking help regarding anything in the [[process]] or general rel value questions that would help you to develop your new rel value.

	== FAQ ==		== FAQ ==

Tantek: add common aliases to rel registry to the intro for improved discoverability

2011-04-02T00:46:13Z

add common aliases to rel registry to the intro for improved discoverability

← Older revision		Revision as of 00:46, 2 April 2011
Line 2:		Line 2:

	The microformats wiki has the closest thing to a real-world rel value registry.		The microformats wiki has the closest thing to a real-world rel value registry.
	We have the most comprehensive documentation of [[existing-rel-values]] currently which performs quite well as a rel registry, perhaps even better than any other "official" attempts at rel registries out there.		We have the most comprehensive documentation of [[existing-rel-values]] currently which performs quite well as a rel registry, perhaps even better than any other "official" attempts at rel registries (AKA link relation registry or link relations list) out there.

	== stable rel values ==		== stable rel values ==

Tantek: add FAQ: Is there a machine processable version of the microformats rel registry - yes - yay for semantic HTML tables on a wiki!

2011-04-02T00:38:19Z

add FAQ: Is there a machine processable version of the microformats rel registry - yes - yay for semantic HTML tables on a wiki!

← Older revision		Revision as of 00:38, 2 April 2011
Line 76:		Line 76:
	# W3C HTML5 (via WHATWG's "HTML") has the effective as liberal MIT license		# W3C HTML5 (via WHATWG's "HTML") has the effective as liberal MIT license
	# RFC/IETF/IANA has no obvious license and thus it is unclear.		# RFC/IETF/IANA has no obvious license and thus it is unclear.

			=== Is there a machine processable version of the microformats rel registry ===
			''Q: Is there a machine processable version of the microformats rel registry? ''

			A: Yes. Each of the levels of rel values (formats, proposals, brainstorming) are in their own semantic HTML table, in order (1,2,3) on the [[existing-rel-values]] page.

			Machine processors may pick the table of their choosing by choosing the appropriate ordinal (1,2,3) and then parse it as well-formed markup, using the first column of the table as the rel value, the 2nd column as informative text, and the first hyperlink in the 3rd column of a row as the defining specification/draft/proposal where the rel value is further explained.

Tantek: /* FAQ */ How does the microformats rel registry compare to RFC and W3C options, specifically, in terms of public vs private, license etc.

2011-04-02T00:31:47Z

FAQ: How does the microformats rel registry compare to RFC and W3C options, specifically, in terms of public vs private, license etc.

← Older revision		Revision as of 00:31, 2 April 2011
Line 57:		Line 57:

	A: Yes. If you google for "rel registry" this page currently comes up on the first page of results, and may of the other results point to this page. Similarly a searching "rel values" returns results including [[existing-rel-values]] on the first page of results (in fact, the very ''first'' result as of 2011-091 on Google and Yahoo).		A: Yes. If you google for "rel registry" this page currently comes up on the first page of results, and may of the other results point to this page. Similarly a searching "rel values" returns results including [[existing-rel-values]] on the first page of results (in fact, the very ''first'' result as of 2011-091 on Google and Yahoo).

			=== How does the microformats rel registry compare to RFC and W3C options ===
			''Q: How does the microformats rel registry compare to RFC and W3C options?''

			A: The W3C doesn't currently have a rel registry. The closest thing to a W3C rel registry is the HTML4.01 Recommendation (which defines several rel values), and the HTML5 Working Draft. The latter is only edited/updated by a single editor, and thus all "registrations" must be committed by one individual. Such "registrations" are simultaneously published by the WHATWG in their "HTML" specification which are available under the MIT license.

			In comparison, the RFC/IETF/IANA method which appears to be at this URL:

			http://www.iana.org/assignments/link-relations/

			Provides no license, copyright or other statement of how it may be (re)used.

			Finally the microformats [[rel-registry]], and [[existing-rel-values]] as with the rest of the microformats wiki are published with a Creative Commons Public Domain License.

			Thus comparing these three (microformats, W3C/WHATWG, RFC/IETF/IANA) :

			# microformats has the most liberal (least private) availability as public domain
			# W3C HTML5 (via WHATWG's "HTML") has the effective as liberal MIT license
			# RFC/IETF/IANA has no obvious license and thus it is unclear.

Tantek: add FAQ re: discoverability

2011-04-01T23:03:29Z

add FAQ re: discoverability

← Older revision		Revision as of 23:03, 1 April 2011
Line 48:		Line 48:
	''Q: How do provisionally registered values achieve full registration?''		''Q: How do provisionally registered values achieve full registration?''

	The microformats [[process]] documents a number of steps to advance any microformats effort, including new rel values. In short, documenting specific real world use cases for a new rel value, and research into existing content that could benefit from it, as well as earlier/other attempts at such concepts help greatly.		A: The microformats [[process]] documents a number of steps to advance any microformats effort, including new rel values. In short, documenting specific real world use cases for a new rel value, and research into existing content that could benefit from it, as well as earlier/other attempts at such concepts help greatly.

	Also the microformats [[process]] has been updated this year (2011) to provide a more explicit path from draft, to specification, to standard. Those take additional steps such as documenting real world uses of a provisional rel value, implementations, test suites, test results.		Also the microformats [[process]] has been updated this year (2011) to provide a more explicit path from draft, to specification, to standard. Those take additional steps such as documenting real world uses of a provisional rel value, implementations, test suites, test results.

			=== Is the microformats rel registry discoverable ===

			''Q: Is the microformats rel registry discoverable?''

			A: Yes. If you google for "rel registry" this page currently comes up on the first page of results, and may of the other results point to this page. Similarly a searching "rel values" returns results including [[existing-rel-values]] on the first page of results (in fact, the very ''first'' result as of 2011-091 on Google and Yahoo).

Tantek: /* How do provisional values achieve full registration */ t/g

2011-04-01T22:53:13Z

How do provisional values achieve full registration: t/g

← Older revision		Revision as of 22:53, 1 April 2011
Line 50:		Line 50:
	The microformats [[process]] documents a number of steps to advance any microformats effort, including new rel values. In short, documenting specific real world use cases for a new rel value, and research into existing content that could benefit from it, as well as earlier/other attempts at such concepts help greatly.		The microformats [[process]] documents a number of steps to advance any microformats effort, including new rel values. In short, documenting specific real world use cases for a new rel value, and research into existing content that could benefit from it, as well as earlier/other attempts at such concepts help greatly.

	Also the microformats [[process]] has been updated this year (2011) to provide a more explicit path from draft, to specification, to standard. Those take additional steps such as documenting real world uses of ~~the provision~~ rel value, implementations, test suites, test results.		Also the microformats [[process]] has been updated this year (2011) to provide a more explicit path from draft, to specification, to standard. Those take additional steps such as documenting real world uses of a provisional rel value, implementations, test suites, test results.