Tuesday, June 10, 2008

XML: How to get the benefits without the heartache, part 2

    "From bitter experience, I have learned that the only way to approach document-centric XML applications is from the content creation and modification side of the application functionality spectrum. There is little point in having a wonderful back-end system for content management and exploitation if there is no author-friendly way of creating and modifying that content."-- XML: How to get the benefits without the heartache, part 2


Oisin McGuinness said...

Interesting article, but the 1st two links to "part 1" on itworld.com point to a flash drive article, and various searches on itworld.com don't turn up "part 1". The link to your previous columns at the end of the article also don't have "part 1" in them. Can you post a link to "part 1"?


Oisin McGuinness

Sjoerd Visscher said...

Why do you call XML-aware editing tools "classic"?

Sean said...


I call them "classic" because they use long established standards and principles: the pre-eminence of structure, permanent validity w.r.t. a schema etc.


Sjoerd Visscher said...

Of course I ask because I work on Xopus, where we try hard not to be "classic". Certainly the structure in Xopus isn't pre-eminent.

So if you agree that Xopus isn't a "classic" XML-aware editor, and so your criticism doesn't apply to it, then I agree with what you wrote.

<spam>And then I would add that Xopus is the best of both worlds.</spam>