Property:Contains text
- Text
- schema:text (schema | Schema.org, V 14.0)
D
let's dump into a page! [[Discourse graphs within survey reading course]] +
apologies I didn't make it to [[discourse modeling]]! +
the idea [[DiscourseGraphs]] is rooted in a bunch of models like [[SEPIO]] (h/t <@602622661125996545>) and [[ScholOnto]] that have been around for various amounts of time, though not yet with (to my knowledge) serious widespread adoption. +
Hello Pooja and welcome 🙂 I certainly share your concerns here, and would love to read any writing or work you've done on the topic! I'm curious if you had any initial inklings of [[Discovery]] systems that go beyond the [[Search#Black Box Model]] ? I have my own ideas but as you say, everyone has a unique standpoint and experience that structures their ideas so I would love to hear yours! +
the idea is exactly to merge the [[Garden and Stream]] we have here, or as olde wiki culture called it, [[DocumentMode and ThreadMode]] in a process of [[Gradual Enrichment]]
http://meatballwiki.org/wiki/DocumentMode
http://meatballwiki.org/wiki/ThreadMode +
[[Page Schemas#Creating a new Schema]]
Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using [[Page Forms]] is something that is an interface for filling in values for a template.
For an example of how this shakes out, see
[[:Category:Participant]]
[[Template:Participant]]
[[Form:Participant]]
* go to a `Category:CategoryName` page, creating it if it doesn't already exist.
* Click "Create schema" in top right
* If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
* Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
* Once you're finished, save the schema
* Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy. +
E
[[Page Schemas#Creating a new Schema]]
Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using [[Page Forms]] is something that is an interface for filling in values for a template.
For an example of how this shakes out, see
[[:Category:Participant]]
[[Template:Participant]]
[[Form:Participant]]
* go to a `Category:CategoryName` page, creating it if it doesn't already exist.
* Click "Create schema" in top right
* If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
* Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
* Once you're finished, save the schema
* Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy. +
[[Page Schemas#Creating a new Schema]]
Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using [[Page Forms]] is something that is an interface for filling in values for a template.
For an example of how this shakes out, see
[[:Category:Participant]]
[[Template:Participant]]
[[Form:Participant]]
* go to a `Category:CategoryName` page, creating it if it doesn't already exist.
* Click "Create schema" in top right
* If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
* Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
* Once you're finished, save the schema
* Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy. +
[[Page Schemas#Creating a new Schema]]
Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using [[Page Forms]] is something that is an interface for filling in values for a template.
For an example of how this shakes out, see
[[:Category:Participant]]
[[Template:Participant]]
[[Form:Participant]]
* go to a `Category:CategoryName` page, creating it if it doesn't already exist.
* Click "Create schema" in top right
* If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
* Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
* Once you're finished, save the schema
* Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy. +
I think of all of these tools as "personal hypertext notebooks" - basically taking what is possible in wikis (organizing by means of linking, hypertext) and lowering the barrier to entry (no need to spin up a server, can just download an app and go).
The common thread across these notebooks then is allowing for organizing and exploring by means of bidirectional hyperlinks between "notes":
- In [[Obsidian]] each linkable note is a markdown file and can be as short or long as you like
- in [[Logseq]]/[[Roam]] and other outliner-style notebooks, you can link "pages", and also individual bullets in the outlines on each page.
In this way, the core functionality of these tools is similar to a wiki, but they do leave out a lot of the collaborative functionality that makes wikis work well (granular versioning and edit histories, talk pages, etc.). So for folks like <@305044217393053697> who are comfortable with wikis already, they add marginal value IMO.
Their technical predecessors in the "personal (vs. collaborative) wiki" space include [[TiddlyWiki]] and [[emacs org-mode]] (and inherit their technical extensibility: many users create their own extensions of the notebooks' functionality. an example is the [[Roam Discourse Graph extension]] that <@824740026575355906> is using).
These tools also tend to trace their idea lineage back to vannevar bush's [[Memex]] and ted nelson's [[Xanadu]]. +
[[Page Schemas#Creating a new Schema]]
Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using [[Page Forms]] is something that is an interface for filling in values for a template.
For an example of how this shakes out, see
[[:Category:Participant]]
[[Template:Participant]]
[[Form:Participant]]
* go to a `Category:CategoryName` page, creating it if it doesn't already exist.
* Click "Create schema" in top right
* If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
* Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
* Once you're finished, save the schema
* Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy. +
[[Page Schemas#Creating a new Schema]]
Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using [[Page Forms]] is something that is an interface for filling in values for a template.
For an example of how this shakes out, see
[[:Category:Participant]]
[[Template:Participant]]
[[Form:Participant]]
* go to a `Category:CategoryName` page, creating it if it doesn't already exist.
* Click "Create schema" in top right
* If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
* Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
* Once you're finished, save the schema
* Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy. +
i agree it's not universal! my feeling is that [[Claim]]: a statement (claim or evidence) might be the more universal element:
- empirical work also consists of statements about the world (this is less controversial)
- design/technological innovation rests in part on claims about a) what is needed in the world, what is hard to do, constraints, and b) what is needed to succeed: examples here: https://deepscienceventures.com/content/the-outcomes-graph-2 (h/t <@559775193242009610>)
- theories often consist of systems of core claims (e.g., in models like what <@824740026575355906> and <@734802666441408532> are working with, where we can think of the claims as subgraphs of the overall knowledge graph)
see, e.g., [[Evidence]] from this review of models of scientific knowledge https://publish.obsidian.md/joelchan-notes/discourse-graph/evidence/EVD+-+Four+positivist+epistemological+models+from+philosophy+of+science%2C+including+Popper%2C+emphasiz...+statements+as+a+core+component+of+scientific+knowledge+-+%40harsDesigningScientificKnowledge2001
and [[Evidence]] convergence/contrasts across users of the [[Roam Discourse Graph extension]] in terms of building blocks: common thread across all was Evidence +
We have been developing code for extraction of "claims" from IPCC [[executive summary]]s . <@322545403876868096> <@499904513038090240> So far we have the following design:
* exec summary for chapter => 15-20 paras
* bold leading sentence for each para => leading_claim
* subsequent sentences => supporting_claims
* annotation (high +
F
Looking forward to your work in this space! I do know about [[Fedwiki]] but only as a spectator. I tried to convince a few colleagues to set up a network of Fedwikis in our research domain, but nobody was keen on becoming a sysadmin to run their own Wiki instance. +
I don't know of any either! The closest I know of is ward's [[Fedwiki]]: but i plan on making one (probably more related to <#1038983225348993184> than this channel, which i am trying hard not to derail lol) +
[[Page Schemas#Creating a new Schema]]
Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using [[Page Forms]] is something that is an interface for filling in values for a template.
For an example of how this shakes out, see
[[:Category:Participant]]
[[Template:Participant]]
[[Form:Participant]]
* go to a `Category:CategoryName` page, creating it if it doesn't already exist.
* Click "Create schema" in top right
* If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
* Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
* Once you're finished, save the schema
* Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy. +
G
<@690574739785121815> can probably point to others, including his own work with the [[GLOBE system]] 🙂
http://globe.umbc.edu/
[[Source]]: Infrastructuring for Cross-Disciplinary Synthetic Science: Meta-Study Research in Land System Science +
the idea is exactly to merge the [[Garden and Stream]] we have here, or as olde wiki culture called it, [[DocumentMode and ThreadMode]] in a process of [[Gradual Enrichment]]
http://meatballwiki.org/wiki/DocumentMode
http://meatballwiki.org/wiki/ThreadMode +
encouraging the use of the thread for the sake of people's notifications as we enter slow-mode.
sidebar: this to me is one of the more interesting uses of this kind of wiki-bot, in a more long-lived chat and communication medium (glad 2 have <@708787219992805407> here for the long-timescales perspective btw). in both this and any future workshops, being able to plug in something like a wikibot that can let different threads get tagged to common concepts through time to different/overlapping discord servers and output to potentially multiple overlapping wikis is v interesting to me.
I'm gonna continue to make it easier to deploy because i feel like the [[Garden and Stream]] metaphor is one that can unfold on multiple timescales, and it would be cool to build out the ability to make that easier: how cool would it be if you didn't have to decide on a chat/document medium or have to make a new set at the start of an organizing project since it was arbitrary anyway and your infra supported use and crossposting across many media.
Eg. the very understanding surfacing of [[The Google Docs Problem]] because of [[Mediawiki]]'s lack of [[Synchronous Editing]] [[Live Editing]] and the need to remember to link out to external services rather than that being a natural expectation of a multimodal group and having systems that explicitly support that is illustrative to me. Maybe one description is being able to deploy a [[Context of Interoperability]] [[Interoperability]]: during this time period I am intending these documents/discord servers/hashtags/social media accounts/etc. to be able to crosspost between each other so that everyone needs to to as little as possible to make their workflows align +