Monday, January 14, 2013

w3c compliance standards


Web Design and Applications  
Web Design and Applications involve the standards for building and Rendering Web pages, including HTML, CSS, SVG, Ajax, and other technologies for Web Applications (“WebApps”). This section also includes information on how to make pages accessible to people with disabilities (WCAG), to internationalize them, and make them work on mobile devices.

Web Architecture
Web Architecture focuses on the foundation technologies and principles which sustain the Web, including URIs and HTTP.

Semantic Web
In addition to the classic “Web of documents” W3C is helping to build a technology stack to support a “Web of data,” the sort of data you find in databases. The ultimate goal of the Web of data is to enable computers to do more useful work and to develop systems that can support trusted interactions over the network. The term “Semantic Web” refers to W3C’s vision of the Web of linked data. Semantic Web technologies enable people to create data stores on the Web, build vocabularies, and write rules for handling data. Linked data are empowered by technologies such as RDF, SPARQL, OWL, and SKOS.

XML Technology
XML Technologies including XML, XML Namespaces, XML Schema, XSLT, Efficient XML Interchange (EXI), and other related standards.

Web of Services
Web of Services refers to message-based design frequently found on the Web and in enterprise software. The Web of Services is based on technologies such as HTTP, XML, SOAP, WSDL, SPARQL, and others.

Web of Devices
W3C is focusing on technologies to enable Web access anywhere, anytime, using any device. This includes Web access from mobile phones and other mobile devices as well as use of Web technology in consumer electronics, printers, interactive television, and even automobiles.

Browsers and Authoring Tools
The web's usefulness and growth depends on its universality. We should be able to publish regardless of the software we use, the computer we have, the language we speak, whether we are wired or wireless, regardless of our sensory or interaction modes. We should be able to access the web from any kind of hardware that can connect to the Internet – stationary or mobile, small or large. W3C facilitates this listening and blending via international web standards. These standards ensure that all the crazy brilliance continues to improve a web that is open to us all.

Thursday, January 10, 2013

SEO and w3c standards: Social Media impact on SEO

SEO and w3c standards: 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 ran...

Wednesday, January 9, 2013

Three drafts published by the Web Cryptography Working Group


08 January 2013
The Web Cryptography Working Group has published three documents .
  • A 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. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.
  • A First Public Working Draft of WebCrypto Key Discovery. This specification describes a JavaScript API for discovering named, origin-specific pre-provisioned cryptographic keys for use with the Web Cryptography API. Pre-provisioned keys are keys which have been made available to the UA by means other than the generation, derivation, imporation functions of the Web Cryptography API. Origin-specific keys are keys that are available only to a specified origin. Named keys are identified by a name assumed to be known to the origin in question and provisioned with the key itself.
  • A First Public Working Draft of Web Cryptography API Use Cases. This document is an informative overview of the target use cases for a cryptographic API for the web. These use cases, described as scenarios, represent some of the set of expected functionality that may be achieved by the Web Cryptography API, which provides an API for cryptographic operations such as encryption and decryption, and the Key Discovery API, which specifically covers the ability to access cryptographic keys that have been pre-provisioned.
Learn more about the Security Activity. This document is

Registered Organization Vocabulary Draft Published


08 January 2013
The Government Linked Data Working Group has published the First Public Working Draft of Registered Organization Vocabulary. This is a vocabulary for describing organizations that have gained legal entity status through a formal registration process, typically in a national or regional register. It focuses solely on such organizations and excludes natural persons, virtual organizations and other types of legal entity or 'agent' that are able to act. It should be seen as a specialization of the more flexible and comprehensive Organization Ontology. Learn more about the eGovernment Activity.

Monday, January 7, 2013

Last Call: Simple Delivery Profile for Closed Captions (US)


03 January 2013
The Timed Text Working Group has published a Last Call Working Draft of Simple Delivery Profile for Closed Captions (US). This document, expected to become a Group Note, specifies the Simple Online Delivery Profile (US) of the Timed Text Markup Language (TTML). The primary goal of the profile is to establish a minimum level of interoperability between TTML10 and legacy caption formats employed in US markets, such as CEA608 and CEA708. Comments are welcome through 31 January. Learn more about the Video in the Web Activity.

Last Call: CSS Text Decoration Module Level 3; Update to Cascading and Inheritance Level 3


03 January 2013
The Cascading Style Sheets (CSS) Working Group published a Last Call Working Draft of CSS Text Decoration Module Level 3. This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks. Comments are welcome through 31 January.
The group also published today a draft of CSS Cascading and Inheritance Level 3. One of the fundamental design principles of CSS is cascading, which allows several style sheets to influence the presentation of a document. When different declarations try to set a value for the same element/property combination, the conflicts must somehow be resolved. The rules for finding the specified value for all properties on all elements in the document are described in this specification. Learn more about the Style Activity.