57
edits
Talk:Discourse Modeling: Difference between revisions
Talk:Discourse Modeling (view source)
Revision as of 17:58, 13 November 2022
, 17:58, 13 November 2022→Section 3 Kyle
No edit summary |
|||
| Line 163: | Line 163: | ||
* {{d|id=edge-complexity |a=KK |type=question |text=will defining edges/relationships turn out to be more complicated than creating templates for nodes? |supports=}} | * {{d|id=edge-complexity |a=KK |type=question |text=will defining edges/relationships turn out to be more complicated than creating templates for nodes? |supports=}} | ||
* {{d|id=when-done |a=KK |type=question |text=how do we know when we are done? |supports=}} | * {{d|id=when-done |a=KK |type=question |text=how do we know when we are done? |supports=}} | ||
** {{d|id=internal-consistency |a=SJ |type=claim |text=we need to create an internally consistent way of sharing templates |supports=template-start}} | |||
*** {{d|id= |a=KH |type=claim |text=challenge: templates are universally available, which means that anyone can break our template|supports=internal-consistency}} | |||
* {{d|id= |a=KM |type=question |text=should we decompose Questions into further properties (like a Q has a subject and object) or leave it nat language?|supports=}} | |||
** {{d|id= |a=KH |type=claim |text=we should stick to natural language | source=self |supports=}} | |||
* {{d|id=wiki-granularity |a=KH |type=question |text=if you represent a dg in a wiki, what is a page? what's the granularity? every source is a page? |supports=}} | |||
** {{d|id=wiki-all-pages |a=KM |type=claim |text=it seems everything is a page. |extends=wiki-granularity }} | |||
*** {{d|id=wiki-sections |a=SJ |type=claim |text=sections of a page are not a page. |opposes=wiki-all-pages }} | |||
** {{d|id=wiki-node-pages |a=SJ |type=claim |text=everything we want to be a node should be a page. |extends=wiki-granularity }} | |||
** {{d|id=wiki-subgraph-pages |a=SJ |type=claim |text=wiki transclusion also allows any subgraph to have a page, transcluding other nodes. |extends=wiki-granularity }} | |||
*** {{d|id=wiki-pages-busy |a=SJ |type=claim |text= then each page needs a title - lots of work. and makes the history view busy, a UX question affecting exploration. |opposes=wiki-node-pages }} | |||
** {{d|id=wiki-pages-manageable |a=SJ |type=claim |text=True, this is a Q of interfaces. Wiki recent changes scales well, we don't need to worry about that yet. we can use wikibase to scale ux issues and hide certain types of history (eg source edits). But we can do it this way for a demo. |opposes=wiki-pages-busy }} | |||
:: '''NB''': ''this last is really 'oppose in part, support in part'. speaking to wanting a vocabulary of connection types'' | |||
*** {{d|id=start-with-transclusion|a=KH |type=claim |text=first attempt: everything is a page, we rely on transclusion to group things |supports=wiki-pages-manageable}} | |||
** {{d|id= |a=KH |type=question |text=can we have the entire Q as a page title? |extends=wiki-pages-busy }} | |||
* {{d|id= |a=KK |type=claim |text=there are many to many relationships between sources & evidence |supports=}} | |||
* {{d|id= |a= |type=claim |text=source property could be a url and we could create an entity for the source that scrapes data and populates fields. If you expect something will be used more than once you probably want it to have the full data|supports=}} | |||
* {{d|id=starting-dgs |a=SJ |type=claim |text=let's identify a discussion we want to capture, and figure out how to name it. |supports=}} | |||
<!-- | <!-- | ||
* {{d|id= |a= |type=claim |text=|supports=}} | * {{d|id= |a= |type=claim |text=|supports=}} | ||
* {{d|id= |a= |type=claim |text=|supports=}} | * {{d|id= |a= |type=claim |text=|supports=}} | ||
* - decision: start with naming & schemas first | * - decision: start with naming & schemas first | ||
* - do we start with a schema or refine as we go? | * - do we start with a schema or refine as we go? | ||
| Line 184: | Line 204: | ||
* - we can do this by hand - dozen schemas | * - we can do this by hand - dozen schemas | ||
* - we can then decide whether we want to do smw or use wikidata & their respective modelling tradeoffs | * - we can then decide whether we want to do smw or use wikidata & their respective modelling tradeoffs | ||
* - start with creating a "source" template: source: url, publisher, date, author ? | * - start with creating a "source" template: source: url, publisher, date, author ? | ||
* - kk: [[question]] will defining edges/relationships turn out to be more complicated than creating templates for nodes? | * - kk: [[question]] will defining edges/relationships turn out to be more complicated than creating templates for nodes? | ||
* - KK: how do we know when we are done? | * - KK: how do we know when we are done? | ||
* - SJ: need to create an internally consistent way of sharing templates | * - SJ: need to create an internally consistent way of sharing templates | ||
* - kH: templates are universally available, which means that anyone can break our template | * - kH: templates are universally available, which means that anyone can break our template | ||
| Line 212: | Line 229: | ||
* - sj: this gets to my interest, naming | * - sj: this gets to my interest, naming | ||
* - sj: a great next step would be intifying a discussion wewant to capture | * - sj: a great next step would be intifying a discussion wewant to capture | ||
--> | |||