Forum Moderators: phranque
Could I use XML/.NET right now without a hitch -- or would my work spoil in anything but newer browsers or something?
Also, I mean either using XML or .NET -- I know they're two separate things but .NET uses XML.
Thanks for any help on this, I'm quite lost as you can tell.
As for .NET it will never really penetrate the *nix developers, so whether it really becomes wide spread is questionable.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
All I want to do is validate my document at XHTML 1.0 Transitional. What I don't get is the second portion of the code :: <html...> :: I see it on many Web sites after viewing the source.
I understand lang="en" simply classifies the element by its language --english...and that xmlns is a namespace or something--
Are these pages using XML from a database, or is this simply mark-up for XHTML.
Thanks for any help.
It is creating a namespace for your document. When we all go full blown xml every document will need one. You have schemas and dtds that tell your parser what your made up tags should be interpreted as. How many <book> or <price> tags do you think will be floating around. The namespace gives it a way of making those pages unique to your dtd or schema.
This is just regular mark up. Notice the name space goes to the w3.
To answer your question about xml and .net, yes. I am currently creating sites in both .net and xml. With xml you must translate it into html for browsers to understand it. This is xslt. .Net uses a form of xslt to translate from its native xml to aspx pages. Xml is very handy with huge database web farms. If you have large oracle or sql server databases then you are probably using xml.
Data driven sites like google use xml exstensivly.
HTML will always be the end language of the web browser, but these other technologies will ride on top of it for more dynamic and interactive applications.
.NET is Microsofts attempt to corner the web services market, but there are alternatives to .NET - virtually any J2EE situation will offer the same functionality.
For more information about the future of web services and software to support it, take a look at www.silverstream.com, www.xmlspy.com, and if you can find the April issue of BUSINESS 2.0 magazine (might be on line) there is a good article about companies that are actually using web services.
I am planning to learn about all this.
