From OntologPSMW

(Difference between revisions)
Jump to: navigation, search
(Resources)
(Resources)
 
(2 intermediate revisions by one user not shown)
Line 23: Line 23:
 
This session will last one hour and will be in two parts of roughly equal length: a speaker presentation and a discussion session. Participants at the session will not only be able to ask questions but will also have an opportunity to contribute to the topic.
 
This session will last one hour and will be in two parts of roughly equal length: a speaker presentation and a discussion session. Participants at the session will not only be able to ask questions but will also have an opportunity to contribute to the topic.
  
* '''[[JohnSowa|John Sowa]]''' "''Knowledge Graphs:  Past, Present, Future''" [http://bit.ly/34DyeQi Slides] [http://bit.ly/2LJbAgW Video Recording]
+
* '''[[JohnSowa|John Sowa]]''' "''Knowledge Graphs:  Past, Present, Future''" [http://bit.ly/34DyeQi Slides] [http://bit.ly/2LJbAgW Video Recording] [https://youtu.be/LS-bCyaY024 YouTube Video]
 
* General Discussion.  All attendees are invited to participate in the discussion.  To ask a question or make a contribution, please "raise your hand" on the [http://bit.ly/2LkAbKj Chat Room].  The meeting will be recorded and the recording will be posted on this meeting page.
 
* General Discussion.  All attendees are invited to participate in the discussion.  To ask a question or make a contribution, please "raise your hand" on the [http://bit.ly/2LkAbKj Chat Room].  The meeting will be recorded and the recording will be posted on this meeting page.
  
Line 144: Line 144:
 
== Resources ==
 
== Resources ==
 
* [http://bit.ly/2LJbAgW Video Recording]
 
* [http://bit.ly/2LJbAgW Video Recording]
 +
* [https://youtu.be/LS-bCyaY024 YouTube Video]
 
* [http://bit.ly/34DOmRV Ontology Summit YouTube Channel]
 
* [http://bit.ly/34DOmRV Ontology Summit YouTube Channel]
  

Latest revision as of 13:58, 11 September 2019

[ ]
    (1)
Session Introductory
Duration 1 hour60 minute
3,600 second
0.0417 day
Date/Time September 11 2019 16:00 GMT
9:00am PDT/12:00pm EDT
5:00pm BST/6:00pm CEST
Convener Ken Baclawski

Contents

This session will last one hour and will be in two parts of roughly equal length: a speaker presentation and a discussion session. Participants at the session will not only be able to ask questions but will also have an opportunity to contribute to the topic.     (2A1)

[edit] Conference Call Information     (2B)

[edit] Participants     (2C)

[edit] Proceedings     (2D)

[11:55] Ken Baclawski: Welcome! John's slides are available at http://bit.ly/34DyeQi     (2D1)

[12:03] RaviSharma: thanks for slides link - Ravi     (2D2)

[12:06] RaviSharma: notes: KG are subset of semantic network     (2D3)

[12:07] RaviSharma: will define Kyndi work and correlation     (2D4)

[12:19] David Eddy: and when do we start to look at "un-natural language"? The text artifacts called software.     (2D5)

[12:21] MikeBennett: John is right that an ontology standard is a fixed thing, but that is not necessarily bad - it's the same as a natural language dictionary (but for concepts not words): it freezes things at a point in time to make some tasks easier, and must evolve slowly over time. As dictionaries do.     (2D6)

[12:21] RaviSharma: ken hope we are recording?     (2D7)

[12:22] Ken Baclawski: @RaviSharma: Yes, we are recording.     (2D8)

[12:25] David Eddy: @Mike... but dictionaries EXCLUDE the un-natural language in use in software     (2D9)

[12:32] MikeBennett: @David I'm making an analogy not an example.     (2D10)

[12:36] janet singer: @Mike - and dictionaries don't really fix meanings. They arguably fix pronunciations but treat meaning in prioritized cases of use (current and archaic). They are well set up to evolve by incorporating new use cases. What would such a treatment of ontology look like?     (2D11)

[12:39] MikeBennett: @Janet what they have in common is that they make static what is generally fluid. My point wrt John's point is that doing this is not necessarily a problem, as he suggests. It has a use.     (2D12)

[12:39] MikeBennett: Indeed this is what standards are, in general.     (2D13)

[12:42] janet singer: @Mike -Yes, but a lot of thought needs to go into a standard to make it evolvable.     (2D14)

[12:46] janet singer: A dictionary happens to be structured to be evolvable, which is why it persists. A glossary that presented single meanings for terms is more analogous to a fixed ontology     (2D15)

[12:48] David Eddy: @Janet - but formal, published dictionaries evolve at the publishing pace of the content owner (publishers like OAD, Webster, etc.)... what about local language with local meanings?     (2D16)

[12:50] janet singer: @David - Like online internet/urban slang dictionaries? They update more quickly     (2D17)

[12:51] David Eddy: @Janet... you would allow use of internet dictionaries in a project?     (2D18)

[12:53] David Eddy: Having just checked, jcl, cics & db2 are not in WordNet.     (2D19)

[12:54] RaviSharma: is Arun Majumdar on chat?     (2D20)

[12:55] janet singer: @David - Each standard is appropriate/inappropriate per context of use. I was thinking through Mikes response of the example of dictionaries to Johns critique of fixing ontologies     (2D21)

[12:55] David Eddy: I'm pretty sure I can anticipate Christiane's response if I asked to have such technical terms include in WordNet.     (2D22)

[12:57] janet singer: Yes, inclusion of new words and uses in dictionaries is a newsworthy event depending on how conservative that resource is     (2D23)

[12:58] Ken Baclawski: @RaviSharma: I don't see Arun Majumdar yet.     (2D24)

[12:59] David Eddy: @Janet - Jcl, cics & db2 are hardly new terms     (2D25)

[13:02] janet singer: New or too specialized a community of use, or otherwise outside the purview of the resource.     (2D26)

[13:02] RaviSharma: @john - in cog mem when one queries, are you addressing a subset of software that then accesses repository or sources of info?     (2D27)

[13:03] RaviSharma: John can you request Arun     (2D28)

[13:03] janet singer: Each dictionary has criteria for evolving. But dictionaries in general are structured to be evolvable. What are lessons from dictionaries for evolvability in ontologies?     (2D29)

[13:04] Ram D. Sriram: @John: It would be useful to get an understanding on the gaps and what needs to be done for future work.     (2D30)

[13:06] MikeBennett: @Janet that is the important question.     (2D31)

[13:06] David Eddy: @Janet >> But dictionaries in general are structured to be evolvable. << but not on the time scale needs of projects.     (2D32)

[13:08] David Eddy: @Janet... this gives me the idea to ask people with iPhones know the OAD is embedded in both iOS & macOS. Sorry... no idea for Android or Windows.     (2D33)

[13:09] AlexShkotin: where we on youtube?     (2D34)

KenBaclawski: There will be links in the meeting pages to the youtube recordings. Here is the YouTube Channel     (2D35)

[13:10] janet singer: @David - can you explain re OAD and iPhones?     (2D36)

[13:10] David Eddy: @Janet... connect with me on LinkedIn & we can discuss... not trivial topic.     (2D37)

[edit] Resources     (2E)

[edit] Previous Meetings     (2F)


[edit] Next Meetings     (2G)