On 7/25/13 9:03 AM, Ron Wheeler wrote:
> The problem of Boeing trying to find out "What do we know about lithium
> batteries overheating?" is very similar to you and I wanting to know
> "What are the ways to cook quinoa?"
> The information needed could be anywhere in many different formats.
> Ontologies may play a minor role but the big technological breakthroughs
> are coming in other places.
Like? (01)
You need an Ontology and Linked Data to solve these kinds of problems.
Same applies to the privacy issues associated with PRISM [1] and TEMPORA
[2] . (02)
The Semantic Web technology stack suffers from a cocktail comprised of: (03)
1. poor narratives -- RDF zealotry dominates narratives while defensible
terminology and technology genealogy are for heretics! (04)
2. rote learning and recitals of mantras (a variation of point 1) --
simple challenges to viewpoints tend to end up in the "TimBL said so"
or "W3C said so" bucket (05)
3. participant profile homogeneity -- there is an imbalance between
academia and industry i.e., to many from academia (06)
4. tool profile homogeneity -- a majority of tools are aimed at
so-called "Semantic Web Programmers" (as subClassOf "Web Programmer)
rather than also catering to the needs of end-users, integrators,
systems analysts, architects, domain experts etc. (07)
5. dog-fooding is a rarity -- as in point 2 above, there is typically
little to show relative to all the papers and presentations that many
(outside the Semantic Web community) perceive as "chest pounding"
without practical and demonstrable substance. (08)
Data Virtualization without compromising individual privacy is the big
elephant in the room. Technologies associated with "the Semantic Web"
stack are mighty useful re. addressing this fundamental challenge that's
been compounded by the Web 2.0 phenomena. (09)
When you get beyond the challenge outlined above, you also have to deal
with drill-downs across virtualized data (i.e. semantically enhanced
views over heterogeneous data sources) which is where Boeing troubles
are a very good example. Basically, the Who, What, Where, When, and
deductible Why of the problem they are having with batteries etc.. (010)
Links: (011)
[1] http://www.google.com/search?q=prism+privacy&ie=UTF-8&oe=UTF-8 -- PRISM
[2]
http://www.google.com/search?client=safari&rls=10_6_8&q=tempora+privacy&ie=UTF-8&oe=UTF-8 (012)
-- TEMPORA. (013)
-- (014)
Regards, (015)
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 (016)
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)
|