nfoNotes
Job Jar & Diary
n000000>
2010-04-11-13:45 -0700
|
|
nfoNotes |
|
| Status | Date |
Description |
|
| 2010-04-11 | Deal with abstractions and the definition of OpenFormula operations and functions | ||
| 2010-04-11 | Make a page that describes the plumbing levels, and deals with octet streams, XML streams, and Zip packages | ||
| 2010-04-11 | Make an OpenFormula NumCheck folio | ||
| 2008-05-06 | n080501: Make a folio on ODF verification and conformance assessment. | ||
| 2008-05-06 | n080501: Make a folio on ODF resources because some are showing up in clippings and will need to be drawn over from the diary. | ||
| 2008-04-17 | A harmonization markup of ODF would be yet another document. I wonder how that is permitted to be adapted. Check the notice in the documents. | ||
| 2008-04-17 | n080404: Make folio for International Standard IS 26300, OpenDocument [dh:2008-04-17 These serve as models for what will be done for OOXML and other relevant specifications, with their caching.] | ||
| 2008-04-17 | n080402: Make folio for the OASIS OpenDocument TC | ||
| 2008-03-31 | I need to get from Bootstrap Stage to Hard Hat Stage [dh:2008-04-16 We are in Hard Hat Beginnings now and I think I will leave it like that until the end of April when I am ready to flip a switch and have more interesting notes. One problem is going to be bringing related sites up to speed with nfoWorks.] | ||
| 2008-03-31 | Act on the 2008-03-30 #60.113 notes and start building genuine content. | ||
| 2008-03-14 | I need some sort of Envisioning or Approach folio that accounts for where we are and what the overall game is. I am not sure how exactly I want that and I may draft something to see how it actually works. [dh:2008-04-16 The "About nfoWorks page provides some of that, but not very specifically. Hold this thought.] | ||
| 2008-03-13 | Create a folio that has the open-source license we intent to use. This will be a professional appearance document-engineering deal too. | ||
| 2008-03-13 | Create a folio that has the Creative Commons information and license information that we operate under | ||
| 2008-03-11 | Start working back through paper notebooks where there are topics and notes and links that could move to notes here. | ||
| 2008-03-11 | Move notes to some easier backlog place and remove the clutter from this job jar. | ||
| 2005-12-28 | I've started using the term "document engineering" and it refers to some of these folio structures and conventions that I have been evolving in the time since this particular job jar was begun. The best example is at http://NuovoDoc.com/products right now, where I finally created a bridge between professional-appearance forms and the document-engineering forms. I really like that, whatever structures might be used for them. These are going to show up as TROSTing patterns, because it is about that, although nfoWare's commitment to confirmable experience is about that too. But I think TROSTing is the central place to deal with that, even though I can carry pattlets here too. | ||
| 2005-12-26 | Notebook #49.35-36 have some observations and thoughts about document processing and its topics, the need for long-lived documents and how preservation is to be achieved, etc. | ||
| 2004-03-13 | I want to honor what Doug Englebart means by Bootstrapping too and reflect that and acknowledge the connection with that way of thinking. I notice two things right off: the journey does not resemble the result, and the result may not be in the artifact as much as who we are being in the matter of augmentation and how that is expressed in the artifact. I am also mindful of Kierkegaard's door and Wittgenstein's ladder. | ||
| 2004-02-15 | An interesting document-processing project is to carry versions and difference files of the IETF RFC catalog. And then to have a tool that scrapes the index.txt files into a database view, with changes and additions searchable and reviewable. This should provide ways to make quick links to replacement RFCs, etc., and also to go get the RFC. This makes a nice little information-processing tool and demonstration of a number of Situating Data principles. Something about Information Architecture too. | ||
| 2004-02-13 | Make a FrontPage template for the notes pages that I will be creating here. | ||
| 2004-02-01 | It occurred to me that this business about media recording-life is related to software engineering principles, and also ISO 9000 ones with regard to risk management and preserving an account of the basis for decisions, not just what the decision is, and the assumptions about operational conditions that should then be verified regularly. There is something here about accountability and trust and managing risk. I don't know where more should be said about this, but someplace. Data and Accountability and the like. | ||
| 2004-02-01 | I am wondering about risk management (reading CACM 47, 2 (February 2004), 61-65) around media for data. It would seem that, at the beginning of a project, one needs to record data on the intended media very early and use this as an early warning condition on the deterioration of recorded media that is created when a system is in production. Then there are lots of conditions to keep data on (including tracking batches of new media, etc.). And finding out what vendors do to establish the retention life of their media, etc. | ||
| 2004-01-16 | Bill Anderson and I are running into more problems about coherence and the failure of email clients, for example, to have specified, confirmable behavior. A lot of what goes on is kept transparent and it just works, and when it doesn't work the breakdown and the degree of inscrutability are pronounced. It occurs to me that there are aspects of trust, confirmable experience, coherence, and toolcraft all wrapped up in this. And software engineering. I am not sure how to get this all handled. It would seem that the first thing to do is even be able to describe the situation, and then look for appropriate tools. | ||
| 2004-01-10 | Oh my, accessibility for nfoWare/nfoWorks. Now there's a serious spiral. I really don't care about WAP and PDAs and such, but accessibility is an issue. And, where does the first spiral fit? [dh:2008-03-11 Applies to nfoWorks too.] | ||
| 2004-01-10 | Bring back the Jack Dennis material on reproducibility as one of the inspirations of confirmable experience. This is a big deal. [2004-02-19: It is Earl Van Horn, not Jack. I should definitely do this, too.] | ||
| 2004-01-10 | I keep wanting to bring back the Jack Dennis work on references in virtual processes, and what I thought I had accomplished with it. It may need to be used to make mirrored-referencing work properly with different locations of the material. | ||
| 2004-01-10 | With regard to cross-references and such, there is also the interesting challenge about using a (potentially-dated) mirror and needing to have some way to link to the genuine image of the material. I can get some of this from the ODMA site where I worked on this a little. This needs to be spiraled too. There is something to be done with the identification of link types and also having this work on/from a mirror. | ||
| 2004-01-10 | The style guide for nfoWare/nfoWorks needs to point out that nfoWare/nfoWorks is always shown in bold italics. This is a hint to create a style guide here. [dh:2008-03-11 Applies to nfoWorks too.] | ||
| 2004-01-09 | There is something to be said for being able to do it by hand and then to automate. Most of what we have on nfoWorks is presently "manual" (with the help of web servers, FTP, FrontPage 2003, and a bunch more invisible technology under that). That is to say, the content is mostly developed by hand, except for some use of special FrontPage extensions for inclusion of material. But nothing very active is happening with these pages (er, well, except that it all works with browsers). That is, there is no scripting and no content processing/generation on the server, and most of the text is here because someone typed every word of it at a keyboard and it is included explicitly in the HTML that carries the content. Sheesh [dh:2008-03-11 still a problem after all these years.]. | ||
| 2004-01-09 | Why nfoWorks? Lest I forget, how was the name chosen, what was the original idea for the domain, and then what happened that caused this to be expanded? Also, include something on nfoWorks as artifacts: documents, articles, books, as well as software. There might be physical artifacts of a different kind as well, so one might speculate on that as a thought problem. [dh:2008-03-11 an nfoWare question that seems to apply to nfoWorks too.] | ||
| done | 2010-04-11 | n100401: Make a folio on Attribution, especially for the blog pages | |
|
done 2008-04-19 |
2008-04-17 | n080403: Make folio for the OASIS OpenDocument Specifications, with cached specifications (downloadable if permitted by the notice in the documents) | |
| done | 2008-04-17 | n000001: Add placeholders for n080402, n080403, and n080404 | |
|
done 2008-04-16 |
2008-03-14 | Create an "About nfoWorks" folio describing what nfoWorks is, as well as I can at the moment. [dh:2008-04-16 This is done and the about page has had all of its [tbd] items completed enough for now.] | |
| done 2008-03-14 |
2008-03-13 | Make 2008/03/n080301 the nfoDiary folio. This could be a full-up document-engineering thingy at some point. But not today. [Actually, I did make it a full-up document-engineering thingy.] | |
| done | 2008-03-11 |
|
|
| done | 2008-03-11 | Include old (earlier dated) notes from nfoWare to be reviewed for application to nfoWorks too. [dh:2008-03-11 See the preceding notes from years gone by.] | |
| done | 2008-03-11 | Customize from nfoWare notes/ to make first of nfoWorks notes/ diary and job jar. |
 |
created 2008-02-18-13:33 -0800 (pst) by
orcmid |
