[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dss] Application Profile
At 04:49 PM 8/14/2003 +0100, Nick Pope wrote: >Content-Transfer-Encoding: 7bit > >Trevor, > >Having looked further at the text I now understand what the text in 3.1.2 is >saying. > >So for item c) below the replacement for "A combination of these profiles >yeilds an Application Profile" with >"A combination of a Protocol Profile, Signature format Profile and Binding >Profiles yields an Application Profile which fully describes the service >(see 3.10 and 3.11)". That's much better than current text, thanks. > > a) I personally believe that Application Profiles should be able to be > > selected through the schema. > > > > However, the requirements document need not specify how the application > > profile is signalled as this is a protocol requirement, on that it can be > > indicated either implicetlky or explicetly. So I suggest that > > you leave it > > open in the requirements document and keep it in the schema for > > the moment. The requirements doc currently *does* get to the level of detail of saying whether things are implicit or explicit. So if we want Application Profile to be explicit, I wouldn't mind giving it its own section under 3.5, in the same way that "Requested Signing Key" or "Intended Audience" have their own section. Would you mind if I made that change? I guess it's pedantic, I'd just like the requirements doc and schema to match as much as possible. > > > > b) In 3.1.2 Can you update the list of profiles to include the > > two mentioned > > at the recent DSS phone conference (Corporate Seal and profile for German > > signature legislation), preceded by the words. "Profiles are currently > > being considered for: ..." Sure. Trevor
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]