Re: What is the logic of storing XML in a Database?

From: Marshall <>
Date: 29 Mar 2007 12:25:58 -0700
Message-ID: <>

On Mar 29, 12:09 pm, "Cimode" <> wrote:
> On 29 mar, 20:26, "Marshall" <> wrote:
> The binding protocol would of course allow
> to bind several widgets to the same relation.

Of course! :-)

> > > Periodically, clients would be able to gather existing schemas
> > > according to areas of interest using simple routines such as
> > > Pull.(AllSchema, AreaofInterest)
> > > Given the amount of space and resources saved, the client could easily
> > > and punctually renew such schemas...Some kind of language would
> > > require to be created for that (or maybe an extension of a relationnal
> > > querying language)...
> > I didn't quite understand this part. I usually think of clients as
> > having the schema they are written against "built-in." This
> > makes it sound like clients are using dynamic schema.
> > That makes sense for ad hoc queries but not so much for
> > client code, which I think of as fixed.
> I was thinking of the possibility of renewing schemas periodically to
> allow the inclusion of new querying capabilities depending on areas of
> interest of users.

Ohhhhhhhhhhh ...

I never thought of that. That's ... a *really* interesting idea.

> For instance, imagine that the client would have
> *core* routines that would allow it for instance to get the weather at
> any time. Then imagine that a user passing by a stock market wireless
> point of access could automatically get the ability to pull out
> *finance* related information thanks to the periodic induction of
> short life span schemas...

Ohhhhhhhhhhhh ...

Oh, my. Oh, dear. You have changed the way I think about this. Oh, my.

Now my whole day will be consumed thinking about the implications of this, and I'll not get anything else done. My wife will be quite unhappy with you. :-)

Marshall Received on Thu Mar 29 2007 - 21:25:58 CEST

Original text of this message