[Fwd: [Action 05-10-31-01] Konrad's Ballot comments]

[Konrad Lanz <Konrad.Lanz@labs.cio.gv.at>]

--- Begin Message ---

• From: Konrad Lanz <Konrad.Lanz@labs.cio.gv.at>
• To: Stefan Drees <stefan@drees.name>
• Date: Tue, 08 Nov 2005 09:59:44 +0100

Dear Stefan,

Please reply which of the following comment have already been addressed 
so that I can also finish [Action 05-10-31-02].

thanks
Konrad

Section 4.6.1:
     - not fully reflecting the resolutions form:
       
http://www.oasis-open.org/apps/org/workgroup/dss/email/archives/200510/msg00011.html 

       
http://www.oasis-open.org/apps/org/workgroup/dss/email/archives/200510/msg00010.html 

     - ResultMinor missing.
       
urn:oasis:names:tc:dss:1.0:resultminor:indetermined:checkOptionalOutputs
     - returning of <ProcessingDetails> for core validation info not 
mentioned.

Line 466 - 487:
    - referencing style to be reconciled with the rest of the document
    - point c) needs better wording. Example --> Appendix.

Line 17:
    - Please add my email address <Konrad.Lanz@iaik.tugraz.at>

Line 504 - 505:
     REPLACE
       < xs:element name="Schema" type="xs:base64Binary" minOccurs="0"/>
     WITH
       <xs:attribute name="SchemaRefs" type="xs:IDREFS" use="optional"/>

Line 555:
    REMOVE
      the word *two*
    FROM:
      This specification defines the following *two* <ResultMinor> values.

Line 642 - 643:
    REPLACE
      *CMS or whatever or*
     WITH
      *non xml input or alternatively*
     IN
       Base64Data can be used for other not yet defined forms of 
verification for *CMS or whatever or* an error can be thrown.

Line 707 - 721:
    Needs better wording.
      only state that it is a general purpose Response element for 
exceptional circumstances.
      Example --> Appendix, add example for "The server is currently 
under maintenance" or "The service operates from 8:00 to 17:00".

Line 707 - 721:
    REPLACE
      These Transforms may reflect idiosyncrasies of different parsers 
or *to* solve encoding issues *and so on*.
    WITH
      These Transforms may reflect idiosyncrasies of different parsers 
or solve encoding issues or the like.

    REPLACE
      Servers MAY also choose not to apply transforms in basic 
processing and to extract the data binary or canonicalize the data 
directly if certain optional
inputs (see sections 3.5.7 point 2 and 1.d.v, 3.5.8) are not to be 
implemented.
    WITH
        Servers MAY choose not to apply transforms in basic processing 
and extract the data binary for direct hashing or canonicalize the data 
directly if certain optional inputs (see sections 3.5.7 point 2 and 
1.d.v, 3.5.8) are not to be implemented.

Line 834:
    REPLACE
      In cases like echoing and such where details could get lost, see 
Appendix A.
    WITH
      If signed data is to be echoed back to the client and hence 
details could get lost refer to Appendix A.

P.S.: Text me on Skype today before 17:00 or mail me, if you need anything.

--- End Message ---