atomic-cli-0.15.0 is not a library.
atomic (CLI)
Status: pre-alpha
A command-line application to create, read and interact with Atomic Data.
atomic 0.12.1
Joep Meindertsma <joep@ontola.io>
Create, share, fetch and model linked atomic data!
USAGE:
atomic-cli [SUBCOMMAND]
FLAGS:
-h, --help Prints help information
-V, --version Prints version information
SUBCOMMANDS:
delta Update the store using an single Delta
get Traverses a Path and prints the resulting Resource or Value.
help Prints this message or the help of the given subcommand(s)
list List all bookmarks
new Create a Resource
populate Adds the default Atoms to the store
tpf Finds Atoms using Triple Pattern Fragments
validate Validates the store
Installation
Install Cargo to build from source.
Install using crates.io:
Or build from this repo:
# Install atomic to path
Usage
# Learn how to use it
# Try some commands
Progress
- Stores & reads stuff from and to .ad3 user files on disk
- A
newcommand for instantiating Atomic Classes - A
listcommand for showing local bookmarks (mappings) - A
getcommand for finding resources and parts of data using Atomic Paths with...- AD3 Serialization
- Basic JSON Serialization
- RDF (Turtle / N-Triples / RDF/XML) Serialization
- Fetch data from the interwebs with
getcommands - Works with
atomic-server(fetches from there, stores there, uses domain etc.) #6 - A
deltacommand for manipulating existing resources - Tests for the cli
- A
mapcommand for creating a bookmark and storing a copy
Config
Atomic creates a ~/.config/atomic folder, which contains a mapping.amp and a store.ad3.
Mapping
The Mapping refers to your user specific set of shortname-URL combinations.
This Mapping lives as a simple text file in ./user_mappping.amp.
person=https://atomicdata.dev/classes/Person
What this should be able to do
This serves as a UX story that guides the development of this CLI.
# Add a mapping, and store the Atomic Class locally
# NOT YET SUPPORTED
# Create a profile for yourself
# By default, atomic creates IFPS resources for your created data, which are publicly stored
# NOT YET SUPPORTED
# Add a mapping for your newly created resource, so you can use that shortname instead of the long IPFS url.
)
# Instead of link to an Atomic Server where you can upload your stuff
# If you don't, your data exists locally and gets published to IPFS
# NOT YET SUPPORTED
# install ontologies and add their shortnames to bookmarks
# when no URL is given, use the Ontola repo's ontologies