Microdata (HTML5) Microdata is a WHATWG HTML specification used to nest metadata within existing content on web pages.[1] Search engines, web crawlers, and browsers can extract and process Microdata from a web page and use it to provide a richer browsing experience for users. Search engines benefit greatly from direct access to this structured data because it allows search engines to understand the information on web pages and provide more relevant results to users.[2][3] Microdata uses a supporting vocabulary to describe an item and name-value pairs to assign values to its properties.[4] Microdata is an attempt to provide a simpler[citation needed] way of annotating HTML elements with machine-readable tags than the similar approaches of using RDFa and microformats. Microdata vocabularies provide the semantics, or meaning of an Item. The following HTML5 markup may be found on a typical “About” page containing information about a person: Here is the same markup with added Schema.org[5][6][7] Microdata:
Unobtrusive JavaScript Unobtrusive JavaScript is a general approach to the use of JavaScript in web pages. Though the term is not formally defined, its basic principles are generally understood to include: A new paradigm[edit] JavaScript historically has had a reputation for being a clumsy, hackish language unsuitable for serious application development.[3][4] This has been largely due to inconsistent implementations of the language itself and the Document Object Model[5] in various browsers, and the widespread use of buggy copy-and-paste code. Runtime errors were so common (and so difficult to debug) that few programmers even tried to fix them, as long as the script behaved more or less the way it was supposed to;[6] scripts often failed completely in some browsers. Other authors have tried to refine and define the essential elements of the unobtrusive paradigm. The Web Standards Project describes four benefits of unobtrusive DOM scripting in their JavaScript Manifesto. Separation of behavior from markup[edit]
schema.org Most webmasters are familiar with HTML tags on their pages. Usually, HTML tags tell the browser how to display the information included in the tag. For example, <h1>Avatar</h1> tells the browser to display the text string "Avatar" in a heading 1 format. Schema.org provides a collection of shared vocabularies webmasters can use to mark up their pages in ways that can be understood by the major search engines: Google, Microsoft, Yandex and Yahoo! 1. 1a. Your web pages have an underlying meaning that people understand when they read the web pages. 1b. itemscope and itemtype Let's start with a concrete example. <div><h1>Avatar</h1><span>Director: James Cameron (born August 16, 1954)</span><span>Science fiction</span><a href=".. To begin, identify the section of the page that is "about" the movie Avatar. <div itemscope><h1>Avatar</h1><span>Director: James Cameron (born August 16, 1954) </span><span>Science fiction</span><a href=".. Back to top 1c. itemprop 1d. 2. 2b. 2c. 3. 3a. 3b. Enumerations
Semantic HTML Semantic HTML is the use of HTML markup to reinforce the semantics, or meaning, of the information in webpages rather than merely to define its presentation or look. Semantic HTML is processed by regular web browsers as well as by many other user agents. CSS is used to suggest its presentation to human users. As an example, recent HTML standards discourage use of the tag <i> (italic, a typeface)[1] in preference of more accurate tags such as <em> (emphasis); the CSS stylesheet should then specify whether emphasis is denoted by an italic font, a bold font, underlining, slower or louder audible speech etc. History[edit] HTML has included semantic markup since its inception.[4] In an HTML document, the author may, among other things, "start with a title; add headings and paragraphs; add emphasis to [the] text; add images; add links to other pages; [and] use various kinds of lists".[5] At one time, HTML also included presentational markup such as <font>, <i> and <center> tags. See also[edit]
How Schema.org Will Change Your Search Results & What it Means for Marketers Jeff Ente is the director of Who's Blogging What, a weekly e-newsletter that tracks over 1,100 social media, web marketing and user experience blogs to keep readers informed about key developments in their field and highlight useful but hard to find posts. Mashable readers can subscribe for free here. Algorithms aren’t going away anytime soon now that websites have a better way to directly describe their content to major search engines. Earlier this month, Google, Bing and Yahoo came together to announce support for Schema.org, a semantic markup protocol with its own vocabulary that could provide websites with valuable search exposure. Nothing will change overnight, but Schema.org is important enough to bring the three search giants together. Schema.org attempts to close a loophole in the information transfer from website data to presentation as search results. How Schema.org Works Schema.org was born out of conflict between competing standards. Until this month. Feb. 12, 1809.
Progressive enhancement Progressive enhancement is a strategy for web design that emphasizes accessibility, semantic HTML markup, and external stylesheet and scripting technologies. Progressive enhancement uses web technologies in a layered fashion that allows everyone to access the basic content and functionality of a web page, using any browser or Internet connection, while also providing an enhanced version of the page to those with more advanced browser software or greater bandwidth. History[edit] "Progressive Enhancement" was coined by Steven Champeon in a series of articles and presentations for Webmonkey and the SXSW Interactive conference between March and June 2003.[1][2] Introduction and background[edit] The strategy is an evolution of a previous web design strategy known as "graceful degradation", wherein designers would create Web pages for the latest browsers that would also work well in older versions of browser software. Core principles[edit] Support and adoption[edit] Criticism and responses[edit]
Gellish Gellish is a formal language that is natural language independent, although its concepts have 'names' and definitions in various natural languages. Any natural language variant, such as Gellish Formal English is a controlled natural language. Information and knowledge can be expressed in such a way that it is computer-interpretable, as well as system-independent and natural language independent. Each natural language variant is a structured subset of that natural language and is suitable for information modeling and knowledge representation in that particular language. All expressions, concepts and individual things are represented in Gellish by (numeric) Unique Identifiers (Gellish UID's). Etymologically speaking, "Gellish" is originally derived from "Generic Engineering Language." Overview[edit] Gellish is intended for the expression of facts (statements), queries, answers, etc. In principle, for every natural language there is a Gellish variant that is specific for that language. 1.
ROCA: Resource-oriented Client Architecture Exhibit 3.0 Project Getting Involved Join us on IRC on freenode or browse the SIMILE Widgets mailing list archives to ask questions about Exhibit. Chances are others may have similar questions, and the list is a great place to share answers. Background The Exhibit 3 project was supported by the Library of Congress. It is a partnership among MIT Libraries, MIT CSAIL and Zepheira, including personnel from the original SIMILE project. Exhibit 3.0 development work proceeds from the proposed architecture (PDF) released in early 2011. Demos Exhibit 3.0: What's New? Exhibit 3.0 is available for community input. Exhibit 3.0 Scripted (client-side) Exhibit 3.0 Staged Beta 2(client/server): Scalability: Browse hundreds of thousands of records Persistence: Pick up where you left off browsing an Exhibit Export data in HTML + RDFa format Community Involvement Developers in the community are encouraged to contribute code.
GRDDL GRDDL (pronounced 'griddle') is a markup format for Gleaning Resource Descriptions from Dialects of Languages. It is a W3C Recommendation, and enables users to obtain RDF triples out of XML documents, including XHTML. The GRDDL specification shows examples using XSLT, however it was intended to be abstract enough to allow for other implementations as well. How it works[edit] XHTML and transformations[edit] A document specifies associated transformations, using one of a number of ways. For instance, an XHTML document may contain the following markup: Document consumers are informed that there are GRDDL transformations available in this page, by including the following in the profile attribute of the head element: The available transformations are revealed through one or more link elements: This code is valid for XHTML 1.x only. Microformats and profile transformations[edit] If an XHTML page contains Microformats, there is usually a specific profile. and