WML (Wireless Markup Language) as a simple markup language
specifically designed to browse websites and other media on
small phone screens like mobile phones and PDAs and slow
connections.

---> Forgetting that XML Is Case Sensitive
ex:  <name>abc</name> and <Name>abc</Name> <NAME>abc</NAME>
both 3 are different

---> Forgetting of End Tags
<name>abc

---> Forgetting the Quotes for the Attribute Value
<name preferred=true>abc</name>  --- error
<name preferred-"true">abc</name> --- oh yeah


---> Typing Spaces in the Name of the Element
<my name>
......
</my name>  --- :(

<myname>
......
</myname>  --- :) :))

<document id="1234">
   <content-type></content-type>
   <data name="blabla" org-name="titi"></data>
</document>
 xml attributes & xml elt names declare here i think this is
best way 
here if use xslt sheet tags also <document-id> like ...


cheers

sree

XML is a set of standards to exchange and publish
information in a structured manner.

XML is a language used to describe and manipulate documents
that follow a structure.

DOM (Document Object Model) and SAX (Simple API for XML) are
APIs to access XML documents. They allow applications to
read XML documents without having to worry about the syntax.
They are complementary: DOM is best suited for browsers and
editors; SAX is best for all the rest.

SOAP-DSIG is used to satisfy the message authentication 
requirement. It is important to note that you can use SOAP-
DSIG and SSL simultaneously by exchanging 


    the above HTTP messages over SSL.     





Technology Satisfied security requirements 
SSL Confidentiality, sender/recipient authentication, and 
message authentication by MAC 
SOAP-DSIG Message authentication by digital signature and 
MAC 


        SSL provides confidentiality and sender/recipient 
authentication. SSL also has functionality for adding MACs 
to transmitted messages. On the other hand, 


SOAP-DSIG can be used to add not only MACs but also digital 
signatures to transmitted messages, but it is not 
sufficient for sender/recipient authentication 


because it is vulnerable to attacks such as replay attacks. 
Therefore, SOAP-DSIG and SSL complement the functionalities 
that the other system lacks. 

         

         Remember that in order to satisfy the requirement 
of non-repudiation, at a minimum you need to simultaneously 
guarantee both message authentication by using a 

        digital signature and sender authentication. 
Therefore, using SOAP-DSIG and SSL (with client 
authentication) simultaneously is the first step towards 
realizing non-        repudiation. Specifically, you use 
SOAP-DSIG for message authentication by using a digital 
signature and SSL client/server authentication for 
sender/recipient authentication.

At a minimum, all you really need is an XML processor and 
an HTTP server.If you're using Visual Basic 6.0 or VBA, 
then you probably want to use either Microsoft SOAP Toolkit 
or PocketSOAP. If you're using VB.NET or C#, then you       
probably want to use Visual Studio.NET or the .NET 
Framework. If you're using Delphi, then you want to use 
Borland's Web services support in Delphi. If you're       
using C++, then you probably want to use Systinet WASP 
Server for C++ or gSOAP. If you're using Java, then you 
have a choice of about a dozen     implementations (Apache 
Axis, Systinet WASP Server for Java, The Mind Electric 
GLUE, Cape Clear Cape Connect, IONA XMLBus, BEA Workshop, 
etc.)

 

            Favorite Java environments are WASP, GLUE, and 
Axis. All offer excellent tools, they're portable across a 
wide range of servlet engines, and they work!WASP and GLUE 
can run standalone.

The difference lies in where the error occurs - on the 
client side (during the generation of the soap request or 
the unmarshalling the response) - or on the server side 
(when unmarshalling the request, processing the message or 
marshalling the response). The client side raises an 
exception  whereas the server side sends a SOAP response to 
the client indicating an error occured on the server side 
(ie. you get a SOAP fault). 

        For example, sending a SOAP encoded request for a 
method that does not exist results in a SOAP fault whereas 
if the server sends a response with a field that does not 
exist in a client side class a SOAP exception will be 
raised.