atomicdata-dev
Atomizer use case - semantic route planning
A concrete use case for Atomizer is a project I have sketched for some years now: Semantic route planning.
Idea is to collect most possible facts about a travel journey - times, geolocations, ticket prices, seat reservations, reimbursements, purposes (generally and for subsets), etc.
Initially I collected information in a wiki which I later rewrote as turtle and rendered (ab)using the Programme ontology: An archived Programme rendering is here with link at the bottom to the turtle source.
At later journeys I skipped the use of a wiki but wrote notes directle as turtle instead. But writing timestamps and waypoints by hand quickly gets boring and is prone to errors. And more importantly requires skills in a language most humans won't ever desire to learn.
A recent example of a complex journey is this where I also maintained a summary listing authored in markdown in a writing style that I imagine could potentially be machine-generated from semantic source: https://couchdesign.dk/india/
Would be cool if I could throw URIs like this and Atomic Data server would store the JSON-AD equivalent of lines 99-196 of this turtle file (i.e. the first day of this Programme rendering). And for my upcoming journey to Kosovo, I could throw URIs like this and this and atomizer would try scrape as much as possible from it.
Then, when I book tickets I would feed my PDF files e.g. from https://bahn.com/ - and CalDAV URIs exported from ÖFFI on my Android phone.
I could then create several outputs from that data - a slippymap with geodata, and an iCalendar file - both published for friends and family to be able to follow my journey as it unfolds, and an export for my accounting for use both in my own company and for producing documentation fr those sponsoring some of my trips.
