OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters forNamespaceProcessing)

Alex had been working on and discussing those 
concepts on comp.text.sgml long before we had XML. 
He is a very forward thinking guy.

We discussed it then because of the threads on mapping 
from SGML to objects and all the mismatches of that 
if one wanted a generalized system.   DOM actually 
bridged a lot of that with a high level 
interface, awkward though it is.   Data binding 
is a good idea, but the problem for the SGML systems 
was the requirements, particularly in IETMs, of reuse 
among different services (the military kind) that 
did not typicaly accept each other's document formats 
so the system had to accept multiple document types 
and reuse them.
The IETM database design (IETMDB) tried to solve that 
but the best implementations were...sigh... relational. 
It had also been discussed in the CALS enterprise 
papers but object systems of the time were too immature 
and the notion that stepping back to data-centrisms 
too "backward looking".

There's a lot to be said for cheap PCs and cheaper CPUs 
with even cheaper RAM. 


Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h

-----Original Message-----
From: Fuchs, Matthew [mailto:matthew.fuchs@commerceone.com]

That being said, there is no reason one can't
layer that kind of view of a document over the DOM, so one accesses the DOM
through interfaces that behave in the expected way (from a Java/C++
perspective) but maintain a DOM underneath.  Alex Milowski actually
suggested something along these lines a long time ago in the early days of