Want this question answered?
XML
the function of xml tags is to display to web browser kind of applications, such as html, but with tags which one you wanna to type.
That would refer to the location of the style sheet for your XML document
==VRML and XML== ==VRML== VRML stands for Virtual Reality Modeling Language, anteriorly Virtual Reality Markup Language. VRML is to create 2D and 3D objects to be viewed on the web. ==XML== XML stands for Extensible Markup Language. It's the base of numbers of web desing codes as HTML or XHTML
You can use xml tags to enclose data and carry it over the web onto web pages and display. Lets say you have an xml of courses and you wnat to show it, you would have data like course title, course description etc, you simply create your tags in xml like <course titile> put your course title here</course title> and so on, the resulting xml file (containing your data) could be easily displayed over the internet.
XML
XML Web services offer a simpler model for distributed applications than that provided by .NET Remoting. XML Web services are fine-tuned for Internet scenarios and cross-platform use. Although you can apply .NET Remoting in these scenarios, thanks to its SOAP formatter and HTTP channel, .NET Remoting is more suitable as a high-speed solution for binary communication between proprietary .NET components, usually over an internal network. And although XML Web services can't match the communication speed of .NET Remoting over a binary channel, they still lend themselves to high-performance designs thanks to their stateless nature and ASP.NET's multithreaded hosting service. Here's a quick overview of the major differences between the XML Web service and .NET Remoting technologies: * XML Web services are more restricted than objects exposed over .NET Remoting. An XML Web service works in a similar way to a SingleCall .NET Remoting object. It isn't possible to create a singleton or a client-activated object. * Because of the restricted nature of XML Web services, the design issues are simplified. XML Web services are generally easier to create than remotable components (and easier to design well). * Communication with .NET Remoting can be faster than XML Web service communication if you use a binary formatter. XML Web services support only SOAP message formatting, which uses larger XML text messages. * XML Web services support open standards that target cross-platform use. For example, each .NET XML Web service has an associated WSDL document that describes how a client can interact with the service. Therefore, any client that can parse an XML message and connect over an HTTP channel can use an XML Web service, even if the client is written in Java and hosted on a UNIX computer. * XML Web services are designed for use between companies and organizations. They can use a dynamic discovery mechanism or a UDDI registry that "advertises" services to interested parties over the Internet. * XML Web services don't require a dedicated hosting program because they are always hosted by ASP.NET. That also means that they gain access to some impressive platform services, including data caching, Web farm-ready session state management, authentication, and an application collection for global, shareable objects. These features, if required, can be extremely difficult to re-create by hand in a component exposed through .NET Remoting. * Because XML Web services work through Microsoft Internet Information Services (IIS) and ASP.NET, they can communicate with clients using the default HTTP channel (usually port 80). This means that consumers can use XML Web services just as easily as they can download HTML pages from the Internet. There's no need for an administrator to open additional ports on a firewall. source - http://www.microsoft.com/mspress/books/sampchap/6723.aspx [utsav.verma at gmail.com]
XML (eXtensible Markup Language) is a set of rules for encoding documents. The rules could describe anything from the rules of HTML to various file formats. WSDL (Web Services Description Language) provides a model for describing web services. WSDL uses the XML to specify its rules.
XML is actually highly flexible and so has many benefits and advantages, however on the downside it can be quite verbose for certain applications like in web services.
The term Web services describes a standardized way of integrating web based applications using the XML, SOAP, WSDL and UDDI open standards over an internet protocol backbone.
XML is far better for data storage, JSON seems to be used more often for web services, api and the like.
Robert Tabor has written: 'Microsoft .NET XML Web Services' 'Poetical Relationships'
There are many websites and schools offline that offer various courses on the subject of web services. However, those courses often require previous knowledge of HTML and XML.
xml is used on webpages and web services and can also be used to create data bases and to store and carry data.
If you open the xml in most web browser it will state an error code denoting the type of malformation of the xml. you can use an xml tool like an xml editor to validate and correct your xml.
xml is a markup language that is used ti dispplay data and web pages as intended. XML has no semantic menating and you create your own tags in accordance with xml specifications.
the function of xml tags is to display to web browser kind of applications, such as html, but with tags which one you wanna to type.