IMHO, XML still has to become used much wider than it is right now. As client-side XSLT support increases our web applications will soon enough start spitting XML to the browser instead of (X)HTML.Originally Posted by momos
| SitePoint Sponsor |


IMHO, XML still has to become used much wider than it is right now. As client-side XSLT support increases our web applications will soon enough start spitting XML to the browser instead of (X)HTML.Originally Posted by momos
There’s more than one way to skin a cat.
XSLT is used already for these things, but most of the time it is parsed(to XHTML) on the server.
btw XHTML is XML


This is my point exactly. If clients had a better XSLT support there will be no need to do the transformations on the server side, which IMO not only simplify things for application development but it's the way it should be done. Moreover, and going quite off topic, clients should ideally have to handle content type negotiation themselves and avoid the burden on the server side.Originally Posted by momos
Don't want to start yet another endless discussion, but I don't think so.Originally Posted by momos
.XHTML is a family of current and future document types and modules that reproduce, subset, and extend HTML 4. (W3C Definition)
There’s more than one way to skin a cat.




Those are the only encodings really really necessary. The others can be ignored, including "e;.Originally Posted by wwb_99
libxml2 is far from a simple printfOriginally Posted by wwb_99




In a non-pedantic sense it is: "Whereas HTML was an application of SGML, a very flexible markup language, XHTML is an application of XML--" (Wikipedia)Originally Posted by nacho


Originally Posted by Ezku
Being accurate is being pedantic?
There’s more than one way to skin a cat.
I'm with Ezku!


Of course you are.Originally Posted by momos
![]()
It's also rather interesting to see that you both give more value to a definition in a wiki than to that one given by W3C, but oh wait, am I being pedantic again, or is it cynical this time?
Back to topic?![]()
There’s more than one way to skin a cat.


We've already talked about the relationship between XHTML and XML.
http://www.sitepoint.com/forums/show...5&postcount=11




Say I have a lollipop. I say "this is candy". Am I incorrect? Now replace the lollipop with an XHTML document and candy with XML.
You fail to realise that those two by no means contradict each other.Originally Posted by nacho
But yeah, let's not drag this any longer![]()


It all depends on how you define "is".
Do you mean that a is b if all elements of a are an element of b?
Or do you also require that all elements of b are an element of a?


Wow... I didn't realize that we had to put XHTML in a single box.
From what I've read so far XHTML is a descendant of HTML 4. It extends it but it also a valid XML document.
So with that in mind it's both XML and HTML (hey! maybe that's why it's called XHTML... I feel the cynical in me wanting to take the keyboard)
Don't start doubting Myrdhrin, it is exactly what you are saying


So why wasnt a universal binary format developed? If most of the parsing is done by computers, it would be easier for a computer to read binary forms, rather than parsing text.Originally Posted by timvw


wouldnt be any differnt though if it was some other storage format. If flash supported an odd binary format, the same could be said.Originally Posted by Eric.Coleman


Don't blame me for that :POriginally Posted by psyon
Edit: That is why they are trying to push binary xml now, not?
(I wanted to ask: Why do most linux distros use plain text in /etc instead of a binary register? But that's not completely right because you have a human <-> machine interaction there instead of a machine <-> machine)


I can send 4 bytes representing an integere over a network connection. This value represents the length of the data to follow. I just described the data, but its not human readable.Originally Posted by ronanmagee

HTTP Headers are also only used for machine-machine communication, yet they chose to make it plain english and readable. Is it so that people can use netcat to talk to webservers and read webpages? Doubtful...




Isn't it funny that on every thread there always is someone who can continue complaining about something, and when that someone quits complaining, there is always someone who can complain more.Originally Posted by psyon
Don't like XML ? Don't use it. Maybe you are one of those people who can read the following:
EEF072 AB23A1 F15676 F5416S F1F415 765172 B0B98A 67BC45
you can find good example of xml scripts at this website http://www.kissmobilescripts.com




bonefry, I don't see anyone complaining in this thread. What I see is people asking other people why they use XML and what its advantages are. When the arguments for using XML that are given are not very good and can be countered with other arguments, and people from both sides persevere at that, do you see that as complaining?
The reason that people are - what you call - complaining about XML may very well be a good indicator that something is wrong with it or at the very least that it is not all what it's cranked up to be.
If the people complaining were vendors of some XML alternative it would be a different situation of course, but I don't believe any posters here have special business interests in questioning XML.
I once had a problem.
I thought: "Oh, I know: I'll just use XML!"
Now I had two problems.
If you had read just a bit further you would see the phrase:Originally Posted by nacho
XHTML 1.0 (this specification) is the first document type in the XHTML family. It is a reformulation of the three HTML 4 document types as applications of XML 1.0


Please, don't be ridiculous. Do you really think I would point to W3C without ever having read the specifications? I know exactly what XHTML stands for, and that's exactly why I reacted to momos' comment.Originally Posted by 33degrees
(By the way, have you read it yourself?)Had he said XML and XHTML are both markup languages (i.e. a lollypop is a candy), or XHTML is an application of XML, I had never said anything about it. But he did not. He made a bold assertion, thinking probably that I wouldn't know better.It is a reformulation of the three HTML 4 document types ...
To better reflect my meaning, and making use of Ezku's sweet example:
An apple pie is made of apple, yet IS NOT AN APPLE, is it?.
Having said that, I'd ask once more not to make of this thread a flame war, because it was never my intention. Let's keep focused on what is really relevant. We're not getting anywhere anyhow.
Last edited by nacho; Aug 11, 2005 at 22:12. Reason: typo
There’s more than one way to skin a cat.




This may have been said before, but one reason could be that programs have bugs, and once you have to search for a bug, having information in human-readable format tends to be helpful.Originally Posted by psyon
Dagfinn Reiersøl
PHP in Action / Blog / Twitter
"Making the impossible possible, the possible easy,
and the easy elegant" -- Moshe Feldenkrais




Yes but many arguments aremade to statements ripped out of context.Originally Posted by Captain Proton
And when posting on a thread one should at least read half the comments in there before posting his own oppinion, because an answer to its questions might allready be there. But I saw that many members only read the last 3 comments or so. And at this pace we will never agree on something and the same oppinions that are on page x can be found again on page y.
Bookmarks