Property:Contains text
- Text
- schema:text (schema | Schema.org, V 14.0)
S
Also I am doing another [[Sorry Anagora]] (https://anagora.org/sorry-anagora) by speculating about the overlay syntax in-medium, but the need for repeated wikilinks above there revives my interest in recursive wikilinks that can be used in overlapping terms +
my examples are more the latter.
there are also strong roots in this idea of [[Infrastructure]] in CSCW, studying lots of attempts to get scientists to adopt new infrastructure and why they... didn't work.
one challenge is the [[Claim]] that "infrastructures often fail because of the inertia of the installed base" (existing software, workflows, norms, institutions, legal codes, etc.)
one decent entry point [[Source]] on this:
Information Infrastructures and the Challenge of the Installed Base +
another classic [[Source]] on [[Infrastructure]] is Steps Toward an Ecology of Infrastructure: Design and Access for Large Information Spaces +
<@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 +
[[Source]] for the figure in the previous msg: https://assets.pubpub.org/5nv701md/01521405455055.pdf +
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/ +
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 +
Maybe [[Synthesis Infrastructures 2022]] or something? but we haven't made one yet no 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. +
T
Hey I'm writing a message that relates to [[Test Topic]] as part of [[Test Project]] +
Now I am going to link a message into a specific section in my [[Test Topic#New Section]] and also see if we propagate that through to the wikilinks in [[Test Project]] +
Now hopefully without the uncaught exceptions for [[Test Topic]] +
Now I am going to link a message into a specific section in my [[Test Topic#New Section]] and also see if we propagate that through to the wikilinks in [[Test Project]] +
Test message +
[[Testing Wikibot]] +
[[Testing Wikibot]] +
[[Testing Wikibot]] +
[[Testing Wikibot2]] +
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 +
in thinking about some of the problems from this weekend like the (affectionately titled) [[The Google Docs Problem]] and various other interface problems with the wiki, where it'll always be easier for people to interact with a system from something they're more used to using, I've been thinking about a more generalized kind of bridging where one can set a [[Context of Interoperability]] where for a given workshop, time period, project, etc. people can plug their tools together and work in a shared space without needing to make all of them anew - so for the simple example of this discord and this wiki, it should be possible to reuse this space to eg. connect to a different (or multiple) wikis, and vice versa to have a different discord connect to it. Along those lines, being able to have a synchronizing eg. git repository of the pages on the wiki so that people could edit them in obsidian or logseq or whatever their tool of choice is... this feels like an incredibly generic idea, so I feel like there must already be a ton of work on it, but it feels like it starts by just making a framework for bridging where the n-to-n problem is simplified by having a set of tools for auth and format translation and modeling documents and messages... I'm going to start sketching one piece of that with the [[Mediawiki-Git Bridge]], but I'm curious to hear if anyone either has any ideas, prior experience, or unmet needs that I might be orbiting around here +