-   Terms of Use and Privacy
Dream | Journal | Memory | Subject
cutup   rss
  -   Terms of Use and Privacy
Dream | Journal | Memory | Subject
cutup   rss

<<   <   >   >>

2020-12-04 | Journal | Break Barrier

There is this idea that there are certain blocks to creative motion forward in some particular areas. I've had these blocks for years at a time. Somehow the particular item or investigation that was so crucial at one time, stalls, and it builds an even stronger barrier. Instead of breaking through, there are hundreds of other detours and other efforts, some seeming just as creative or interesting or productive, but sitting there, an old granite wall that just gets thicker and scarred, is the real block.

Right after I got laid off, over a year ago, I pushed to get the full, explodable DFD working. I created a few levels down for one area, but that is as far as I got. I haven't been able to look at it much, since. I got lots of other stuff working, like getting MCJ running on full wxPython or my dream that led me to complete L1G3R. The whole time, though, I didn't complete the explodable DFD.

I can look at this a couple ways. Sometimes this is just a pure block, and there is no other good reason. The block just grows and you can't push past it. But sometimes there is a reason, lurking in the background that you are unaware of, but when you are ready, it is also ready for you. I broke through today. I cracked open the DFD, Component, and flowchart code, and started working on them. I found the triples code that I used to generate the SPARQL in this article. At the same time, though, I remembered that the triples are wrong. I discovered this when I tried to load them here. I suspect that I need to refactor some of my triples, as they may not be proper. I'd like to keep it simple, to keep with my file-system idea. Any application to DFDs or system component diagrams or data-flow should be relatively simple to be useful.


2020-12-05 :

I found this this morning. It references a DFD the authors created that is published here. This is exactly what I need to get my cruftbuster stuff in line with a published ontology. It is not based in BFO, but I'm more concerned with simplicity and minimal inference, which I imagine this will do just fine. The article does not deal with levels, but I already have some conventions that help in this regard. Finally, this provides something that should also be compatible with owl2vowl.

ouroboros cruft_buster ontologies

Articles tagged with ouroboros on Aggie Codrust:

2020-04-29: Victory Lap
2020-04-17: MCJ Tomoe
2020-04-04: MCJ wxPython
2020-03-13: DAGs Splendid
2020-02-29: wx Supply Chain
2020-02-28: Will it scale?
2020-01-10: What is the goal?
2020-01-02: Pause If Weird
2019-12-31: 7 o'clock
2019-12-21: What is the problem?
2019-12-09: Bootstrapping
2019-12-09: Core Structure
2019-11-29: What am I Doing?
2019-11-02: Why? Hope?
2019-10-27: Too Complicated?
2019-10-26: Long Slog
2019-10-22: News Fluffer
2019-10-19: Breathing
2019-08-11: Forward and Backward

Articles tagged with ouroboros on Luv Counter XYZ:

2021-09-12: Bus Ride
2020-12-13: Ummm... Why?
2020-11-29: Taking Stock
2020-08-26: Home
2020-08-23: Global Virus Reach

Articles tagged with ouroboros on O.R.N.G.:

2019-08-07: Knowledge
2019-08-03: Bits of Tree
2019-06-27: Straight Down the Line
2019-05-19: Triple Tree
2019-05-18: Honeycomb Start
2019-05-11: Ouroboros Tree
2018-08-12: Data
2018-07-10: Woman Emerging from Manhole
2018-03-07: Braid of Life
2018-01-11: Train Circle
2017-11-05: Wu-Tang Clan
2017-10-23: proust
2017-10-13: Fire and Data
2017-10-11: risk of frameworks
2017-08-06: Finger Divine
2017-06-25: 1279 BC
2014-05-15: Circle
2010-11-02: Do you see?
2006-08-03: Information Markup