RE: [dss] Approach to code-signing profile

[Paul Madsen <p.madsen@entrust.com>]

Title: Approach to code-signing profile

The graph diagram suggests one possibility for addressing the policy-wise server 'meta profile' touched on in a previous thread.

 

        code-signing

         /

        /

Core ---------- wss

   |    \

   |      \

   |        \

 pws       timestamp

   |    \

   |      \

  wss    \

           timestamp

 

Policy-wise server (pws) would be defined as a restricted schema of core schema (essesntially removing the optional inputs in the request) - particular profiles could then either reference the restricted pws schema or core or both. In this model, pws would define neither processing rules nor element semantics - these operations would be left to the actual schemas themselves.

 

Defning pws as a schema rather than another profile doc would allow us to fully leverage the mechanisms for service advertisement.

 

As it stands, the core schema does not appear to facilitate such extension as we use anonymous types and 'inline' the element definitions.

 

Paul

  

-----Original Message-----
From: Nick Pope [mailto:pope@secstan.com]
Sent: Tuesday, January 20, 2004 8:34 AM
To: Pieter Kasselman; dss@lists.oasis-open.org
Subject: RE: [dss] Approach to code-signing profile

Thanks for this.

 

I like your concept of showing the profiles as a hierachy / directed graph with the Core as the root.

 

Nick

-----Original Message-----
From: Pieter Kasselman [mailto:PKasselman@betrusted.com]
Sent: 20 January 2004 11:11
To: dss@lists.oasis-open.org
Subject: [dss] Approach to code-signing profile

Hi, here is an outline on the approach to the code-signing profile.

<<oasis-dss--csprofile-dicussion-01.doc>>

Cheers

Pieter