I continue to meet key stakeholders around the world as part of my introduction to W3C. The last two weeks have been focused on Asia.

India

I visited India last week partly to help launch the new W3C office at a conference. My experience in the conference and in meetings illustrated opportunities that W3C has in India: better communication of our work, greater participation in this work by engineers from India, and expanding our technical scope.

The conference itself demonstrated the strong support for W3C within India. Keynote speakers included key government ministers as well as icons of India’s high-tech industry. The conference attracted 600 people from industry, government, and academia. The technical program brought together leading researchers and spanned an impressive set of topics.

In India, W3C’s office is hosted by TDIL – Technology Development for Indic Languages. This partnership will strengthen our internationalization work, part of ensuring that the Web is available for all people. With 22 official languages in India, in addition to a larger number of languages and dialects – making the Web available irrespective of language and literacy level is a key issue for India and consonant with our values. Many of the conference presentations related to that topic.

Outside the conference was equally rewarding. India has important vendor groups such as Nasscom and Mait who co-sponsored the conference. And TDIL is part of a government ministry. My visit gave me the opportunity to meet with several executives of these organizations and reinforce my belief that there is a strong commitment to W3C in India.

China

In China there was a similar enthusiasm and set of highlight events for W3C.

The visit got off to a good start even before it began – with news that China Unicom became the first large IT vendor in China to join as a W3C Member.

There is great interest in W3C in China. I gave several presentations about the Expanding Web Platform to hundreds of engineers from companies and universities at places such as Beihang University in Beijing. The deep questions illustrated the interest and technical savvy of these engineers in topics such as HTML5, accessibility, and the Semantic Web.

Also of importance were meetings with key decision makers and larger public meetings. At a dinner for W3C member laboratories in China – the local leaders of global firms participated in discussions about how to create a stronger W3C community in China. And at a conference sponsored by CESI – the China national electronics standards institute – related to ISO/IEC JTC1 SC 38, I had an opportunity to deliver remarks about how W3C standards related to the new standardization effort underway in SC 38.

Japan

Japan has always been a strong point for W3C in Asia, but additional opportunities exist.

As background, the Japan team – also noting strong ties with our Korean office – is in the process of putting together a workshop in September on Web TV.

Meeting with technical visionaries and government officials, it is clear that Asian industry is poised to play a strong role in this area. After all, many of the innovations in television manufacturing already take place in Asia. As the convergence continues between the Web and all access devices (including television), what better place than Japan to have our Web TV workshop?

It’s really great to see that W3C setting up it’s office in India and other Asian Countries.
As a web geek I am a big follower of W3C, and I am pretty sure that there are many great things going to happen with the help of engineers, webmasters from these countries..
Thanks for keeping us updated.. Great Job!!!

I’m glad to see the W3C is still around and making great strides forward in bringing everyone together on the same page for progress. I’m a Mainframe programmer from the early days and I was one of the first programmers to realize the potential of SGML. There wasn’t many people around back then who could understand how SGML could play a signifigant role on business. So, when the W3C was formed, I was very pleased and hoped it would last. Thanks for doing such a good job.

I do hope to see you soon in Manila, Philippines! We’re trying to keep the semantic and valid web community alive in this part of the globe, in fact we’re actually planning a Web Designer conference this October, hope you’d all be interested in sponsoring us. :)

W3C engineers, Hello, I am from China, a program developer, here are my suggestions for the HTML5 standard, my English is very poor, like him to bear with me.

We develop web applications, you often encounter nasty XSS injection problems, such as one that will allow users to submit HTML code forum, it is easy for users to submit the HTML code malicious attack, because the HTML code Inside, you can use JAVASCRIPT and FLASH, etc. to add their own logic. It was launched ubb code, this code is very easy to use, but does not solve the problem completely solved.

I think a favorable way to reduce XSS injection attacks, just a immature view Pleased to meet you.

My advice start ================ ================

I feel I can add a security HTML5 standard tag, like this HTML code . Who is included in the tag inside the html code, have been monitoring them, they are difficult to do a bad thing.

Security tags are not there any display on the page, just like the hidden form.

In order to improve the efficiency of the browser resolution, tag is ignored by default, to use its web page, must open the JAVASCRIPT code, like this
var manager = new safelyManager ();
manager. open ();

Security tags can set different security levels:

High security level, by the security area marked trap, ignore all the scripts, flash and other plug-ins are the most secure mode.

Medium security level, by the security area marked trap, in a state of isolation with the outside world can not rewrite external dom, can not get the prompt box, and can only run the footsteps of some of the graphic display and the browser will use the red box It is a mark unsafe areas.

Low security level, just as there is no security tag

The goal is to prevent xss attacks from untrusted HTML source code, such as post on the forum will be strictly controlled safety mark up, not evil

The W3C blog is for discussions within W3C and the Web community at large. Announcements, issues on Web standards and educational materials among other topics are posted here; see the W3C home page for official announcements from W3C.