C000000: DMware Construction Job Jar & Notes

Status	Date	Description


	2007-05-02	N000701: Make a folio for the project notations and then use an include page to have the current notations summary on the front page.
	2007-04-30	Cross-reference the notes and the Astraendo catalogs. There will be further prospects for confusions later as I get into development and techniques
	2007-04-29	If necessary, create redirects from n000000 and n000001-log.htm to N000000 and N000001.
	2006-06-08	Move the notations article into a Note. Then include it up there because it is referred to up there. I should move some of the references over time.
	2006-06-08	N021001: Self-Reference in ‹ob›. This is definitely a cross-over paper. It really is about Miser and especially obs, but it is also about self-reference as an abstraction in computer science. I need to be reconciled about the notion of truth that is used too. I need to think about the ways that a code can appeal to elements of itself. This is in some sense a crude form of reflection that is sensible internally only (unless computational logic allows otherwise). There is self-reference all over, in terms of being able to refer to components of the code itself at the appropriate time. This is going to bear further thinking. There is self-reference as internal reflection, but not contemplation or consideration. It would be interesting to see if there was something that could have that interpretation.
	2006-06-08	N021000: The well-definedness bind. This is important in the treatment of Peano Arithmetic too. It is a Miser Note, because it relates to what I can do in oMiser with regard to preserving mathematics. One thing I want to do here is decide what the proper name for ob.proc is. In some sense it is ob.code, not ob.proc, and I need to think about that, because identity is all based on code even though the performance may be different. But this is one of those cases where that doesn't matter.
	2006-06-08	N020701: Embracing the Transfinite. This is definitely Astraendo. It is inspired by early discussion on phil-logic.
	2006-06-08	N020700: Managing Miser-Theory.info. This may be unnecessary or it should be over in the construction section. Figure that all out when the time comes.
	2006-06-08	N020600: oMiser Sketch. This needs serious repaving and refactoring into a folio. This will all work, although it will be disruptive to have N020600a be the job jar. I can move just N020600a to a higher letter and work the rest all right, I think. Once I have the job jar, I need to do serious repaving. I will leave the images and drawings to make sure they can be linked from all versions. But I will go to updated folio structure and use include pages into the synopsis section.
	2006-06-08	N020300: Evolution of Ob Structure. This is a Miser Note. This is an useful historical account. It needs a folio structure badly. Things to include involve (1) starting with Plex, (2) switching to list structures, (3) using individuals as generators of classes of singletons, and (4) the current scheme with individuals, singletons, and pairs.
	2006-06-08	N011101: Miser Synopsis Concepts. This one stays here as a folio. It might be a glossary rather than a concepts statement. Take a look at this.
	2006-06-08	Fix the standard structure on this page, using the proper fonts and title block for a catalog. The catalog needs to reflect N000001 and N000000 and have the usual form.
	2006-06-08	R010101 and R010101a - These need to be made into a folio and linked to the developments here as further information and more details.
	2006-06-08	N010207: What's An Algorithm. OK, this is meant to be a serious treatment of this particular topic. I think this belongs in Astraendo. Miser Notes are really to be specific to Miser and Frugal and thinking about them, techniques, discussions, etc.
	2006-06-08	I need to clean up the N000001 page to list only those articles that have been started, and remove the shading business. The never-initiated folios need to go into a job jar for reincarnation as opportunities arise.
	2006-06-08	N010205: Programs Are Rarely Algorithms. This one also deserves a folio. It is also an Astraendo. This is one I want to elevate to discussion fairly soon, because it relates to the problems of defects in programs that has been illustrated lately.
	2006-06-08	N010204: Framework Versus Structure. I am not sure what in my Programs Are Rarely Algorithms pitch led to this, but it is a worthy topic, and it might be better grounded around the Miser Project. I will look for inspiration when it is time to work this one over. This is probably an Astraendo.
	2006-06-08	N010202: Homage to the Bit. This needs to play out the original abstraction idea, along with the notion of features, tied to the manifestation notion. This is clearly Astraendo, illustrated by thinking around Miser and Frugal, especially Frugal.
	2006-06-08	N010201: Manifesting Abstractions - this is related to homage to the bit and so on. This deserves preservation as a folio with an include-page tombstone at the top level. This is clearly Astraendo.
	2006-06-08	N001100 : Computational Notions of Truth. This is on Computational Notions of Truth and deserves some further work. I just realized that I don't want ob-yes and ob-no, or I need a good explanation of why I do or don't have them. In the case of ob equality, there are simply two answers. They are automatically duals. And this is the only operation in oMiser that returns a "truth value." So the operation is not really a relationship as much as it is a comparison. The results of the comparison and the conditions for the result are clearly defined. This raises an interesting problem. This could be Astraendo as easily as Miser-Theory. I think it is Astraendo illustrated by oMiser.
	2006-06-08	N001000 convert to a folio with a single tombstone. This is Miser as theoretical system. It involves the Einstein quotation. There appears to be some serious rework required.
	2006-06-08	Create a nested notes/yyyy/mm/ folder structure for these notes and reorganize into folios with their own job jars.
	2003-12-19	I have to think more about data. I notice that UML is a great example of how the content of language is not in the inscriptions. The UML diagrams and the technique have almost not semantics at all. That UML is a formal scheme with no formal content is striking. However, we operate in data and text languages the same way. So the insight is that it is nothing new, rather than there is some defect of UML. UML is a great example of language acts. I think this is because UML is proposed to be descriptive. [dh:2004-01-06 I think this goes under situating data in nfoWare, so I will move this note there.]
done	2007-05-02	N020600: Set up folio in the appropriate place and map the current materials to that location. There will be a mammoth number of repairs necessary just to get all of the links and images to work. I will also need to monitor the site log for failures involving any of these pages.
done 2007-04-30	2007-04-29	Make some sort of note at a higher level to indicate that there are changes made with regard to case sensitivity and there may be breakage until we get everything tidied up.
done 2007-04-30	2007-04-29	Capitalize the note filenames in the development-site folders and leave the capitalizations in the file system and VSS.
done 2007-04-30	2007-04-29	Use the proper title block sizes and styles for this header and the catalogs.
done 2007-04-30	2007-04-29	Add N000000 and N000001 to the catalog.
done 2007-04-30	2006-06-08	Fix N000001 to have the standard structure.
done 2007-04-30	2007-04-29	Update N000001 to use the modern format for title block, construction block, and the catalog layout.
done	2007-04-29	Find any uncapitalized note names in the file system and replace them with capitalized ones.
done	2007-04-29	n000001-log: Rename to N000001 and make sure that is the form used on the site.
done	2007-04-29	n000000: Rename to N000000 and make sure that is the form used on the site.
done	2006-06-08	N010205: Fix the algorithm statement and put in the version of Python used. Add history notes about this part. Contract to the top section. I need to put in the version 1.5.2 version and the date of the code. Also, this gives me something I can post about.