Re: comment: topicmapmail Digest, Vol 74, Issue 1
Patrick Durusau <patrick-Q/[email protected]> Tue, 10 Apr 2012 19:59:25 -0400
| Newsgroups | gmane.text.xml.xtm.general |
|---|---|
| Message-ID | <[email protected]> |
Neal, On 04/09/2012 11:35 AM, Neal McNamara (nealmc) wrote: > Hi Patrick, > > I enjoyed your post . . . huddled masses indeed. > Thanks! > It brought to mind the quandary that faced me more than 30 years ago. > The DoD was pushing forward a program they called IWSDB for Integrated > Weapons System Database. As a contractor for the Navy, I was glad that > they were finally going to reconcile the disparate data in each of the > services. Highest on my mind was semantic interoperability. > > So I began contacting officials to ask how they were going to > reconcile terminology. And of course I found this little detail had been > overlooked. They were going to have an integrated database, but they had > no idea how to wrangle the data definitions into a single structure. > Apparently applying computer power to the issue would be enough. > > Today, despite the potential of the internet, they simply have > automated the Babel. > I ran across some intelligence "integration" software today that claims to integrate various sources but: 1) On what basis integration occurs is never specified, and 2) How different groups might (or might not) share that integration was also not specified. Not that everyone would ever agree but I would think re-use at least within an agency would be a value-add. Any thoughts on a small data patch suitable for intelligence integration demonstration? Possibly for non-US intelligence types? I say non-U.S. because I ran across a proposal recently that wants to capture 5 years worth of data when the agency in question has a track record of not using 90 day old data well. Building a bigger haystack is unlikely to produce better search results. Hope you are having a great day! Patrick > Warm regards, > > Neal > > > > -----Original Message----- > From: topicmapmail-bounces-Zo64W7twoUFWk0Htik3J/[email protected] > [mailto:topicmapmail-bounces-Zo64W7twoUFWk0Htik3J/[email protected]] On Behalf Of > topicmapmail-request-Zo64W7twoUFWk0Htik3J/[email protected] > Sent: Saturday, April 07, 2012 11:00 AM > To: topicmapmail-Zo64W7twoUFWk0Htik3J/[email protected] > Subject: topicmapmail Digest, Vol 74, Issue 1 > > Send topicmapmail mailing list submissions to > topicmapmail-Zo64W7twoUFWk0Htik3J/[email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.infoloom.com/mailman/listinfo/topicmapmail > or, via email, send a message with subject or body 'help' to > topicmapmail-request-Zo64W7twoUFWk0Htik3J/[email protected] > > You can reach the person managing the list at > topicmapmail-owner-Zo64W7twoUFWk0Htik3J/[email protected] > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of topicmapmail digest..." > _______________________________________________ > topicmapmail mailing list > topicmapmail-Zo64W7twoUFWk0Htik3J/[email protected] > http://www.infoloom.com/mailman/listinfo/topicmapmail > -- Patrick Durusau patrick-Q/[email protected] Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) OASIS Technical Advisory Board (TAB) - member Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau