[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Structuring of the core types
Hi DSS enthusiasts, in the last call we discussed the topic of rearranging the ~ 60 structure elements into additional sub-topics. A approach we discussed was the separation of request-related, response-related and Optionals. But there are types that are used both in requests and responses. So we need a general section. The Optionals itself group into inputs, outputs and generals. And they can be distinguished between signing, verification and general. And the distinction between base and core should be considered: General - base AnyType, ... - core InputDocument, ... Request - base RequestBaseType, ... - core SignRequestType,VerifyRequestType, ... Response - base ResponseBaseType, ... - core SignResponseType,VerifyResponseType, ... Optionals -Input - General - base ServicePolicy, ... - core Schemas, ... -Sign KeySelector, ... -Verify AdditionalKeyInfo, ... -Output - General - base AppliedPolicy, ... - core DocumentWithSignature, ... -Verify SigningTimeInfo, ... At the first glance I got the feeling that these additional structuring does not add any clearity. You cannot guess upfront where a specific element will be located. So it's as (un-)useful as a 60 items list. What's your view on this? 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]