Conversation
|
Curvenote Preview
|
nokome
reviewed
Mar 26, 2026
nokome
left a comment
There was a problem hiding this comment.
Some initial minor comments. Will come back to it tomorrow.
|
|
||
| The easy answer would be to upload PDFs as blobs and call it done. But that misses the point. A PDF on a decentralized network is still a PDF — opaque, monolithic, and inert. The interesting possibilities emerge when we represent the _content itself_ in standardized, structured ways. Structured content enables deep links into specific sections, figures, or claims. It enables [modularity and composability](https://articles.continuousfoundation.org/articles/how-modularity-changes-systems) — individual components of a publication that can be referenced, reused, and recombined independently. And it enables distributed annotations — third parties adding new layers of meaning on top of the original text, without the author or the hosting platform needing to do anything. These are the capabilities that make decentralized scientific publishing worth pursuing, and they all require structure. | ||
|
|
||
| We've taken a first step. The OXA [AT Protocol lexicon](https://oxa.dev/articles/documentation/atproto-lexicon) defines the schema for representing scientific documents as structured records in any [Personal Data Server (PDS)](https://atproto.com/guides/the-at-stack) — discoverable on the network's [firehose](https://atproto.com/specs/sync), portable between hosts, and subject to the same sync, auth, and moderation primitives as a Bluesky post. There's still a lot of work ahead, but the foundation is in place. |
There was a problem hiding this comment.
I feel like a better segue from "they all require structure" is to first briefly intro OXA as a schema for structured documents, and now we're bring that schema to the Atmosphere with the OXA Lexicon. Creates a logical pathway that builds from a community coalescing around a schema for scientific documents and leading onto new forms of publishing.
|
|
||
| A few choices are worth calling out: | ||
|
|
||
| **OXA defines its own facet lexicon** rather than reusing Bluesky's `app.bsky.richtext.facet`. Bluesky's facets are designed for social microblogging — mentions, links, and hashtags. Scientific documents need typographic formatting: emphasis, strong, and in the future subscript, superscript, inline math, and citations. The `app.bsky` feature union is also closed, while OXA's is declared with `"closed": false` for extensibility. |
There was a problem hiding this comment.
The
app.bskyfeature union is also closed, while OXA's is declared with"closed": falsefor extensibility.
I know I wrote this originally, but it needs to be checked.
Co-authored-by: Nokome Bentley <nokome@stenci.la> Co-authored-by: Rowan Cockett <rowanc1@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.