http://qs1969.pair.com?node_id=491323


in reply to Thoughts on designing a file format.

Would you consider it worthwhile to add a field (or set of fields) for an update/edit history, incorporating both date of the (edit/update) and the author of same?

An impractical (but in some ways desireable) addition would be a field or set of fields to hold sequential difs for each edit. Notion is that it would amount to an internal cv repository, which would afford a subsequent editor/reader some hints about whether (for example) writer B's remark was in the same thread of changes as writer A's (if not, it might be merely similar or tangential, whereas if in same_thread, might be a child of A's).

Update: I view including dif's as "impractical" because doing so could bloat a file worse than M$ does (mucho header/file info, very little unique content) ...to say nothing of complexities (what do you do about the reader/revisor who's not running on a compatible OS or using a compliant editor?)

  • Comment on Re: Thoughts on designing a file format.

Replies are listed 'Best First'.
Re^2: Thoughts on designing a file format.
by demerphq (Chancellor) on Sep 12, 2005 at 17:47 UTC

    Well I would view that as either a header issue, that is on the file level, or as a data record specification issue. I should say though that I tried to stay away from the data as a whole as I'm more concerned with the strucuture of the container and not so much what it contains.

    In other words, in some situations support for change records is required, but how its implemented I would think would require a lot of contextual analysis that can't be broadly generalized. Although please feel free to outline your thoughts on the subject, its not really something thats come up for me regularly, in fact only once really.

    ---
    $world=~s/war/peace/g