splitting up the documents

["William Allen Simpson" <wsimpson@greendragon.com>]

As I read this huge SPKI document, I find that I cannot even read it all
at one sitting.

It seems to me that there is a lot of duplication with the requirements
draft.  There really needs to be only one document with the "design
requirements", another with "SPKI objects", and another with examples
and implementation details.

Look at how nicely they split up the MIME set.

> From: Markku-Juhani Saarinen <mjos@ssh.fi>
>   The main certificate text would define the certificate contents on an
>   abstract level, while this "implementation notes" or "spki standard
>   operation" document would bring it down to almost code level.
>
>   Maybe we want to have four separate (RFC) documents in the end:
>     1. Certificate
>     2. Protocol
>     3. S-Expressions
>     4. Implementation Notes
>
>   As the certificate draft alone is currently at 82 pages, the SPKI has
>   grown beyond simple. And it will apparently continue to grow.
>

WSimpson@UMich.edu
    Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32
BSimpson@MorningStar.com
    Key fingerprint =  2E 07 23 03 C5 62 70 D3  59 B1 4F 5E 1D C2 C1 A2

---

• Prev by Date: ASCII versus binary
• Next by Date: Re: ASCII versus binary
• Prev by thread: Re: ASCII versus binary
• Next by thread: getting rid of intersection algebra
• Index(es):
  • Main
  • Thread