latest web and standards
- Web2.0
-
Web 2.0 is the term given to describe a second generation of the World Wide Web that is focused on the ability for people to collaborate and share information online. Web 2.0 basically refers to the transition from static HTML Web pages to a more dynamic Web that is more organized and is based on serving Web applications to users. Other improved functionality of Web 2.0 includes open communication with an emphasis on Web-based communities of users, and more open sharing of information. Over time Web 2.0 has been used more as a marketing term than a computer-science-based term. Blogs, wikis, and Web services are all seen as components of Web 2.0.
Web 2.0 was previously used as a synonym for Semantic Web, but while the two are similar, they do not share precisely the same meaning. [2]
- Semantic Web
-
An extension of the current Web that provides an easier way to find, share, reuse and combine information more easily. It is based on machine-readable information and builds on XML technology's capability to define customized tagging schemes and RDF's (Resource Description Framework) flexible approach to representing data. The Semantic Web provides common formats for interchange of data (where on the Web there is only had interchange of documents). It also provides a common language for recording how the data relates to real world objects, allowing a person, or a machine, to start off in one database, and then move through an unending set of databases which are connected not by wires but by being about the same thing. [2]
- Semantic Markup
-
Semantic markup involves using elements that are appropriate to content meaning rather than its presentation.
Semantic markup involves using elements that are appropriate to content meaning rather than its presentation. As assignment of appropriate element types also structures a document, for example headings break a document into sections, semantic markup is also (simultaneously) described as structural markup.
The distinction between semantic and structural markup open to interpretation. If, by assigning an element type, the author is seeking to create meaningfor example their desire is that a level-one heading should be understood by the reader as having a different meaning than the same content described as a level-two headingthen the markup may be considered semantic.
Another reason for casting HTML markup as structural may be due to its limited value as a semantic language. For example, a heading element is somewhat of a relative distinction, it is more 'significant' than body copy, but does it signify the beginning of a chapter, the title of an article or a blog entry? The markup is unable to communicate such distinctions. By contrast, languages such as XML enable the author to more clearly describe content at a meta-level.
The benefits of semantic markup
Semantic markup in Word: A non-web example of the benefits of a semantic approach to content markup can be found when using Microsoft Word. If headings are used consistently throughout a document, a table of contents can be generated auto-magically. If text has only been styled to look like a heading, then the program cannot distinguish headings from body copy and the resulting table of contents is likely to be meaningless.
Semantic markup also enables content to be shared more readily. Computer programs (for example, search engine indexing programs) are able to more accurately interpret content when semantic markup is used:
- content types are explicit, for example, an image, tabled data and a list are understood be intrinsically different content types
- content hierarchies may be explicit, for example, text marked-up level-one heading element can be assumed to be of greater significance than text marked-up as a level-two heading element (on the same webpage)
- content relationships may be more apparent, for example, parent-child relationships may be assumed in the decision to structure a document using heading elements; the level-one heading one is the main topic, level-two heading a sub-topic, and so on
Semantic markup can be used by assistive technologies, such as text-to-speech browsers, for example:
- Heading elements can be used to quickly navigate within webpage content (emulating the process of scanning available to sighted users)
- Attributes can be added to aid pronunciation of words and phrases taken from languages other than that set as the document's 'native' language
- W3C - World Wide Web Consortium
-
The World Wide Web Consortium is a non-profit organization founded by Tim Berners-Lee which is responsible for setting the standards for common web creation and access methods. Major documents include the specifications for the HTML and XHTML languages and the Web Content Accessibility Guidelines. [4]
Short for World Wide Web Consortium, an international consortium of companies involved with the Internet and the Web. The W3C was founded in 1994 by Tim Berners-Lee, the original architect of the World Wide Web. The organization's purpose is to develop open standards so that the Web evolves in a single direction rather than being splintered among competing factions. [2]
- Accessibility, Web Accessibility
-
Web accessibility is about enabling equal access to online content and services for all people, including those with visual and mobility impairment.
In practice, authoring an accessible website includes:
- Structuring content using code that indicates information types and hierarchies (semantic markup); semantic markup enables a screen reader to emulate the process of scanning a webpage (using headings and link text) and read webpage content aloud
- Marking-up content with 'hooks' that enable content to be effectively accessed with assistive technologies (such as screen readers)
- Creating an interface that is device-neutral, for example supports keyboard alternatives to mouse-based interaction
Code validation and accessibility
Valid code alone does not ensure that web content is accessible....
Web accessibility initiatives often include a validation process; checking the code of a webpage against a formal technical or applied standard, often using an automated service (validator).
One of the limitations of automated validation is a literal (non-contextual) interpretation of a standard. A validator can only be used to check the accuracy of markup and not whether or not the markup is appropriate.
For example, to increase the size of text an author could use a heading element:
This text will be larger
As the markup is 'correct' in terms of structure and syntax, it will both make the enclosed text larger and pass an automated validation test. However using semantic markup to create a visual effect is an inappropriate application of the standard.
Based on the use of the heading element (<h4>), the text 'This text will be larger' is accorded a greater relative importance than the surrounding text. This 'relative importance' may then be reinterpreted, for example factored into search ranking for the webpage; or repurposed, for example used by a screen reader to quickly 'scan' content.
The key benefit of validation is in avoiding markup errors that may have an adverse affect on accessibility.
For example, failing to close an element may affect both the visual presentation and the semantic meaning of content. At its most extreme, poorly formed markup (or 'tag soup'), can result in an unusable webpage.
Valid code alone does not ensure that web content is accessible - however content may be made more accessible through considered adherence to relevant technical and applied standards. [3]
- Usability
-
Usability is a measure of the quality of a person's experience in interacting with content or services.
Initially a discipline focused on computer software development, usability also relates to website design and is evaluated in terms of:
- Ease of learning
How fast can a user who has never seen the user interface before learn it sufficiently well to accomplish basic tasks? - Efficiency of use
Once an experienced user has learned to use the system, how fast can he or she accomplish tasks? - Memorability
If a user has used the system before, can he or she remember enough to use it effectively the next time or does the user have to start over again learning everything? - Error frequency and severity
How often do users make errors while using the system, how serious are these errors, and how do users recover from these errors? - Subjective satisfaction
How much does the user like using the system?
Website usability
In the context of website design, the quality of the user experience is typically discussed in terms of:
- Look-and-feel
- Navigation
- Interface design
- Information architecture
- Ease of learning
- RSS
-
RSS is the acronym used to describe the de facto standard for the syndication of Web content. RSS is an XML-based format and while it can be used in different ways for content distribution, its most widespread usage is in distributing news headlines on the Web. A Web site that wants to allow other sites to publish some of its content creates an RSS document and registers the document with an RSS publisher. A user that can read RSS-distributed content can use the content on a different site. Syndicated content can include data such as news feeds, events listings, news stories, headlines, project updates, excerpts from discussion forums or even corporate information.
Because there are different versions of RSS, the term RSS is most frequently used as a name to mean the syndication of Web content, rather than as an acronym for its founding technology. When using the name RSS the speaker may be referring to any of the following versions of Web content syndication:
- RDF Site Summary (RSS 0.9, RSS 1.0)
- Rich Site Summary (RSS 0.91, RSS 1.0)
- Really Simple Syndication (RSS 2.0)
When using the term RSS, most will use it in reference to Rich Site Summary or the previous version called RDF Site Summary. When referring to Really Simple Syndication, it will usually be called RSS 2.0, not RSS. There are several versions of RSS available, with the most commonly implemented version being RSS 0.91. The most current version, however, is RSS 2.0 and it is backward-compatible with RSS 0.91. RSS was originally developed by Netscape. The RSS 2.0 specification was authored by Dave Winer. [2]
- Feed Aggregator
-
In Internet technology it is software or a hosted application that collects feeds from various sources and displays it in a single consolidated view, either in a window on your desktop or in a Web browser. Also called feed aggregator or RSS aggregator. [2]
- Feed
-
A Web document that is a shortened version of a Web page that has been created for syndication. Feeds usually end in .xml or .rss. [2]
- Blog - Web log
-
Short for Web log, a blog is a Web page that serves as a publicly accessible personal journal for an individual. Typically updated daily, blogs often reflect the personality of the author.
Blogger is the author of a Web log OR a person who blogs. [2]
Blog, a contraction of 'web' and 'log', describes a website comprising of date-related entries (or posts).
Blogs are typically of a personal nature, although their use by companies as a marketing tool is increasing. [3]
- B-Blog
-
Short for business blog, a blog used by a business to promote itself. [2]
- Tagging
-
Commonly used in blogs, site authors attach keyword descriptions (called tags) to identify images or text within their site as a categories or topic. Web pages and blogs with identical tags can then be linked together allowing users to search for similar or related content. If the tags are made public, online pages that act as a Web-based bookmark service are able to index them. tags can be created using words, acronyms or numbers. Tags are also called tagging, blog tagging, folksonomies (short for folks and taxonomy), or social bookmarking.
OR The act of placing RFID labels bar codes on items is called tagging. [2]
- Podcasting
-
Podcasting is similar in nature to RSS, which allows subscribers to subscribe to a set of feeds to view syndicated Web site content. With podcasting however, you have a set of subscriptions that are checked regularly for updates and instead of reading the feeds on your computer screen, you listen to the new content on on your iPod (or like device).
The format used for podcasting is RSS 2.0 with enclosures. The podcasting enclosures refer to all binary (non-text) downloads. You can read the text description of the enclosure before downloading the item to view. [2]
- Webcast
-
To use the Internet to broadcast live or delayed audio and/or video transmissions, much like traditional television and radio broadcasts. For example, a university may offer on-line courses in which the instructor Webcasts a pre-recorded or live lecture, or an enterprise may Webcast a press conference in lieu of or in addition to a conference call. Users typically must have the appropriate multimedia application in order to view a Webcast.
OR To use push technology, to send Web-based information to an Internet user.
OR The data transmission that results from one of the above methods.
Netcast is another name for Webcast. [2]
- AJAX, Ajax - Asynchronous Javascript and XML
-
Short for Asynchronous JavaScript and XML, it is a term that describes a new approach to using a number of existing technologies together, including the following: HTML or XHTML, Cascading Style Sheets, JavaScript, the Document Object Model, XML, XSLT, and the XMLHttpRequest object. When these technologies are combined in the Ajax model, Web applications are able to make quick, incremental updates to the user interface without reloading the entire browser page. [Source: mozilla developer center] [2]
AJAX is a method to utilize the abilities of Javascript, the Document Object Model, and XML to create interactivity on the web. [4]
Ajax is a web development technique used for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user requests a change. This is intended to increase the web page's interactivity, speed, functionality, and usability.
Ajax is asynchronous in that loading does not interfere with normal page loading. JavaScript is the programming language that Ajax function calls are made in. Data retrieved using the technique is commonly formatted using XML, as reflected in the naming of the XMLHTTPRequest object from which Ajax is derived.
Ajax is a cross-platform technology usable on many different operating systems, computer architectures, and Web browsers as it is based on open standards such as JavaScript and XML, together with open source implementations of other required technologies. [5]
- Validation
-
Validation is the process of checking data against a standard or requirement.
The term is commonly used when:
- Quality assuring a webpage at a technical level (code validation), or
- Checking the information entered by a person when sending information or using an online service (form validation).
Code validation
Webpage validation involves checking the code used to create a webpage (markup), against a computer-language specification.A language specification sets out the parts of the language, and how the language can be used to write instructions that can be understood (processed or parsed) by a computer.
Languages commonly used to write (author) webpages include:
- Hypertext Markup Language (HTML)
- Extensible Hypertext Markup Language (XHTML)
- Extensible Markup Language (XML)
- Cascading Style Sheets (CSS)
Validation and accessibility:
Specification-based validation is comparable to a grammar-check. Although words (elements) may be spelt correctly (use the correct tags) and be drawn from the same language, without appropriate grammar (structure) they can be meaningless.For content to be accessible, the author must markup content into elements that convey the meaning of the content (semantic-markup).
Semantic markup can be used as a 'hook' by assistive technologies that enable users with disabilities to access web content, for example:
- using a screen reader, the H key can be used to move between headings to quickly scan the content of a webpage
- markup that is well-formed is more likely to be correctly interpreted by a screen reader
Valid markup does not necessarily make for accessible web content. [3]
References: [1]www.designtalkboard.com [2]www.webopedia.com [3]www.motive.co.nz [4]www.joedolson.com [5]www.wikipedia.org [6]www.beseenwebdesign.com [7]www.launchmark.com [8]www.101webbuilders.com [9]www.answers.com [10]www.usabilityfirst.com [11]www.designer-info.com
Content(s) on this page is provided for informational purposes only, and is copyrighted by and belong to the respected owner(s) as referenced. If you own the rights to any of the content(s) and wish they be removed, please contact us and we will remove them immediately or at your choice, provide a credit and a link.




