Wednesday, December 26, 2012

Best Practices for Search Engine Optimization


The visible text content of your pages is a primary factor that search engines utilize to find, index and deliver your pages to prospective site visitors. …try to integrate search terms into your page copy in a natural fashion so that the terms make sense in context and complement the overall message of the page content.

Effective search engine optimization is not about “tricking” the search engines into ranking your site favorably. Rather, SEO is a research process designed to eliver relevant information to the people seeking that information.

If your organization’s mission has to do with environmental protection, are your target visitors most likely to search for “acid rain”, “save the “greenhouse effect”, or all of the above? Do you want to reach visitors who are local, regional or national in scope? These are considerations that need careful attention as you begin the SEO process.

Flash animation and video may look cool to site visitors, but search engines cannot read or index the content embedded within multimedia objects.That is not to say that you shouldn’t use multimedia where appropriate, but be aware that it is not search engine-friendly. ( SEO - Right video at the right time is priceless )

SEO - Tips for your Website Effectiveness

Tuesday, December 25, 2012

SEO title tag mistakes

  • The title tag shows up in search results as the blue link, and a good one helps the site get more clicks and visitors from search results.
  • Title tags are a crucial SEO element that can help the website show up higher when people search Google for the words in it.
  • Title tags show up when web pages are shared on social media sites like Facebook. 
 

Avoid these and you'll be ahead of the game, ranking higher in search results and enticing more people to click on your site. 

1."Home" or "Home Page" in title tag  
2.Domain name in title tag
3.Too long  
4.Too short
5.No keywords
6.Just the business name  
7.First few words aren't important or eye-catching  
8.Doesn't include geographic location (if location is important to business)
9.Too many keywords that make it look spammy

Monday, December 17, 2012

Guidance on Applying WCAG 2.0 to Non-Web ICT: Updated Draft Published


13 December 2012
The Web Content Accessibility Guidelines Working Group (WCAG WG)  published an updated Working Draft of Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT). It is a draft of an informative (that is, not normative) W3C Working Group Note that will clarify how Web Content Accessibility Guidelines (WCAG) 2.0 can be applied to non-Web ICT. Please see important information in the Call for Review e-mail. Comments are welcome through 15 February 2013. Read about the Web Accessibility Initiative (WAI).

WOFF File Format 1.0 is a W3C Recommendation


13 December 2012
The WebFonts Working Group has published a W3C Recommendation of WOFF File Format 1.0. This document specifies the WOFF font packaging format. This format was designed to provide lightweight, easy-to-implement compression of font data, suitable for use with CSS @font-face rules. Any properly licensed TrueType/OpenType/Open Font Format file can be packaged in WOFF format for Web use. User agents decode the WOFF file to restore the font data such that it will display identically to the input font. Learn more about the Fonts Activity.

Role Attribute Proposed Recommendation Published


13 December 2012
The Protocols and Formats Working Group (PFWG) published a Proposed Recommendation of Role Attribute, an XML attribute that allows authors to add semantic information to documents. Role Attribute supports WAI-ARIA, the Accessible Rich Internet Applications technical specification for making dynamic, interactive web content accessible to people with disabilities. Comments are welcome through 1 February 2013. Read the Role Attribute Proposed Recommendation e-mail announcement for more information, and about the Web Accessibility Initiative (WAI).

Thursday, December 6, 2012

Last Call: Proximity Events

06 December 2012
The Device APIs Working Group has published a Last Call Working Draft of Proximity Events. This specification defines a means to receive events that correspond to a proximity sensor detecting the presence of a physical object. Comments are welcome through 24 January. Learn more about the Ubiquitous Web Applications Activity.

Last Call: State Chart XML (SCXML): State Machine Notation for Control Abstraction

06 December 2012
The Voice Browser Working Group published a Las Call Working Draft of State Chart XML (SCXML): State Machine Notation for Control Abstraction. This document describes SCXML, or the "State Chart extensible Markup Language". SCXML provides a generic state-machine based execution environment based on CCXML and Harel State Tables. Comments are welcome through 11 January 2013. Learn more about the Voice Browser Activity.

Last Call: Internationalization Tag Set (ITS) Version 2.0

06 December 2012
The MultilingualWeb-LT Working Group published a Last Call Working Draft of Internationalization Tag Set (ITS) Version 2.0. This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS) 2.0. ITS 2.0 is the successor of ITS 1.0; it is designed to foster the creation of multilingual Web content, focusing on HTML, XML based formats in general, and to leverage localization workflows based on the XML Localization Interchange File Format (XLIFF). Comments are welcome through 10 January 2013. Learn more about the Internationalization Activity.

Updated Working Drafts of The Screen Orientation API, XMLHttpRequest, DOM4

06 December 2012
The Web Applications Working Group published three Working Drafts :
  • The Screen Orientation API. The Screen Orientation API's goal is to provide an interface for web applications to be able to read the screen orientation state, to be informed when this state changes and to be able to lock the screen orientation to a specific state.
  • XMLHttpRequest. The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server.
  • DOM4, published in co-operation with the Web Hypertext Application Technology Working Group. DOM defines the event and document model the Web platform uses. The DOM is a language- and platform neutral interface that allows programs and scripts to dynamically access and update the content and structure of documents.
Learn more about the Rich Web Client Activity.

Wednesday, November 28, 2012

Registration Opens for W3Conf 2013, W3C's Developer Conference

28 November 2012
W3Conf W3C announces today W3Conf: Practical Standards for Web Professionals, W3C's second annual developer conference, in San Francisco on 21-22 February 2013. Presentations will focus on practical, cutting-edge standards that developers and designers can use across browsers today, and give a glimpse into what's coming. The conference will feature leading experts in the Web industry on HTML5, CSS, graphics, mobiles, accessibility, multimedia, APIs, and more. Space is limited, so register now.

Packaged Web Apps (Widgets) - Packaging and XML Configuration (Second Edition) is a W3C Recommendation

27 November 2012
The Web Applications Working Group has published a W3C Recommendation of Packaged Web Apps (Widgets) - Packaging and XML Configuration (Second Edition). This specification standardizes a packaging format and metadata for a class of software known commonly as packaged apps or widgets. Unlike traditional user interface widgets (e.g., buttons, input boxes, toolbars, etc.), widgets as specified in this document are full-fledged client-side applications that are authored using technologies such as HTML and then packaged for distribution. Examples range from simple clocks, stock tickers, news casters, games and weather forecasters, to complex applications that pull data from multiple sources to be "mashed-up" and presented to a user in some interesting and useful way. Learn more about the Rich Web Client Activity.

Thursday, November 22, 2012

Online Symposium: Easy-to-Read on the Web

21 November 2012

Registration is now open for the online symposium on Easy-to-Read on the Web to be held on 3 December 2012. Researchers, practitioners, content authors, designers, developers, users with disabilities, and others are invited to participate. The symposium will address how to make information on the Web easier to understand, particularly by people with cognitive disabilities and people with low language skills. The symposium will explore user needs and the state of the art in research, development, and practice to contribute to a common understanding of easy-to-read on the Web. For details and registration, see Easy-to-Read on the Web - Online Symposium. Learn more about the Web Accessibility Initiative (WAI).

