HTML
  Home arrow HTML arrow Page 4 - W3C Web Standards
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
HTML

W3C Web Standards
By: Justin Cook
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 36
    2004-04-12

    Table of Contents:
  • W3C Web Standards
  • An Eagle's-Eye View
  • First Component: XHTML
  • Attributes
  • Second Component: CSS2
  • Code Explanation
  • Third Component: ECMAScript

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    W3C Web Standards - Attributes


    (Page 4 of 7 )

    A rule that applies to attributes as well as the element they describe, is that they must be in lowercase. That's fine for most of us, but some may have to change their coding style, or even the IDE they use.
    Also, attribute values must always be quoted, even if we're dealing with numeric values.

    Oh and one more thing, no more minimization. This means that


    <hr noshade>

    must now be written as:


    <hr noshade=”noshade” />

    What's My Name?

    XHTML 1.0 has deprecated the 'name' attribute, and further versions will drop it altogether. That means we will identify elements by their 'id'. We'll see the use of this as we get into the style sheets.

    XML / DOCTYPE / NameSpace

    We need to define that our page is complying with the rules, and here's how we do it, at the top of every page.


    <?xml version="1.0"? >
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional //EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

    It's best to use the transitional Document Type Definition while we're getting accustomed to the ins and outs of Web Standards. And really, we only need the XML declaration if the character encoding is anything other than UTF-8 or UTF-16.

    And that's about it for a brief overview of XHTML, we can get into the meat now!

    More HTML Articles
    More By Justin Cook


       · Nice article Justin. Clear quiet a few things related to W3C Web Standards.
       · Hi,I have a doubt on this... Is it web standards or xhtml tutorial?
     

    HTML ARTICLES

    - Comparing Browser Response to Active Client ...
    - Testing Browser Response to Active Client Pa...
    - Active Client Pages: Completing the Code for...
    - ACP and Browsers: Setting up an Example
    - How Browsers Respond to Active Client Pages
    - Completing a Tree with Active Client Pages
    - HTML Form Verification and ACP
    - Building an ACP Tree
    - Completing an ACP 3D HTML Table Image Gallery
    - Building an ACP 3D HTML Table Image Gallery
    - A Multiple Page Image Gallery with Active Cl...
    - Building an Image Gallery with Active Client...
    - Concluding a Menu for All Browsers
    - A Vertical Menu for All Browsers
    - Downloading Long HTML Pages with ACP







    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 3 Hosted by Hostway
    Stay green...Green IT