RE: [dss] Finalizing core spec

[Trevor Perrin <trevp@trevp.net>]

Hi Nick, all,

Let me summarize what I think is the consensus, and where we need more 
discussion.

Hopefully we can finish these off in the next day or two, and get a new draft.


At 11:44 AM 4/13/2004 +0100, Nick Pope wrote:
> >
> > 1) Since we've decided to handle Async support in a profile, should we
> > remove TryAgainLater?  Or allow profiles to introduce new ResultMajor
> > codes?  Or just leave it as is?
>
>I would be interested to get Andreas' view, but I would suggest that
>ResultMajor should not be restricted to those value given in the standard to
>allow flexibility for the asynch profile to define other return values.

Andreas agrees, I do too, so the tentative consensus is:
  - Remove TryAgainLater
  - Allow profiles to add new ResultMajor codes


> > 2) Andreas has proposed the client could indicate multiple
> > profile URIs in
> > a request (i.e the client could say "the WSS *and* German Sig-Law
> > profiles
> > are in effect).  See this thread:
> > http://lists.oasis-open.org/archives/dss/200404/msg00019.html
>
>I agree

I disagree, I think it'll be confusing to have multiple profiles in effect, 
since they'll likely have clashing requirements.

However, the tentative consensus is in favor of this (you and 
Andreas).  I'd like to see a concrete proposal - right now the 'Profile' is 
indicated as an attribute, perhaps we would add an "AdditionalProfile" 
optional input that could occur multiple times?  What happens if 
requirements conflict?


>One other minor change in 4.5.7 when updating a signature the attribute
>"Type" is used to identify the type/form of updated signature required.  In
>the XAdES profile, and the Core, "SignatureType" is used to identify the
>basic type of signature (CMS, XMLSig, Timestamp).  SignatureForm is used to
>identify the different forms (ES-T, BES etc).
>
>I suggest that in element "ReturnUpdatedSignature" we rename the attribute
>"type" to be "Form".

I'd rather stick with the generic term 'Type'.  'Form' is specific to the 
XAdES profile.  We use 'Type' in a few other places for parameterizing 
elements (AddTimestamp, Base64Signature, DetailType), and XML-DSIG uses it 
as well.


Trevor