User Interface Safety Directives for Content Security Policy Draft Published

The Web Application Security Working Group has published the First Public Working Draft of User Interface Safety Directives for Content Security Policy. This document defines directives for the Content Security Policy mechanism to declare a set of input protections for a web resource's user interface, defines a non-normative set of heuristics for Web user agents to implement these input protections, and a reporting mechanism for when they are triggered. Learn more about the Security Activity.

Tuesday, November 6, 2012

W3C Community Convenes in France for TPAC 2012

29 October 2012

TPAC 2012    The W3C community meets in Lyon, France for TPAC 2012 W3C's annual face-to-face Membership meeting. Participants will coordinate technical directions for the Open Web Platform, explore its impact across industries and devices, and discuss organizational strategy. More than 450 people will participate in Working Group meetings, an Advisory Committee meeting, and a Plenary Day for breakout discussions on a a variety of topics. Although participation in TPAC is limited to those already in W3C groups, the TPAC proceedings are public and will be made available shortly after the meeting. Follow the meeting on social networking sites with tag #tpac. W3C also welcomes local developers today to a Meetup at the Lyon City Hall.

Last Call: Publishing and Linking on the Web

25 October 2012

The Technical Architecture Group has published a Last Call Working Draft of Publishing and Linking on the Web. Publishing a page on the Web is fundamentally different from printing and distributing a page in a magazine or book. This document is intended to inform future social and legal discussions of the Web by clarifying the ways in which the Web's technical facilities operate to store, publish and retrieve information, and by providing definitions for terminology as used within the Web's technical community. This document also describes the technical and operational impact that does or could result from legal constraints on publishing, linking and transformation on the Web. Comments are welcome through 13 December. Learn more about the Technical Architecture Group.

Monday, October 22, 2012

The OWL Working Group has published twelve Proposed Edited Recommendations

18 October 2012

The OWL 2 Web Ontology Language, informally OWL 2, is an ontology language for the Semantic Web with formally defined meaning. OWL 2 ontologies provide classes, properties, individuals, and data values and are stored as Semantic Web documents. OWL 2 ontologies can be used along with information written in RDF, and OWL 2 ontologies themselves are primarily exchanged as RDF documents. Comments on the Proposed Edited Recommendations are welcome through 15 November.

  • OWL 2 Web Ontology Language Document Overview. This document serves as an introduction to OWL 2 and the various other OWL 2 documents. It describes the syntaxes for OWL 2, the different kinds of semantics, the available profiles (sub-languages), and the relationship between OWL 1 and OWL 2.
  • OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax. The meaningful constructs provided by OWL 2 are defined in terms of their structure. As well, a functional-style syntax is defined for these constructs, with examples and informal descriptions. One can reason with OWL 2 ontologies under either the RDF-Based Semantics or the Direct Semantics. If certain restrictions on OWL 2 ontologies are satisfied and the ontology is in OWL 2 DL, reasoning under the Direct Semantics can be implemented using techniques well known in the literature.
  • OWL 2 Web Ontology Language Mapping to RDF Graphs.This document defines the mapping of OWL 2 ontologies into RDF graphs, and vice versa.
  • OWL 2 Web Ontology Language Direct Semantics. This document provides the direct model-theoretic semantics for OWL 2, which is compatible with the description logic SROIQ. Furthermore, this document defines the most common inference problems for OWL 2.
  • OWL 2 Web Ontology Language RDF-Based Semantics. This document defines the RDF-compatible model-theoretic semantics of OWL 2.
  • OWL 2 Web Ontology Language Conformance. This document describes the conditions that OWL 2 tools must satisfy in order to be conformant with the language specification. It also presents a common format for OWL 2 test cases that both illustrate the features of the language and can be used for testing conformance.
  • OWL 2 Web Ontology Language Profiles. This document provides a specification of several profiles of OWL 2 which can be more simply and/or efficiently implemented. In logic, profiles are often called fragments. Most profiles are defined by placing restrictions on the structure of OWL 2 ontologies. These restrictions have been specified by modifying the productions of the functional-style syntax.
  • OWL 2 Web Ontology Language New Features and Rationale.This document is a simple introduction to the new features of the OWL 2 Web Ontology Language, including an explanation of the differences between the initial version of OWL and OWL 2. The document also presents the requirements that have motivated the design of the main new features, and their rationale from a theoretical and implementation perspective.
  • OWL 2 Web Ontology Language Quick Reference Guide. This document provides a non-normative quick reference guide to the OWL 2 language. It also provides links to other documents, including the OWL 2 Primer for language introduction and examples, the OWL 2 Structural Specification and Functional Syntax document for more details of the functional syntax, and the OWL 2 New Features and Rationale document for new feature descriptions.
  • OWL 2 Web Ontology Language XML Serialization. This document specifies an XML serialization for OWL 2 that mirrors its structural specification. An XML schema defines this syntax and is available as a separate document, as well as being included here.
  • rdf:PlainLiteral: A Datatype for RDF Plain Literals. This document presents the specification of a primitive datatype for the plain literals of RDF.
  • OWL 2 Web Ontology Language Primer. This primer provides an approachable introduction to OWL 2, including orientation for those coming from other disciplines, a running example showing how OWL 2 can be used to represent first simple information and then more complex information, how OWL 2 manages ontologies, and finally the distinctions between the various sublanguages of OWL 2.
  • OWL 2 Web Ontology Language Manchester Syntax. This Working Group Note of The Manchester syntax is a user-friendly compact syntax for OWL 2 ontologies; it is frame-based, as opposed to the axiom-based other syntaxes for OWL 2. The Manchester Syntax is used in the OWL 2 Primer, and this document provides the language used there. It is expected that tools will extend the Manchester Syntax for their own purposes, and tool builders may collaboratively extend the common language.
  • OWL 2 Web Ontology Language Data Range Extension: Linear Equations. This Working Group Note specifies a syntax and semantics for incorporating linear equations with rational coefficients solved in the reals in OWL 2.

Learn more about the Semantic Web Activity.

Push API Draft Published

18 October 2012

The Web Applications Working Group has published the First Public Working Draft of Push API. This specification defines a “Push API” that provides webapps with scripted access to server-sent application data, for simplicity referred to here as "Push messages" as delivered by "Push services". Push services are a way for application servers to send messages to webapps, whether or not the webapp is active in a browser window. The specific method to be used by a webapp is either selected by the user through selecting a Web Intent Push Service provider, or by the browser. The Push API is defined to promote compatibility with any underlying delivery method. Learn more about the Rich Web Client Activity.

Friday, October 5, 2012

User Agent Accessibility Guidelines (UAAG) 2.0 Drafts Published

04 October 2012

