This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

XML Data Apps

Stefan Tilkov,

Mark Nottingham on using XML in data-oriented apps. I’m puzzled by his scenario 1:

If you’re thinking in terms of Infosets, XQuery Data Models and the like, your data model is based on XML. This is the approach extolled by most Web services proponents, often through the use of XML Schema-aware tools that bind XML to objects.

I feel that this is a paradox — I would divide that into 1a) the folks who think in the term of XML as a serialization format and 1b) those who want to work with XML documents because they see them as the core benefit of a Web services-based solution.

On March 3, 2005 4:25 PM, Mark Nottingham said:

I think your 1a is my 1, and your 1b is my 2a. Is there something I’m missing?


On March 3, 2005 4:37 PM, Mark Nottingham said:

Oops, sorry - switch those two.

On March 3, 2005 5:20 PM, Stefan Tilkov said:

Your 1 describes folks that mis-use XML as a record-data serialization format. Your 2 describes folks who use UML or RDF.

Where are those who think in terms of documents and describe them with Relax NG? They don’t seem to fit in your 1 or 2. Yet those folks do think in terms of XML - where would you put them?

On March 4, 2005 11:13 PM, Mark Nottingham said:


I talked about the problems of using XML as a serialisation format in 2a; 1 is about modelling your data in XML. RelaxNG would fit into 1.

On March 4, 2005 11:40 PM, Stefan Tilkov said:

Why then do you talk about “often through the use of XML Schema-aware tools that bind XML to objects” in scenario 1? That sounds to me like something belonging firmly in the 2 camp :-)