[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: The relentless march of abstraction (fwd)
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: Dave Winer <firstname.lastname@example.org>, email@example.com
- Date: Wed, 28 Feb 2001 10:12:04 -0600
The problem of the reply is it is unfocused.
I am keeping too many threads in my head at one
time. I apologize if that seems aimed at you
They like the browser for the same reason they
like their refrigerator: easy to use once they
master the controls. They don't mind things
like ice and water dispensers because their
use is obvious on first examination (until they
find out the ice maker can clog). We are
all lazy and past a certain age don't like
to learn new things to replace old things
that worked well-enough. Human-in-the-loop.
Netscape's ambition was to replace the operating
system with the browser, to be a neo-MAC. That
got them into deep kimchi because it took a
refrigerator and turned it into the kitchen.
They got creamed by a kitchen-maker that already
had all the plumbing on the shelf.
What we have to make sure of is that if the
XML processor is servicing the ice-maker on
the refrigerator, it doesn't clog. It is
data plumbing. The browser should be irrelevant
in the sense that the wrapper language handlers
(HTML, X3D, SVG) should not affect the
XML plumbing. Well-formed should be well-formed.
Yet, if we add more PSVI, we are on the slippery
slope Rick Jeliffe talks about.
So, where does it stop and how is it stopped?
XML Schema, like HTML, X3D, SVG is an XML
application language. What special status
does it have with regards to the XML data
model? Is it a refrigerator or a kitchen
(an application or an environment)?
Intergraph Public Safety
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Dave Winer [mailto:firstname.lastname@example.org]
Sent: Wednesday, February 28, 2001 9:51 AM
To: Bullard, Claude L (Len); email@example.com
Subject: Re: The relentless march of abstraction (fwd)
Huh? I think there's a disconnect here Claude.
I don't get how this message is responsive to mine. In fact I agree with a
lot of what you say.
However.. For whatever reason (outside of my control) users find browsers
friendly, and ignore their flaws, and are scared of non-HTML interfaces.
This is what's going on in 2001. Last fall we tried doing it all in an
outliner, and it appealed to people who like and understand outliners, but
that's a very small group of people. When we switched over to rendering in
HTML people got excited. Go figure. I wish it were otherwise.
----- Original Message -----
From: "Bullard, Claude L (Len)" <firstname.lastname@example.org>
Sent: Wednesday, February 28, 2001 7:26 AM
Subject: RE: The relentless march of abstraction (fwd)
> As if HTML were the only rendering language
> and web browsers were the only clients....
> Assertion: Client-side XML depends on the
> services of a robust XML processor to do
> heavy lifting chores. Server side does too.
> The problem is designing messages that
> work well for multiple configurations of
> common processes.
> 1. How many chores does it do before
> it becomes one mother-fat library object
> itself in bad need of modularization?
> 2. Do the inconsistent data models
> of the various chore handlers make
> the noisiness of the result unendurable?
> Bits on the wire WON'T do it. That way
> lies endless consulting costs and increasing
> coupling to vendor-specific idiosyncracies. We see
> it every day here where different parsers
> and different handlers are making a nightmare
> of network messaging apps such that we have
> to tell our partners *XML.DLL version zed*
> or nothing, or we have to build all the
> components and frankly, why bother with
> XML if we have to do that.
> This is real world stuff from real programmers
> doing real work and all very hosed that XML
> technology is not living up to the promise
> of blind interoperability based on the spec.
> So, kindly get down to that and ignore the
> relentless FUD. The march is relentless because
> it is trying to go somewhere. We'd like to
> know a little bit more about the destination.
> IOW, how many sets of PSVI properties have
> to be handled and how soon will that be
> defined much less implemented?
> Y'all shot the grove guys down and claimed
> you knew more and could do a better job.
> Our feet are waiting to vote.
> Ekam sat.h, Vipraah bahudhaa vadanti.
> Daamyata. Datta. Dayadhvam.h
> -----Original Message-----
> From: Dave Winer [mailto:email@example.com]
> I agree with Don and Tim here.
> Especially if there's a server on the user's machine, reading XML feeds,
> doing a lot of churning, and generating HTML that any 4.0-level browser
> The xml-dev list is sponsored by XML.org, an initiative of OASIS
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: firstname.lastname@example.org