The User Agent Accessibility Guidelines Working Group (UAWG) today published updated Working Drafts of User Agent Accessibility Guidelines (UAAG) 2.0 and Implementing UAAG 2.0. UAAG defines how browsers, media players, and other "user agents" should support accessibility for people with disabilities and work with assistive technologies. UAAG 2.0 is updated to better address mobile devices and input by speech, touch, and gesture. See the call for review e-mail for a summary of changes. Comments are welcome through 9 November 2012. Learn more about the Web Accessibility Initiative (WAI).

Web Audio Processing: Use Cases and Requirements Draft Published

The Audio Working Group has published the First Public Working Draft of Web Audio Processing: Use Cases and Requirements. This document introduces a series of scenarios and a list of requirements guiding the work of the W3C Audio Working Group in its development of a web API for processing and synthesis of audio on the web. Learn more about the Rich Web Client Activity.

Web Intents Addendum - Local Services Draft Published

04 October 2012

The Device APIs Working Group and Web Applications (WebApps) Working Group have jointly published a Working Draft of Web Intents Addendum - Local Services. This specification is an addendum to Web Intents, that defines how Web Intents enabled User Agents can discover and communicate with local Web Intents Services. Learn more about the Ubiquitous Web Applications Activity, and the Rich Web Client Activity.

Network Service Discovery Draft Published

04 October 2012

The Device APIs Working Group has published a Working Draft of Network Service Discovery. This specification defines a mechanism for an HTML document to discover and subsequently communicate with HTTP-based services advertised via common discovery protocols within the current network. Learn more about the Ubiquitous Web Applications Activity.

Tuesday, October 2, 2012

About Google PageRank

PageRank is an analysis and ranking algorithm created by Larry Page and used in part by Google to assess the relative importance of websites. The algorithm assigns a numeric weighting from 0-10 (where 10 is the highest ranking) for each webpage on the Internet; thus PageRank denotes a site’s importance in the eyes of Google.

The PageRank is derived from a theoretical probability value on a logarithmic scale like the Richter Scale. The PageRank of a particular page is roughly based upon the quantity of inbound links as well as the PageRank of the pages providing the links. It is known that other factors, e.g. relevance of search words on the page and actual visits to the page reported by the Google toolbar also influence the PageRank. See, http://en.wikipedia.org/wiki/PageRank

W3C Workshop: Making the Multilingual Web work

02 October 2012

W3C announced  the sixth MultilingualWeb workshop in a series of events exploring the mechanisms and processes needed to ensure that the World Wide Web lives up to its potential around the world and across barriers of language and culture. To be held 12–13 March 2013 in Rome, this workshop is made possible by the generous support of the Food and Agriculture Organisation of the United Nations. Anyone may attend at no charge and the W3C welcomes participation by both speakers and non-speaking attendees. Early registration is encouraged due to limited space.

Building on the success of five highly regarded previous workshops in Madrid, Pisa, Limerick, Luxembourg, and Dublin, this workshop will emphasize the application of theory and technology to meet practical needs. The workshop brings together participants interested in the best practices and standards needed to help content creators, localizers, language tools developers, and others meet the challenges of the multilingual Web. It provides further opportunities for networking across communities that span the various aspects involved. We are particularly interested in speakers who can demonstrate novel solutions for reaching out to a global, multilingual audience. Registration is available online.

Two Drafts Published by the Tracking Protection Working Group

02 October 2012

The Tracking Protection Working Group has published two Working Drafts today.

  • Tracking Preference Expression (DNT).This specification defines the technical mechanisms for expressing a tracking preference via the DNT request header field in HTTP, via an HTML DOM property readable by embedded scripts, and via properties accessible to various user agent plug-in or extension APIs. It also defines mechanisms for sites to signal whether and how they honor this preference, both in the form of a machine-readable tracking status resource at a well-known location and via a Tk response header field, and a mechanism for allowing the user to approve site-specific exceptions to DNT as desired.
  • Tracking Compliance and Scope. This specification defines the meaning of a Do Not Track (DNT) preference and sets out practices for websites to comply with this preference.

Learn more about the Privacy Activity.

Web API Design Cookbook Note Published

02 October 2012

The Device APIs Working Group has published a Group Note of Web API Design Cookbook. This document captures common practices in designing APIs that fit well into the Web platform as a whole, using WebIDL. Learn more about the Ubiquitous Web Applications Activity.

W3C launches System Applications Working Group

02 October 2012

W3C announced today the launch of the System Applications Working Group, whose mission is to define a runtime environment, security model, and associated APIs for building Web applications with comparable capabilities to native applications. See the System Applications Working Group Charter for more information, and read more about the Ubiquitous Web Domain.

W3C Workshop: Web Performance

28 September 2012

W3C announced a Workshop on Web Performance, 8 November, hosted by Google at their Mountain View, California campus. As the Open Web Platform expands, the need for high performance implementation has grown, particularly on mobile devices. Participants will examine a broad range of performance issues and how they might be addressed. There is no fee to participate in this Workshop and W3C Membership is not required. All participants are required to submit a statement of interest by 29 October. Learn more about W3C's Web Performance Working Group, which also invites people to share performance issues via their survey on Open Web Platform Performance Priorities.

Sunday, September 30, 2012

CSS Intrinsic & Extrinsic Sizing Module Level 3 Draft Published

27 September 2012
The Cascading Style Sheets (CSS) Working Group has published the First Public Working Draft of CSS Intrinsic & Extrinsic Sizing Module Level 3. @@This module extends the CSS sizing properties with keywords that represent content-based "intrinsic" sizes and context-based "extrinsic" sizes, allowing CSS to more easily describe boxes that fit their content or fit into a particular layout context. CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. Learn more about the Style Activity.

W3C Renews Audio Working Group

26 September 2012
W3C announced today the renewal of the Audio Working Group, whose mission is to add advanced sound and music capabilities to the Open Web Platform. The new charter adds a new deliverable, the Web MIDI API, which will provide a bridge between the browser and MIDI capable devices, such as musical instruments and controllers, and has great interest from the MIDI Manufacturers Association. The charter also clarifies the Web Audio API deliverable and timeline. See the Audio Working Group Charter for more information, and read more about the Interaction Domain.

Saturday, September 29, 2012

Effective way to promote products and services

Effective way to promote products and services

For many businesses and institutions, having a Facebook page is an effective way to promote their products and services, and can significantly expand their network. Getting tons of fans on Facebook is easy, if you just follow some of these simple ideas.

First off, start with what you already have. Click on the "Suggest to Friends" button and invite friends from your original profile. The number of fans you will get from this method depends mainly on the number of friends that you actually have and your relationship with them. Aside from this, you should also invite your e-zine and e-mail subscribers. Send out an e-mail to your subscribers informing them of your fan page, and place a logo of Facebook in your newsletters.

Get the people who regularly visit your site to go to your Facebook fan page by embedding eye-catching things on your website. Choose from a number of widgets that you can embed on your site, such as the Fan Box widget, where you can display your page stream and some fans, or the Live Stream widget, which fans can use to send comments in real time. You can also load nice videos on your Facebook page and embed them on your website or your blog. The video serves as a link to your Facebook fan page.

