Microformat

Uses your system voice; voice and rate in settings.

Snapshot

≈ 5 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

Microformats (μF) are predefined HTML markup (like HTML classes) created to serve as descriptive and consistent metadata about elements, designating them as representing a certain type of data (such as contact information, geographic coordinates, events, products, recipes, etc.). They allow software to process the information reliably by having set classes refer to a specific type of data rather than being arbitrary. Microformats emerged around 2005 and were predominantly designed for use by search engines, web syndication and aggregators such as RSS. Google confirmed in 2020 that it still parses microformats for use in content indexing. Microformats are referenced in several W3C social web specifications, including IndieAuth and Webmention. Although the content of web pages has been capable of some "automated processing" since the inception of the web, such processing is difficult because the markup elements used to display information on the web do not describe what the information means. Microformats can bridge this gap by attaching semantics, and thereby obviating other, more complicated, methods of automated processing, such as natural language processing or screen scraping. The use, adoption and processing of microformats enables data items to be indexed, searched for, saved or cross-referenced, so that information can be reused or combined.…

Microformats (μF) are predefined HTML markup (like HTML classes) created to serve as descriptive and consistent metadata about elements, designating them as representing a certain type of data (such as contact information, geographic coordinates, events, products, recipes, etc.). They allow software to process the information reliably by having set classes refer to a specific type of data rather than being arbitrary. Microformats emerged around 2005 and were predominantly designed for use by search engines, web syndication and aggregators such as RSS. Google confirmed in 2020 that it still parses microformats for use in content indexing. Microformats are referenced in several W3C social web specifications, including IndieAuth and Webmention. Although the content of web pages has been capable of some "automated processing" since the inception of the web, such processing is difficult because the markup elements used to display information on the web do not describe what the information means. Microformats can bridge this gap by attaching semantics, and thereby obviating other, more complicated, methods of automated processing, such as natural language processing or screen scraping. The use, adoption and processing of microformats enables data items to be indexed, searched for, saved or cross-referenced, so that information can be reused or combined. , microformats allow the encoding and extraction of event details, contact information, social relationships and similar information. , microformats continue to be supported by modern web browsers and search engines as part of structured data processing on web pages. However, their usage has declined in favor of more recent standards such as JSON-LD and Schema.org, which provide greater flexibility for expressing structured information. Despite this, microformats remain in use in legacy systems and are still recognized by parsers for extracting semantic information from HTML content. They continue to be referenced in various web specifications and contribute to machine-readable data extraction in HTML documents. Microformats2, abbreviated as mf2, is the updated version of microformats. Mf2 provides an easier way of interpreting HTML structured syntax and vocabularies than the earlier ways that made use of RDFa and microdata. Neither CommerceNet nor Microformats.org operates as a standards body. The microformats community functions through an open wiki, a mailing list, and an Internet relay chat (IRC) channel. Most of the existing microformats originated at the Microformats.org wiki and the 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. relationship, description of the target address in an anchor-element ( ... ) rev reverse relationship, description of the referenced document (in one case, otherwise deprecated in microformats ) 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. With wrapping in spans (or other HTML elements) with specific class names (in this case geo , latitude and longitude , all part of the geo microformat specification): The birds roosted at 52.48 , -1.89 Software agents can recognize exactly what each value represents and can then perform a variety of tasks such as indexing, locating it on a map and exporting it to a GPS device. Joe Doe The Example Company 604-555-1234 http://example.com/ With hCard microformat markup, that becomes: Joe Doe The Example Company 604-555-1234 http://example.com/ Here, the formatted name ( fn ), organisation ( org ), telephone number ( tel ) and web address ( url ) have been identified using specific class names and the whole thing is wrapped in class="vcard" , which indicates that the other classes form an hCard (short for "HTML vCard") and are not merely coincidentally named. Other, optional, hCard classes also exist. Software, such as browser plug-ins, can now extract the information, and transfer it to other applications, such as an address book. The birds roosted at 52.48 , -1.89 and: Joe Doe The Example Company 604-555-1234 http://example.com/

Text derived from https://en.wikipedia.org/w/index.php?oldid=1360192170 under CC BY-SA 4.0; modifications have been made.