TaxisDB: A temporal, immutable, reflective, triple-oriented database engine built on YottaDB

[Athanassios Hatzis]

Read first: Every Database Had Its Own Storage Engine — Then Came Substrate Architecture
https://taxisdb.com/posts/every-database-had-its-own-storage-engine-then-came-substrate-architecture/

It explains where TaxisDB fits in the database landscape and the architectural idea behind it. YottaDB provides the transactional storage foundation. TaxisDB builds the database semantics above it: EATV transaction statements, identity, history, schema-as-data, reflection, constraints, assertions, retractions and indexing. TaxisBase then provides a reusable semantic layer for richer domain modeling and data querying.

Your feedback, criticism, and ideas are welcome. Drop me a line if you interested in participating in this project and how you would like to contribute.

For a pilot study, I'm looking to convert VistA data and FileMan routines into TaxisDB. Could someone point me to a release that has sufficient data, i.e., patient records with full history and connected FileMan globals (labs, meds, notes, encounters, etc.) rather than just an empty docker install? I'd like something realistic enough to validate the conversion pipeline end-to-end. Any recommendations for a distribution, demo dataset, or synthetic-data loader that fits this would be appreciated.  For example
https://github.com/WorldVistA/VistA-FHIR-Data-Loader

Is that recommended, has anyone tried this ?

Official Web Site
https://taxisdb.com

GitHub:
https://github.com/taxisdb/taxisdb
https://github.com/taxisdb/taxisbase

Hacker News:
https://news.ycombinator.com/item?id=49525733

Read the article first. Then tell me whether TaxisDB deserves to exist.

[David Whitten]

You probably can use the VEHU Docker image. 

This is a partially filled in docker image created as a support database for VistA classes at the VistA Electronic Health University classes. 

This should help you find them

https://hub.docker.com/search?q=VEHU

Dave Whitten

713-870-3834

PS: could you send another email (or a response to this one) that elaborates on some of your jargon ?

What is EATV transactions and how do they contrast with M transactions ?

Would a simple global reference like ^DPT(1564) be sufficient as an identity string for the M sub-tree below it ?

I assume schema-as-data is using a VA data dictionary as a reflection mechanism to define the constraints of some kinds of data. 

Would the intertwining of the Data Dictionary and the LABORATORY TEST File#63 be relevant ?

https://vivian.worldvista.org/dox/Global_XkxBQig2MA==.html

Fields in VA FileMan files are constrained by the Data Dictionary, for example in the INPUT TRANSFORM. There are also other constraints in the code.

How do you plan to handle the POINTER to other files ? VARIABLE POINTERS are also going to be a problem, as well as COMPUTED FIELDS. 

Finally, it would be useful to talk to George Lilly about his triple store code and design.

Likewise Conor Dowling has done some great work (FMQL)

They each have worked on SPARQL systems

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+unsubscribe@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hardhats/d17035a8-a651-4705-bbbd-4f0bebaeb771n%40googlegroups.com.