People are attracted to unique and interesting material. A great way to get more people to check out your Facebook page and like it is to add interesting stuff on your fan page. Make your fan page unique by uploading an attractive welcome video on your main canvas page. Here, you can share what your page is about and why people should "Like" it. There are also a number of Facebook applications that you can try adding to your page to make it more appealing, such as Vpype, a live video-streaming application where you can air Internet shows directly from your page. There are also several companies that create custom Facebook applications, depending on what you want.

After doing this you post interesting updates, articles and news relevant to your business on your Facebook, so that people who are added in your list get the post and are forced to comment on your profile. By doing this the user who will comment on your profile will in return automatically post your comment to all users in his profile. This will notify more users about your existence and you will end up getting more people in your network.

Don't forget to link, link, link. Make sure you add a link on your personal profile page that will direct your visitors to your Facebook fan page. Place your fan page’s URL right below your profile picture, on the "Write something about yourself" area, so that it will be easily visible to friends who visit your page. You can also link your fan page to other sites, such as Twitter. Your Facebook updates will automatically get posted to your Twitter account, and you can also promote your fan page on your background and Twitter bio field.

Above are the ways of doing it but the most important thing is that you keep on posting on your Facebook profile. You have to be very active on Facebook. An active profile is the key to attracting more and more users.
These are only a few of the things you can do to increase your Facebook fans. Try them out!

Source: www.isnare.com

Monday, September 24, 2012

W3C Workshop: Do Not Track and Beyond

20 September 2012

W3C announced today a Workshop on Do Not Track and Beyond, 26-27 November in Berkeley, California. W3C is currently creating standards that define mechanisms for expressing user preferences around Web tracking. The Working Group has produced drafts of Do Not Track specifications, concurrent with various implementations in browsers and Web sites and heightened press and policymaker attention. At the same time, public awareness of online privacy issues has increased.

Workshop participants will discuss the Consortium's next steps in the area of tracking protection and Web privacy. What have we learned from Do Not Track standardization and real-world implementations? What should we look at next and beyond DNT?

There is no fee to participate in this Workshop and W3C Membership is not required. All participants are required to submit a position paper by 19 October and space is limited. W3C thanks UC Berkeley and TRUST Science and Technology Center for hosting the meeting, and Yahoo! for sponsoring the event. Learn more about the W3C Privacy Activity.

Saturday, September 15, 2012

Web Cryptography API Draft Published

13 September 2012

The Web Cryptography Working Group has published the First Public Working Draft of Web Cryptography API. This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Key storage is provided for both temporary and permanent keys. Access to keying material is contingent on the same origin policy. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications. Learn more about the Security Activity.

Simple Delivery Profile for Closed Captions (US) Draft Published

13 September 2012

The Timed Text Working Group has published the First Public Working Draft of Simple Delivery Profile for Closed Captions (US). This document defines the behavior expected of a presentation processor using the player constraints for such an online delivery profile. The Simple Online Delivery profile is focused on streamlined delivery of closed captions on the Internet. This interoperability profile supports core TTML features to deliver content originating legacy formats such as CEA-608 and -708 content, and is targeted primarily for delivery in US markets. The Simple Delivery Profile for Closed Captions focuses interoperability using TTML 1.0 to support delivery of closed captions for video content. Other profiles based on TTML 1.0 may target other types of subtitles such as on-screen text or graphics. This interoperability profile is a proper subset of TTML 1.0 plus features required to support US Government closed captioning requirements for online presentation. Learn more about the Video in the Web Activity.

Three drafts published by the CSS Working Group

11 September 2012

The Cascading Style Sheets (CSS) Working Group has published three Working Drafts  .

  • CSS Conditional Rules Module Level 3. This module contains the features of CSS for conditional processing of parts of style sheets, conditioned on capabilities of the processor or the document the style sheet is being applied to. It includes and extends the functionality of CSS level 2, which builds on CSS level 1. The main extensions compared to level 2 are allowing nesting of certain at-rules inside '@media', the addition of the '@supports' and '@document' rules for conditional processing.
  • CSS Image Values and Replaced Content Module Level 4. This module contains the features of CSS level 4 relating to the <image> type and replaced elements. It includes and extends the functionality of CSS Image Values and Replaced Content Module Level 3. The main extensions compared to level 3 are several additions to the ‘<image>’ type, additions to the ‘<gradient>’ type, extensions to the ‘image()’ function, definitions for interpolating several ‘<image>’ types, and several properties controlling the interaction of replaced elements and CSS's layout models.
  • CSS Transforms. CSS transforms allows elements styled with CSS to be transformed in two-dimensional or three-dimensional space. This specification is the convergence of the CSS 2D transforms, CSS 3D transforms and SVG transforms specifications.

Learn more about the Style Activity.

HTML+RDFa 1.1 Draft Published

11 September 2012

The RDFa Working Group has published a Working Draft of HTML+RDFa 1.1.This specification defines rules and guidelines for adapting the RDFa Core 1.1 and RDFa Lite 1.1 specifications for use in HTML5 and XHTML5. The rules defined in this specification not only apply to HTML5 documents in non-XML and XML mode, but also to HTML4 and XHTML documents interpreted through the HTML5 parsing rules. Learn more about the Semantic Web Activity.

Monday, September 10, 2012

Easy-to-Read on the Web - Online Symposium - Call for Papers

06 September 2012
The Research and Development Working Group (RDWG) will hold an online symposium to explore easy-to-read language to meet the needs of people with cognitive disabilities or low language skills. The Call for Papers is open until 12 October 2012. Learn more about the Easy-to-Read on the Web Symposium and the Web Accessibility Initiative (WAI).

Last Call: Document Object Model (DOM) Level 3 Events Specification

06 September 2012
The Web Applications Working Group has published a Last Call Working Draft of Document Object Model (DOM) Level 3 Events Specification. This specification defines the Document Object Model Events Level 3, a generic platform- and language-neutral event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event. The Document Object Model Events Level 3 builds on the Document Object Model Events Level 2. Comments are welcome through 27 September. Learn more about the Rich Web Client Activity.

Report: Current State and Roadmap of Standards for Web Applications on Mobile

05 September 2012
Thumbnail of application platform diagram that appears in the report W3C has published a new edition of Standards for Web Applications on Mobile, an overview of the various technologies developed in W3C that increase the power of Web applications, particularly in the mobile context.
A deliverable of the MobiWebApp project, this seventh edition of the document highlights changes since May 2012, particularly two new proposed charters to start work on Near-Field Communications (NFC) and System Applications (i.e. native apps built with Web technologies), and the work on Web Intents, storage quota management and multimedia integration.
Learn more about the Web and Mobile Devices.

Wednesday, September 5, 2012

SEO - Right video at the right time is priceless

Using Videos In News Releases for Better SEO

In a survey conducted by Forbes Magazine, 75% of senior executives said that they watched work-related videos per week and another 52% related that they prefer to watch work-related videos on YouTube once a week.
Many Internet savvy people who used to harvest information by reading text have learned to appreciate the importance of videos.

Advantages of video in press release

