n120501
nfoWorks
nfoNote
nfoLocker
Concept
Diary & Job Jar
|
|
n120501
nfoWorks
nfoNote |
0.00 2012-09-24 11:20 -0700 |
Status |
Date |
Description |
|
| 2012-09-24 | Based on the thinking reflected in the item just below, nfoLocker approach should be in devNotes and cross-linked as indicated. Many of the items backwards from #68.100 will fit more conveniently there. The Approach will need to be consistent with priorities in the 5P, which will be at nfoLocker Concept anyhow?? | ||
| 2012-09-24 | Consider how to work a separation between nfoLocker Concept, nfoLocker Approach, and detailed development activities. I think nfoLocker approach could be here or separately, depending on convenience. I am thinking separately is better, with cross-referencing. The approach can be specific about concept. The concept should point to the latest approach. That should be OK for managing interdependencies. | ||
| 2012-09-24 | With regard to platform targets, it would seem to be where current implementations of ODF are found or under development and where the platform provides appropriate security for a security-providing application. | ||
| 2012-09-24 | Work backwards through the #68.99/.100 pages to collect items for this folio and also the ones that go into development. There are a variety of requirements to be considered and prioritized. It is not clear which go here and which go with specific developments. Since this is nfoLocker, it is not necessary to be shy about going beyond the specification of an ODF supplement and also addressing the proof of concept and ultimate availability of hardened libraries and fixtures. | ||
| 2012-09-24 | Set this up as a multi-page folio, but there will only be the single "current" folio tree, accessed via n120501b. So it represents some sort of set versioning. When a subordinate page is itself not just revised by supplanted, that forces supplanting of "latest." So it will generally be the case that the sub-pages are supplanted first, and then the supplanted "latest" that refers to them is introduced. | ||
| 2012-08-18 | The conceptual organization can be handled in a set of diagrams. This should identify all of the resilient components that go into the procedure. Note that the package can have a custom implementation and so can the manifest and encryption.xml document. (Maybe this should be nfoLocker.xml?) | ||
| in progress 2012-09-24 |
2012-08-18 | Include 5P considerations as well. This may need to be reflected in the individual development bits as well. [dh:2012-09-24-11:01 The 5P are being developed on a dry-erase board. They will be included on a folio page here. | |
| in progress 2012-05-11 |
2012-05-03 | 0.01: Add and refine the basis sketch of what the functionality and constraints will be. See notebook #68 and preceding material, as well as a few e-mails that expressed the basic idea. d120501, d120501c | |
| done | 2012-09-02 | Clean up page titles and links to be correct for n120501 and in the latest styles for page format and page encoding: n120501, n120501a, n120501b, n120501c | |
|
done 2012-05-11 |
2012-05-03 | Elevate the general fragment identifier problem throughout the notes collection | |
|
done 2012-05-05 |
2012-05-03 | Review n100401 for fragment identifiers and correct crosslinks in the title blocks that were not updated in the n08xxxx boilerplate. | |
|
done 2012-05-04 |
2012-05-03 | Correct the form of fragment identifiers: n120501, n120501a, n120501c | |
|
done 2012-05-04 |
2012-05-03 | Add to the catalog | |
| done | 2012-05-03 |
|
|
| done | 2012-05-03 | Make placeholders for n120501, n120501a, n120501b, and n120501c | |
| done | 2012-05-03 |
Create this page ready for recording Diary & Job Jar items of this nfoNote. |
|
created 2012-05-03-15:56 -0700 (pdt) by
orcmid |
