Property:Contains text
- Text
- schema:text (schema | Schema.org, V 14.0)
G
This project, [[Git-Mediawiki]] looks pretty good: https://github.com/Git-Mediawiki/Git-Mediawiki
I'm gonna see if i can get a further translating layer between wiki markup and markdown going, thank god for [[Pandoc]] +
Yes, that's a prominent use case for [[Glamorous Toolkit]]. +
Note that [[Glamorous Toolkit]] is not (yet) a development environment for Python. What is described here is "data science" on a Python codebase. You analyze the code, but you cannot change it. For Pharo Smalltalk, there is excellent code refactoring support in addition to analysis features. +
I think this is probably covered by [[Glamorous Toolkit]] (cc <@499904513038090240> who is a core user)! +
Thanks for [[Glamorous Toolkit]] . Watched the video and understood most of it. Impressive, and maybe the future, but not quite what I wanted now - it requires a fluency with creating new types of object on the fly and so a change in orientation. I want something that I can tag the methods with (say) 'PDF conversion', 'prototype`, etc. I don't mind dumping that as static docs and navigating with Obsidian. +
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 🙂 +
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. +
we're in the process of consolidating the ideas into group pages, so far the group pages are incomplete, but tomorrow (I'm on Pacific time, US) will work on that and take whatever ya write and move it over there 🙂 <@322545403876868096> got this started here: https://synthesis-infrastructures.wiki/Workshop_Working_Groups and then we'll split those up into pages in [[Category:Group]] +
H
Excuse me let me be a good role model on continuous archiving. One of the reasons I am excited about academics adopting [[Mastodon]] is because [[ActivityPub]] is built on [[Linked Data]], which i think inspires the possibility for fundamentally new modes of scholarly communication. I have written about this in the past ([[Has DOI::10.48550/arXiv.2209.07493]], but will do my best to decenter my own ideas except for when I am using them as a demonstration for others as part of a demonstration of using the technology developed for the workshop +
[[Blue Obelisk]] is (i.e. still active) a remote asynchronous collaboration with no central management or funding. A large part consists of nodes representing software packages. See [[https://en.wikipedia.org/wiki/Blue_Obelisk]]. It works because several of the authors knew/know each other and agreed at the outset to adopt an interoperability mantra "Open Data, Open Standards, Open Source" (ODOSOS).
Because everyone agrees the same approach to interoperability the nodes can develop indeoendently! The management is informal - a mailing list and occasional back channels. So there is a collaborative network - see WP article. +
I
Yes, as a scientist I also made this assumption. For example the [[IPCC report]] is 10,000 pages of scientific discourse. Hmm! +
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 +
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 +
J
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 +
[[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. +
thank you! [[meta]] why zoom instead of something like [[jitsi]] +