Jump to content

Talk:Discourse Modeling: Difference between revisions

m
Line 34: Line 34:


== Section 2 Konrad ==
== Section 2 Konrad ==
- KM: take  contributions to this wiki as data to generate a discourse graph?
* - KM: take  contributions to this wiki as data to generate a discourse graph?
- create schema, show others how to create the different node types
* - create schema, show others how to create the different node types
- take db backend, ingest it, execute queries against it
* - take db backend, ingest it, execute queries against it
- viz may not be super-sophisticated, but a view or 2 framed on each node type would be worthwhile: eg how does a question related to claims, how are claims informed by different articles (evidence)
* - viz may not be super-sophisticated, but a view or 2 framed on each node type would be worthwhile: eg how does a question related to claims, how are claims informed by different articles (evidence)
- need to populate the wiki with the elements of a discourse graph --> create viz --> share code
* - need to populate the wiki with the elements of a discourse graph --> create viz --> share code
- SJ: would like to accomplish naming: coming up with names for each of those components, and names for things at differnt scales - discussion, family of hyptheses, family of experiments
* - SJ: would like to accomplish naming: coming up with names for each of those components, and names for things at differnt scales - discussion, family of hyptheses, family of experiments
- this will allow us to say that if you have identified x ideas, hypotheses, etc - how many discourses do you need to describe? how many graphs are needed to illustrate those discourses - when are people working on the same graph?
* - this will allow us to say that if you have identified x ideas, hypotheses, etc - how many discourses do you need to describe? how many graphs are needed to illustrate those discourses - when are people working on the same graph?
- what does it mean to have different graphs that share some pieces, or different graphs in or close to the same namespace
* - what does it mean to have different graphs that share some pieces, or different graphs in or close to the same namespace
- --> boil down to the naming of the pieces and how you place the connections - ho much context do you need to figure out how many connections there are?
* - --> boil down to the naming of the pieces and how you place the connections - ho much context do you need to figure out how many connections there are?
- KM: taking this as an opportunity to  learn SPARQL
* - KM: taking this as an opportunity to  learn SPARQL
- we need namespaces before we can qury anything - naming is critical!
* - we need namespaces before we can qury anything - naming is critical!
- KH: also relatively  
* - KH: also relatively  
- Sj: we should name and make list of queries - queries nee their own names
* - Sj: we should name and make list of queries - queries nee their own names
- KM: agora?
* - KM: agora?
- SJ: group of people interested in wiki linking and editable networks & knowledge federation
* - SJ: group of people interested in wiki linking and editable networks & knowledge federation
- goals:
* - goals:
- make linking always do something sensible - best effort connection between links
* - make linking always do something sensible - best effort connection between links
- agora is a url pattern that will try to resolve it
* - agora is a url pattern that will try to resolve it
- redirect strings to appropriate resources
* - redirect strings to appropriate resources
- each reader gets a filter - only see certain nodes & connection based on sort preferences  
* - each reader gets a filter - only see certain nodes & connection based on sort preferences  
- KM: sounds like auto-complete for knowledge graphs
* - KM: sounds like auto-complete for knowledge graphs
- each agora has a few default sections - ex will try to generate related out nodes, related agoras you know with the same title or fuzzy match, any text it finds in your own agaora ad-hov
* - each agora has a few default sections - ex will try to generate related out nodes, related agoras you know with the same title or fuzzy match, any text it finds in your own agaora ad-hov
- elevate dgsd by making a section that tries to generate a dg or discourses that mention this node
* - elevate dgsd by making a section that tries to generate a dg or discourses that mention this node
- dg is a shape you compile on the fly - could try to  generate a dg x stteps away and show you different families that might be referencingthis
* - dg is a shape you compile on the fly - could try to  generate a dg x stteps away and show you different families that might be referencingthis
- spirit of the agora is automatic discovery & openness to engagement
* - spirit of the agora is automatic discovery & openness to engagement
- KH: impression is that it is a collection - how would I learn that someone rlsewants to do something to my node
* - KH: impression is that it is a collection - how would I learn that someone rlsewants to do something to my node
- diff between creating a new link with the same name as your node and creating a link to your specic node
* - diff between creating a new link with the same name as your node and creating a link to your specic node
- KK: diff between agora and what we enision?
* - KK: diff between agora and what we enision?
- sj: no typology of links
* - sj: no typology of links
- graph visualization does not ignore non-typed connections
* - graph visualization does not ignore non-typed connections
- KH: existing descriptions of agora other than the site itself?
* - KH: existing descriptions of agora other than the site itself?
- KK:what actions will  we need to take to get where we want to go?
* - KK:what actions will  we need to take to get where we want to go?
- how do we turn parts of this wiki into the components of a dg?
* - how do we turn parts of this wiki into the components of a dg?
- KM: we have folks write and annotate in the wiki and use the annotation capabiliies of SMW to call out what the node types are
* - KM: we have folks write and annotate in the wiki and use the annotation capabiliies of SMW to call out what the node types are
- getting the data into the wiki is literally people interacting and annotating
* - getting the data into the wiki is literally people interacting and annotating
- but first we need to figure out naming and schema
* - but first we need to figure out naming and schema
- template objects, other objects, tools that can be used to define the schema
* - template objects, other objects, tools that can be used to define the schema
- KH: prefer many short examples
* - KH: prefer many short examples
- SJ: like the idea of a self-referntial discourse about the state of discourse graphs
* - SJ: like the idea of a self-referntial discourse about the state of discourse graphs
- question: can  a discourse be a bout a topic? are discourses about a certtain over-arching hypothesis where you make claims and discover evidence?
* - question: can  a discourse be a bout a topic? are discourses about a certtain over-arching hypothesis where you make claims and discover evidence?
- KH: what do you do when your discourse does not fit a Dg?
* - KH: what do you do when your discourse does not fit a Dg?
- (examples from physics with no well-posed question)
* - (examples from physics with no well-posed question)
- (discussion of results graphs and requests for experiments)
* - (discussion of results graphs and requests for experiments)
- need to figure out how DGs work in these differnt fields and circumstances
* - need to figure out how DGs work in these differnt fields and circumstances
- sj: meta: need to identify existing discourse maps, and existing graphs, that could be thought of as d.g.s
* - sj: meta: need to identify existing discourse maps, and existing graphs, that could be thought of as d.g.s
- (proofs, discourse diagrams, text summarization graphs, argument maps, decision maps + flowcharts, ...)
* - (proofs, discourse diagrams, text summarization graphs, argument maps, decision maps + flowcharts, ...)
 
*
- sj: need to capture axioms / assumptions
* - sj: need to capture axioms / assumptions
- kh: making tacit knowledge explicit!!
* - kh: making tacit knowledge explicit!!
*


== Section 3 Kyle ==
== Section 3 Kyle ==
42

edits