Hi Stefan,
looks fine for my but Oxygen complains about:
Conversion to DITA failed
Header level raised from 2 to 4 without intermediate header
level
Greetings,
Andreas
for the upcoming meeting, I here below provide the head of the
still changing CSD02 WD01 because we can guided by this
IMO better discuss the reference changes requested from TAB
review.
All the best,
Stefan
$ echo; cat dss-core-v2.0-csd02-wd01-prose.md \
| filter --content-section=-"Typographical Conventions"
![OASIS
Logo](http://docs.oasis-open.org/templates/OASISLogo-v2.0.jpg)
-------
# Digital Signature Service Core Protocols, Elements, and Bindings
Version 2.0
## Committee Specification Draft 02 WD01
## 07 October 2018
### Specification URIs
#### This version:
*
http://docs.oasis-open.org/dss-x/dss-core/v2.0/csprd02/dss-core-v2.0-csprd02.md
(Authoritative)
*
http://docs.oasis-open.org/dss-x/dss-core/v2.0/csprd02/dss-core-v2.0-csprd02.html
*
http://docs.oasis-open.org/dss-x/dss-core/v2.0/csprd02/dss-core-v2.0-csprd02.pdf
#### Previous version:
*
http://docs.oasis-open.org/dss-x/dss-core/v2.0/csprd01/dss-core-v2.0-csprd01.docx
(Authoritative)
*
http://docs.oasis-open.org/dss-x/dss-core/v2.0/csprd01/dss-core-v2.0-csprd01.html
*
http://docs.oasis-open.org/dss-x/dss-core/v2.0/csprd01/dss-core-v2.0-csprd01.pdf
#### Latest version:
* http://docs.oasis-open.org/dss-x/dss-core/v2.0/dss-core-v2.0.md
(Authoritative)
*
http://docs.oasis-open.org/dss-x/dss-core/v2.0/dss-core-v2.0.html
* http://docs.oasis-open.org/dss-x/dss-core/v2.0/dss-core-v2.0.pdf
#### Technical Committee:
* [OASIS Digital Signature Services eXtended (DSS-X)
TC](https://www.oasis-open.org/committees/dss-x/)
#### Chairs
* Andreas Kuehne (kuehne@trustable.de), Individual
* Stefan Hagen (stefan@hagen.link), Individual
#### Editors
* Andreas Kuehne (kuehne@trustable.de), Individual
* Stefan Hagen (stefan@hagen.link), Individual
#### Additional artifacts:
This prose specification is one component of a Work Product that
also includes:
* JSON and XML schemas:
http://docs.oasis-open.org/dss-x/dss-core/v2.0/csprd02/schema/
#### Related work:
##### This specification replaces or supersedes:
* _Digital Signature Service Core Protocols, Elements, and
Bindings Version 1.0_. Edited by Stefan Drees. 11 April 2007.
OASIS Standard.
http://docs.oasis-open.org/dss/v1.0/oasis-dss-core-spec-v1.0-os.html.
#### Declared XML namespaces:
* http://docs.oasis-open.org/dss-x/ns/core
* http://docs.oasis-open.org/dss-x/ns/base
#### Abstract
This document defines JSON and XML based request/response
protocols for signing and verifying documents and other data. It
also defines a timestamp format, and a signature property for use
with these protocols. Finally, it defines transport and security
bindings for the protocols.
## Status
This document was last revised or approved by the OASIS Digital
Signature Services eXtended (DSS-X) TC on the above date. The
level of approval is also listed above. Check the "Latest version"
location noted above for possible later revisions of this
document. Any other numbered Versions and other technical work
produced by the Technical Committee (TC) are listed at
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dss-x#technical.
TC members should send comments on this specification to the TC's
email list. Others should send comments to the TC's public comment
list, after subscribing to it by following the instructions at the
"Send A Comment" button on the TC's web page at
https://www.oasis-open.org/committees/dss-x/.
This specification is provided under the [RF on Limited
Terms](https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode)
Mode of the OASIS IPR Policy, the mode chosen when the Technical
Committee was established. 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 TCâs web
page (https://www.oasis-open.org/committees/dss-x/ipr.php).
Note that any machine-readable content ([Computer Language
Definitions](https://www.oasis-open.org/policies-guidelines/tc-process#wpComponentsCompLang))
declared Normative for this Work Product is provided in separate
plain text files. In the event of a discrepancy between any such
plain text file and display content in the Work Product's prose
narrative document(s), the content in the separate plain text file
prevails.
#### Citation format:
When referencing this specification the following citation format
should be used:
**[DSS-v2.0]**
_Digital Signature Service Core Protocols, Elements, and Bindings
Version 2.0_. Edited by Andreas Kuehne and Stefan Hagen. 07
October 2018. OASIS Committee Specification Draft 02 / Public
Review Draft 02.
http://docs.oasis-open.org/dss-x/dss-core/v2.0/csprd02/dss-core-v2.0-csprd02.html.
Latest version:
http://docs.oasis-open.org/dss-x/dss-core/v2.0/dss-core-v2.0.html.
## Notices
Copyright  OASIS Open 2018. All Rights Reserved.
All capitalized terms in the following text have the meanings
assigned to them in the OASIS Intellectual Property Rights Policy
(the "OASIS IPR Policy"). The full
[Policy](https://www.oasis-open.org/policies-guidelines/ipr) may
be found at the OASIS website.
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 section are included on all such copies and derivative
works. However, this document itself may not be modified in any
way, including by removing the copyright notice or references to
OASIS, except as needed for the purpose of developing any document
or deliverable produced by an OASIS Technical Committee (in which
case the rules applicable to copyrights, as set forth in the OASIS
IPR Policy, 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.
This document and the information contained herein is provided on
an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that
believes it has patent claims that would necessarily be infringed
by implementations of this OASIS Committee Specification or OASIS
Standard, to notify OASIS TC Administrator and provide an
indication of its willingness to grant patent licenses to such
patent claims in a manner consistent with the IPR Mode of the
OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if
it is aware of a claim of ownership of any patent claims that
would necessarily be infringed by implementations of this
specification by a patent holder that is not willing to provide a
license to such patent claims in a manner consistent with the IPR
Mode of the OASIS Technical Committee that produced this
specification. OASIS may include such claims on its website, but
disclaims any obligation to do so.
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' procedures with respect to rights in any
document or deliverable produced by an OASIS Technical Committee
can be found on 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 implementers or users of this OASIS Committee
Specification or OASIS Standard, can be obtained from the OASIS TC
Administrator. OASIS makes no representation that any information
or list of intellectual property rights will at any time be
complete, or that any claims in such list are, in fact, Essential
Claims.
The name "OASIS" is a trademark of
[OASIS](https://www.oasis-open.org/), 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
https://www.oasis-open.org/policies-guidelines/trademark for above
guidance.
-------
## Table of Contents
[[TOC]]
-------
# 1 Introduction
## 1.1 IPR Policy
This specification is provided under the [RF on Limited
Terms](https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode)
Mode of the [OASIS IPR
Policy](https://www.oasis-open.org/policies-guidelines/ipr), the
mode chosen when the Technical Committee was established. 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 TCâs web page
([https://www.oasis-open.org/committees/dss-x/ipr.php](https://www.oasis-open.org/committees/dss-x/ipr.php)).
## 1.2 Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this specification are to be interpreted as described in IETF
RFC 2119 [[RFC2119](#RFC2119)] and RFC 8174 [[RFC8174](#RFC8174)].
The key words âMUSTâ, âMUST NOTâ, âREQUIREDâ, âSHALLâ, âSHALL
NOTâ, âSHOULDâ, âSHOULD NOTâ, âRECOMMENDEDâ, âMAYâ, and âOPTIONALâ
in this document are to be interpreted as described in
[[RFC2119](#refRFC2119)] and [[RFC8174](#refRFC8174)].
### 1.2.1 Terms and Definitions
For the purposes of this document no specific terms or definitions
have been identified as deviating from the usual meaning in the
context of XML / JSON schema, digital signatures or transport.
### 1.2.2 Abbreviated Terms
ASN.1ÂÂ â Abstract Syntax Notation One
URIÂÂÂÂÂ â (IETF) Uniform Resource Identifier
XMLÂÂÂÂ â (W3C) Extensible Markup Language
XSDÂÂÂÂ â (W3C) XML Schema
## 1.3 Normative References
[DSBXSD] A. Kuehne, S. Hagen. *DSS 2.0 Base XML
Schema*. OASIS.
[DSIGRWXSD] A. Kuehne, S. Hagen. *DSS 2.0 adapted XMLDSig
XML Schema*. OASIS.
[DSS1Async] A. Kuehne. *Asynchronous Processing Abstract
Profile*. OASIS,
[oasis-dss-profiles-asynchronous\_processing-spec-v1.0-os.html](http://docs.oasis-open.org/dss/v1.0/oasis-dss-profiles-asynchronous_processing-spec-v1.0-os.html)
[DSS1Core] S. Hagen. *DSS 1.0 Core Protocols*. OASIS,
[oasis-dss-core-spec-v1.0-os.html](http://docs.oasis-open.org/dss/v1.0/oasis-dss-core-spec-v1.0-os.html).
[DSS2JSON] A. Kuehne, S. Hagen. *DSS 2.0 Core JSON
Schema*. OASIS.
[DSS2XSD] A. Kuehne, S. Hagen. *DSS 2.0 Core XML
Schema*. OASIS.
**[ESIFrame]****ÂÂÂÂÂÂÂÂÂÂÂ ****[TR 119 102
V1.2.1](http://www.etsi.org/deliver/etsi_tr/119000_119099/119001/01.02.01_60/tr_119001v010201p.pdf)******Electronic
Signatures and Infrastructures (ESI); The framework for
standardization of signatures; Definitions and abbreviations
[http://www.etsi.org/deliver/etsi\_tr/119000\_119099/119001/01.02.01\_60/tr\_119001v010201p.pdf](http://www.etsi.org/deliver/etsi_tr/119000_119099/119001/01.02.01_60/tr_119001v010201p.pdf)
#### RFC2119
Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
#### RFC2396
Berners-Lee, T., "Uniform Resource Identifiers (URI): Generic
Syntax.", RFC 2396, DOI 10.17487/RFC2396, August 1998,
<http://www.rfc-editor.org/info/rfc2396>.
replace with:
**[RFC3986]** Berners-Lee, T., Fielding, R., and L. Masinter,
"Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC
3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>.
#### RFC2440
Callas J., Donnerhacke L., Finney H., Thayer R., "OpenPGP Message
Format", RFC 2440, DOI 10.17487/RFC2440, November 1998,
<http://www.rfc-editor.org/info/rfc2440>.
replace with:
**[RFC4880]** Callas, J., Donnerhacke, L., Finney, H., Shaw, D.,
and R. Thayer, "OpenPGP Message Format", RFC 4880, DOI
10.17487/RFC4880, November 2007,
<https://www.rfc-editor.org/info/rfc4880>.
#### RFC2616
Fielding R., "Hypertext Transfer Protocol â HTTP/1.1", RFC 2616,
DOI 10.17487/RFC2616, June 1999,
<http://www.rfc-editor.org/info/rfc2616>.
replace with (maybe the right individual RFC):
**[RFC7230]** Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC
7230, DOI 10.17487/RFC7230, June 2014,
<https://www.rfc-editor.org/info/rfc7230>.
**[RFC7231]** Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231,
DOI 10.17487/RFC7231, June 2014,
<https://www.rfc-editor.org/info/rfc7231>.
**[RFC7232]** Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
Transfer Protocol (HTTP/1.1): Conditional Requests", RFC 7232, DOI
10.17487/RFC7232, June 2014,
<https://www.rfc-editor.org/info/rfc7232>.
**[RFC7233]** Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke,
Ed., "Hypertext Transfer Protocol (HTTP/1.1): Range Requests", RFC
7233, DOI 10.17487/RFC7233, June 2014,
<https://www.rfc-editor.org/info/rfc7233>.
**[RFC7234]** Fielding, R., Ed., Nottingham, M., Ed., and J.
Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
RFC 7234, DOI 10.17487/RFC7234, June 2014,
<https://www.rfc-editor.org/info/rfc7234>.
**[RFC7235]** Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
Transfer Protocol (HTTP/1.1): Authentication", RFC 7235, DOI
10.17487/RFC7235, June 2014,
<https://www.rfc-editor.org/info/rfc7235>.
#### RFC2648
Moats, R., "A URN Namespace for IETF Documents", RFC 2648, DOI
10.17487/RFC2648, August 1999,
<https://www.rfc-editor.org/info/rfc2648>.
#### RFC2822
Resnick, P., "Internet Message Format", BCP_ETC, RFC 2822, DOI
10.17487/RFC2822, April 2001,
<http://www.rfc-editor.org/info/rfc2822>.
replace with:
**[RFC5322]** Resnick, P., Ed., "Internet Message Format", RFC
5322, DOI 10.17487/RFC5322, October 2008,
<https://www.rfc-editor.org/info/rfc5322>.
#### RFC3161
Adams, C., Cain, P., Pinkas, D., and R. Zuccherato, "Internet
X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)", RFC
3161, DOI 10.17487/RFC3161, August 2001,
<https://www.rfc-editor.org/info/rfc3161>.
#### RFC5652
[RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD
70, RFC 5652, DOI 10.17487/RFC5652, September 2009,
<https://www.rfc-editor.org/info/rfc5652>.
Remark: As used in DSS, all implementations based upon RFC 5652
and previous releases of CMS will suffice. For the sake of
simplicity the "urn:ietf:rfc:3369" is used throughout the document
to indicate a CMS message as specified in RFC 5652 or RFC 3369 or
any version (including PKCS \#7.
#### RFC8174
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key
Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017,
<http://www.rfc-editor.org/info/rfc8174>.
#### RFC8259
Bray, T., "The _javascript_ Object Notation (JSON) Data Interchange
Format", RFC 8259, DOI 10.17487/RFC8259, December 2017,
<http://www.rfc-editor.org/info/rfc8259>.
[SAML2RWXSD] A. Kuehne, S. Hagen. *DSS 2.0 adapted SAML 2.0Â
XML Schema*. OASIS.
**[SOAP] **M. Gudgin et al. *SOAP Version 1.2
Part 1: Messaging Framework.*Â W3C Recommendation, June 2003.
Â[http://www.w3.org/TR/xmlschema-1/](http://www.w3.org/TR/xmlschema-1/)
**[SOAPAtt]**ÂÂÂÂÂÂÂÂÂÂÂÂÂ H. F. Nielsen, H. Ruellan *SOAP Message
Transmission Optimization Mechanism,* W3C Working Group Note, 8
June 2004
Â[http://www.w3.org/TR/soap12-af/](http://www.w3.org/TR/soap12-af/)
**[SOAPMtom]**ÂÂÂÂÂÂÂÂÂ Martin Gudgin, Noah Mendelsohn *SOAP 1.2
Attachment Feature,* W3C Recommendation 25 January 2005
Â[http://www.w3.org/TR/soap12-mtom/](http://www.w3.org/TR/soap12-mtom/)
**[WS-I-Att]ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ **Ch. Ferris, A. Karmarkar, C. K. LiuÂ
*Attachments Profile Version 1.0,* The Web
Services-Interoperability Organization (WS-I)*,*20 April 2006
[http://www.ws-i.org/Profiles/AttachmentsProfile-1.0.html](http://www.ws-i.org/Profiles/AttachmentsProfile-1.0.html)
[XML]ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Extensible Markup Language (XML) 1.0
(Fifth Edition), T. Bray, J. Paoli, M. Sperberg-McQueen, E. Maler,
F. Yergeau, Editors, W3C Recommendation, November 26, 2008,
[http://www.w3.org/TR/2008/REC-xml-20081126/](http://www.w3.org/TR/2008/REC-xml-20081126/).
ÂLatest version available at
[http://www.w3.org/TR/xml](http://www.w3.org/TR/xml).
**[XML-C14N]******** **J. Boyer. *Canonical XML Version
1.0*. W3C Recommendation, March 2001.
Â[http://www.w3.org/TR/xml-c14n](http://www.w3.org/TR/xml-c14n)
**[XML-xcl-c14n]**ÂÂÂÂÂÂ Exclusive XML Canonicalization Version
1.0. W3C Recommendation 18 July 2002
[http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/](http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/)
**[****XML-ns]**ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ T. Bray, D. Hollander, A. Layman.Â
*Namespaces in XML.*Â W3C Recommendation, January 1999.
[http://www.w3.org/TR/1999/REC-xml-names-19990114](http://www.w3.org/TR/1999/REC-xml-names-19990114/)
**[XML-NT-Document]**
[http://www.w3.org/TR/2004/REC-xml-20040204/\#NT-document](http://www.w3.org/TR/2004/REC-xml-20040204/)
**[XML-PROLOG]**ÂÂÂÂ Tim Bray, Jean Paoli, C. M. Sperberg-McQueen,
et al. Prolog and Document Type Declaration in Extensible Markup
Language (XML) 1.0 (Third Edition), W3C Recommendation, 04
February 2004,
[http://www.w3.org/TR/REC-xml/\#sec-prolog-dtd](http://www.w3.org/TR/REC-xml/#sec-prolog-dtd)
**[xml:id]ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ **xml:id, Version 1.0, W3C
Recommendation, 9 September 2005, http://www.w3.org/TR/xml-id/
**[XMLDSIG]** D. Eastlake et al. XML-Signature Syntax
and Processing. W3C Recommendation, February 2002*.
*[http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/](http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/)
[XML-Schema-1]ÂÂÂÂ W3C XML Schema Definition Language (XSD) 1.1
Part 1: Structures, S. Gao, M. Sperberg-McQueen, H. Thompson, N.
Mendelsohn, D. Beech, M. Maloney, Editors, W3C Recommendation,
April 5, 2012,
[http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/](http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/).
ÂLatest version available at
[http://www.w3.org/TR/xmlschema11-1/](http://www.w3.org/TR/xmlschema11-1/).
[XML-Schema-2]ÂÂÂÂ W3C XML Schema Definition Language (XSD) 1.1
Part 2: DatatypesW3C XML Schema Definition Language (XSD) 1.1 Part
2: Datatypes, D. Peterson, S. Gao, A. Malhotra, M.
Sperberg-McQueen, H. Thompson, Paul V. Biron, Editors, W3C
Recommendation, April 5, 2012,
[http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/](http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/).
ÂLatest version available at
[http://www.w3.org/TR/xmlschema11-2/](http://www.w3.org/TR/xmlschema11-2/).
**[****XPATH]**ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ XML Path Language (XPath) Version
1.0. W3C Recommendation 16 November 1999
[http://www.w3.org/TR/xpath](http://www.w3.org/TR/xpath)
## 1.4 Non-Normative References
[ASN.1]ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Introduction to ASN.1.
[https://www.itu.int/en/ITU-T/asn1/Pages/introduction.aspx](https://www.itu.int/en/ITU-T/asn1/Pages/introduction.aspx)
[CHPGW]ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ DSS Extension for Local Signature
Computation Version 1.0, Working Draft for Committee Specification
04.
[https://www.oasis-open.org/committees/download.php/62576/localsig-v1.0-csprd04.pdf](https://www.oasis-open.org/committees/download.php/62576/localsig-v1.0-csprd04.pdf)
[ISO8601]ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Data elements and interchange formats â
Information interchange â Representation of dates and times,
International Standard, ISO 8601:2004(E), December 1, 2004,
[https://www.iso.org/standard/40874.html](https://www.iso.org/standard/40874.html).
[ISO639-1]ÂÂÂÂÂÂÂÂÂÂÂÂÂ Codes for the representation of names of
languages â Part 1: Alpha-2 code, International Standard, ISO
639-1:2002 (en),
[https://www.iso.org/obp/ui\#iso:std:iso:639:-1](https://www.iso.org/obp/ui#iso:std:iso:639:-1:ed-1:v1:en).
[JENSEN-2009]ÂÂÂÂÂÂ Meiko Jensen, Lijun Liao, and JÃrg Schwenk.
2009. The curse of namespaces in the domain of XML signature. In
Proceedings of the 2009 ACM workshop on Secure web services (SWS
'09). ACM, New York, NY, USA, 29-36.
ÂDOI:
[https://doi.org/10.1145/1655121.1655129](https://doi.org/10.1145/1655121.1655129)
[RFC7049]ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ C. Bormann, University Bremen TZI, Concise
Binary Object Representation (CBOR), ISSN: 2070-1721, October
2013.
Â[https://tools.ietf.org/html/rfc7049](https://tools.ietf.org/html/rfc7049)
**[RFC7515]****ÂÂÂÂÂÂÂÂÂÂÂ **M. Jones, Microsoft, JSON Web
Signature (JWS), ISSN: 2070-1721, May 2015.
[https://tools.ietf.org/html/rfc7515](https://tools.ietf.org/html/rfc7515).
$
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC
that generates this mail. Follow this link to all your TCs in
OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
Andreas KÃhne
phone: +49 177 293 24 97
mailto: kuehne@trustable.de
Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612
Director Andreas KÃhne
Company UK Company No: 5218868 Registered in England and Wales
|