会议主题：W3C CEO与工程师面对面
会议日期：5月9日(周日)下午1点开始
会议地点：北航会议中心
预定人数：50人
参与费用：不收取任何费用
主办方：W3C中国，Web标准化交流会

W3C CEO Dr. Jeff Jaffe 5月来北京, Web标准化交流会努力争取到了这次难得的机会,邀请到Dr. Jeff Jaffe与工程师一起探讨Web前端的发展和与之相关的各类问题.希望大家积极报名.相信一定会收获不小~

从最开始接触网站,到后来的所谓”div+css”,再到现在的web标准,重构,大前端……一直没有深刻去理解”Web Standard”这个概念,以及为什么一定要遵守web标准. 看完论坛里对于这一问题的讨论更是让我恍惚了一下.

好吧,那就先来看看人家W3C官方的解释吧:

What does “Web standard” mean?

W3C publishes documents that define Web technologies. These documents follow a process designed to promote consensus, fairness, public accountability, and quality. At the end of this process, W3C publishes Recommendations, which are considered Web standards.

ok,人家老外解释得很简单:W3C发布了一些用于定义Web技术的文档.这些文档是为了要促使在设计跟质量上达成共识,形成公平.在这一过程的最后,W3C公布一些推荐的文档,我们称其为Web标准.真是有够宏观的.

那再来看看Web Standards对于这一概念更具体点的解释:

Tim Berners-Lee’s dream for his invention, the World Wide Web, is a common space where users can share information to work together, to play, and to socialize (The World Wide Web, A very short personal history). As web developers, creating business, social, and educational sites, we turn this dream into reality.

But in this period of tremendous growth, the Web needs guidance to realize its full potential. Web standards are this guidance. These standards help ensure that everyone has access to the information we are providing, and also make web development faster and more enjoyable.

Standards compliance makes it easier for people with special needs to use the Web. Blind people may have their computer read web pages to them. People with poor eyesight may have pages rearranged and magnified for easier reading. And people using hand-held devices can browse the Web just as easily as those using high-end workstations.

As we will explain, there are also many practical reasons for developers to be concerned with web standards. Search engines can do a better job of indexing sites, for example. Using browser-specific code often doubles or triples the work to create web pages, and leaves a lot to be desired when new media are introduced. This situation will only get worse without the sound direction of web standards.

恩,这里解释得就稍微具体一些了,或者说解释的角度更实际一些了. 既然这里面还提到了一个”practical reasons”,那就接着往下看:

What are the advantages of using web standards?

3.1 Accessibility

3.1.1 To software/machines

Complying with web standards can give your web pages greater visibility in web searches. The structural information present in compliant documents makes it easy for search engines to access and evaluate the information in those documents, and they get indexed more accurately.

Because use of web standards makes it easier for server-side as well as client-side software to understand the structure of your document, adding a search engine to your own site becomes easier and gives better results.

Standards are written so that old browsers will still understand the basic structure of your documents. Even if they can’t understand the newest and coolest additions to the standards, they’ll be able to display the content of your site. The same, of course, applies to robots – systems that collect information from your site on behalf of search engines and other indexers.

Compliant code gives you the opportunity of validating your page with a validation service. Validators process your documents and present you with a list of errors. This makes finding and correcting errors a lot easier, and can save you a lot of time.

Compliant documents can easily be converted to other formats, such as databases or Word documents. This allows for more versatile use of the information within documents on the World Wide Web, and simplified migration to new systems – hardware as well as software – including devices such as TVs and PDAs.

3.1.2 To people

Accessibility is an important idea behind many web standards, especially HTML.

Not only does this mean allowing the web to be used by people with disabilities, but also allowing web pages to be understood by people using browsers other than the usual ones – including voice browsers that read web pages aloud to people with sight impairments, Braille browsers that translate text into Braille, hand-held browsers with very little monitor space, teletext displays, and other unusual output devices.

As the variety of web access methods increases, adjusting or duplicating websites to satisfy all needs will become increasingly difficult (indeed, some say it’s impossible even today). Following standards is a major step towards solving this problem. Making your sites standards-compliant will help ensure not only that traditional browsers, old and new, will all be able to present sites properly, but also that they will work with unusual browsers and media.

Some consequences of ignoring standards are obvious: the most basic consequence is that you will restrict access to your site. How much business sense does it make to limit your audience to only a fraction of those who wish be a part of it? For a business site, denying access to even small portions of a target audience can make a big difference to your profit margin. For an educational site, it makes sense to allow access not only to affluent, able-bodied school-children with graphical browsers, but also to children in regions with poorly-developed infrastructure who are best served by text-only browsing, or disabled students using specialized browsers.

The same principle applies to all types of websites — while straying from the standards and taking advantage of browser-specific features may be tempting, the increased accessibility which comes from standards-compliance will lead to far greater rewards in the long run.

3.2 Stability

Most web standards are generally designed with forward- and backward-compatibility in mind — so that data using old versions of the standards will continue to work in new browsers, and data using new versions of the standards will “gracefully degrade” to produce an acceptable result in older browsers.

Because a website may go through several teams of designers during its lifetime, it is important that those people are able to comprehend the code and to edit it easily. Web standards offer a set of rules that every Web developer can follow, understand, and become familiar with: When one developer designs a site to the standards, another will be able to pick up where the former left off.

看了好多关于web标准的讨论也好,文章也好,最终让我们回归到原本,最权威的两大官方机构对于Web Standards这一概念的解释,可以清楚地了解到Web标准的一些理念了.

它既不是之前说的”div+css”,也不仅仅是后来纠正过来的概念:结构与表现分离. Web标准是一个大的思想指导,方向就是指导你用正确的方式去编码,去开发网页,可以让更多的人(包括残障人士),用各种不同的终端设备,通过不同的平台去浏览你的数据. 数据传输是互联网的核心,当数据可以不受任何约束的情况下自由地流通到各个终端那里,让需要它的人受益,共享,进而形成有用的数据,形成良性循环.我想这是Web标准最终的理想状态吧. 而伴随着这一理想状态的实现,给我们开发人员带来的好处也是很明显的,开发成本的降低,开发效率的提高等等等等.

辩证地看待Web标准,也许在某些情况下它的优势体现得不是那么的明显,尽管过程中会遇到这样那样的问题,但是为了将来那个美好的理想状态,做为前端开发者的一员,我觉得我们都有义务去尽量依照Web标准去开发我们的页面和网站.

大的概念理清楚了,接下来就真的要实践了,真正的从”头”开始学习”大前端”!

PS,我喜欢greengnn提到的这个大前端概念,大气!呵呵 不像之前的美工啦 cutter啦 那么见不得世面的感觉~