There is no problem in checking documents through MDN on a daily basis, but some APIs cannot be found or the principles are unclear, so you can only check what the specification says, so this article will talk about how to check the specification.
Before checking the specification, you must first know where the specification is...
First enter w3 , further search to ALL STANDARDS AND DRAFTS , here you can find the specifications of , HTML
, CSS
, DOM
, Web API
and XML
, but not here, because its core is .HTTP
js
ECMA-script
It must be very obscure to look at the specification directly. In fact, you should figure out how to read the specification before reading the specification. It is recommended to read:
- How to Read W3C Specs or its Chinese version
- How to Read the W3C Specification
The core summary is directly brought out here.
- Establish clear awareness: Specifications are written for implementers, not end users ;
- Many specifications include a dedicated section to explain how they are organized and how they should be read;
- Familiar with specification-specific vocabulary;
- It's important to remember that you don't have to read the specs verbatim. Learn to skip reading and focus on the meaningful parts;
- Skip namespace related discussion chapters;
- Learn to read BNF, which is used in many places;
- Learn to read DTDs and find answers to grammar questions from them;
- If a technology involves programmable scripting, that information is included in the binding.
- With patience and perseverance, you will be amazed at the wealth of information you can get from the W3C specifications.
Of course, the standard must be in English, but W3C is also actively promoting the translation of the standard. For the translation situation, you can poke the W3C standard translation .
According to my needs, I found the Chinese translation of CSS2.1 , CSS Home and HTML .