Toots for paulwalk@mastodon.social account

Written by paulwalk on 2025-01-01 at 10:01

This looks interesting - “Markwhen” - timelines in Markdown. https://thenewstack.io/introduction-to-markwhen-a-markdown-timeline-tool-for-devs/

=> More informations about this toot | View the thread

Written by paulwalk on 2024-12-17 at 07:58

My company - Antleaf - became a Samvera Partner this year. I’m very pleased to be able to work more closely with that community - there is a ton of good and innovative development going on there. Here is a summary of Samvera in 2024.

=> View attached media

=> More informations about this toot | View the thread

Written by paulwalk on 2024-11-27 at 07:11

OpenAlex is a significant development - it’s worth trying to ensure it doesn’t get co-opted by the usual suspects.

I’ve voted!

https://hcommons.social/@cameronneylon/113552274972532964

=> More informations about this toot | View the thread

Written by paulwalk on 2024-11-15 at 11:46

I seem to have unintentionally adopted the American Chemical Society style in my footnotes, e.g.

Production-Grade Container Orchestration. Kubernetes. https://kubernetes.io/ (accessed 2024-11-15).

Does this even matter?!

=> More informations about this toot | View the thread

Written by paulwalk on 2024-11-15 at 11:40

I'm not an academic, but I often write (semi)technical docs for academic-adjacent readers. My docs will often contain lots of links to websites, which I usually reference as footnotes.

I vaguely feel that I should be doing this “better”. Every couple of years I fire up Zotero and try to use that instead. But I'm then stymied by the need to choose a citation “style”.

Is there a sensible default for someone like me to adopt? Or shall I ignore the whole sorry mess and just go back to footnotes.

=> More informations about this toot | View the thread

Written by paulwalk on 2024-11-07 at 07:46

This is an excellent resource for software developers working with DOIs. It dispels all of the most stupid myths I have heard said about DOIs, and some others I didn’t know (e.g. the finer aspects of comparing DOI strings)

https://fosstodon.org/@joewass/113437281415235360

=> More informations about this toot | View the thread

Written by paulwalk on 2024-10-17 at 09:09

I recall, years ago, arguing with a prominent OA advocate who frequently blamed “librarians" for the sorry state of academic publishing. I repeatedly made the point that academics, as a class, were complicit in this. As @rmounce points out here, perhaps we are about to find out how much the "academy" really cares about open-access….

https://mastodon.social/@rmounce/113321871454385261

=> More informations about this toot | View the thread

Written by paulwalk on 2024-10-17 at 08:01

The COAR Notify Protocol has had a significant revision. Some highlights:

  1. Moved to new domain: https://coar-notify.net/

  1. Specification is now versioned https://coar-notify.net/specification/1.0.0/

  1. PURLs replaced in JSON-LD context & vocab terms

  1. Much better documentation of workflows using Mermaid generated flow-chart diagrams https://coar-notify.net/catalogue/workflows/repository-pci/

More details in news item: https://coar-notify.net/2024/significant-revision-to-specification/

=> More informations about this toot | View the thread

Written by paulwalk on 2024-09-06 at 10:54

The Making Data Count meeting has been... interesting….Much talk about how to "incentivise" researchers to share their data.

20 years ago, software devs figured out that sharing source-code was A Good Idea because it enabled them to build better software.

Academic researcher seem stymied by FOMO. "If I share my data before I've published, then someone else might get the credit and I won't progress in my career”.

Maybe academic researchers get the environment they deserve :-(

[#]MDCSummit

=> More informations about this toot | View the thread

=> This profile with reblog | Go to paulwalk@mastodon.social account

Proxy Information
Original URL
gemini://mastogem.picasoft.net/profile/109851871178164279
Status Code
Success (20)
Meta
text/gemini
Capsule Response Time
302.191804 milliseconds
Gemini-to-HTML Time
2.66872 milliseconds

This content has been proxied by September (3851b).