Conference Call 2004-01-15

Ontolog invited Speaker Presentation Thu 2004-01-15    (8AR)

Conference Call Details    (8AS)

• Subject: [ontolog] Ontolog invited Speaker Presentation - LeoObrst - Thu 2004-01-15    (8AT)
• Comments/Agenda:    (8AU)
  • Agenda Comments: ... build rapport; ... sync up; ... distribute, assign or arbitrate virtual ownership of tasks; ... and use it to deal with emergencies. ... plus, member suggested agenda items.    (8AV)
  • Please post your suggested agenda items if you would like to see anything put onto the agenda    (8AW)
  • please post or upload any material to be shared to the list, to the wiki or by ftp upload prior to the meeting    (8AX)
  • VNC session will be started 5 minutes before the call at: http://vnc2.cim3.net:5800/    (8AY)
    • view-only password: "ontolog"    (8AZ)
    • if you plan to be logging into this shared-screen option (which the speaker may be navigating), and you are not familiar with the process, please try to call in 5 minutes before the start of the session so that we can work out the connection logistics. Help on this will generally not be available once the presentation starts.    (8B0)
  • Information relating to this session is shared on this wiki page: http://ontolog.cim3.net/cgi-bin/wiki.pl?Conference_Call_2004-01-15    (8B1)
• Date: Thursday, Jan 15, 2004    (8B2)
• Start Time: 10:30 AM Pacific Standard Time    (8B3)
• End Time: 11:55 AM Pacific Standard Time    (8B4)
• Dial-in Number: 1-702-851-3330 (Las Vegas, Nevada)    (8B5)
• Participant Access Code: "040115#" (call PeterYim at +1(650)578-9998 if you have dial-in problems)    (8B6)

Attendees    (8B7)

• Attended:    (8B8)
  • LeoObrst    (8B9)
  • PeterYim    (8BA)
  • FarrukhNajmi    (8BB)
  • Zachary Alexander (ebTDesign LLC)    (8BC)
  • Paul Macias (LMI)    (8BD)
  • BillMcCarthy    (8BE)
  • AdamPease    (8BF)
  • KurtConrad    (8BG)
  • BoNewman    (8BH)
  • PatCassidy    (8BI)
  • BobSmith    (8BJ)
  • CeceliaHickel    (8BK)
  • Carl Mattocks (co-Chair OASIS ebXMLRegistry Semantic Content SC; CHECKMi)    (8BL)
  • JackPark    (8BM)

• Expecting:    (8BN)
  • BillBurcham (0.5)    (8BO)

• Regrets:    (8BP)
  • MonicaMartin    (8BQ)

Agenda Ideas    (8BR)

Agenda & Proceedings    (8BS)

• LeoObrst will be delivering a presentation entitled "Ontologies for Semantically Interoperable Systems" during this conference call. This is the long awaited talk we were hoping Leo could do for us.    (8BT)

• About the speaker: Dr. Leo J. Obrst is an Artificial Intelligence Scientist at the MITRE Corporation, where he leads the Information Semantics Teams, and is a key participating member of numerous Semantic Web standards. He is one of the co-conveners of [ontolog]. He is co-author, with MichaelDaconta and KevinSmith (both [ontolog] members as well) of the recently published book "The Semantic Web - A Guide to the Future of XML, Web Services, and Knowledge Management" (Wiley 2003, ISBN 0-471-43257-1)    (8BU)

• Leo's presentation can be access by pointing your web browsers to:    (8BV)
  • http://ontolog.cim3.net/file/resource/tutorial/OntologiesForSemanticallyInteroperableSystems-ONTOLOG--LeoObrst_20040115b.htm    (8BW)
  • Any material outside of the prepared presentation, if they are called up, may be available under the VNC session detailed above    (8BX)

• If you have questions for the presenter, will appreciate your posting them here: (please identify yourself)    (8BY)

•    (8BZ)
  • Leo, along the line of an earlier exchange on this forum, could you give an opinion on when (say, what applications) you feel each of the following is best suited for ontological engineering work -- Topic Maps, OWL, KIF & Protege (--ppy)    (8C0)

•    (8C1)
  • Leo, this presentation, as in nearly all I've seen about ontology, seems not to address the need for ontology content development and use. It addresses motivations for ontologies, their use, languages, and ideas about mapping and brokering, but nothing about choosing a common upper ontology to support semantic integration. Without reusing a common upper ontology, systems won't be semantically interoperable, but rather tighly coupled stovepipes, because in doing ground up ontology development, the resulting ontologies are much too limited in scope to be reused for unanticipated applications. This can be seen by looking at the many bottom-up ontologies on the semantic web. They invariably have highly specific concepts, unexplained by more general terms. How would you respond? - Adam    (8C2)

•    (8C3)
  • Leo, Within the industry, we seem to be making significant strides in being able to create, and to some extent manipulate formal ontologies. However, I haven’t seen the same degree of progress in our ability to specify the design requirements (the pragmatics)for those doing the ontological development. Would you care to comment? –Bo Newman --    (8C4)

•    (8C5)
  • Leo, Ontologies, as reflections of how people ‘see the world,’ are subject to evolution and change. This could be seen as a destabilizing force on highly explicit formal ontologies, thus limiting their effective life. How would you address this problem? -- Bo Newman --    (8C6)

•    (8C7)
  • Leo, When speaking of Ontologies, you are clearly limiting your comments to explicit “formal ontologies.” How do you address the greater domain of “classical ontologies” which have heavy tacit and implicit components? -- Bo Newman --    (8C8)

•    (8C9)
  • Leo, what are some of the most pressing infrastructure needs to develope and manage ontologies? What trends to you forsee to address these? -- Farrukh Najmi --    (8CA)

• call ended 12:03pm    (8CB)