|Microformat was a good articles nominee, but did not meet the good article criteria at the time. There are suggestions below for improving the article. Once these issues have been addressed, the article can be renominated. Editors may also seek a reassessment of the decision if they believe there was a mistake.|
Archive 1 (Feb 2006—August 2007)
- It is reasonably well written.
- a (prose): b (MoS):
- It is factually accurate and verifiable.
- It is broad in its coverage.
- a (major aspects): b (focused):
- It follows the neutral point of view policy.
- Fair representation without bias:
- It is stable.
- No edit wars etc.:
- It is illustrated by images, where possible and appropriate.
- The Microformat-logo.png needs to have its fair-use rationale filled out — specifically it needs to have the "Article" and "Portion" sections filled out.
- Encyclopedic articles should not use slang ie. don't call it "the web" (in the lead, for example) and some text is a bit too colloquial for an encyclopedic. Example from the lead: "Current microformats allow the encoding and extraction of events, contact information, social relationships and so on." I fixed up another one in my tidying of "Technical overview" if you want to see what I mean. One that I did not correct (because I was not sure how you wanted to phrase it) was "the whole thing," a very vague and unencyclopedic term, under "Example"
- Many statements require a citaiton:
- "Most of the existing microformats were created at the Microformats.org wiki and associated mailing list, by a process of gathering examples of web publishing behaviour, then codifying it. Some other microformats (such as rel=nofollow and unAPI) have been proposed, or developed, elsewhere." (Background)
- Anything in the the "Technical overview" section that is not common. For one example "Other, optional, hCard classes also exist."
- Redlinks under "Specific microformats" (and, if you're up to it, all of them – but this is not mandatory as the reader can click on the Wikipedia link to verify their existence)
- All of the Proposed microformats
- Most of "Uses of microformats"
- The "Intellectual property" section
- I think there needs to be a bit more stating the obvious to make the article a bit more accessible to readers unfamiliar with the terminology that you use. Technical terms, even those with linked Wikipedia articles, should be briefly explained, in no more than a sentence if possible, for the layman. Alternatively, you might want to create a subsection under "background" that states the obvious for a completely oblivious reader.
- The subsection "in-context examples" should be moved to the "See also" section
- The prose under "Technical overview" needed some tidying up, which I took the liberty of doing myself, but this sentence "For example, in the text "The birds roosted at 52.48,-1.89" is a pair of numbers which may be understood, from their context, to be a set of geographic coordinates." makes no sense. I get what you're trying to say, but perhaps you should reformat it rather than myself, so make sure you get the exact idea across.
- Be careful of using words that create a subjective time frame. For an example from "Example," "It is now possible for software..." the now of now will not be the now of 100 years from now. An objective time frame must be established, for example, "Since the early 2000s" or something like that.
- All references must conform to citation templates (Ref #6 is an excellent example) or similar formats.
- Paragraphs do not consist of one or two sentences. All one or two sentence paragraphs must be merged with surrounding paragraphs.
- The "Uses of microformats" section is too small and should either be expanded or merged with "Specific microformats" to create a larger "Forms and uses of microformats" or something similar.
- The "Evaluation of microformats" section needs to be revamped for many reasons, the most pressing being that there are too many sub-sections with too few details. "Accessibility," for example, is only one long sentence!
Also, and this is not mandatory for a GA pass, but the citation templates should be employed horizontally, rather than vertically, to make it easier for editors working on the article. When a reviewer encounters minor problems, the article may be placed on hold for a period of up to seven days. In this case, however, the overall feel I get from this article is that it reads like more of a technical manual than an encyclopedic article, not to mention that it has a large host of problems. While I feel that it might be possible to address these concerns within seven days, I feel that the article and the community would benefit more if some time was taken to shape this article and have it undergo either a Wikiproject specific review, or at least a personal proof read after having taken a week break from the final version that you want to submit for future GAN consideration. For these reasons, I am failing the article for now. If you feel that this review is in error, you make seek a good article reassessment. Thank you for your work thus far. Cheers, CP 03:47, 18 October 2007 (UTC)
"sometimes abbreviated μF or uF"
I thought abbreviations are supposed to be easier to write/type. I don't know about you, but I don't have a μ key on my keyboard. I just searched microformats.org for "μf" and many results from their mailing list came up, but no official page. Anyone know the origins of this abbreviation? --Henry W. Schmitt (talk) 05:02, 18 November 2007 (UTC)
- The prefix micro-, abbreviated μ, is part of the International System of Units, the modern form of the metric system. Both micro- and μ are derived from Greek. When used in its more precise sense, micro- and μ mean a millionith. Alternatively, they can mean small or little as in microformats. I have occasionally used μsoft, to abbreviate the name of that little company in Redmond, WA. John Harvey (talk) 12:03, 19 November 2007 (UTC)
- Yes the redirection of μF should point to Farad with an option there to go to the microformats page (the opposite of the way it is now) - changing this now. That use has been around much longer than microformats and is the most commonly-used multiple of the farad. Obviously whoever came up with the idea of using it for microformats was unaware of the existence let alone importance of this abbreviation in electronics. Yerocus (talk) 18:46, 13 October 2011 (UTC)
This section of the article does not say anything specific enough to be useful (all pages that use microformats are in the public domain?? all microformat specifications?? I suggest rewriting or deleting that part 184.108.40.206 (talk) 20:57, 15 February 2008 (UTC)
The article needs an update
The section in which the article says that Firefox 3 is "going to" partially implement microformats should be updated with current informations. IE8 may need that too.. I'd do it myself, but i'm no expert in the field. Asymmetric (talk) 17:07, 13 March 2009 (UTC)
- Yes, that is true. I'm also not a Wikipedia expert but I think that it does need to be changed. --Matthew Bauer (talk) 19:42, 13 March 2009 (UTC)
Plain old Semantic HTML
If PoSH is going to redirect to Microformats (which I disagree with but is understandable) then there should at least be something discussing it on the page. I'll put in a section stub but I encourage someone who is more knowledgeable to flesh it out. FunnyYetTasty (talk) 16:24, 11 August 2010 (UTC)
Microformats under development
I removed this entire subsection as none of the listed microformats appear to be undergoing active development. They haven't been touched in years. If this is not the case then feel free to put back selected microformats. Here is the sub-section of the article I removed:
Microformats under development
Among the many proposed microformats, the following are undergoing active development:
- hAudio – for audio files and references to released recordings
- citation – for citing references
- currency – for amounts of money
- figure – for associating captions with images
- geo extensions – for places on Mars, the Moon, and other such bodies; for altitude; and for collections of waypoints marking routes or boundaries
- species – for the names of living things (already used by Wikipedia  and the BBC Wildlife Finder)
- measure – for physical quantities, structured data-values
I am familiar with hAudio and measure, and these are definitely moribund. Not so sure about the rest. HairyWombat 16:06, 28 April 2013 (UTC)
- "Exploratory Discussions". Microformats.org. 2008-08-15. Retrieved 2008-09-06.
- figure 0.3 · Microformats Wiki
- Wikipedia:WikiProject Microformats/classes - Wikipedia, the free encyclopedia
- measure · Microformats Wiki