[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xml-dev
Subject:    Re: [xml-dev] Four fine text-based data formats ... liberate yourself from one (silo) data format
From:       Liam R E Quin <liam () w3 ! org>
Date:       2013-03-25 22:37:44
Message-ID: 1364251064.23240.137.camel () localhost ! localdomain
[Download RAW message or body]

On Mon, 2013-03-25 at 09:10 -0400, Simon St.Laurent wrote:

> I have severe problems with using schemas to lurch toward the maximum 
> possible straitjacket that can fit some part of a problem.

You could replace "schemas" in there with "leather straps" or "UML" or
almost any sort of constraining technology.

XML Schemas are not a substitute for thinking and understanding. Neither
(as others have said) do they necessarily enforce a waterfall model.
Continuous refinement and agile spirals are equally possible.

A lot of people came to SGML and XML from "big engineering", civil
engineering (leather straps, I think, are not very civil) and were used
to the idea that you do a formal specification before you try building
anything.

A lot of money gets wasted that way, but on the other hand agile
development for aircraft or space rocket design also has problems. The
cost of experimentation is too high, so you use simulations, and tests,
ideally a long way away from anywhere else, e.g. in Sim-mule Asian
Cities.

You could argue that publishers enforce a waterfall too - first the book
proposal, table of contents, sample chapter, then the agreed-upon
outline and schedule, and then a sequence of words, magically followed
by publication of a physical object. In fact, of course, the proofing
and editing cycle can also be a spiral, and the final book doesn't need
to be very linear (it's hard to make an effective narrative within a
non-linear rhetorical framework but see e.g. "Patchwork Girl").

So when you rail against XML and say how much more comfortable you are
with JSON, it sounds to me as if you're really railing against those
shoe-wearing bureaucratic civil engineers who wanted
first-this-then-that.

I agree that's a problem, although if several different organizations
are involved it's often necessary politically if not technically, and
the schema there can help (as David and others suggest) as a sort of
documentation.

Liam



-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php


[prev in list] [next in list] [prev in thread] [next in thread]