Re: Using TM to help define the future of XML

Patrick,

  It's worth remembering--by those old enough and still possessing sufficient memory--that the adoption of SGML as a military requirement by the US DoD 30 years ago (MIL-STD-38784) was the single greatest impetus to its widespread adoption. 

  The required application of Topic Maps by DoD logisticians and purchase agents could be a boon.

Have a great day & a better tomorrow,

Neal McNamara

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"What I am questioning is whether "[others will] enthusiastically
appreciate this expressiveness!" ????

Example (from history): One (alleged) used case for topic maps was to
eliminate duplication of documentation for military systems. The
production of which was a line item in every contract and even if the
documentation was the same, the military was still paying for it.

Question: Some people wanted this to save money, be more efficient, etc.

Now, let's look at who did not want it:

1) Vendors of military systems, who by simply running a new cover page
or making minor changes, were charging full rate for a completely new
set of documentation. Consider that the documentation for an F-15 weighs
in at more than the aircraft and you get an idea of the documentation we
are talking about. This is pure gravy.

2) Contract managers, who the more contract $$$ they manage, the more
important their office, themselves, etc. 

3) The employees and contractors of the vendors who produce the
documentation for which the vendor charge yet again, increasing the
importance of the contract managers office.

And so on and so on.

So who are we going to sell this topic map system to, exactly? "