I agree with Kingsley, in particular: (01)
1. poor narratives -- RDF zealotry dominates narratives while
defensible terminology and technology genealogy are for heretics! (02)
True, and this makes it harder when approaching potential customers. (03)
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 (04)
3. participant profile homogeneity -- there is an imbalance between
academia and industry i.e., to many from academia (05)
Points 2 and 3 are particularly true. When approaching customers SW
technology is seen as too academic; practicalities are not yet well
understood. Also, there are few practical cases where SW technology
has a clear impact in final implementation -the BBC is however, to the
best of my knowledge, a very good example. It is not just the case but
also how the use of SW technology is highlighted. This helps to sell.
The TBL recurrent presence is good and bad. From my little experience
with industry he is sometimes seen as "coming from academia" and so
therefore his views are not always well understood and dont always
help to make the case when selling a final solution. (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)
SW technology is sometimes seen as detached from main stream
technology so one frequent question that I have faced is "where do I
get a SW programmer?" and also "ontologies/controlled vocabularies are
expensive I dont want to end up in there, is this a must? Again, with
my little experience I have seen that usually customers want
interoperability/integration. Such projects have an end user in mind,
and there is usually a domain expert who helps in the design and
conceptualization of the final solution. SW should be understood as a
complementary technology, one more guy in the neighborhood. A
technology that powers up all other technologies. For instance, it
should be clear that SQL and SPARQL can complement each other. one
should not be seen as a replacement of the the other -IMHO. Again, I
may be wrong given my limited experience with customers. (08)
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. (09)
Very true. coming back to the imbalance between industry and academia.
I think we really need to hear it from the big guys -MS, Amazon,
Apple, etc. (010)
On Thu, Jul 25, 2013 at 3:27 PM, Kingsley Idehen <kidehen@xxxxxxxxxxxxxx> wrote:
> 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?
>
> 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] .
>
> The Semantic Web technology stack suffers from a cocktail comprised of:
>
> 1. poor narratives -- RDF zealotry dominates narratives while defensible
> terminology and technology genealogy are for heretics!
>
> 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
>
> 3. participant profile homogeneity -- there is an imbalance between academia
> and industry i.e., to many from academia
>
> 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.
>
> 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.
>
>
> 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.
>
> 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..
>
> Links:
>
> [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
> -- TEMPORA.
>
>
> --
>
> 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
>
>
>
>
>
>
>
> _________________________________________________________________
> 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
> (011)
--
Alexander Garcia
http://www.alexandergarcia.name/
http://www.usefilm.com/photographer/75943.html
http://www.linkedin.com/in/alexgarciac (012)
_________________________________________________________________
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 (013)
|