Talk:Discourse Modeling: Difference between revisions

- everywhere there is a link - there is a hover that shows everything that links to X

- rather than having to click on x we can see links on hover }}

- {{d|id=social-utility |a=KK  |type= claim  |text=KK: this would encode proof of use, proof of utility}}

- {{d|id=querying |a=DA  |type= question  |text=DA: with sparql queries - can you browse the whole wiki  tree and parse out what you want from that?}}

- {{d|id=querying |a=KM  |type= claim  |text=Km: yes - it's the right query language for this kind of data}}

- {{d|id=querying |a=DA  |type= question  |text=DA: can you see the context for the link inside of the page? if I'm referring to a link, can I see the sentence that link is embedded in?}}

- {{d|id=querying |a=KM  |type= claim |text= we'd need to annotate the wiki using the DG schema and then query against that schema -- the amazing thing about sparql is that anything thats connected, you can get there}}

- {{d|id=tool |a=KK |type=claim  |text= seems like we're  rediscovering properties native to roam and trying to put them in the wiki}}

- {{d|id=structure |a=DA  |type= claim  |text=DA:DA: the hover is sugar - we can get there by putting everything on a page:  on the bottom of a claims page we have everything that mentions this claim and an extra field that describes, enriches the mention (support/oppose) context}}

- {{d|id=agora |a=KM  |type= claim  |text=KM  agora is partly a discovery algo for a graph

- component of building an autocomplete for DGs is a mechanism to discover  graphs and do the autocomplete so they algo can work off of

- once there are DG to work from, agora algo seems like a useful tool to search the ecosystem }}

- {{d|id=agora |a=DA  |type= question  |text= how do you get data into an agora ?}}

- {{d|id=agora |a=SJ  |type= claim |text= a mediawiki could be an agora}}

- {{d|id=agora |a=KH |type= question  |text= we still have to encode each node as a page if we want to build on this agaora model}}

- {{d|id=granularity |a=SJ  |type= question  |text= SJ: question about the appropriate level of granularity?}}

- {{d|id=granularity |a=KH  |type= question  |text=KH: also identity question - what is the smallest item you can point to?}}

- {{d|id=structure |a=SJ  |type= claim  |text=SJ: 2 separate ID  Q:  

- let's add the concept of a page for a graph

- something you can hold in your mind as an image  

- more than one claim

- individual claims shouldn't be pages, but nodes or entities

- if we want to do this in the wikiverse we can talk about them as entities

- SMW will represent entitites as pages but it doesn't scale}}

- {{d|id=SMW |a=DA  |type= question  |text=SMW will not support a large volume?}}

- {{d|id= SMW |a=SJ  |type= evidence  |text= SMW is  designed for pages to jave sizeable amt of text, well-formatted and structured

- we're talking about entire constellations }} (also a claim)

- {{d|id=viz |a=SJ  |type= question  |text= Q of what viz we need -  

- can still use mw as a viz - what happens when we hover over?

- want to be able to see the links while loking at the claim in context }}

- {{d|id=tool |a=SJ |type= claim  |text=SJ: it does  make sense to use a wiki for prototyping and experimenting - like where we want to carve distinctions

- it's nice to be able to go back & forth in a collab text format

- take snapshots and convert to a permanently structured DG

- more lastingly machine readable version of the same discourse

- wiki capture could feel more like a discourse if the discourse originated with people

- iteratively annotate and structure}}

- {{d|id= tool |a=KH  |type= question  |text=KH: it's nice to have a familiar authoring tool like a wiki

- {{d|id=approach |a=KH  |type= claim  |text= it  would make sense to start with something like we did and have an external tool go over it and store it for later processing

- wiki is a data entry tool

- we still don't have relations