HTML 5 is the newest iteration of HTML, the basic language of the Web.HTML 5 will replace both current versions, HTML 4.01 and XHTML 1.0 and DOM Level 2 HTML Before discussing HTML 5, you should be familiar with the basics of how to write HTML code. HTML is very easy to get the hang of, and once you're excellent with writing code in standards-compliant XHTML and also find the new features of HTML 5 to be very easy to implement. Html5 defines the 5 major revision of core language of the world wide web.html5 is combination of new features are introduces for helping to web authors. New features are adding based on research authority practices special thing was defining clear. In rich internet application to reduce the need for property plug. Example of ria is adobe flash and Microsoft Silverlight the rules and regulations of w3c time table html5 will reach the standards by late 2010 .html5 is coming with a lot of new attributes and elements for using the modern web service. it also perform web form 2.0. Html5 specifies scripting programming interfaces. Such as Drag and drop
Timed media play back
Cross document managing
Browser history management.
HTML 5 makes familiar lot of the coding practices that were used in earlier versions of HTML... It aims to reduce the need for proprietary plug-in-based rich internet application (RIA) technologies such as Adobe Flash, Microsoft Silverlight, and Sun JavaFX. HTML 5 also simplifies code by getting rid of elements that have fallen out of use or proved to be unhelpful. Because of an array of browser problems, frames will no longer be allowed, and because style sheets handle style better than HTML tags, "presentational" tags like <font>, <centre> and <strike> will no longer be valid. WS-Security
A flexible and feature-rich extension to SOAP to apply security to Web services is WS-Security (Web Services Security, short WSS). This was published by OASIS and it is a member of the WS-* family of web service specifications. Three main mechanisms are described by WS-Security:
* How to sign SOAP messages to assure integrity. Signed messages provide also non-repudiation. * How to encrypt SOAP messages to assure confidentiality. * How to attach security tokens.
A variety of signature formats, encryptions algorithms and multiple trust domains is allowed by this specification, and is open to various security token models, such as: * X.509 certificates
* Kerberos tickets
* UserID/Password credentials
* Custom defined token
The security features in the header of a SOAP message, working in the application layer was incorporated by WS-Security. To accommodate a wide variety of security models and security technologies this specification can be used in conjunction with other Web service extensions and higher-level application-specific protocols. The typical SOAP use case with a communication between trusted peers (using HTTPS) does not need WS-Security at all. It is described in Alternative, and reduces complexity and improves performance. If a SOAP intermediary is required, and the intermediary is not or less trusted, messages need to be signed and optionally encrypted. This might be the case of an application level proxy at a network perimeter that will terminate TCP connections. The standard method for non-repudiation is to write transactions to an audit trail that is subject to specific security safeguards. However, if the audit trail is not sufficient, digital signatures may provide a better method to enforce non-repudiation. WS-Security can provide this. lthough almost all SOAP services implement HTTP bindings, in theory other bindings such as JMS or SMTP could be used; in this case end-to-end security would be required. Even if the web service relies upon transport layer security, it might be required for the service to know about the end user,...