Entity Seal Profile of the OASIS Digital Signature Service

OASIS Standard

11 April 2007

This Version:




Latest Version:




Technical Committee:

OASIS Digital Signature Services TC


Nick Pope, Thales eSecurity

Juan Carlos Cruellas, Centre d'aplicacions avançades d'Internet (UPC)


Nick Pope, Thales eSecurity


This document defines a profile of the OASIS DSS protocol and XML signature for the purpose of creating and verifying entity seals.


This document was last revised or approved by the membership of OASIS on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.

Technical Committee members should send comments on this specification to the Technical Committee's email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee's web page at http://www.oasis-open.org/committees/dss/.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/dss/ipr.php.

The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/dss/.


OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.

OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.

Copyright © OASIS® 1993-2007. All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.


The names "OASIS" are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

Table of Contents

1      Introduction. 4

1.1 Terminology. 4

1.2 Namespaces. 4

1.3 Normative References. 4

2      Profile Features. 6

2.1 Identifier 6

2.2 Scope. 6

2.3 Relationship To Other Profiles. 6

2.4 Signature Object 6

2.5 Transport Binding. 6

2.6 Security Binding. 6

2.6.1 Security Requirements. 6

2.6.2 TLS X.509 Mutual Authentication. 6

3      Profile of Signing Protocol 7

3.1 Element <SignRequest>. 7

3.1.1 Element <OptionalInputs>. 7

3.1.2 Element <InputDocuments>. 7

3.2 Element <SignResponse>. 7

3.2.1 Element <Result>. 7

3.2.2 Element <OptionalOutputs>. 7

3.2.3 Element <SignatureObject>. 7

4      Profile of Verifying Protocol 8

4.1 Element <VerifyRequest>. 8

4.1.1 Element <OptionalInputs>. 8

4.1.2 Element <SignatureObject>. 8

4.1.3 Element <InputDocuments>. 8

4.2 Element <VerifyResponse>. 8

4.2.1 Element <Result>. 8

4.2.2 Element <OptionalOutputs>. 8

5      Profile of ESeal Signatures. 9

6      Server Processing Rules. 10

6.1 Sign. 10

6.2 Verify. 10

A.     Acknowledgements. 11


1        Introduction

The DSS signing and verifying protocols are defined in [DSSCore].  As defined in that document, these protocols have a fair degree of flexibility and extensibility.  This document profiles the core to support creation and validation of a "seal" created by a given Entity or Organization on electronic data.

The seal is a form of electronic signature which:

a)       protects the integrity of the document,

b)       includes the time at which the seal was applied proving that the data existed at the given time,

c)       includes the identity of the entity requesting the seal,

d)       may include a statement of intent for applying the seal.

This profile includes a few options that require further profiling for implementing interoperable systems.

1.1 Terminology


"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be interpreted as described in IETF RFC 2119 [RFC 2119].  These keywords are capitalized when used to unambiguously specify requirements over protocol features and behavior that affect the interoperability and security of implementations.  When these words are not capitalized, they are meant in their natural-language sense.

This specification uses the following typographical conventions in text: <ns:Element>, Attribute, Datatype, OtherCode.

1.2 Namespaces

Conventional XML namespace prefixes are used in this document:

·         The prefix dss: (or no prefix) stands for the DSS core namespace [Core-XSD].

·         The prefix ds: stands for the W3C XML Signature namespace [XMLSig].

·         The prefix xades: stands for the ETSI XML Advanced Electronic Signature namespace [XAdES]

Applications MAY use different namespace prefixes, and MAY use whatever namespace defaulting/scoping conventions they desire, as long as they are compliant with the Namespaces in XML specification [XML-ns].

1.3 Normative References

[Core-XSD]             S. Drees et al.  DSS Schema.  OASIS, February, 2007

[DSSCore]              S. Drees et al.  Digital Signature Service Core Protocols and Elements.  OASIS, February, 2007

[DSS-XAdES]          Juan Carlos Cruellas et al. XAdES Profile of the OASIS Digital Signature Service

[RFC 2119]             S. Bradner.  Key words for use in RFCs to Indicate Requirement Levels. IETF RFC 2396, August 1998.


[XAdES]                  XML Advanced Electronic Signatures ETSI TS 101 903, February 2002 (shortly to be re-issued)


[XML-ns]                 T. Bray, D. Hollander, A. Layman.  Namespaces in XML.  W3C Recommendation, January 1999.


