Cart
[Home] [By Thread] [By Date] [Recent Entries]
Lockheed Martin (texas) did it for IETMs using SGML. It
was a favored design for IETMs. It wasn't efficient
for real time use, but for dynamic assembly of a
deliverable, it worked great. IOW:
1. Author parts in a parts system, typically
relational.
2. Bind that into an interactive deliverable.
And yeah, isn't that what we do with HTML and
ASP, PERL, etc.? All done before the web was
a gleam.
A dynamically generated hypertext is just another report,
or a collection of reports with scriptable intelligence.
Do I need schemas for that? Not all the time. That
is why systems like IADS made validation optional.
In fact, support for DTDs was an add-on that I insisted
on just because it made my job easier. We worked
the CASS system the same way even earlier. Old ground.
You're right about the object-oriented standards
issue, IMO. I still think data objects scale
better than distributing semantics, though.
len
From: Michael Champion [mailto:mc@x...]
My favorite example would be an industrial-strength technical
manual. Codd proved that you CAN normalize all that ordered,
hierarchically structured, textual and data-oriented information and
pull it back together with the relational calculus, but I've never
heard of anyone actually pulling that feat off with real data and real
DBMS software. [Sure, just a simple 100-way join, no problem :-) ]
|
