0 header
0 stuff
0 with no
0 defined ending
0 !TEXMAP etc etc.
1 a real part
0 !TEXMAP END
QED
I happen to agree that the header is too onerous. I have difficulty envisioning usecases for some of its contents. The !HISTORY lines in particular belong in CMS metadata; they do not belong in the source file itself. I don't see much value in adding a !NEEDSWORK because I don't see why that data needs to be machine-readable either.
But you cannot make the case that the header is currently machine-parseable. Nor can you, without an end-of-header designator, possibly write a future-proof header delineator.
I'm not going to get worked up about this; there are far more important issues. I'm just trying to set the record straight.
Allen
0 stuff
0 with no
0 defined ending
0 !TEXMAP etc etc.
1 a real part
0 !TEXMAP END
QED
I happen to agree that the header is too onerous. I have difficulty envisioning usecases for some of its contents. The !HISTORY lines in particular belong in CMS metadata; they do not belong in the source file itself. I don't see much value in adding a !NEEDSWORK because I don't see why that data needs to be machine-readable either.
But you cannot make the case that the header is currently machine-parseable. Nor can you, without an end-of-header designator, possibly write a future-proof header delineator.
I'm not going to get worked up about this; there are far more important issues. I'm just trying to set the record straight.
Allen