11+++
2- title = ' StandardsReport '
2+ title = ' Why Should Businesses Care About Web Standards? '
33date = 2006-10-07T19:51:00+00:00
44draft = false
55description = ' Converted from twiki - v1.5'
66cover.hidden = true
7- # tags = []
7+ author = " Cynthia Manuel"
8+ tags = [' edge-report' ' standards'
89+++
910
10- %META: TOPICPARENT {name="[ EdgeReports] ( EdgeReports " wikilink ") "}%
11-
12- ### Why Should Businesses Care About Web Standards?
13-
14- By: Cynthia Manuel
15-
16- The World Wide Web began as a networked information project at \< a
17- href="< http://www.cern.ch/ > " target="\_ blank"\> CERN\< /a\> , where Tim
18- Berners-Lee, now Director of the \< a href="< http://www.w3.org/ > "
19- target="\_ blank"\> World Wide Web Consortium\< /a\>
20- \[ [ W3C] ( W3C " wikilink ") \] , developed a vision of the project to
21- disseminate scientific literature. In October 1994, Lee, founded the
22- World Wide Web Consortium ([ W3C] ( W3C " wikilink ") ) at the \< a class=elnk
23- href="< http://web.mit.edu/ > " target="\_ blank"\> MIT\< /a\> ,\< a
24- href="< http://www.csail.mit.edu/index.php > " target="\_ blank"\> Laboratory
25- for Computer Science \[ MIT/LCS\]\< /a\> where, in collaboration with
26- CERN, the Web originated, with support from \< a class=elnk
27- href="< http://www.w3.org/Consortium/Prospectus/DARPA > "
28- target="\_ blank"\> DARPA\< /a\> and the \< a href="< http://europa.eu > ."
29- target="\_ blank"\> European Commission.\< /a\>
11+ The World Wide Web began as a networked information project at
12+ [ CERN] ( http://www.cern.ch/ ) , where Tim Berners-Lee, now Director of the
13+ [ World Wide Web Consortium (W3C)] ( http://www.w3.org/ ) ,
14+ developed a vision of the project to disseminate scientific literature. In
15+ October 1994, Lee, founded the
16+ World Wide Web Consortium ([ W3C] ( http://www.w3.org/ ) ) at the
17+ [ MIT] ( http://web.mit.edu/ )
18+ [ Laboratory for Computer Science (MIT/LCS)] ( http://www.csail.mit.edu/index.php )
19+ where, in collaboration with CERN, the Web originated, with support from
20+ [ DARPA] ( http://www.w3.org/Consortium/Prospectus/DARPA ) and the
21+ [ European Commission] ( http://europa.eu ) .
3022
3123The World Wide Web is an application built on top of the Internet and,
3224as such, has inherited its fundamental design principles:
3325
34- \< ul \> \< li \> Interoperability: Specifications for the Web's languages
35- and protocols must be compatible with one another and allow any hardware
36- and software used to access the Web to work together.\< /li \>
26+ - Interoperability: Specifications for the Web's languages and protocols must
27+ be compatible with one another and allow any hardware and software used to
28+ access the Web to work together.
3729
38- \< li \> Evolution: The Web must be able to accommodate future
30+ - Evolution: The Web must be able to accommodate future
3931technologies. Design principles such as simplicity, modularity, and
4032extensibility will increase the chances that the Web will work with
4133emerging technologies such as mobile Web devices and digital television,
42- as well as others to come.\< /li \>
34+ as well as others to come.
4335
44- \< li\> Decentralization: Decentralization is without a doubt the newest
45- principle and most difficult to apply. To allow the Web to scale to
46- worldwide proportions while resisting errors and breakdowns, the
47- architecture (like the Internet) must limit or eliminate dependencies on
48- rigid hierarchies.\< /li\>\< /ul\>
36+ - Decentralization: Decentralization is without a doubt the newest principle
37+ and most difficult to apply. To allow the Web to scale to worldwide
38+ proportions while resisting errors and breakdowns, the architecture (like the
39+ Internet) must limit or eliminate dependencies on rigid hierarchies.
4940
50- > > * "Lack of standards makes websites more expensive for clients and
51- > > developers, makes pages break for users, and will break the web
52- > > itself, unless the situation improves."* Â \< a
53- > > href="< http://www.webstandards.org > " target="\_ blank"\> Web Standards
54- > > Project\< /a\>
41+ > Lack of standards makes websites more expensive for clients and
42+ > developers, makes pages break for users, and will break the web
43+ > itself, unless the situation improves.
5544
56- \< /blockquote \>
45+ (from the [ Web Standards Project ] ( http://www.webstandards.org ) )
5746
5847When we speak about standards for the Web, we are speaking of the
5948standards established by the [ W3C] ( W3C " wikilink ") for the core
6049technologies that constitute the World Wide Web:
6150
62- \< ul\>\< li\> Structural Languages\< /li\> \< ul\>\< li\>\< a
63- href="< http://www.w3.org/TR/html4/ > " target="\_ blank"\> HTML
64- 4.01\< /a\>\< /li\> \< li\>\< a
65- href="< http://www.w3.org/TR/2000/REC-xml-20001006 > "
66- target="\_ blank"\> XML 1.0\< /a\>\< /li\>\< /ul\>\< /ul\>
67-
68- \< ul\>\< li\> Presentation Languages\< /li\> \< ul\>\< li\>\< a
69- href="< http://www.w3.org/TR/REC-CSS1 > " target="\_ blank"\> Cascading Style
70- Sheets 1\< /a\>\< /li\> \< li\>\< a href="< http://www.w3.org/TR/CSS2/ > "
71- target="\_ blank"\> Cascading Style Sheets 2\< /a\>\< /li\> \< li\>\< a
72- href="< http://www.w3.org/TR/xsl/ > " target="\_ blank"\> XSL (under
73- development)\< /a\>\< /li\>\< /ul\>\< /ul\>
74-
75- \< ul\>\< li\> Object Models\< /li\> \< ul\>\< li\>\< a
76- href="< http://www.w3.org/DOM/ > " target="\_ blank"\> Document Object Model
77- 1 Core HTML/XML\< /a\>\< /li\>\< /ul\>\< /ul\>
78-
79- \< ul\>\< li\> Scripting\< /li\> \< ul\>\< li\>\< a
80- href="< http://www.ecma.ch/ecma1/STAND/ecma-262.htm > "
81- target="\_ blank"\> ECMAScript\< /a\> (the "official" version of
82- JavaScript)\< /li\>\< /ul\> \< ul\>\< li\>\< a
83- href="< http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference > "
84- target="\_ blank"\> Mozilla Developer
85- Documentation\< /a\>\< /li\>\< /ul\>\< /ul\>
51+ - Structural Languages
52+ - [ HTML 4.01] ( http://www.w3.org/TR/html4/ )
53+ - [ XML 1.0] ( http://www.w3.org/TR/2000/REC-xml-20001006 )
54+
55+ - Presentation Languages
56+ - [ Cascading Style Sheets 1] ( http://www.w3.org/TR/REC-CSS1 )
57+ - [ Cascading Style Sheets 2] ( http://www.w3.org/TR/REC-CSS2 )
58+ - [ XSL (under development)] ( http://www.w3.org/TR/xsl/ )
59+
60+ - Object Models
61+ - [ Document Object Model 1 Core HTML/XML] ( http://www.w3.org/DOM/ )
62+
63+ - Scripting
64+ - [ ECMAScript] ( http://www.ecma.ch/ecma1/STAND/ecma-262.htm ) (the "official" version of JavaScript)
65+ - [ Mozilla Developer Documentation] ( http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference )
8666
8767... as well as emerging standards, such as those for television-based
8868and PDA-based browsers.
8969
90- \< H4 \> So What Does All This Mean to the Bottom Line?\< /H4 \>
70+ #### So What Does All This Mean to the Bottom Line?
9171
9272By deploying Internet solutions that rigidly adhere to the core web
9373technologies, you:
9474
95- \< ul\> \< li\> Ensure both forward and backward compatibility with the
96- browser and system of your visitor.\< /li\> \< li\> Gain greater visibility
97- in Web searches. The structural information present in standards
98- compliant documents makes it easy for search engines to access and
99- evaluate the information in those documents, and they get indexed more
100- accurately.\< /li\> \< li\> Can easily convert your content to other
101- formats, such as databases or Word documents. This allows for more
102- versatile use of the information within your company and greatly reduces
103- both web and print production costs.\< /li\> \< li\> Guarantee your ability
104- to migrate your content to new systems as they are developed - hardware
105- as well as software - including devices such as TVs and
106- PDAs.\< /li\>\< /ul\>
75+ - Ensure both forward and backward compatibility with the browser and system of
76+ your visitor.
77+ - Gain greater visibility in Web searches. The structural information present in
78+ standards compliant documents makes it easy for search engines to access and
79+ evaluate the information in those documents, and they get indexed more accurately.
80+ - Can easily convert your content to other formats, such as databases or Word
81+ documents. This allows for more versatile use of the information within your
82+ company and greatly reduces both web and print production costs.
83+ - Guarantee your ability to migrate your content to new systems as they are
84+ developed - hardware as well as software - including devices such as TVs and PDAs.
10785
10886The most basic consequence of ignoring standards when deploying your
10987Internet solution is that you will restrict access to your site. How
@@ -112,7 +90,7 @@ fraction of those who wish be a part of it? Denying access to even small
11290portions of a target audience can make a big difference to your profit
11391margin.
11492
115- \< H4 \> FINI Takes Standards Based Architecture a Step Further\< /H4 \>
93+ #### FINI Takes Standards Based Architecture a Step Further
11694
11795By rigidly adhering to the standards of the core technologies while
11896developing solutions, we discovered that we could create a single
@@ -122,7 +100,6 @@ that look and work the same regardless of what browser, system or device
122100is being used to access the site.
123101
124102If you would like more information about the standards based, single
125- version Internet solutions that we are deploying please call or \< a
126- href="[ mailto:info@fini.net ] ( mailto:info@fini.net ) "\> email us\< /a\>
127- today. We are eager to share with you our mechanics for online
128- profitability. We promise you will be amazed!
103+ version Internet solutions that we are deploying please call or
104+ [ email us] ( mailto:info@fini.net ) today. We are eager to share with you our
105+ mechanics for online profitability. We promise you will be amazed!
0 commit comments