opensci.devopensci.dev

Hello OXA:AT

A post about publishing from Curvenote on AT Proto with OXA, published on AT Proto with OXA

Hello OXA:AT

This article is published from Curvenote's SCMS, via an AT Proto backend ๐Ÿš€ using OXA:AT and we're pulling this content and the entry in the main blog listing from my PDS.

Check for the record here: https://pdsls.dev/at://did:plc:he25xs7kizd6vw3z3pqb4tif/site.standard.document or in the dropdown above.

At atproto.science?

If were at the #atprotoscience sessions at the conference yesterday, I hope you asked Rowan for an oxa sticker, he guards the main stash! But if not, maybe you caught his keynote, know what OXA is and the work the Continuous Science Foundation is doing to grow and support that standard. Read on anyways.

What's OXA:AT

Disclaimer, the acronym OXA:AT is not official or anything, I literally just coined that for this post, but I think it fits.

What is official is the AT Protocol variant of the OXA representation, published in the lexicon over here: https://github.com/oxa-dev/oxa/tree/main/lexicon

Read more about that here: https://oxa.dev/articles/oxa-on-at-proto and as you'll see it's incomplete and under development so if you want to help shape and extend OXA:AT then get involved in the RFCs at https://oxa.dev/rfc.

How AT Proto is this?

The AT Protocol variant of oxa it 100% being aligned with ATProto principles with the aim to enable modular scientific work to be shared on the network, building on oxa as a standard.

In terms of this post, this is a first but awesome step at getting a Markdown based article packaged as OXA:AT and published via Curvenote's stack, then consumed this front end renderer (soon to be AppView?). The front end here is still getting it's feed from the SCMS's REST API and we've some more to figure out before we are scooping from the jetstream, and meshing the SCMS's features (packaging, versioning, publishing) with native distribution and discovery on AT Proto.

We are up and moving though! This already has got me thinking about versioning aspects that I think should be part of the one of the OXA RFCs.

Previous Versions

The previous version of this post, complete with typos, is at at://did:plc:he25xs7kizd6vw3z3pqb4tif/site.standard.document/3mi5pmxphkb26.