Property:Contains text

From Synthesis Infrastructures
previous 202050100250500next 20
Showing 20 pages using this property.
.
...#joelchan86-22-11-12 17:53:19 +
hi peter, yes, the `[[...]]` (wikilinks) syntax has been quite widely adopted, spread from wikis!  +
A
A System for Interleaving Discussion and Summarization in Online Collaboration#sneakers-the-rat-22-11-12 16:02:25 +
[[A System for Interleaving Discussion and Summarization in Online Collaboration#Evidence]] This section of the document references some [[Other Work]]  +
A Turn for the Scruffy#sneakers-the-rat-22-11-12 03:30:30 +
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?  +
Aakanksha Naik#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
ActivityPub#sneakers-the-rat-22-11-02 08:12:57 +
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  +
ActivityPub#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  +
ActivityPub#sneakers-the-rat-22-11-08 23:32:39 +
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/  +
ActivityPub#sneakers-the-rat-22-11-09 23:25:43 +
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  +
ActivityStreams#sneakers-the-rat-22-11-09 23:25:43 +
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  +
Akila Wijerathna-Yapa#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
Amy Zhang#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
Anagora#sneakers-the-rat-22-11-10 20:58:52 +
yes [[anagora]] does have a rough kind of federation! it's a very very permissive model which I love, markdown and plaintext with wikilinks, a lot of the wikis that it federates with are just git repositories of .md files 🙂  +
Andre Vacha#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
Angelina Lesnikova#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
Arthur Perret#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
B
Belinda Mo#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
Benjamin Goering#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
Blue Obelisk#petermr-22-11-13 09:06:34 +
[[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.  +
Brad DeGraf#sneakers-the-rat-22-11-12 19:32:48 +
[[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.  +
C
CLAIM#Wutbot-22-11-13 18:04:14 +
From the Gutenberg city of Mainz, the [[CLAIM]] home of modern intellectual synthesis and dissemination - thank you for your participation! I've enjoyed our discussions and look forward to their continuation!  +
Retrieved from "https://synthesis.jon-e.net/index.php?title=Property:Contains_text&oldid=1043"