982
edits
Linked Data: Difference between revisions
→Markup Syntax: new section
(→Discord: new section) |
(→Markup Syntax: new section) |
||
| Line 8: | Line 8: | ||
|Text=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 | |Text=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 | ||
|Link=https://discord.com/channels/1029514961782849607/1037261659368067072/1037278126918619188 | |Link=https://discord.com/channels/1029514961782849607/1037261659368067072/1037278126918619188 | ||
}} | |||
== Markup Syntax == | |||
{{Message | |||
|Author=sneakers-the-rat | |||
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024 | |||
|Date Sent=22-11-03 22:51:30 | |||
|Channel=In terms of overlap with my own | |||
|Text=[[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 | |||
|Link=https://discord.com/channels/1029514961782849607/1037786518800039978/1037861609885925467 | |||
}} | }} | ||