XML Turns 5 36
GiMP writes "According to the World Wide Web Consortium, XML turns 5 years old today. XML is used by many programs as a generic container for data. Applications range from websites, to word processor documents, to video games. It seems like only yesterday it was only a working-draft."
Long let it reign (Score:1)
Quite old.. (Score:2, Interesting)
XXML (Score:5, Funny)
XXXML, or extensible extensible extensible markup language, is expected to undergo widespread early adoption by pr0n sites, as it permits a hitherto unimaginable flexibility in permutations and combinations of content...
Re:Quite old.. (Score:5, Funny)
<reply type="flame">
<quote><text><sentence type="question" language="english"> I wonder what replacements are in development, if any?</sentence></text></quote>
<text><sentence type="answer" language="english">Hopefully a more compact format.</sentence></text>
</reply>
Re:Quite old.. (Score:2)
Especially when you have to entity-encode all of them for a Slashdot comment!
Seriously, the point is to make it programmatically accessible/writeable and human-readable, not necessarily easy to hand-type. (Despite the fact that many apps using XML (Tomcat, Ant, others) tend to have hand-written XML files.)
Compact or SUV (Score:3, Insightful)
And here, all this time I thought bigger was better.
In any case, this point always comes up. "XML is too verbose." But a certain amount of verbosity in programming is good (vis Python vs APL) though too much is bad (Cobol vs Java).
So is XML too verbose?
Given the right tools we could easily transform "<quote><text><sentence type="question" language="english">" reversably (thats important) to "<q><t><s t="q" l="e">" which certainly is less verbose. I'd be willing to bet that most XML DTDs/Schema would allow for most tags to be reduced to one or two alphabetic characters (that would be 700+ different elements). If thats too much you could build a simple tool defaulting the attributes, eliding the close "</...>" bits quoting unquoted attributes and so on. Which could give us "<q><t><s t=q>". Too verbose still? I could easily go a few steps further but won't.
In any case, the challenge for those who find XML verbose is to find an isomorphic representation. That is a representation R and transformations XR taking XML to the other representation and RX going the other way so that XR(RX(text)) = text that is less verbose. Lots of people will thank you I expect.
Umm... (Score:1)
Get any cool presents?
Daniel
well then (Score:5, Funny)
Re:well then (Score:3, Funny)
Re:well then (Score:1)
Not to mention that a song should not be published on-line without some proper sort of DRM protection.
The RIAA will not be happy about this.
Re:well then (Score:4, Funny)
Just think, if we spoke XML, we could easy exchange data between people without speaking their language!
Re:well then (Score:3, Insightful)
Daniel
Re:well then (Score:2)
The funniness of your parent comment lies in the fact that all these buzz-word "synergists" thing that XML is the cure all. And the comment is poking fun of that in an angry but correct sort of way.
Re:well then (Score:1)
Oh well, I didn't pick up the irony when I read it. Shoot.
Daniel
xml turns 5... (Score:3, Funny)
Re:xml turns 5... (Score:5, Interesting)
XML's self-description is one layer deep: data and metadata are packaged together. This layer can be seen as one layer of insulation against obsolescence: so long as the metadata remains meaningful, the meaning of the data can be ascertained and recovered. But the metadata is itself data, and if it too loses its meaning then it will be of no help at all.
For any data at all to have a semantic value it must have a context, and contexts change over time. XML is meant to ease the translation of data between contexts, but it cannot preserve meaning for all time.
Re:xml turns 5... (Score:3, Interesting)
Re:xml turns 5... (Score:2, Interesting)
Quite so; a recent attempt at preserving old media is noted here [slashdot.org].
With this in mind, may I direct the attention of budding geek archivists and antiquarians to Bruce Sterling's (and others') Dead Media Project [deadmedia.org], which seeks to document and analyse the conditions surrounding the life and death of media?
Re:xml turns 5... (Score:2)
Get Facts Straight. (Score:3, Funny)
Well, even though "XML" doesn't obey proper grammatical rules, this Roman figures it to add up to one thousand forty.
Plus, most people know that 1040 is associated with April 15 (at least in the USA)..
Re:Get Facts Straight. (Score:2)
X = 10
M = 1000
L = 50.
10 + 1000 + 50 = 1060
That's not 1040... Maybe if you do a permutation, you'd have
MXL or XLM both of which could add up to 1040... but X + M + L = 1060.
Sorry, it just doesn't work.
Re:Get Facts Straight. (Score:3, Funny)
Smaller numbers to the left of larger numbers are subtracted instead of summed.
Good thing tax returns are in Arabic. The Romans would not have tolerated these kinds of arithmetic mistakes,
Re:Get Facts Straight. (Score:2)
If you address each letter individually, or vaguely attempt to address it as a whole.
Yet, if I say IIIV , it is not 2 in Roman numerals. It's just a really messed up number.
Still a toddler... (Score:5, Insightful)
Whenever I look at the last ten to fifteen years of computing history, I am utterly amazed. Think about this: during the Gulf War, with all its high-tech-ness, the best PCs were 386s or low-end 486s, and the best Sun workstations were the lower-end SPARCstations (i.e., perhaps a 40MHz CPU, probably 30MHz).
Whenever I see people who are totally overwhelmed by the almost unbounded number of buzzwords, platforms, and dozens of ways to accomplish the same task, I try to remember that nearly everything we take for granted today was popularized in the last decade (often just in the last five years, like XML). There is a quote in the Solaris Internals book that says there were 3000 UNIX systems in 1982 (or 83). There are several orders of magnitude more systems today. No other time in human history have we had to cope with this sort of change in so short a time.
Still not easy to use for C programmers... (Score:1)
Seems to me this would've been good from the beginning. Sure, we've got things like libexpat, etc. but there's no really easy way to say, convert your C-style structs directly to XML constructs for easy streaming...
Re:Still not easy to use for C programmers... (Score:2)
C really should have reflection, shouldn't it?
In e.g. Ruby or Guile, this would be easy as pie.
BTW, It's really hard to parse XML in i386 assembler, any hints? :)
Re:Still not easy to use for C programmers... (Score:1)
What I meant was, after 5 years there is still no easy way to just take your struct's from
XML is great. I use it all the time in the other languages I use.
But its just not so easy in C
These sort of specs can have that sort of effect on language, it seems
I dunno how I didn't manage to say that in the original post, I guess I should've previewed.
SGML (Score:1, Interesting)
the idea of structured text isn't THAT new!!
XML may collapse under its own complexity (Score:2, Informative)
XML Sucks! (Score:1)
ahh, I remember my 5th birthday... (Score:1)