•One of the most effective ways to grab the attention of media professionals.
•Raise the visibility of your Web page on search engine results pages.
•Promote your video content while generating more website traffic for your brand.

In some cases, photos and video can be featured on other websites that can drive their audience to your news story and garner more publicity for your business. Pictures might be worth a thousand words, but the right video at the right time is priceless.
 

Monday, August 27, 2012

First edition of the Open Data Conference

24 August 2012

W3C will participate in the first edition of the “Open Data Conference” that will take place on September 27, 2012 in Paris, France.

This event with an international dimension will gather public and private decision makers and address some of the pressing challenges facing the Open Data paradigm, such as accountability, privacy, or data licensing.

Among the guests are professor Nigel Shadbolt, a “founding father” of Open Data in England, and Arnaud Montebourg, French Minister of Productive Recovery. Daniel Dardailler, W3C Director of International Relations, will speak on the “Open Data and Future Uses” round-table and present W3C’s involvement in the area.

Registration is open until 24 September, 2012.

Four drafts updated by the CSS Working Group

23 August 2012

The Cascading Style Sheets (CSS) Working Group published four Working Drafts :

  • CSS Fonts Module Level 3. This CSS3 module describes how font properties are specified and how font resources are loaded dynamically. The contents of this specification are a consolidation of content previously divided into CSS3 Fonts and CSS3 Web Fonts modules.
  • CSS Regions Module Level 3. The CSS regions module allows content to flow across multiple areas called regions. The regions are not necessarily contiguous in the document order. The CSS regions module provides an advanced content flow mechanism, which can be combined with positioning schemes as defined by other CSS modules such as the Multi-Column Module or the Grid Layout Module to position the regions where content flows.
  • Selectors Level 4. Selectors are patterns that match against elements in a tree, and as such form one of several technologies that can be used to select nodes in an XML document. Selectors have been optimized for use with HTML and XML, and are designed to be usable in performance-critical code. They are a core component of CSS (Cascading Style Sheets), which uses Selectors to bind style properties to elements in the document.
  • CSS Fragmentation Module Level 3. This module describes the fragmentation model that partitions a flow into pages. It builds on the Page model module and introduces and defines the fragmentation model. It adds functionality for pagination, breaking variable fragment size and orientation, widows and orphans.

Learn more about the Style Activity.

Tuesday, August 21, 2012

Top Free Blog Directories

Below is the list of Top Free Blog Directories.
http://www.technorati.com 8
http://www.globeofblogs.com 7
http://www.blogpulse.com/index.html 7
http://www.globeofblogs.com 7
http://blogs.botw.org/ 6
http://portal.eatonweb.com/ 6
http://www.blogcatalog.com/ 6
http://www.bloghub.com/ 6
http://www.bloggernity.com/ 6
http://www.blogged.com/ 6
http://www.bloggingfusion.com/ 6
http://www.bloggapedia.com/ 6
http://www.weblogalot.com/ 6
http://www.blogdigger.com/index.html 6
http://technorati.com/blogs/directory/ 6
http://www.bloghop.com/ 6
http://www.totalblogdirectory.com/ 5
http://www.indiblogger.in/ 5
http://browseblogs.com/ 5
http://www.today.com/ 5
http://www.browseblogs.com/ 5
http://www.blogdire.com/ 5
http://www.topbloglists.com/ 5
http://www.ontoplist.com/blog-directory/ 5
http://www.blog-directory.org/index.php 5
http://www.delightfulblogs.com/ 4
http://www.lsblogs.com/ 4
http://blogsforsmallbusiness.com/directory/ 4
http://www.thevital.net/ 4
http://www.blogrankings.com/ 4
http://www.biggerblogger.com/ 4
http://www.blogflux.com/ 4
http://www.blogio.net/ 4
http://www.blogarama.com/ 4
http://www.quickblogdirectory.com/ 4
http://www.blogpoint.com/ 4
http://www.blog-watch.com/ 4
http://www.blogadr.com/ 4
http://www.blogdirectory.net/ 4
http://www.bloghints.com/ 4
http://blogville.us/ 4
http://www.blogsweet.com/ 4
http://www.expat-blog.com/en/directory/ 4
http://www.herblogdirectory.com/ 4
http://www.blogbar.net/ 4
http://www.addurlblog.com/ 4
http://www.blogdust.com/blog-directory/ 4
http://www.bloggerhq.net/ 3
http://www.blogbunch.com/ 3
http://blogannounce.info/ 3
http://www.blogshaven.com/ 3
http://www.blogsthatfollow.com/ 3
http://www.bloggeries.com/ 3
http://www.delightfulblogs.com/ 3
http://www.wordpressblogdirectory.com/ 3
http://www.blogfolders.com/ 3
http://theblogresource.com/ 3
http://www.blogbal.com/ 3
http://www.surrealblog.com/ 3
http://www.blogtoplist.com/ 3
http://www.bloguniverse.com/ 3
http://www.myblog2u.com/ 3
http://www.bloggernow.com/ 3
http://followlist.com/ 3
http://www.iblogbusiness.com/ 3
http://www.readablog.com/default.aspx 3
http://www.blog-search.com/ 3
http://www.wilsdomain.com/ 3
http://www.getblogs.com/ 3
http://www.bloglisting.net/ 3
http://grokodile.com/ 3
http://www.righttracker.com/ 3
http://www.blogtagstic.com/ 3
http://www.blogwebdirectory.com/ 3
http://www.bestblogs.org/ 3
http://www.dmegs.com/ 3
http://www.spillbean.com/ 2
http://www.ablogin.com/ 2
http://www.buzzerhut.com/ 2
http://www.blogpopular.net/ 2
http://www.dofollowblogs.com/ 2
http://www.blogdirectorysubmission.com/ 0
http://www.2searchblogs.com/ 0

Friday, August 10, 2012

Last Call: The WebSocket API

09 August 2012
The Web Applications Working Group has published a Last Call Working Draft of The WebSocket API. This specification defines an API that enables Web pages to use the WebSocket protocol (defined by the IETF) for two-way communication with a remote host. Comments are welcome through 30 August. Learn more about the Rich Web Client Activity

XForms 2.0 and 'XForms 2.0: XPath expression module' Drafts Published

08 August 2012
The Forms Working Group has published two First Public Working Drafts:
  • XForms 2.0. XForms is an XML markup for a new generation of forms and form-like applications on the Web, integrated into other markup languages, such as XHTML, ODF or SVG. An XForms-based application gathers and processes data using an architecture that separates presentation, purpose and content. XForms accommodates form component reuse, fosters strong data type validation, eliminates unnecessary round-trips to the server, offers device independence and accessibility, and reduces the need for scripting. XForms 2.0 adds support for defining custom functions, variables, a pluggable expression language with extra functions (XPath 2.0), model-based switch and repeat, Attribute Value Templates, consuming and submitting JSON and CSV instance data, amongst other things.
  • The Forms Working Group has published the First Public Working Draft of XForms 2.0: XPath expression module. This module defines how XPath could be used for addressing instance data nodes in binding expressions, to express constraints, and to specify calculations in XForms. This module is based on XPath 2.0, but an XPath 1.0 backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 2.0. This module also defines the XForms Function Library which contains additional functions that are useful for creating forms.
