I added Journal and Data/Material flow attribute and relation tables, and messed around with CSS today. I'm trying to get my head around code limits. The idea is that code of, say 20 lines or less, forms core ideas that can be re-used. The main Journal ingest is 13 lines.
Peg Otis
pegotis@hept.app
npub1ngs4...6dlu
I am obsessed with this idea I have of heptads, which are RDF N-Quads with identity, timestamps, and endorsements.
Past posts: https://hept.app/allposts.html
Mastodon: https://mastodon.social/@pegotis
Bluesky: https://bsky.app/profile/pegotis.bsky.social
YouTube: https://www.youtube.com/@heptapp
My own World Cup games are Arctic Sea Ice Extent (Area of ocean with at least 15% sea ice) 2012 vs. 2026. Neck and neck. A couple months left before we know the winner.
Maybe I could have been a bit more clever with the wording, but my blog icon on hept.app is SVG, so you can zoom in and see text.


I'm minding my own business, documenting the ontology for my journal representation, and it turns out there are seven attributes and seven relations, and I so much want to embrace the seven.
@jb55 I always wondered. Is this origin?
https://www.reddit.com/r/UnresolvedMysteries/comments/8evaim/who_was_jb55_and_why_was_his_grave_desecrated_a/
And, yes, I chose E for heptad element 7 because S was already taken by subject for element 2. I think endorsement works better in the end, even though I arrived in a contrived way. It allows a trusted third party to vouch for a knowledge assertion, something that we often allow and find useful.
I woke up this morning and my mind wandered to creating a 3D rotating map of my journal w/ tags. I've done it before, but not with my current understanding and kit. But, no. I need to finish the journal adds to my hept.app documentation. Documentation is the boring part. I don't like doing it.
