rel-values-issues - Revision history

Tantek: rel-issues moved to rel-values-issues: move to a name specifically for issues about rel-values in general - got to make room for an actual rel=issues rel value!

2013-05-02T18:40:13Z

rel-issues moved to rel-values-issues: move to a name specifically for issues about rel-values in general - got to make room for an actual rel=issues rel value!

← Older revision	Revision as of 18:40, 2 May 2013
(No difference)

TobyInk: /* Open issues */

2008-02-25T08:27:58Z

Open issues

← Older revision		Revision as of 08:27, 25 February 2008
Line 19:		Line 19:
	{{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-25</span> raised by <span class="fn">[[User:TobyInk\|TobyInk]]</span></span>		{{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-25</span> raised by <span class="fn">[[User:TobyInk\|TobyInk]]</span></span>
	<div class="description">		<div class="description">
			* The following is part of the [[rel-faq\|rel FAQ]]
	<blockquote style="border-left:2px solid blue;padding-left:0.67em">		<blockquote style="border-left:2px solid blue;padding-left:0.67em">
	However, given that the 'rev' attribute has been more often misused by authors than properly used ([http://code.google.com/webstats/2005-12/linkrels.html Google Code: Web Authoring Statistics: Link Relationships]) is it even a good idea to use rev at all?		However, given that the 'rev' attribute has been more often misused by authors than properly used ([http://code.google.com/webstats/2005-12/linkrels.html Google Code: Web Authoring Statistics: Link Relationships]) is it even a good idea to use rev at all?
Line 25:		Line 26:

	However, VoteLinks' use of rev has been [[glossary#grandfathered\|grandfathered]] since it was such an early use. No future microformats should be developed that use 'rev', and any use of 'rev' (apart from the "[[glossary#grandfathered\|grand-fathered]]" case of [[vote-links\|VoteLinks]]) is [[glossary#deprecated\|deprecated]] in microformats.</blockquote>		However, VoteLinks' use of rev has been [[glossary#grandfathered\|grandfathered]] since it was such an early use. No future microformats should be developed that use 'rev', and any use of 'rev' (apart from the "[[glossary#grandfathered\|grand-fathered]]" case of [[vote-links\|VoteLinks]]) is [[glossary#deprecated\|deprecated]] in microformats.</blockquote>
			*# This seems entirely arbitrary to me — the dismissal of an HTML feature because it's often improperly used would also probably rule out <img alt> (often used to provide a "tooltip" or hidden text for SEO), tables (improperly used for layout) and much more. Some people improperly use it I'm sure, but that shouldn't stop us from using rev when suitable. For example, if many pages link to http://example.com/tags/foo with rel=tag, then http://example.com/tags/foo may wish to link back to them with rev=tag. The rev attribute allows people to represent the reverse representation easily without having to propose a whole new microformat.

	===Resolved issues===		===Resolved issues===

TobyInk: Not finished yet...

2008-02-25T08:18:39Z

Not finished yet...

← Older revision		Revision as of 08:18, 25 February 2008
Line 15:		Line 15:
	</div>		</div>
	</div>		</div>

			<div class="vevent">
			{{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-25</span> raised by <span class="fn">[[User:TobyInk\|TobyInk]]</span></span>
			<div class="description">
			<blockquote style="border-left:2px solid blue;padding-left:0.67em">
			However, given that the 'rev' attribute has been more often misused by authors than properly used ([http://code.google.com/webstats/2005-12/linkrels.html Google Code: Web Authoring Statistics: Link Relationships]) is it even a good idea to use rev at all?

			The short answer is unfortunately "no". Use of "rev" {{should}} be avoided.

			However, VoteLinks' use of rev has been [[glossary#grandfathered\|grandfathered]] since it was such an early use. No future microformats should be developed that use 'rev', and any use of 'rev' (apart from the "[[glossary#grandfathered\|grand-fathered]]" case of [[vote-links\|VoteLinks]]) is [[glossary#deprecated\|deprecated]] in microformats.</blockquote>


	===Resolved issues===		===Resolved issues===
Line 23:		Line 34:
	*# Are the rel microformats only valid on anchor tags (<A>)?		*# Are the rel microformats only valid on anchor tags (<A>)?
	# Yes. Other elements have no subject, for there to be a relationship with. [[User:AndyMabbett\|Andy Mabbett]] 17:50, 11 Jan 2008 (PST)		# Yes. Other elements have no subject, for there to be a relationship with. [[User:AndyMabbett\|Andy Mabbett]] 17:50, 11 Jan 2008 (PST)
			# They are also valid on <LINK> elements, though many microformats expressly forbid this usage. [[User:TobyInk\|TobyInk]] 00:18, 25 Feb 2008 (PST)
	</div>		</div>
	</div>		</div>

AndyMabbett: /* Related pages */ issues

2008-01-12T02:16:53Z

Related pages: issues

← Older revision		Revision as of 02:16, 12 January 2008
Line 27:		Line 27:

	==Related pages==		==Related pages==
			*[[issues]]
	*[[rel-tag-issues]]		*[[rel-tag-issues]]
	{{rel-related-pages}}		{{rel-related-pages}}

AndyMabbett: /* Issues */ template

2008-01-12T02:15:19Z

Issues: template

← Older revision		Revision as of 02:15, 12 January 2008
Line 5:		Line 5:
	== Issues ==		== Issues ==

	~~Please use this format:~~		{{issues-format}}
	~~<pre>~~
	~~<nowiki>~~
	~~<div class="vevent">~~
	* {{~~OpenIssue~~}} ~~<span class="summary vcard"><span class="dtstart">YYYY-MM-DD</span> raised by <span class="fn">~~~</span></span>~~
	~~<div class="description">~~
	*# Here is the first issue I have.
	*# Here is the second issue I have.
	~~</div>~~
	~~</div>~~
	~~</nowiki>~~
	~~</pre>~~

	===Open issues===		===Open issues===

AndyMabbett: /* Open issues */ clarify

2008-01-12T02:05:41Z

Open issues: clarify

← Older revision		Revision as of 02:05, 12 January 2008
Line 23:		Line 23:
	* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-12</span> raised by <span class="fn">[[User:AndyMabbett\|Andy Mabbett]]</span></span>		* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-12</span> raised by <span class="fn">[[User:AndyMabbett\|Andy Mabbett]]</span></span>
	<div class="description">		<div class="description">
	*# I think there is a general issue with requiring @rels where publishers normally use text, not links; contrary to [http://microformats.org/wiki/microformats microformats are not... an attempt to get everyone to change their behavior...]" and the principle "[http://microformats.org/wiki/principles adapt to current behaviors]"; I see no reason why microformats should not use both, with the same value. In other words, ~~for~~ some microformats ([[rel-tag]], [[rel-license]], etc.) <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, where rel values cannot be used by editors.		*# I think there is a general issue with requiring @rels where publishers normally use text, not links; contrary to [http://microformats.org/wiki/microformats microformats are not... an attempt to get everyone to change their behavior...]" and the principle "[http://microformats.org/wiki/principles adapt to current behaviors]"; I see no reason why microformats should not use both, with the same value. In other words, in some current and proposed microformats, properties using, say, [[rel-tag]], [[rel-license]], etc. (and possibly for rel-tag itself), <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, where rel values cannot be used by editors.
	</div>		</div>
	</div>		</div>

AndyMabbett: /* Open issues */ [[]]

2008-01-12T01:58:25Z

Open issues: [[]]

← Older revision		Revision as of 01:58, 12 January 2008
Line 23:		Line 23:
	* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-12</span> raised by <span class="fn">[[User:AndyMabbett\|Andy Mabbett]]</span></span>		* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-12</span> raised by <span class="fn">[[User:AndyMabbett\|Andy Mabbett]]</span></span>
	<div class="description">		<div class="description">
	*# I think there is a general issue with requiring @rels where publishers normally use text, not links; contrary to [http://microformats.org/wiki/microformats microformats are not... an attempt to get everyone to change their behavior...]" and the principle "[http://microformats.org/wiki/principles adapt to current behaviors]"; I see no reason why microformats should not use both, with the same value. In other words, for some microformats (rel-tag, rel-license, etc.) <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, where rel values cannot be used by editors.		*# I think there is a general issue with requiring @rels where publishers normally use text, not links; contrary to [http://microformats.org/wiki/microformats microformats are not... an attempt to get everyone to change their behavior...]" and the principle "[http://microformats.org/wiki/principles adapt to current behaviors]"; I see no reason why microformats should not use both, with the same value. In other words, for some microformats ([[rel-tag]], [[rel-license]], etc.) <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, where rel values cannot be used by editors.
	</div>		</div>
	</div>		</div>

AndyMabbett at 01:58, 12 January 2008

2008-01-12T01:58:02Z

← Older revision		Revision as of 01:58, 12 January 2008
Line 23:		Line 23:
	* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-12</span> raised by <span class="fn">[[User:AndyMabbett\|Andy Mabbett]]</span></span>		* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-12</span> raised by <span class="fn">[[User:AndyMabbett\|Andy Mabbett]]</span></span>
	<div class="description">		<div class="description">
	*# I think there is a general issue with requiring @rels where publishers normally use text, not links; contrary to [http://microformats.org/wiki/microformats microformats are not... an attempt to get everyone to change their behavior...]" and the principle "[http://microformats.org/wiki/principles adapt to current behaviors]"; I see no reason why microformats should not use both, with the same value. In other words, <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, where rel values cannot be used by editors.		*# I think there is a general issue with requiring @rels where publishers normally use text, not links; contrary to [http://microformats.org/wiki/microformats microformats are not... an attempt to get everyone to change their behavior...]" and the principle "[http://microformats.org/wiki/principles adapt to current behaviors]"; I see no reason why microformats should not use both, with the same value. In other words, for some microformats (rel-tag, rel-license, etc.) <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, where rel values cannot be used by editors.
	</div>		</div>
	</div>		</div>

AndyMabbett: /* rel Issues */ mark as resolved

2008-01-12T01:51:54Z

rel Issues: mark as resolved

← Older revision		Revision as of 01:51, 12 January 2008
Line 17:		Line 17:
	</nowiki>		</nowiki>
	</pre>		</pre>

			===Open issues===

	<div class="vevent">		<div class="vevent">
	* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">~~2007~~-06-06</span> raised by <span class="fn">[[~~MikeKaply~~\|~~Mike Kaply~~]]</span></span>		* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-12</span> raised by <span class="fn">[[User:AndyMabbett\|Andy Mabbett]]</span></span>
	<div class="description">		<div class="description">
	*# ~~Are~~ the ~~rel~~ microformats ~~only valid on anchor tags (~~<A>)?		*# I think there is a general issue with requiring @rels where publishers normally use text, not links; contrary to [http://microformats.org/wiki/microformats microformats are not... an attempt to get everyone to change their behavior...]" and the principle "[http://microformats.org/wiki/principles adapt to current behaviors]"; I see no reason why microformats should not use both, with the same value. In other words, <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, where rel values cannot be used by editors.
	# Yes. ~~Other elements have no subject~~, ~~for there to~~ be ~~a relationship with~~. ~~[[User:AndyMabbett\|Andy Mabbett]] 17:50, 11 Jan 2008 (PST)~~
	</div>		</div>
	</div>		</div>

			===Resolved issues===

	<div class="vevent">		<div class="vevent">
	* ~~{{OpenIssue}}~~ <span class="summary vcard"><span class="dtstart">~~2008~~-01-12</span> raised by <span class="fn">[[~~User:AndyMabbett~~\|~~Andy Mabbett~~]]</span></span>		* <span class="summary vcard"><span class="dtstart">2007-06-06</span> raised by <span class="fn">[[MikeKaply\|Mike Kaply]]</span></span>
	<div class="description">		<div class="description">
	*# ~~I think~~ there is a ~~general issue~~ with ~~requiring @rels where publishers normally use text, not links; contrary to~~ [~~http~~:~~//microformats.org/wiki/microformats microformats are not... an attempt to get everyone to change their behavior...~~]~~" and the principle "[http~~://microformats.org/wiki/principles adapt to current behaviors]"; I see no reason why microformats should not use both, with the same value. In other words, <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, ~~where rel values cannot be used by editors.~~		*# Are the rel microformats only valid on anchor tags (<A>)?
			# Yes. Other elements have no subject, for there to be a relationship with. [[User:AndyMabbett\|Andy Mabbett]] 17:50, 11 Jan 2008 (PST)
	</div>		</div>
	</div>		</div>

AndyMabbett: rm redunddant copy

2008-01-12T01:51:04Z

rm redunddant copy

← Older revision		Revision as of 01:51, 12 January 2008
Line 11:		Line 11:
	* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">YYYY-MM-DD</span> raised by <span class="fn">~~~</span></span>		* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">YYYY-MM-DD</span> raised by <span class="fn">~~~</span></span>
	<div class="description">		<div class="description">
	*# ~~Issue 1:~~ Here is the first issue I have.		*# Here is the first issue I have.
	*# ~~Issue 2:~~ Here is the second issue I have.		*# Here is the second issue I have.
	</div>		</div>
	</div>		</div>