[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dss] comments on ESeal wd-02
Trevor, Thanks for your input. See response below: > -----Original Message----- > From: Trevor Perrin [mailto:trevp@trevp.net] > Sent: 06 April 2004 01:53 > To: Nick Pope > Cc: dss@lists.oasis-open.org > Subject: [dss] comments on ESeal wd-02 > > > > Few comments and q's - > > Do you intend to specify transport and security bindings? If not, maybe > this should be an abstract profile? > I plan to add these in the next update. > Is this intended to be a sub-profile of the XAdES profile? The latest > XAdES profile handles the CommitmentTypeIndication within the > <SignedProperties> input. I do plan to use the OptionalInput from the XAdES profile for controlling CommitmentTypeIndication. Whether this makes it a sub-profile is a question of semantics. Personally I wouldn't describe it as such. > > Does <dss:RequesterIdentity> need any profiling? > At the moment I do not think that this should be narrowed down. > Section 1: some weird ungrammatical phrasing - "This document > profiles the > core for profile is to support creation...". Sections 3.1.1 and > 3.1.2 also > have some weird phrasing. > I'll have a look at this. > Sections 3.1.2 and 4.1.3 - what if the server only supports > <DocumentHash>, > but the client sends <Document>? > Is there an error code that can be used to indicate that an option used by the client is not supported? Thanks again Nick
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]