RDFa

RDFa (or Resource Description Framework in Attributes[1]) is a W3C Recommendation that adds a set of attribute-level extensions to HTML, XHTML and various XML-based document types for embedding rich metadata within Web documents. The RDF data-model mapping enables its use for embedding RDF subject-predicate-object expressions within XHTML documents. It also enables the extraction of RDF model triples by compliant user agents. The RDFa community runs a wiki website to host tools, examples, and tutorials.[2] History[edit] RDFa was first proposed by Mark Birbeck in the form of a W3C note entitled XHTML and RDF,[3] which was then presented to the Semantic Web Interest Group at the W3C's 2004 Technical Plenary.[3] Later that year the work became part of the sixth public Working Draft of XHTML 2.0.[4][5] Although it is generally assumed that RDFa was originally intended only for XHTML 2, in fact the purpose of RDFa was always to provide a way to add a metadata to any XML-based language. <? <?

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. It became a Recommendation on September 11, 2007.[1] 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] and XML and transformations[edit]

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. Advocates of unobtrusive JavaScript see it as part of the larger Web standards movement; much as the demand for cross-browser compatibility has driven the increasing emphasis on standardized markup and style, the increasing demand for rich Internet applications is driving the movement toward better practices with the use of JavaScript. Other authors have tried to refine and define the essential elements of the unobtrusive paradigm. Namespaces[edit] var org;if (!

Microformat A microformat (sometimes abbreviated μF) is a web-based approach to semantic markup which seeks to re-use existing HTML/XHTML tags to convey metadata[1] and other attributes in web pages and other contexts that support (X)HTML such as RSS. This approach allows software to process information intended for end-users (such as contact information, geographic coordinates, calendar events, and similar information) automatically. Although the content of web pages is technically already capable of "automated processing", and has been since the inception of the web, such processing is difficult because the traditional markup tags used to display information on the web do not describe what the information means.[2] Microformats can bridge this gap by attaching semantics, and thereby obviate other, more complicated, methods of automated processing, such as natural language processing or screen scraping. Background[edit] Neither CommerceNet nor Microformats.org operates as a standards body. class rel

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]

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]

ROCA: Resource-oriented Client Architecture