Learn more about the XForms Activity.

Networked Service Discovery and Messaging Draft Published

07 August 2012
The Device APIs Working Group has published the First Public Working Draft of Networked Service Discovery and Messaging. This specification defines a mechanism for an HTML document to discover and subsequently communicate with HTTP-based services advertised via common discovery protocols within a user's network. Learn more about the Ubiquitous Web Applications Activity.

Monday, August 6, 2012

Ambient Light Events Draft Published

02 August 2012
The Device APIs Working Group has published the First Public Working Draft of Ambient Light Events. This specification defines a means to receive events that correspond to a light sensor detecting the presence of a light. Learn more about the Ubiquitous Web Applications Activity.

MBUI - Task Models Draft Published

02 August 2012
The Model-Based User Interfaces Working Group has published the First Public Working Draft of MBUI - Task Models. Task models are useful when designing and developing interactive systems. They describe the logical activities that have to be carried out in order to reach the user’s goals. This document covers the specification of Task Models, with a meta-model expressed in UML, and an XML Schema that can be used as the basis for interchange of Task Models between different user interface development tools. Learn more about the Ubiquitous Web Applications Activity.

Web Audio API Draft Published

02 August 2012
The Audio Working Group has published a Working Draft of Web Audio API. This specification describes a high-level JavaScript API for processing and synthesizing audio in web applications. The primary paradigm is of an audio routing graph, where a number of AudioNode objects are connected together to define the overall audio rendering. The actual processing will primarily take place in the underlying implementation (typically optimized Assembly / C / C++ code), but direct JavaScript processing and synthesis is also supported. This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: XMLHttpRequest (using the responseType and response attributes). For games and interactive applications, it is anticipated to be used with the canvas 2D and WebGL 3D graphics APIs. Learn more about the Rich Web Client Activity.

W3C Launches Patent Advisory Group for Tracking Preference Expression

01 August 2012
In accordance with the W3C Patent Policy, W3C has launched a Patent Advisory Group (PAG) in response to a disclosurerelated to the Tracking Preference Expression specification published by the Tracking Protection Working Group; see the PAG charter.
W3C launches a PAG to resolve issues in the event a patent has been disclosed that may be essential, but is not available under the W3C Royalty-Free licensing requirements. Public comments regarding this disclosure may be sent to public-tracking-comments at w3.org (with public archive). Learn more about Patent Advisory Groups.

Wednesday, August 1, 2012

Patent Advisory Group Recommends Continuing Work on Touch Events Version 1

31 July 2012

The Touch Events Patent Advisory Group (PAG) has published a report recommending that W3C continue work on the Touch Events version 1 specification without changes. W3C launches a PAG to resolve issues in the event a patent has been disclosed that may be essential, but is not available under the W3C Royalty-Free licensing requirements. See the original announcement of the PAG.

Last Call: Efficient XML Interchange (EXI) Profile

31 July 2012

The Efficient XML Interchange Working Group has published a Last Call Working Draft of Efficient XML Interchange (EXI) Profile. This document describes a profile of the EXI 1.0 specification for devices with limited memory capacities. Comments are welcome through 14 September. Learn more about the Extensible Markup Language (XML) Activity.

Internationalization Tag Set (ITS) Version 2.0 Draft Published

31 July 2012
The MultilingualWeb-LT Working Group has published a Working Draft of Internationalization Tag Set (ITS) Version 2.0. This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS) 2.0. ITS 2.0 is the successor of ITS 1.0; it is designed to foster the creation of multilingual Web content, focusing on HTML5, XML based formats in general, and to leverage localization workflows based on the XML Localization Interchange File Format (XLIFF). In addition to HTML5 and XML, algorithms to convert ITS attributes to RDFa and NIF are provided. Learn more about the Internationalization Activity.

Tuesday, July 31, 2012

Free SEO Tools

1. Search Engine Submissions

Having your website indexed and searchable by search engines is the first and most important set in SEO for your website. This free service will allow you to submit your website to over 20 key search engines (including Google, Yahoo, Big & Ask) and jump start you SEO campaign. Submit your website to over 20 high quality search engines for free.

2. Website SEO Analysis

Enter your website’s URL on Woo Rank and get a detailed SEO analysis report of your website in seconds. They will also send you a pdf of the same SEO report straight to your email address, should you wish.
Please click here to go to Woo Rank.

3. Keyword Tool

Google’s very own Keyword Tool. You do not have to be registered or signed into Google to use this keyword tool. Use this Keyword Tool to research your keyword and see what people are searching for on Google and how competitve those keywords are.
Please click here to go to Google Keyword Tool.

4. Keyword & Website Analysis

Alexa is one of the key website analysis tools for researching your website and those of your competitors. It will show you the Alexa Rank along with search metrics such as high impact keywords.
Please click here to go to Alexa.

5. Free Back Links Directory

The main method of effective back linking is by getting other sites to send a one way (ie. non reciprocal) to your website. Some directories are good for this and Global-Dir.com offer free one way back links.

Monday, July 30, 2012

Applying WCAG 2.0 to Non-Web ICT - First Draft Published

27 July 2012
The Web Content Accessibility Guidelines Working Group (WCAG WG)  published the First Public Working Draft of Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT). It is a draft of an informative (that is, not normative) W3C Working Group Note that will clarify how Web Content Accessibility Guidelines (WCAG) 2.0 can be applied to non-Web ICT. Please see important background information in the Call for Review e-mail. Comments are welcome through 7 September 2012. Read about the Web Accessibility Initiative (WAI).

Friday, July 27, 2012

W3C Invites Implementations of Page Visibility, Performance Timeline, and User Timing

26 July 2012
The Web Performance Working Group invites implementation of three Candidate Recommendations:
  • Page Visibility which defines a means for site developers to programmatically determine the current visibility state of the page in order to develop power and CPU efficient web applications.
  • Performance Timeline which defines an unified interface to store and retrieve performance metric data. This specification does not cover individual performance metric interfaces.
  • User Timing which defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.
Learn more about the Rich Web Client Activity.

Best Practices for Fragment Identifiers and Media Type Definitions Draft Published

26 July 2012

The Technical Architecture Group has published the First Public Working Draft of Best Practices for Fragment Identifiers and Media Type Definitions. Fragment identifiers within URIs are specified as being interpreted based on the media type of a representation. Media type definitions therefore have to provide details about how fragment identifiers are interpreted for that media type. This document recommends best practices for the authors of media type definitions, for the authors of structured syntax suffix definitions (such as +xml), for the authors of specifications that define syntax for fragment identifiers, and for authors that publish documents that are intended to be used with fragment identifiers or who refer to URIs using fragment identifiers. Learn more about the Technical Architecture Group.

Tuesday, July 24, 2012

Adobe, Google, Microsoft Sponsorships Bolster W3C Staffing of HTML5 Work

