Updated ToDo list for part-1

All the items are closed except for the first two. I commited the changes
already.

While waiting for you and Tommy's feedback, I'll start working on part-2.

-jose

[ ] 2.5.3.3
    The spec doesn't specify how to send notifications. This example is
    misleading.
    Tommy proposes the following text (and I like it):

    "The XKMS service notifies the client about the completion of the
    request processing using the notification mechanism specified in the 
    <PendingNotification> element in the initial request".

    Do we need an example where there's no <PendingNotification>? What
    should the client behavior be in that case? Polling? What does the
    spec. say (I couldn't find the answer).

    We may need an example which gives <PendingNotification> explicitly.

[ ] Update the changelog to reflect all but the minor edits I applied

[X] p. [125]
    Vamsi: The "ds:signature/ds:signatureValue" representation format syntax
    should be replaced by a textual description for consistancy.

    Changed to:

     The content of the <ds:SignatureValue> element used in the request does not 
     match the content of the <RequestSignatureValue> element in the response.

[X] Homogeneize XKISS and XKRSS
    Sometimes the spec uses X-KISS, sometimes XKISS. Same thing for XKRSS.

    Used X-KISS and X-KRSS throughout

[X] [404] Fix font face for URL

[X] Appendix B move to non normative.

[X] 122 TooManyResponses missing a nbsp;
    
[X] Tables at p. [120] and [122]
    The anyURI prefix description looks ugly. Move it to the preceding par.
    
[X] Table at [122]. Use of Sender or Receiver for the last three minor codes
    Tommy proposes Sender. The text in the spec is not synch. with the
    actual values. See [213], [311], [315], 

    Following a mail exchange with Tommy on the list, and with Shivaram's approval,
    modified as follows:

      OptionalElementNotSupported Receiver
      ProofOfPosessionRequired    Sender
      TimeInstantNotSupported     Receiver
      TimeInstantOutofRange       Sender

    --> related par. updated.

[X] Par. [373a] is missing some articles, but I'm unable to fix it
  without knowing what was it supposed to say originally.

  Fixed with Shivaram

[X] 124 and 125 add <span class="ID> as needed.