C000000: DMware Construction Job Jar & Diary

Status	Date	Description

	2004-11-16	Make construction zone at the root level.
done	2004-08-26	Use relative link to the root in the C000003c "You Are Here" block.
	2004-08-26	Refresh the Root level to have proper construction zone, styles, and links to newer material (such as the /license section).
	2004-08-26	Tie the C000003c to C000003 in the same was as for construction material too. But refresh C000003 first.
	2004-08-26	The C000004 page is referenced from "You are Here" on those pages. That pages needs to be reviewed and refreshed.
done 2004-08-26	2004-08-23	Redo the C00000xc.htm Include Pages to provide more-accurate statements. [dh:2004-08-26 Cut loose from AIIM and also make more meaningful to casual visitors, with less emphasis on scaffolding lore.]
	2004-08-20	Conform the DMware /project construction zone to current practice and continue over there.
	2004-08-20	Adjust DMware /project structure to follow the techniques of Orcmid's Lair and NuovoDoc.
in progress	2004-08-20	Update Construction Structure and Construction Materials in the construction section to conform to HTML 4.01 and title styles. C000000, C000003, [dh:2004-08-26 this is a refresh for here]
	2004-08-20	Update C000005 materials to conform to the latest nfoCentrale.net HTML 4.01 and title styles.
done 2004-08-23	2004-08-20	Create project for customization of license suitable for ODMA materials and files.
	2003-08-30	Create the DMware, NuovoDoc, Orcmid's Lair, nfoWare, eoWare separation for appropriate modeling. DMware is going to be focused on open, standards-based resources, including ODMA.info and DMware-tech.info.
	2003-08-30	I was thinking about the character-stream stack and situating it. This is, I suppose, data ware or other to do with transport, but I won't be too picky about this. The situation of character streams for XML is important -- indeed, crucial. Then there is the situation of character streams generally. I can see a retrospective that goes back through serial connections, and down to punched cards (Hollerith). Looking at the lifecycles of these media, their lifespans of use (when did the major university centers remove card readers from their systems? Who still has an 010 card punch and any cards to go with it). There are very rich sources on the toolcraft of punched cards and the evolution to the 80-column card (and the 96-column System 3 abberation). This is a great study because of the relationship to document preservation. Having some time lines would be really valuable because the view of Moore's law and Internet time also holds. Also, the RS232 connection and standard, while there are still serial ports on computers, is also a valuable case. The modem distinction is important. This all fits into the macroscope notion of Dennett as well.
	2003-08-30	I have been thinking about situating XML and the additional problems of situating electronic documents. This leads to recognition of Docware as a different layer. I was also thinking about Document Engineering as well as Information Architecture. Document Engineering, Document Processing, and Document Architecture go together and one aspect of Document Engineering is requirements tracability and life-cycle concerns. This is separate from nfoWare (which is a business angle), and eoWare which is still further out in this picture. I need to look at a division between NuovoDoc and DMware that makes sense and at the same time honors the DMware element. It is appropriate to refer to DMware from NuovoDoc and nfoWare, but not so appropriate to link in the other direction as other than just-more-resource-among-many. I am satisfied now that I can work a division.
	2003-08-16	Update C000004 to provide a proper overview of construction structure and construction materials.
in progress	2003-08-16	Change the C000004 materials on construction sections to refer to construction materials. Go see how this is done on orcmid.com and the GR3 project. C000004c done,
	2003-08-16	Change the C000004 materials to allow for construction zones. Re-knit the structures accordingly at some point.
	2003-08-16	Renormalize here and then renormalize with those sections that support XMLware and the XML Imaging Wrapper project.
	2003-08-16	Renormalize to the HTML 4.01 style requirements currently established with orcmid.com
	2003-03-19	Find a way to have a CD-ROM be browsed properly even though there is no server controlling the delivery of default pages for the directories of the site.

	2002-12-14	Illustrate a problem of coherence and confirmable experience with document systems using the difficulty of font changes on views of this very site. Provide it here in the construction section of the development site so that it travels with the mirror. There can then be links to sites where these ideas are further developed.
	2002-12-14	Document and illustrate, or find a source on the problem of material that may move between generic and anchor-site or development-site specific over time.
C000001	2002-12-14	Isolate Anchor-Site Dependencies. Create a standard procedure for isolating the anchor-site dependencies of any given physical mirror, so that it may be ported to a different anchor site with little or no change.
2003-03-19 partial solution	2002-12-14	Normalize Web Pages to HTML Standard. Find a filter that normalizes all of the DMware pages for conformance to a specific level of the HTML standard. The present pages are not standard (e.g., there is no DTD specification). dh:2003-03-19: We are specifying HTML 4.01 for pages when we next touch them, although there is one Microsoft FrontPage customization involving a special <body> attribute. We are going to tolerate that.
	2002-12-14	Cataloged-Item Cross-Reference Structure. Account for the way that catalogued items are cross-linked with the catalog and how subordinates are cross-linked.
	2002-12-14	Capture Older Job-Jar Items. Go to the end of 1999 (orcmid notebook #17 starting 1999-19-09) and recover items. DMA and ODMA go back farther than that.
	2002-12-14	Redirection of Links. Find a way to redirect links so that off-line versions of a document can find off-line versions of linked documents when it is desirable to stay local (e.g., when mirrors of DMware.info and ODMA.info are on the same CD-ROM). Maybe can be done with client-side JavaScript, and works based on where the page came from?
2003-03-19 partial solution	2002-12-14	Make Style Maintenance Easy. Consider putting some kind of markup inside of DMware.info web pages so that a mechanical process could go through and update certain styles mechanically. Have it be in a way that does not require browsers to support Cascading Style Sheets. dh:2003-03-19: I have a partial solution using Microsoft FrontPage styles and include-page components.
C000000	2002-12-14	Make a Job Jar
	2002-12-12	Create Style Catalog. Set up a construction description for all of the styles that there are - table entries, title blocks, construction blocks, color-shading conventions, grounding cloaked pages, version information, etc.
	2002-12-12	CD-ROM Archives. Create construction structures for anchoring DMware.info, ODMA.info, and DMAtech.info on a commemorative CD-ROM to be available at the time of AIIM 2003.