Add ontodag-fs to Tools - #41
Merged
Merged
Conversation
This was referenced Aug 10, 2026
crtahlin
added a commit
that referenced
this pull request
Aug 10, 2026
* chore: add .gitattributes normalising text files to LF README.md is the only file in the repository with CRLF endings; it was LF from the initial commit until a single edit in April 2026 introduced them. Contributors on normalising editors therefore rewrite all 150 lines, turning one-line additions into ~150-line diffs (#40, #41) and creating avoidable conflicts between PRs that append to different sections. merge=union on the lists keeps both sides when two branches each append a different entry, matching sindresorhus/awesome. Refs #42 * chore: normalise README.md line endings to LF No content change: the file is byte-identical once carriage returns are stripped. Isolated in its own commit so the one-off 150-line diff is reviewable here rather than buried in a contributor's feature PR. Refs #42
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
crtahlin
force-pushed
the
add-ontodag-fs
branch
from
August 10, 2026 10:15
b605e31 to
9c3ad95
Compare
crtahlin
approved these changes
Aug 10, 2026
crtahlin
left a comment
Collaborator
There was a problem hiding this comment.
Approving — entry checks out.
- Format: 147 characters, sentence case, link resolves, not already listed.
- Repository: public, not archived, BSD-3-Clause, actively developed, with tests and a spec.
- Description matches this repository rather than the sibling
ontodag, and is honest that v0 is read-only. - Tools works as the section: the
odag-fsCLI and the FUSE mount are the user-facing surface, which distinguishes it fromswarmfsin Libraries.
I rebased the branch onto main and force-pushed, since #43 normalised the repository to LF line endings and landed between your submission and this review. That turned the diff from +152/−150 into the two lines actually being added; your authorship is unchanged. Apologies for touching your branch — it was our change that caused the conflict, and the fix was already verified locally.
Cafe137
approved these changes
Aug 10, 2026
yjkellyjoo
approved these changes
Aug 10, 2026
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.
Adds ontodag-fs to the Tools section.
What it is. A semantic filesystem in the tradition of Gifford's Semantic File System: directory names are interpreted as queries rather than locations, so
/pet/dogmeans "everything that is a pet and a dog" and/dog/petis the same place. One file appears under every path it belongs to — no copies, no symlinks. Paths can also carry typed bounds, e.g.ls '/parcel/weight(..5kg)/.all', computed exactly. Ships anodag-fsCLI (ls,tree,cat,info, an interactive prompt,--as-of ROOTfor past versions) and a FUSE mount via fusepy.Swarm relation. File content lives on Swarm, fetched through swarmfs (already listed here); the classification lattice persists through recordstore (also listed) against a Bee node. A file's identity is its Swarm content address, so a classification can never dangle — there is nowhere for the content to move to. The repo owns no state of its own;
OntoDAGFileSystemis a plain fsspec backend, so the whole fsspec ecosystem (pandas, pyarrow, DuckDB, …) reads Swarm-backed content through it too. Verified against a live Bee light node on Gnosis mainnet.Status is stated honestly in the description and the repo: v0 is a read-only view — browsing is complete and tested; filing through the filesystem is in progress.
Checklist
BSD-3-ClauseLICENSE, active (last push 2026-08-06).ontodag).README.md/archived.md, and no open PR or issue for it.🤖 Generated with Claude Code