Property:Contains text
- Text
- schema:text (schema | Schema.org, V 14.0)
R
in the spirit of cultivating our garden: [[Reading List]] https://hapgood.us/2015/10/17/the-garden-and-the-stream-a-technopastoral/amp/ +
To add to the [[Reading List#Linked Data]] on [[Linked Data]], [[Standards]], and [[Collaboration]]: a piece from one of the authors of [[ActivityPub]] on the merger of the distributed messaging and linked data communities that I think puts into context what a massive achievement AP was
http://dustycloud.org/blog/on-standards-divisions-collaboration/ +
I am definitely on team "scruffy" per Lindsay Poirier's typology (BTW "[[A Turn for the Scruffy]]" should be on the collective [[Reading List]] for anyone who hasn't come across it) and so yes definitely "Own-terminology" iterating into something shared, part of why i love the semwiki model of building them. On the other end of things for tomorrow - Is there any particular existing ontology/schema/etc. anyone in this group would like to have imported into the wiki for discourse modeling? +
[[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]]. +
These tools are still not entirely mainstream compared to tools like [[Notion]], which is related to your experience trying to learn more about the tools - so they tend to have a steep learning curve!
IMO the best way to get a feel for what they are is to see some examples/videos.
I like this video for an overview of [[Logseq]]: https://www.youtube.com/watch?v=ZtRozP8hfEY&t=6s
I describe [[Roam]] and the [[Roam Discourse Graph extension]] in this portion of a talk I recently gave: https://youtu.be/jH-QF7rVSeo?t=1417 +
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 +
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]]. +
These tools are still not entirely mainstream compared to tools like [[Notion]], which is related to your experience trying to learn more about the tools - so they tend to have a steep learning curve!
IMO the best way to get a feel for what they are is to see some examples/videos.
I like this video for an overview of [[Logseq]]: https://www.youtube.com/watch?v=ZtRozP8hfEY&t=6s
I describe [[Roam]] and the [[Roam Discourse Graph extension]] in this portion of a talk I recently gave: https://youtu.be/jH-QF7rVSeo?t=1417 +
[[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. +
S
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. +
Haven't finished n-back thread capture yet but this rocks and let's keep track of it on the wiki. Scroll up in this thread for [[SEPIO]] + [[ActivityStreams]]/[[ActivityPub]] + [[JSON-LD]]. On a train now and having to work on some other stuff but this is making me unreasonably excited to check out later +
super glad to hear that the endpoint worked btw, i've never used SPARQL and am more used to just making my own data models that generate API queries & parse etc. so I would love to see what you've been doing and how you've been using it - I'll make a [[SPARQL]] page linked off the wiki page that gives the URL and maybe we can embed sample queries and etc. there +
[[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. +
ah, that is both informative and sad to hear. i think ahead of its time is a reasonable diagnosis.
[[ScholOnto]] I think was also ahead of its time: had a working prototype integration into a Word processor for directly authoring discourse-graph like things while drafting a manuscript (described here: https://onlinelibrary.wiley.com/doi/abs/10.1002/int.20188) +
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! +
[[Semantic MediaWiki]] vs [[WikiBase]]: you're right! Semantic mediawiki is more for being an interface that can support unstructured and structured information in the same place, it's a lot more freeform and gestural, but at the cost of predictability/strictness/performance as a database. Definitely different tools with different applications, albeit with a decent amount of overlap in philosophy and etc. +
this is almost exactly the idea with the [[WikiBot]] that pushes to a [[Semantic Wiki]], and good to have a name in [[Gradual Enrichment]]. looking forward to digging though the references and finishing that piece^ tomorrow. (and finishing the n-back linking syntax so I can just directly include the piece in the annotation that is this message). thanks for sharing 🙂 +
[[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. +