Text / j. david eisenberg (http://www.alistapart.com/authors/jdavideisenberg/) Translated / jjgod jiang (http://jjgod.3322.org/)
Translated from How to Read W3C Specs (http://www.alistapart.com/articles/readspec/)
World Wide Web Consortium (W3C) is all maintainer of the specification of Web technology. As a web designer, you may probably visit their sites (w3.org) to find answers about XHTML questions, or want to know from them about the new technologies of XSL Formatting Object or Scalable Vector Graphic.
This way you run to see those regulations, and then hit it immediately and completely. "This thing," you think, "is not read at all." In fact, this is readable, as long as you understand the key part of the information. "
Specification is not a user manual
The Bible is not a read, but it is - a unknown
When you look for an answer, you will find this user manual or user reference guide, because you are using this technology. That is not the purpose of the W3C specification, "Specification" is to tell the program who to implement this technology, what characteristics do it should, and how it is implemented.
This is like the difference between your car user manual and the repair manual. The user manual tells you how to replace the wiper blade, but if you go to the repair manual, it will tell you the size of the blade, how to connect the subsidiary parts, you have to merge all this information together, you will know how to replace the entire rain.
If you are studying the latest technologies, there may be no information for users to refer to you; the only document that can be found is the specification book. In this case, learning how to see the specification is required, not what is extravagant.
