H1, As u may know B2B is Business-to-Business. This literally means communication and exchange of valuable data between business. Now, where does XML come in? XML as it's name suggests, is "Extensible". What this means is that You and I can agree upon a format (tags) to communicate with each other. We can thus share data in a format that is understood by both of us. However, we may be using entirely different databases, servers, back ends or whatever. Furthermore, if later, a third person wants to share data with us, and have access to our data (only if we allow it, of course ), then all he has to do is conform to our format (tags). XML will NOT replace databases. It will only supplement them be giving them powerful capabilities. You may be using Oracle and I may be using DB2....but if both these databases support (and they do)..we can exchange data without any interface problems using XML. Hope this helped clarify something.
Joined: Jun 07, 2000
hi trinity, thanx for the explaination it was very good but the thing again which i donot understand is we talk xml in terms of web based B2B right.So now the question is we r using html for transferring the data (using name/value pairs...) .Then whats so special about xml i can use instead of html for transfer the data Let me give an example for this .. HTML VERSION OF B2B... repuest(name/value retrive data pairs dat to server) CLIENT|.........>|SERVER |..........>| response (reads name/val pairs) |<.........|computation |<..........| DATABASE | | | |
XML VERSION OF B2B (xml file ..?) repuest retrive data CLIENT|.........>|SERVER |..........>| response| (processes) | |<.........| if error send |<..........| DATABASE | | response error back| | |(Xml computation) | | If you see the above figure is that(i hope it is correct rectify if iam wrong.....) you find that only difference , between the HTML computation and XML computation, is the XML part. so I donnot think that XML can do something diffreent from HTML.Except for adding an additional burden on the server for parsing the xml document. One more thing as i said parsing of XML document is done on the Server side.It means that the client will send me the data (whether XML doc or name value pairs...?)then i will validate that xml document on server side and send an error if any back to the client Is this going to fisible...? Iam hope u r able to understand my problem so please help.... Will it replace HTML........in terms of DATA HOW..?
I think you are getting a little confused. XML is just a data format. Using XML says nothing about what transport protocols you use to get XML data to where it is needed. XML is just text, it may be stored in a database, stored in a file, transferred using HTTP, transferred using FTP, transferred on a floppy disk, whatever. XML is primarily a replacement for the millions of ill-designed, inflexible, unreadable application-specific formats which already exist, or would need to be created. A common use is the replacement of a somewhat cryptic CSV or TSV file with an XML equivalent. XML confers several major benefits when used like this. All data is marked up by name, so producing a new application whch reads it is easy to do and easy to test; no more 'is column 7 always the city, or just the next line of the address' confusions. Adding a new tag for extra data in a later version is fully backward compatible and needs no changes to old software. XML is by nature a hierarchical format, which allows things to easily be associated in groups and subgroups. B2B use of XML at the moment is mainly about getting shared data formats in place so that data can be transferred in any appropriate way, and be understood at the far end.