Re: Additional remarks on the DSS core

[Andreas Kuehne <kuehne@trustable.de>]

Hi all,

in addition to the changes below I would suggest a more severe move:

Split the transport aspects of the protocol strictly from the payload.
This especially means to transfer XML objects as base64 blobs even if
the transport protocol is SOAP! This eases the mapping to other
protocols and also prevents nasty interferences between transport and
payload (e.g. by soap namespaces leaking  into the document to be signed).
A significant change would be dropping the ds:Signature element from the
dss:SignatureObject.

What's you opinion?

Greetings,

Andreas
> I would like to propose some additional changes to the core once we are
> going to touch it:
>
>  1. Each request may be attributed with a set of profiles. Therefore
>     drop the profile attributes from RequestBaseType and
>     ResponseBaseType. Introduce a set of 'AppliedProfile' items to
>     OptionalOutputs.
>  2. Each request may be attributes with a set of policies. The section
>     regarding 'ServicePolicy' does not explicitly state the option for
>     multiple policies. Introduce a set of 'AppliedPolicy' items to
>     OptionalOutputs.
>  3. Streamline the core by dropping EscapedXML and InlineXML.
>  4. Consider replacing dss:AnyType by xades:AnyType. The slightly
>     different structures with same name cause irritations.
>  5. Clearify the cardinality and the intentions of the optional elements
>     by enumerating them in OptionalInputs and  OptionalOutputs explicitly.
>  6. Give a the specific type 'xs:boolean' to the flag-type
>     OptionalInputs 'Return*' elements.
>
> Greetings,
>
> Andreas
>


-- 
Andreas Kühne 
phone: +49 177 293 24 97 
mailto: kuehne@trustable.de

Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612

Director Andreas Kühne

Company UK Company No: 5218868 Registered in England and Wales