[XMLSig]                D. Eastlake et al.  XML-Signature Syntax and Processing.  W3C Recommendation, February 2002.




2        Profile Features

2.1 Identifier


2.2 Scope

This document profiles the DSS signing and verifying protocols defined in [DSSCore] and profiles the XML signature format for entity seals created by a given Entity or Organization on electronic data.

2.3 Relationship To Other Profiles

This document profiles the DSS signing and verifying protocols defined in [DSSCore].

2.4 Signature Object

This profile supports the creation and verification of [XMLSig] signatures as defined in section 5.

2.5 Transport Binding

This profile is transported using the HTTP POST Transport Binding defined in [DSSCore].

2.6 Security Binding

2.6.1 Security Requirements

This profile MUST use security bindings that:

·         Authenticates the requester to the DSS server

·         Authenticates the DSS server to the DSS client

·         Protects the integrity or a request, response and the association of response to the request.

·         Optionally, protects the confidentiality of a request and response

The following is recommended to meet these requirements..

2.6.2 TLS X.509 Mutual Authentication

This profile is secured using the TLS X.509 Mutual Authentication Binding defined in [DSSCore].

3        Profile of Signing Protocol

3.1 Element <SignRequest>

3.1.1 Element <OptionalInputs>

The optional inputs from [DSSCore]:

·         <dss:ClaimedIdentity> MUST be supported by the DSS server.  This MAY be sent by the client to provide the claimed identity of the requester.  If present the <Name> element of <dss:ClaimedIdentity> MUST be authenticated by the Security Binding.

·         <dss:SignedProperties> MAY be supported by the DSS server.  If present this MAY be used by the client to request the CommitmentTypeIndication property.  The CommitmentTypeIndication property is requested using the identifier and value as defined in [DSS-XAdES].


3.1.2 Element <InputDocuments>

At least one of the following types of InputDocuments from [DSSCore]:

·         <dss:DocumentHash>

·         <dss:TransformedData>

MUST be supported by the DSS server.  The DSS client may use either form.

If the client uses an element that is not supported by the server, the server SHOULD return ResultMinor set to indicate NotSupportedand ResultMessage set to text providing further details.

3.2 Element <SignResponse>

3.2.1 Element <Result>

This profile defines no additional <ResultMinor> codes.

3.2.2 Element <OptionalOutputs>

This profile requires no optional options.

3.2.3 Element <SignatureObject>

If successful, the server MUST return a <ds:Signature> with the signature properties as defined in section 5.

4        Profile of Verifying Protocol

4.1 Element <VerifyRequest>

4.1.1 Element <OptionalInputs>

This profile places no specific requirements on the optional inputs.

4.1.2 Element <SignatureObject>

The server MUST support <ds:Signature>.

4.1.3 Element <InputDocuments>

The at least one of the input document element from [DSSCore]:

·         <dss:DocumentHash>

·         <dss:TransformedData>

MUST be supported by the DSS server.  The DSS client may use either form Other elements MAY be supported.

4.2 Element <VerifyResponse>

4.2.1 Element <Result>

This profile defines no additional <ResultMinor> codes.

4.2.2 Element <OptionalOutputs>

This profile places no specific requirements on the optional outputs.

5        Profile of ESeal Signatures

The signature form used by the profile is an XML Signature as defined in [XMLSig].

The XML signature MUST contain the element <xades:SignedProperties>within the element <xades:QualifyingProperties> as defined in [XAdES] within the <ds:object> element of the XML signature.

The following property must be present within the <xades:SignedProperties> element:

·         <xades:SigningTime>

In addition, the following may be present:

·         <xades:CommitmentTypeIndication>

The following property must be present within a <ds:SignatureProperty> element:

·         <dss:RequesterIdentity>

The digest value of the <ds:SignatureProperty> and the <xades:SignedProperties> elements shall be included in the signature references.

6        Server Processing Rules

6.1 Sign

In addition to the processing rules define in [Core-XSD] the server MUST:

a)   ensure that the requester is authorized to request an ESeal,

b)       authenticate that requester is as identified in <dss:RequesterIdentity> and, if present, <dss:ClaimedIdentity>

6.2 Verify

In addition to the processing rules define in [Core-XSD] the server MUST:

a)   ensure that the properties required in section 5 are present.


A.   Acknowledgements

The following individuals have participated in the creation of this specification and are gratefully acknowledged:


John Messing, American Bar Association

Dallas Powell, Individual

Juan Carlos Cruellas, Individual

Trevor Perrin, individual