Hi Ezer,
hope you got a nice holiday.
> - line 360 : DocumentRestrictionLevel is _not_ optional, but dtmo it
> MUST be.
>
> <Ezer - this parameter is relevant only for the PDF-Certify operation
> and is not relevant for other types of documents.
Yes, that's why I vote for the optional attribute ! Currently it's the only elemnt not optional in the given schema snippet.
> - DocumentRestrictionLevel : Could you please explain valid values and
> their meaning. Anyway, I would prefer urn instead of an integer.
>
> <Ezer - Any explanation will tie the values to PDF, which I was trying
> to avoid.
Hmm, my colleague was lost when he came across this element. This shouldn't happen to future readers of the profile. Maybe you can give a hint where to look for possible values ...
> - line 537 : DateTime is defined, but never used. All date / time alike
> values are generated by the server.
>
> <Ezer - So your suggestion is to remove it? What about cases when the
> client would like to supply only the time format?
Oh, I see ! I got this element completely wrong. It's not intended to format a transmitted date but the visible representation. OK !
> - line 395 : Does DocumentID tries to introduce a mechanism to sign
> multiple documents with one call ? Dtmo a single call should deliver a
> single signaure. We got this decussion some years ago ...
>
> <Ezer - I was under the impression that the core allows signing multiple
> documents in one call, having each document has its own signature. If
> not, what is the aim of sending several documents?
Please can someone correct me if I'm wrong, but I got the belief that one request gives one signature. A hint may be that the mechanism you introduce here is missing for the core informations.
Greetings
Andreas
