42
edits
Talk:Discourse Modeling: Difference between revisions
Talk:Discourse Modeling (view source)
Revision as of 22:24, 12 November 2022
, 22:24, 12 November 2022→Section 3 Kyle
| Line 86: | Line 86: | ||
== Section 3 Kyle == | == Section 3 Kyle == | ||
* | |||
- 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? | ||
- sj: smw makes this hard for exactly this reason | * - sj: smw makes this hard for exactly this reason | ||
- easier with free form wiki templates and wiki text | * - easier with free form wiki templates and wiki text | ||
- tiny Lua templates (don't need to write Lua) | * - tiny Lua templates (don't need to write Lua) | ||
- define any number of fields | * - define any number of fields | ||
- define how they are presented | * - define how they are presented | ||
- this is just mediawiki w/o the semantic extension | * - this is just mediawiki w/o the semantic extension | ||
- make a mediawiki entry for every thing that has a shape | * - make a mediawiki entry for every thing that has a shape | ||
- edit that v flexibly, schema changes won't break things, won't cascade illegibility | * - edit that v flexibly, schema changes won't break things, won't cascade illegibility | ||
- at scale: smw wiki extension enables multiple dynamic table updates as data changes | * - at scale: smw wiki extension enables multiple dynamic table updates as data changes | ||
- KK: question: problem extending to smw later? | * - KK: question: problem extending to smw later? | ||
- no | * - no | ||
- not as long as template is compatible with smw | * - not as long as template is compatible with smw | ||
- 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 | ||
- KM: should we decompose the Q into further properties (like a Q has a subject and object) or leave it nat language | * - KM: should we decompose the Q into further properties (like a Q has a subject and object) or leave it nat language | ||
- KH: we should stick to nat language | * - KH: we should stick to nat language | ||
- KH: if you represent a dg in a wiki, what is a page? what's the granularity? every source is a page? | * - KH: if you represent a dg in a wiki, what is a page? what's the granularity? every source is a page? | ||
- KM: seems like everything is a page? | * - KM: seems like everything is a page? | ||
- sj: sections of a page are not a page | * - sj: sections of a page are not a page | ||
- sj: everything we want to be a node should be a page | * - sj: everything we want to be a node should be a page | ||
- sj: wiki supports transclusion | * - sj: wiki supports transclusion | ||
- kh: then each pp needs a title - lots of work | * - kh: then each pp needs a title - lots of work | ||
- sj: this is a q iof interfaces - we can do it this way for a demo | * - sj: this is a q iof interfaces - we can do it this way for a demo | ||
- KH: makes the history list a bit busy - this is a ux question affecting exploration | * - KH: makes the history list a bit busy - this is a ux question affecting exploration | ||
- KK: many to many relationships between sources & evidence | * - KK: many to many relationships between sources & evidence | ||
- source property could be a url and we could create an entity for the source that scrapes data and populates fields | * - 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 | * - if you expect something will be used more than once you probably want it to have the full data | ||
- sj: claim: this level of precision is important to dgs | * - sj: claim: this level of precision is important to dgs | ||
- sj: claim wiki recent changes scale well | * - sj: claim wiki recent changes scale well | ||
- sj: we can use wikibase to scale ux issues and hide certain types of history (eg source edits) | * - sj: we can use wikibase to scale ux issues and hide certain types of history (eg source edits) | ||
- KH: first attempt: everything is a page, we rely on transclusion to group things | * - KH: first attempt: everything is a page, we rely on transclusion to group things | ||
- KH: can we have the entire Q as a page title? | * - KH: can we have the entire Q as a page title? | ||
- 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 | ||
* | |||