24 July 2012
W3C is pleased to announce commitments from Adobe, Google, and Microsoft for sponsorship funding that will enable W3C to provide additional staffing in support of the HTML Working Group's full range of activities, including editing several specifications and developing tests. These sponsorships will help W3C fill a position announced in June in response to an April call for editors from the HTML Working Group Chairs. In their April email, the Chairs also outlined the group's parallel efforts to finalize a stable HTML5 standard by 2014 and engage with the community on future HTML features. Learn more about the HTML Working Group.

Three Provenance Last Call Drafts Published

24 July 2012
The Provenance Working Group published three Last Call Working Drafts . Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness.
  • PROV-DM: The PROV Data Model introduces the provenance concepts found in PROV and defines PROV-DM types and relations. The PROV data model is domain-agnostic, but is equipped with extensibility points allowing domain-specific information to be included.
  • PROV-O: The PROV Ontology expresses the PROV Data Model using the OWL2 Web Ontology Language (OWL2). It provides a set of classes, properties, and restrictions that can be used to represent and interchange provenance information generated in different systems and under different contexts. It can also be specialized to create new classes and properties to model provenance information for different applications and domains.
  • PROV-N: The Provenance Notation is introduced to provide examples of the PROV data model: aimed at human consumption, PROV-N allows serializations of PROV instances to be created in a compact manner. PROV-N facilitates the mapping of the PROV data model to concrete syntax, and is used as the basis for a formal semantics of PROV. The purpose of this document is to define the PROV-N notation.
Comments on the Last Call Working Drafts are welcome through 18 September. The group also published a Working Draft of PROV Model Primer, which provides an intuitive introduction and guide to the PROV specification for provenance on the Web. The primer is intended as a starting point for those wishing to create or use PROV data. Learn more about the Semantic Web Activity.

Last Call: SPARQL 1.1 Query Language

24 July 2012
The SPARQL Working Group has published a Last Call Working Draft of SPARQL 1.1 Query Language. RDF is a directed, labeled graph data format for representing information in the Web. This specification defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. SPARQL contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. SPARQL also supports aggregation, subqueries, negation, creating values by expressions, extensible value testing, and constraining queries by source RDF graph. The results of SPARQL queries can be result sets or RDF graphs. Comments are welcome through 21 August. Learn more about the Semantic Web Activity.

SEO Advice :Create a free product or service

Content drives most traffic when you offer something useful. There are many types of useful content you can create and they largely depend on the niche of your site. You can have articles with tons of advice, or short tips but one of the most powerful ways to get traffic is to create a free product or service. When this product or service gets popular and people start visiting your site, chances are that they will visit the other sections of the site as well.

Free products and services are great for getting free traffic to your site and one of the best varieties in this aspect is viral content. Viral content is called so because it distributes like a virus – i.e. when users like your content, they send it to their friends, post it on various sites, and promote it for free in many different ways. Viral content distributes on its own and your only task is to create it and submit it to a couple of popular sites. After that users pick it and distribute it for you. Viral content can be a hot video or a presentation but it can also be a good old article or an image.

Thursday, July 19, 2012

W3C Identifies how the Web will Transform the Digital Signage Industry

18 July 2012
W3C announced new momentum for making the Web the future interoperable platform for Digital Signage. W3C issued a summary of key topics and use cases for bringing Digital Signage to the Web, as well as a first gap analysis of enhancements to the Web to enable the transformation of the Digital Signage ecosystem. Digital signage covers a spectrum of display sizes and locations, from sports arenas and urban video terminals of every shape, to monitors in elevators, storefront windows, train stations, and public kiosks featuring rich interactivity. In June, an initial opportunity to discuss next-generation Web-based Digital Signage services drew industry stakeholders to a W3C Workshop "All Signs Point to the Web," hosted by NTT. Read the full press release about the Workshop report and join the Web-based Signage Business Group to develop use cases and requirements for standardization.

Registration Open for Mobile Web Training Courses (in English y en Español)

18 July 2012
Registration is now open for a new round of mobile Web online training courses which begin on 3 September 2012. In these courses, you learn to "mobilize" pages and deliver a good Web experience on mobile devices. These 6-week long W3C online training courses, supported by experienced and professional trainers, let you study at your own pace. The courses are separately delivered in English and in Spanish:
Learn more about W3C online training for developers.

Monday, July 16, 2012

Basic optimization tips : Effects on traffic

Meta Description

The meta description tag is an element search engines use to help determine what the page is about. The tag also appears as your site description in search results, so writing your tag to appeal to human eyes can lead to increased clicks on your listing. You will notice that the search engine bolds the keywords you originally searched for in the description tag. If you do not have a description tag, Google will write one for you, and you really don't want that.

Google PageRank

Your Google PageRank (toolbar PageRank is between 0 and 10 - the higher, the better) is basically a measure of trust and authority. Domains with a higher PR are likely to rank for more terms than sites with low PR.

Alexa Rank

Your Alexa Rank is actually a measure of traffic to your site where they rank your site compared to all other sites in the world. If your site is in the top 100,000 Alexa rank, your traffic is probably doing OK. For example, pearanalytics.com floats between 47,000 and 75,000.

Title Tag

The title tag is an element that the search engines use to help determine what the page is about. Since it shows up as the first line of your listing in search results, it can make or break your clicks if it does not sound appealing to people. A concise and appropriate title tag projects an image of professionalism as well as encourages users to bookmark your page, knowing they won't have to edit text to remember what they bookmarked.

Robots.txt

Your robots.txt file, located in your root folder, is a way for webmasters to indicate which pages/folders/directories should not be accessed by crawlers or search engines. A good example are any pages behind a login. However, there are some serious misuses of the robots file that we come across sometimes, and we want to try and alert you to those. Overusing or blocking too many sections of your site could cause harm to your inbound link effectiveness.

Page Load Time

Having slow loading pages can affect your rankings, and ultimately your traffic. Even the traffic you do get may bounce at a higher rate on slow loading pages. If you have an e-commerce site, expect a loss in sales for pages that load too slowly.

Clean URL

Use clean URLs and add targeted keywords where you can to enhance the SEO friendliness of your site. You will notice search engines will highlight those pages in the results, so having pages that are descriptive is better than random characters and number sequences, which is almost always the case. But be careful about pages that have affiliate codes or ID's in them. If they are duplicate copies of existing pages on the site, you want to be sure the search engine is not seeing these affiliate pages as duplicate content. You can "NOINDEX" them if necessary.

Domain Age

A young domain will likely not rank well immediately depending on competitiveness, unless there is a major social or viral event to drive a massive amount of traffic to the site in a short period of time. Domain age is used in the "trust and authority" calculation the search engine does. Also, purchase your domain out to 5 or 10 years instead of just 1 or 2 years at a time. That makes the search engine comfortable that you plan on being around a while.

Analytics

While this won't affect your traffic, it is what you need to measure YOUR traffic. 

 

Friday, July 13, 2012

W3C Release :Four Device API Specifications Published; HTML Media Capture Last Call

