ontolog-forum
[Top] [All Lists]

Re: [ontolog-forum] ONTOLOG community event planning and scheduling sess

To: ontolog-forum@xxxxxxxxxxxxxxxx
From: Kingsley Idehen <kidehen@xxxxxxxxxxxxxx>
Date: Tue, 10 Sep 2013 08:50:30 -0400
Message-id: <522F1596.3090501@xxxxxxxxxxxxxx>
On 9/9/13 11:06 PM, David Eddy wrote:
Peter -

On Sep 09, 2013, at 10:34 PM, Peter Yim wrote:

Please post something onto the wiki at:
http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit/Suggestions ...
or start a thread under the [ontology-summit] mailing list to raise
awareness, get buy-in, and develop that proposal further.

The issue of legacy systems & the uselessness of SW to help with legacy systems needs has been put on this list repeatedly, by at least JFS & myself... to resounding sounds of silence.


Consider this... from Capers Jones... there are some 50 "major" software languages, 1,500 "minor" languages & a new language is introduced at the rate of 1 per month.  I assume the SW stack is on the far tail of the 1,500 minor list.

This is the sort of "diversity" the Global 2000 (or whatever company size label you want) is wrestling with.


I've spoken with a large firm that's been in the news recently & one of their senior technical officers told me they have some 28 DBMS engines in house.  That's not databases, that's database engines.  Personally I could only count to about 15.

How will the SW help with that mess?

David,

How about (if you don't mind) phrasing the question a little differently? For instance, wouldn't it be easier to start by outlining key characteristics of a solution to the data integration mess en route to determining alignment or misalignment with the Semantic Web stack?



From what I've seen over the past 8 years the SW is just going to add yet another layer of opaque complexity to the legacy systems.

Depends on the solution. Some do and some don't, in my experience.

 Intellectually stimulating?  Absolutely.  Useful?  Dubious.

Jim Hendler told me to my face there was nothing in the SW for legacy systems... which I entirely believe.

I don't think Jim holds that view. Of course, I am happy to be proven wrong.




One final rant... do think about the fast approaching Retirement Brain Drain.   

My generation of mainframers who built these reliable, long-lived but difficult to grok legacy systems is headed to retirement.   The Millennials mostly cannot spell JCL, much less know what it is (while they reinvent it).

So who's going to keep the Systems of Record running?  

How is something in the SW going to help keep the legacy systems working?

If we understand the key characteristics of the problem and the solution (as you see them), articulating potential solutions will be much easier.


Kingsley

____________________________
David Eddy
Babson Park, MA

781-455-0949

deddy@xxxxxxxxxxxxx



 
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
 


-- 

Regards,

Kingsley Idehen	      
Founder & CEO 
OpenLink Software     
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen




Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J    (01)

<Prev in Thread] Current Thread [Next in Thread>