Microformat Issues

(Difference between revisions)

Jump to: navigation, search
m (IP Issues: fix)
Current revision (18:44, 2 May 2013) (view source)
(rel-values-issues is what it means here)
 
(47 intermediate revisions not shown.)
Line 1: Line 1:
-
<h1> Microformat Issues </h1>
+
<entry-title> Microformat Issues </entry-title>
-
These are externally raised issues about microformats in general (these issues MUST apply to more than one microformat, which MUST be explicitly listed, otherwise the issue should be raised on the format specific issues page) 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]
+
These are externally raised issues about microformats in general.
-
As this is a general microformats issues page, please only note ''concrete'' real world issues. Theoretical issues will be deleted, as will any issues raised that do not contain documentation of specific real-world examples that use real-world microformats (not just brainstorms).
+
Some issues may be ACCEPTED and perhaps cause changes or improved explanations in one or more specifications or microformats in general. Some issues may be REJECTED for a variety of brief reasons, and others contain longer discussions.  
-
__TOC__
+
As this is a general microformats issues page, please only note ''concrete'' real world issues.  Theoretical issues may be deleted, as will any issues raised that do not contain documentation of specific real-world examples that use real-world microformats (not just brainstorms).
-
== Issues ==
+
Please be sure that an issue applies to more than one microformat or pattern, otherwise the issue should be raised on the format/pattern specific issues page. Please check [[issues-resolved]] and [[issues-closed]] to first see if your issue has a resolution.
-
=== Format Specific Issues ===
+
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]
-
Please raise format specific issues on the respective page:
+
== Closed Issues ==
-
* [[hcard-issues]]
+
Resolved issues that have no further actions to take.
-
* [[hcalendar-issues]]
+
* See [[issues-closed]]
-
* [[hreview-issues]]
+
-
* etc.
+
-
=== IP Issues ===
+
== Resolved Issues ==
-
* 2006-12-08 raised by [[User:AndyMabbett|Andy Mabbett]].
+
Resolved issues that have outstanding [[to-do]] items.
-
*# ''As discussed in [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007531.html], the current position on the IP rights relating to microformats is unclear, or at least not clearly expressed. It seems to me that there should be an unambiguous statement of the current position, either for each individual format, or collectively, on a page to which people with concerns may be directed.''
+
* See [[issues-resolved]]
-
*#* ACCEPTED.  A clearer statement of both copyright and patents both in specific specs and in general would be a good thing. In general, the end result that our current copyright/patent statements seek is Creative Commons, W3C, and IETF compatibility in terms of both copyrights, and royalty free patent policies. I [[to-do#Tantek|will work]] on this [[User:Tantek|Tantek]] 11:58, 9 Dec 2006 (PST)
+
-
*#** {{OpenIssue}} This appears to be unresolved; and in the light of, for example, [[hCard#Copyright the hCard 'spec']], the statement in the FAQ that "[http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F Microformats are open standards licensed under Creative Commons Attribution]" to be, at best, erroneous and misleading. [[User:AndyMabbett|Andy Mabbett]] 11:04, 10 Mar 2007 (PST)
+
-
*#**Also [http://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Attribution&curid=7391090&diff=117538680&oldid=117536621 causing concern here]. '''Prompt resolution would be advisable''' [[User:AndyMabbett|Andy Mabbett]] 09:04, 24 Mar 2007 (PDT)
+
-
*#*** First, [[citation]] is not ready for use in Wikipedia anyway.  Second, what is unclear about the Creative Commons/W3C/IETF license and patent statements?  This appears to be a theoretical issue / nitpick.  Yes, things can be made clearer, but "erroneous" and "misleading" are inaccurate labels.
+
-
*#*** This is not a citation issue. For example, [[hcard#Copyright|hCard's current copyright statement]] is not compatible with the Creative Commons license:<br><blockquote>{{MicroFormatCopyrightStatement2004}}</blockquote><br>If you look at the wikicode, this is actually the "MicroFormatCopyrightStatement2004" default microformat copyright.--[[User:JoeAndrieu|JoeAndrieu]] 15:09, 24 Mar 2007 (PDT)
+
-
* Further to the above (but out-dented for clarity), [[hresume|hResume]] cedes copyright to "the authors": "This specification is (C) 2006 by the authors"; and names just one author; Ryan King. What legal standing does the "the authors (sic) intend to submit..." clause have? What exists, to reassure someone (or some mega corporation's lawyers) contemplating or already using hResume that they won't be invoiced by Mr King? Why aren't the other people who contributed to that spec jointly credited with its copyright? [[User:AndyMabbett|Andy Mabbett]] 17:34, 24 Mar 2007 (PDT)
+
== Issues ==
 +
=== opened 2006 ===
-
=== Legal Entity Issues ===
+
<div class="hentry" id="hcard-vs-vcard-name">
-
* {{OpenIssue}} 2007-03-24 raised by [[User:JoeAndrieu|Joe Andrieu]]
+
{{OpenIssue}}  
-
*#* What is the legal entity that owns and controls microformats?
+
<span class="entry-summary author vcard">
-
*#* It could be argued that current [[faq#Q:_Who_controls_microformats.3F|Admins]] are technically operating as a legal partnership, based on statements in the [[faq|FAQ]] and coordinated actions as "microformats". As I understand it, all that is required to be legally considered a partnership is to act like one; no paperwork is required. Is that the intention? 
+
<span class="published">2006-05-11</span>
-
*#** I am not a lawyer, but I have run into this problem before.
+
[http://microformats.org/wiki/index.php?title=hcard-faq&diff=6324&oldid=6323 FAQ by <span class="fn">Brian Suda</span>], expanded/reraised by [[User:Tantek|Tantek]]
-
*#* Who owns and controls uF IP? 
+
</span>
-
*#** Note that this relates directly to the [[microformats-issues#IP|IP question]] above. The current standard copyright statement (quoted [[microformats-issues#IP|above]])  places IP in the hands of the authors, not in the hands of any specific "community" nor the public domain, despite language in the FAQ and elsewhere regarding "Creative Commons" licensing.  Even if there is a CC license, ''who'' is doing the licensing? The authors individually? An as yet unnamed legal entity operating as microformats?
+
<div class="entry-content discussion issues">
-
*#* According to [http://who.godaddy.com/WhoIs.aspx?domain=microformats.org DNS registrar records], the domain name is owned by Rohit Khare of KnowNow. Rohit used to be at CommerceNet. Does Rohit own uF? Or just the domain name?
+
* <strong class="entry-title">why does hCard use "vcard" as the root class or hCalendar use "vevent"?</strong>
-
*#* The website is apparently hosted by John Companies. Who is the account holder? How is it paid? Who pays for it? Or is it donated? John Companies lists no phone number and the number for John Kozubik (registrant of the johncompanies.com url) in the DNS registry record is no longer valid. (I emailed him and asked, but I'm sure someone here at uF will know the answer...)
+
** Originally partly [[hcard-faq#Why_does_hCard_use_vcard_as_the_root_class_name|an FAQ written by Brian Suda]], this slight inconsistency between the name of the format and the name of the root class name consistently causes confusion in a large percentage of newcomers to microformats. - [[User:Tantek|Tantek]]
-
*#* Perhaps more legally clear, who was it that accepted receipt of funds raised in the past?  (It is my understanding that funds have been raised and spent in support of certain events. Please correct me if I'm wrong.)
+
*** Looks like a typo (just one letter difference)
-
*#** Were any tax-related document filed for current and or past fundraising? If so, through what tax ID #?
+
*** Cognitive dissonance: saying "use hCard" but implying use "vcard" class name, or the implication causing one to just say "use vcard", e.g. [https://twitter.com/cssquirrel/status/129602573635289088 Kyle Weems]: <blockquote>I always end up saying "vcard" instead of "hcard" because I never write "hcard" in the code. It's weird having "two" formats that are 1:1.</blockquote>
-
*#* It is my understanding that there is no formal corporation protecting those involved and retaining control and IP of assets. Is this correct?
+
*** Ambiguity in discussions, e.g. put "vcard" in your HTML - meaning, class name, or a link to a .vcf file?
-
=== Governance Issues ===
+
*** Cognitive load: extra bit of information to remember when marking up a microformat
-
:See: [[governance-issues]]
+
*** in contrast to [[hReview]], [[hListing]], [[hRecipe]], etc. which all have root class name same as name of microformat (albeit lowercased, however some publishers have used the 2nd-letter-uppercase version as the root class name, e.g. class="hReview", enough for Google's rich snippet parsers to liberally accept it, so those could be improved as well.).
 +
** Though in microformats we believe very strongly in the [[principle]] of [[reuse]], we have to admit that in this case experience/evidence has shown that this may be a case where we re-used something too far beyond it's original meaning. Or perhaps we errantly called two slightly different things by the same name.
 +
*** '''ACCEPTED PROPOSED RESOLUTION.''' In [[microformats-2]], all vocabularies are named the same as their root class names, e.g. "h-card", "h-event", "h-entry" etc. - [[User:Tantek|Tantek]]
 +
</div>
 +
</div>
-
===Miscellaneous issues===
+
=== opened 2010 ===
-
* {{OpenIssue}} 2006-10-17 raised by [[User:AndyMabbett|Andy Mabbett]] on [[wiki-feedback]]; moved here 2007-03-10.
+
Issues opened/raised in 2010.
-
*#  What is currently described as a "specification" on [[hCard]] and [[hCalendar]] is no such thing.
+
-
*#  Andy, what would it take to turn it into a "specification"?--[[User:JoeAndrieu|JoeAndrieu]] 15:13, 24 Mar 2007 (PDT)
+
-
=== New Issues ===
+
<div class="hentry" id="class-collisions">
 +
{{OpenIssue}}
 +
<span class="entry-summary author vcard">
 +
<span class="published">2010-08-24</span>
 +
[http://html5doctor.com/microformats/#comment-10241 raised by <span class="fn">Wim</span>], expanded by [[User:Tantek|Tantek]]
 +
</span>
 +
<div class="entry-content discussion issues">
 +
* <strong class="entry-title">microformats classes like 'url' or 'region' already in use</strong>. "Using class for the microformat markup is clearly a problem, in part because it’s so easy to overlap with other markup. Authors use classes like “url” or “region” all the time, and might not be aware of the hCard format. All sorts of markup might look like a microformat."
 +
** There has also been an anecdotal report of a design firm who was not (yet) familiar with microformats seeing the "extra" classes that "that don't seem to be used" (without corresponding CSS rules) and asking if they "can remove them". By making microformats class names different from generic words, authors unfamiliar with microformats may at least notice such distinction and infer special functionality accordingly. - [[User:Tantek|Tantek]]
 +
** ACCEPTED. Pretty sure this was raised before, in IRC/lists elsewhere, but this URL was the earliest one I could find to capture it. - [[User:Tantek|Tantek]]
 +
** 2011-10-26 [https://twitter.com/richardtvaughan/status/129235473414631424 confirmed by Richard Vaughan]:
 +
*** "... Microformats can screw with existing CSS rules. ..."
 +
** [https://twitter.com/richardtvaughan/status/129236380873261057 and follow-up same day also]:
 +
*** "microformats are the easiest as it's just CSS classes, but may be a pain to implement if those class names are already used."
 +
** See also '''Beware of microformats/CSS naming collisions''' section in http://knol.google.com/k/google-rich-snippets-tips-and-tricks (no edit history, date unknown, found 2011-350)
 +
** '''ACCEPTED. PROPOSED RESOLUTION.''' We are fixing this with [[microformats-2]], all property names have prefixes to avoid such collisions. E.g. 'url' becomes 'u-url' and 'region' becomes 'p-region'. See [[microformats-2#h-card|microformats 2: h-card properties]] for more. - [[User:Tantek|Tantek]]
 +
</div>
 +
</div>
 +
 
 +
=== opened 2011 ===
 +
Issues opened/raised in 2011.
* ...
* ...
-
== Template ==
+
=== Template ===
 +
{{issues-format}}
 +
 
 +
=== Format Specific Issues ===
 +
Please raise format specific issues on their respective page(s):
 +
 
 +
* [[hatom-issues]]
 +
* [[hcard-issues]]
 +
** [[representative-hcard-issues]]
 +
* [[hcalendar-issues]]
 +
* [[hlisting-issues]]
 +
* [[hresume-issues]]
 +
* [[hreview-issues]]
 +
* [[rel-values-issues]]
 +
** [[rel-home-issues]]
 +
** [[rel-license-issues]]
 +
* [[vote-links-issues]]
 +
* [[xfn-issues]]
 +
* [[xfolk-issues]]
 +
* [[xmdp-issues]]
 +
* [[xoxo-issues]]
 +
** [[xoxo-opml-issues]]
 +
 
 +
Issues regarding microformats in progress (brainstorms etc.) are documented on their respective pages.
 +
 
 +
=== Pattern Specific Issues ===
 +
Please raise pattern specific issues on the respective page:
 +
 
 +
*[[abbr-design-pattern-issues]]
 +
** [[accessibility-issues#abbr-design-pattern]].
 +
*[[include-pattern-issues]]
 +
* etc.
-
Please use this format (copy and paste this to the end of the list to add your issues):
+
=== Domain Specific Issues ===
-
* {{OpenIssue}} YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
+
*[[accessibility-issues]]
-
*# ''Issue 1: Here is the first issue I have.''
+
*[[code-issues]]
-
*# ''Issue 2: Here is the second issue I have.''
+
*[[external-issues]]
 +
*[[tests-issues]]
==See also==
==See also==

Current revision


These are externally raised issues about microformats in general.

Some issues may be ACCEPTED and perhaps cause changes or improved explanations in one or more specifications or microformats in general. Some issues may be REJECTED for a variety of brief reasons, and others contain longer discussions.

As this is a general microformats issues page, please only note concrete real world issues. Theoretical issues may be deleted, as will any issues raised that do not contain documentation of specific real-world examples that use real-world microformats (not just brainstorms).

Please be sure that an issue applies to more than one microformat or pattern, otherwise the issue should be raised on the format/pattern specific issues page. Please check issues-resolved and issues-closed to first see if your issue has a resolution.

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. — Tantek

Contents

Closed Issues

Resolved issues that have no further actions to take.

Resolved Issues

Resolved issues that have outstanding to-do items.

Issues

opened 2006

open issue! 2006-05-11 FAQ by Brian Suda, expanded/reraised by Tantek

  • why does hCard use "vcard" as the root class or hCalendar use "vevent"?
    • Originally partly an FAQ written by Brian Suda, this slight inconsistency between the name of the format and the name of the root class name consistently causes confusion in a large percentage of newcomers to microformats. - Tantek
      • Looks like a typo (just one letter difference)
      • Cognitive dissonance: saying "use hCard" but implying use "vcard" class name, or the implication causing one to just say "use vcard", e.g. Kyle Weems:
        I always end up saying "vcard" instead of "hcard" because I never write "hcard" in the code. It's weird having "two" formats that are 1:1.
      • Ambiguity in discussions, e.g. put "vcard" in your HTML - meaning, class name, or a link to a .vcf file?
      • Cognitive load: extra bit of information to remember when marking up a microformat
      • in contrast to hReview, hListing, hRecipe, etc. which all have root class name same as name of microformat (albeit lowercased, however some publishers have used the 2nd-letter-uppercase version as the root class name, e.g. class="hReview", enough for Google's rich snippet parsers to liberally accept it, so those could be improved as well.).
    • Though in microformats we believe very strongly in the principle of reuse, we have to admit that in this case experience/evidence has shown that this may be a case where we re-used something too far beyond it's original meaning. Or perhaps we errantly called two slightly different things by the same name.
      • ACCEPTED PROPOSED RESOLUTION. In microformats-2, all vocabularies are named the same as their root class names, e.g. "h-card", "h-event", "h-entry" etc. - Tantek

opened 2010

Issues opened/raised in 2010.

open issue! 2010-08-24 raised by Wim, expanded by Tantek

  • microformats classes like 'url' or 'region' already in use. "Using class for the microformat markup is clearly a problem, in part because it’s so easy to overlap with other markup. Authors use classes like “url” or “region” all the time, and might not be aware of the hCard format. All sorts of markup might look like a microformat."
    • There has also been an anecdotal report of a design firm who was not (yet) familiar with microformats seeing the "extra" classes that "that don't seem to be used" (without corresponding CSS rules) and asking if they "can remove them". By making microformats class names different from generic words, authors unfamiliar with microformats may at least notice such distinction and infer special functionality accordingly. - Tantek
    • ACCEPTED. Pretty sure this was raised before, in IRC/lists elsewhere, but this URL was the earliest one I could find to capture it. - Tantek
    • 2011-10-26 confirmed by Richard Vaughan:
      • "... Microformats can screw with existing CSS rules. ..."
    • and follow-up same day also:
      • "microformats are the easiest as it's just CSS classes, but may be a pain to implement if those class names are already used."
    • See also Beware of microformats/CSS naming collisions section in http://knol.google.com/k/google-rich-snippets-tips-and-tricks (no edit history, date unknown, found 2011-350)
    • ACCEPTED. PROPOSED RESOLUTION. We are fixing this with microformats-2, all property names have prefixes to avoid such collisions. E.g. 'url' becomes 'u-url' and 'region' becomes 'p-region'. See microformats 2: h-card properties for more. - Tantek

opened 2011

Issues opened/raised in 2011.

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>

Format Specific Issues

Please raise format specific issues on their respective page(s):

Issues regarding microformats in progress (brainstorms etc.) are documented on their respective pages.

Pattern Specific Issues

Please raise pattern specific issues on the respective page:

Domain Specific Issues

See also

Microformat Issues was last modified: Thursday, May 2nd, 2013

Views