12 July 2012
The Device APIs Working Group has published four Working Drafts:
  • a Last Call Working Draft of HTML Media Capture.The HTML Media Capture specification defines HTML form extensions that facilitate user access to media capture capabilities of the hosting device. Comments are welcome through 09 August.
  • a First Public Working Draft of Pick Media Intent, which enables access to a user's media gallery from a Web application.
  • a First Public Working Draft of Proximity Events, which defines a means to receive events that correspond to a proximity sensor detecting the presence of a physical object.
  • a Working Draft of Pick Contacts Intent, which enables access to a user's address book service from a Web application.
Learn more about the Ubiquitous Web Applications Activity.

W3C Release :File API Draft Published

12 July 2012
The Web Applications Working Group has published a Working Draft of File API. Web applications should have the ability to manipulate as wide as possible a range of user input, including files that a user may wish to upload to a remote server or manipulate inside a rich web application. This specification defines the basic representations for files, lists of files, errors raised by access to files, and programmatic ways to read files. Additionally, this specification also defines an interface that represents "raw data" which can be asynchronously processed on the main thread of conforming user agents. The interfaces and API defined in this specification can be used with other interfaces and APIs exposed to the Open Web Platform. Learn more about the Rich Web Client Activity.

W3C Release :Two JSON-LD First Drafts Published

12 July 2012
JSON has proven to be a highly useful object serialization and messaging format. JSON-LD harmonizes the representation of Linked Data in JSON by outlining a common JSON representation format for expressing directed graphs; mixing both Linked Data and non-Linked Data in a single document. The RDF Working Group has published two related First Public Working Drafts:
  • JSON-LD API 1.0 outlines an API and a set of algorithms for transforming JSON-LD documents in order to make them easier to work with in programming environments like JavaScript, Python, and Ruby.
  • JSON-LD Syntax 1.0 outlines a common JSON representation format for expressing directed graphs; mixing both Linked Data and non-Linked Data in a single document.
Learn more about the Semantic Web Activity.

Thursday, July 12, 2012

SEO and w3c standards: SEO Tasks

SEO and w3c standards: SEO Tasks: Basic SEO Tasks 1. Table based layouts are an outdated and ineffective practice for web design         a. Check xhtml/css templates 2. ...

Thursday, July 5, 2012

Impact of W3C Validation over SEO

 Here we can refer some experts comments to analyze the Effect of W3C Validation over SEO

1. Aaron Wall, of  SEOBook:
    If you want to get links from web designers who charge high rates then W3C validation is important to SEO, otherwise it has little direct importance outside of ensuring proper rendering to end users. When one visits Amazon.com or Google or Yahoo! (or just about any billion Dollar+ internet company) they will find a website that doesn’t validate. Why is that?

2. Brent Payne, SEO Director for Tribune
    I like to keep errors under 25 or so, though Tribune has 100+ errors. Perfect code, I don’t think is necessary but you don’t want to have too malformed of HTML. Some say it is a ranking factor, I say you just don’t want to have stuff that is too unexpected for the bots.

3. Dennis Goedegebuure, Senior Manager & Head of SEO at eBay Inc.
    It depends on the type of errors and how many, it all depends on whether the crawler can actually read the real content of the page.

4. Matt Cutts the official voice of Google
Here is a video with what Matt has to say regarding the problems:
With Respect to Effect of W3C Validation over SEO
As you can see from the above testimonials, validation has no direct impact over SEO and you will not receive any bonus from Google. But this doesn’t mean that you don’t have to fix some of the problems to make the site more appealing to the visitors and have a really speedy website.

Tuesday, July 3, 2012

Social Media impact on SEO

The long and short of the answer would appear to be yes. Both Google and Bing admitted late last year to using "social signals" to help rank search results. Additionally Google has a Beta test version of social search under is Labs tools that directly signals which social media outlet it has pulled results from, as well as it's Beta version of the "+1 button" which is it's answer to the Facebook "Like" button. 

From Bing:

“We do look at the social authority of a user. We look at how many people you follow, how many follow you, and this can add a little weight to a listing in regular search results.”

And from Google:

“Yes, we do use [tweeted links and RTs] as a signal. It is used as a signal in our organic and news rankings. We also use it to enhance our news universal by marking how many people shared an article.”

The bottom line is this.  Social signals do matter from an SEO standpoint, but they aren’t strong enough to justify artificially padding your Facebook “likes”, Twitter “tweets” and Google “+1s.”  Instead, providing your website readers with social tools that make sharing your content on social networks easy to do and encouraging them to share articles they enjoy on social networking sites should be enough to grow your social signals profile in an effective and sustainable way.

Selectors API Level 2 Draft Published

28 June 2012
The Web Applications Working Group has published a Working Draft of Selectors API Level 2. Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors, and for testing if a given element matches a particular selector. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring and testing specific elements, especially compared with the more verbose techniques defined and used in the past. Learn more about the Rich Web Client Activity.

Media Capture and Streams Draft Published

28 June 2012
The Web Real-Time Communication and Device APIs Working Groups published a Public Working Draft of Media Capture and Streams. This document defines a set of JavaScript APIs that allow local media, including audio and video, to be requested from a platform. Lean more about Ubiquitous Web Applications Activity.

Web Intents Draft Published

26 June 2012
The Web Intents Task Force, jointly operated by the Device Applications (DAP) Working Group and the Web Applications (WebApps) Working Group, has published a First Public Working Draft of Web Intents. This document defines DOM interfaces and markup used by client and service pages to create, receive, and reply to Web Intents messages, and the procedures the User Agent carries out to facilitate that process. Learn more about the Ubiquitous Web Applications Activity and the Rich Web Client Activity.

Friday, June 29, 2012

SEO with ASP.NET 4.0 Framework

For commertial website development we cant ignore on page search engine optimization, On page SEO or search engine optimisation is making sure that your website is as search engine friendly as possible. If your website is not optimised then you have less chance of getting good results in the search engines, ( basic seo tasks ) here are some of the improvements added in ASP.NET - 4.0 Framework
1. Now you can add the meta key words and description in code-behind also. Previously in aspx page, in html markup, we used to provide meta tags
<meta name="keywords" content="SEO improvement, .net framework 4.0"
<meta name="description" content="you can imporve SEO"
> 
Now, in .net 4.0, you can do this in code-behind  
Page.MetaDescription = "you can improve SEO";
Page.MetaKeywords = "SEO improvement,.net framework 4.0"
2. Response.RedirectPermanent() method : Its common that, aspx page names will change some times. Then, old links will become stale and search engines will point to these stale pages, . Although we handle this by redirecting to new pages, still it will throw an temporary redirect response(HTTP 302), which causes the negative impact in search engines and your page rank will reduce.  
<PRE class="brush: plain">New method Response.RedirectPermanent() method will throw an Permanent redirect(HTTP 301), which makes the search engines to replace their old links with new links and your page rank will not affect because of this.
</PRE>
 
 
 

Related posts:

Differences Between IIS URL Rewriting and ASP.NET Routing SEO with ASP.NET 4.0 Framework