(New page: Web and standards go hand by hand, straight together. Our users and developers expect V3 to be compliant with several standards in two main aspects: the code outputted by V3 and the source...) |
(No difference)
|
Revision as of 02:03, 9 February 2008
Web and standards go hand by hand, straight together. Our users and developers expect V3 to be compliant with several standards in two main aspects: the code outputted by V3 and the source code of V3.
Editor Output
The code outputted by V3 must be, by default, compliant with the W3C XHTML 1.0 Transitional Specifications and DTD. The following aspects must be considered to properly achieve the expected compliance results:
- The standards markup syntax must be respected;
- Elements not defined in the DTD must be avoided;
- Elements marked as deprecated must be avoided;
- The document structure must respect the DTD rules.
The "style" attribute syntax must instead be compliant with the CSS 2.1 Specifications.
Other that the XHTML 1.0 Transitional compliance, the editor must be flexible enough to accept plugins and configurations that modify the output format according to other needs. Some standards we would also like to support are:
Source Code
Some projects and corporations have precise rules regarding the files present in their software distributions. The W3C XHTML 1.0 Transitional standards can be used to satisfy most of the needs in this sense. It means that all HTML files delivered with the V3 code must be compliant to those standards.
Not only must the plain source code of the editor be compliant to the XHTML 1.0 Transitional standards. Any piece of HTML rendered by V3, to be injected in web pages, must be compliant to those standards as well.