n130601a: Zip Format Abstraction

Status

Date

Description

2017-03-03

n130601: Need to figure out how would aspect for OPC that is also DCF-consistent.

2017-03-03

n130601: Physical layer is wacky and needs to be abstracted

2013-06-09

n130601 will share n130401-cache material. This is done rather than having to remove the common ones around.

2013-06-09

The data model used for the levels of Zip profiling require a means to express specializations and limitations of the layers on which a dependent profile relies. It may be appropriate to use some form of UML restriction model for this. I need a prefix for the abstract level. Maybe "x"? "v"? alpha? See what mining in OPC suggests. [dh:2013-06-09 from n000000]

2013-06-09

The various levels of self-extracting Zip techniques are also relevant. It is not clear when and how those enter in here. They need to be detectable, even if or especially when they are not executable on a given platform.

2013-05-26

For abstracting Zip I may need a separate treatment than for DCF. That's in order to account for the representation of DCF in Zip by appeal to a Zip abstraction, perhaps reconciled with OPC, but able to be used for at least verifying Zip files even if proprietary features cannot be worked with. The components can at least be identified and the package structure confirmed without using proprietary features. [dh:2013-06-01 from n000000]

2013-05-18

The CRC-32 algorithm needs to be obtained. See APPNOTE 6.3.3 section 4.4.7. [dh:2013-05-20 I have ordered the book that is cited in APPNOTE 6.3.3. I also have identified, in n000000, the need for a treatment of CRC algorithms, including their use in correction. dh:2013-05-26 The book has been received and there is need for more analysis. A proposed folio for CRC and especially CRC-32 has been identified in n000000. dh:2013-06-09 From n130401a, but may belong in a development folio instead or as well.]

2013-05-18

It is necessary to confirm that ZIP64™ is not part of the proprietary portion of the Zip specification 6.3.3. [dh:2013-05-26 That's apparently the case for "type 1." "type 2" may be related to use of encryption. It is not clear.][dh:2013-06-09 from n130401]

2013-05-18

The introduction of encryption and of ZIP64™ makes the finding and reconciliation of lengths even more challenging. This is going to be difficult. [dh:2013-06-09 from n130401]

2013-05-18

There are further complications when a a multiple-disk Zip is handled. Apparently every one has an "End of Central Directory" record. [dh:2013-06-09 from n130401]

2013-05-18

There are interesting constraints concerning the use of 0-valued entries when a Zip is formed by streaming. [dh:2013-06-09 from n130401]

2013-05-06

I am curious what patterns apply to this work also. I need to reword the Navigational Data Model not to be so heavy about "patterns" too. [dh 2013-06-09 in n130401a also.]

2013-05-02

Use the Navigational Data Model to provide the levels of abstraction/representation for Zip, test assertions, and implementation notes: <http://trosting.org/info/2005/08/i050809b.htm>. Achieve an appropriate layering with cross-references on how the interpretation of lower levels as carriers of higher ones can work. [dh:2013-06-09 from n130401, used there also]

2013-04-18

Some of these dependencies will not be relevant to the test assertions, so they will be in the development methodology instead. [dh:2013-06-09 from n130401]

2013-04-18

There will also be a dependency on other library functions, such as CRC, Deflate, etc. [dh:2013-06-09 from n130401]

2013-04-18

There will also be a dependency on the streaming model. [dh:2013-06-09 from n130401]

2013-04-18

Link to d130301b: Software-Component Toolcraft as well. [dh:2013-06-09 from n130401]

done
2017-03-03

2017-02-26

n130601: Should feature DCF

done
2017-03-03

2017-02-26

n130601: Treat this as a Model?

done
2017-03-03

2017-02-26

n130601: Provide 5P

done

2017-02-25

Switch n130601c and n130401c content which were apparently edited in the wrong places

done

2013-06-09

Bring over work items of n130401a that are best handled here.

done

2013-06-09

This material conforms to the 2008-02-18 styles for Site Bootstrapping. Check those pages for additional details of the approach and the styles. Contact the nfoWorks technical coordinator with questions and to report any defects that you notice.

done

2013-06-09

Make placeholders for n130601, n130601a, n130601b, and n130601c

done

2013-06-09

Create this page ready for recording Diary & Job Jar items of this nfoNote.