vote-links-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
mNo edit summary
m (Reverted edits by I MADE THOUSANDS OF ACCOUNTS IN MICROFORMATS WIKI GO TO CHECK OUT THE USER LIST ([[User talk:I MADE THOUSANDS OF ACCOUNTS IN MICROF)
 
(12 intermediate revisions by 8 users not shown)
Line 1: Line 1:
=Vote-link Issues=
These are issues that people have raised regarding [[vote-links]]. If you'd like to raise an issue here, please put the date and your name and clearly state your issue.
== Template ==
{{issues-format}}
==Issues==
==Issues==


These are issues that people have raised regarding [[vote-links]]. If you'd like to raise an issue here, please put the date and your name and clearly state your issue.
* {{OpenIssue}} 2005-06-21 raised by Hixie
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how VoteLinks must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle conflicting content?
 
* {{OpenIssue}} 2006-08-23 by porneL
*# ''What is the relation of vote links and [[rel-nofollow|rel=nofollow]]? <a rev="vote-against"> may actually have positive effect on referenced page in search engines that don't understand vote links. <a rev="vote-against" rel="nofollow"> makes more sense in this case, however nofollow means that PR should not be affected, which might be in conflict with interpretation of vote-against.
 
* {{OpenIssue}} 2007-01-04 by SteveIvy (originally by tantek in irc)
*# ''[[rel-faq#Should_.27rev.27_even_be_used|According to the 'rel' FAQ]], 'Use of "rev" SHOULD be avoided. However, VoteLinks, is being grandfathered since it was such an early use. No future microformats should be developed that use "rev".' Would it be useful to put vote-links through the proper process and see what comes of it?
 
* {{OpenIssue}} 2009-02-02 by icoloma
*# It has been raised in the FAQ that votes should not be implemented using GET links, since GET is expected to be idempotent and in fact could be followed by search engines or link-prefetching browser plugins. Instead, the proposal  should describe a method using POST forms, or using javascript code to actually cast the vote (like using Rails' POST links).
*#* I think you're misunderstanding the purpose of votelinks. They're not for polling systems. This is a non-issue; I propose that it be marked closed. [[User:TobyInk|TobyInk]] 08:31, 3 February 2009 (UTC)
*#** As someone who was similarly confused on my first encounter with vote links, I think a case could be made for clarifying this in the spec. In particular, the specification's example, which consists of two links to 'Do melt the cheese!' and 'Don't melt the cheese!', seems to be exactly the kind of polling thing that vote links isn't for. Could we come up with a better example? [[User:Chrismear|Chrismear]] 16:39, 20 February 2009 (UTC)


* 2005-06-21 raised by Hixie
* {{OpenIssue}} 2009-03-20 by [[User:TobyInk|TobyInk]]
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how votelinks must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle conflicting content?
*# Who voted for the link? The author of the page or the person [[representative-hcard|represented by the page]]? It would be nice to have some clarity.


* 2006-08-23 by porneL
==See also==
*# ''What is the relation of vote links and rel=nofollow? <a rev="vote-against"> may actually have positive effect on referenced page in search engines that don't understand vote links. <a rev="vote-against" rel="nofollow"> makes more sense in this case, however nofollow means that PR should not be affected, which might be in conflict with interpretation of vote-against.
*[[vote-links]]

Latest revision as of 11:25, 22 September 2013

Vote-link Issues

These are issues that people have raised regarding vote-links. If you'd like to raise an issue here, please put the date and your name and clearly state your issue.

Template

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">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</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
</div>
</div>

Issues

  • open issue! 2005-06-21 raised by Hixie
    1. Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how VoteLinks must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle conflicting content?
  • open issue! 2006-08-23 by porneL
    1. What is the relation of vote links and rel=nofollow? <a rev="vote-against"> may actually have positive effect on referenced page in search engines that don't understand vote links. <a rev="vote-against" rel="nofollow"> makes more sense in this case, however nofollow means that PR should not be affected, which might be in conflict with interpretation of vote-against.
  • open issue! 2007-01-04 by SteveIvy (originally by tantek in irc)
    1. According to the 'rel' FAQ, 'Use of "rev" SHOULD be avoided. However, VoteLinks, is being grandfathered since it was such an early use. No future microformats should be developed that use "rev".' Would it be useful to put vote-links through the proper process and see what comes of it?
  • open issue! 2009-02-02 by icoloma
    1. It has been raised in the FAQ that votes should not be implemented using GET links, since GET is expected to be idempotent and in fact could be followed by search engines or link-prefetching browser plugins. Instead, the proposal should describe a method using POST forms, or using javascript code to actually cast the vote (like using Rails' POST links).
      • I think you're misunderstanding the purpose of votelinks. They're not for polling systems. This is a non-issue; I propose that it be marked closed. TobyInk 08:31, 3 February 2009 (UTC)
        • As someone who was similarly confused on my first encounter with vote links, I think a case could be made for clarifying this in the spec. In particular, the specification's example, which consists of two links to 'Do melt the cheese!' and 'Don't melt the cheese!', seems to be exactly the kind of polling thing that vote links isn't for. Could we come up with a better example? Chrismear 16:39, 20 February 2009 (UTC)
  • open issue! 2009-03-20 by TobyInk
    1. Who voted for the link? The author of the page or the person represented by the page? It would be nice to have some clarity.

See also