Property:Contains text

Text
schema:text (schema | Schema.org, V 14.0)

Usage283

Filter<p>The <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Help:Property_page/Filter">search filter</a> allows the inclusion of <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Help:Query_expressions">query expressions</a> such as <code>~</code> or <code>!</code>. The selected <a rel="nofollow" class="external text" href="https://www.semantic-mediawiki.org/wiki/Query_engine">query engine</a> might also support case insensitive matching or other short expressions like:</p><ul><li><code>in:</code> result should include the term, e.g. '<code>in:Foo</code>'</li></ul><ul><li><code>not:</code> result should to not include the term, e.g. '<code>not:Bar</code>'</li></ul>

Showing 3 pages using this property.

W

Worm Community System (WCS)#joelchan86-22-11-13 03:36:24 +

another classic [[Source]] on [[Infrastructure]] is Steps Toward an Ecology of Infrastructure: Design and Access for Large Information Spaces +

X

Xanadu#joelchan86-22-11-11 14:05:36 +

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]]. +

Z

Zenodo#sneakers-the-rat-22-11-03 22:51:30 +

[[Project Ideas#Linked Data Publishing On Activitypub]] ooh I'm very interested in this. so are you thinking a [[Twitter#Bridge]] -> [[ActivityPub#Bridge]] where one could use markup within the twitter post to declare [[Linked Data#Markup Syntax]] and then post to AP? I have thought about this kind of thing before, like using a bot command syntax to declare prefixes by doing something like ``` @ bot prefix foaf: https:// (ontology URL) ``` or ``` @ bot alias term: foaf.LongerNameForTerm ``` so that one could do maybe a semantic wikilink like `[ [term::value] ]` either within the tweet or as a reply to it (so the tweet itself doesn't become cluttered/it can become organized post -hoc?). I've also thought about a bridge (I called [[Threadodo]] ) that implements that kind of command syntax to be able to directly archive threads to [[Zenodo]] along with structured information about the author, but this seems more interesting. I can help try and clear some of the groundwork out of the way to make it easier for you and other interested participants to experiment. I have asked around fedi a bunch for a very minimal AP server implementation, and I could try and find one (or we could try and prototype one) if you want to experiment with that :), and I can also document and show you a tweepy-based bot that has an extensible command/parsing system too +