<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    It seems that my idea to exploit deterministic CBOR certainly was
    not "mine" :)<br>
    The future format for financial messaging may very well be CBOR:
    <a class="moz-txt-link-freetext" href="https://fido-web-pay.github.io/">https://fido-web-pay.github.io/</a><br>
    With the coming URL object identifier RFC, deterministic CBOR beats
    XML and JSON hands down.<br>
    Anders<br>
    <a class="moz-txt-link-freetext" href="https://github.com/cyberphone/cbor-everywhere">https://github.com/cyberphone/cbor-everywhere</a><br>
    <br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>New deterministic CBOR Libraries (Rust & Swift) from
              Blockchain Commons</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Resent-Date:
            </th>
            <td>Thu, 16 Feb 2023 01:00:25 +0000</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Resent-From:
            </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:public-vc-wg@w3.org">public-vc-wg@w3.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Wed, 15 Feb 2023 16:59:31 -0800</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td>Christopher Allen
              <a class="moz-txt-link-rfc2396E" href="mailto:ChristopherA@lifewithalacrity.com"><ChristopherA@lifewithalacrity.com></a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td>Credentials Community Group
              <a class="moz-txt-link-rfc2396E" href="mailto:public-credentials@w3.org"><public-credentials@w3.org></a>, W3C Verifiable
              Credentials WG <a class="moz-txt-link-rfc2396E" href="mailto:public-vc-wg@w3.org"><public-vc-wg@w3.org></a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">CC: </th>
            <td>Wolf McNally <a class="moz-txt-link-rfc2396E" href="mailto:wolf@wolfmcnally.com"><wolf@wolfmcnally.com></a>, Shannon
              Appelcline <a class="moz-txt-link-rfc2396E" href="mailto:shannon.appelcline@gmail.com"><shannon.appelcline@gmail.com></a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <div dir="ltr">Since I know that many projects in the broader
        Credentials Community already use CBOR, I'd like to announce
        Blockchain Commons' release of dCBOR libraries for Rust and
        Swift. In particular, these two languages demonstrate our
        support of use cases for dCBOR for mobile in Android and iOS:<br>
        <ul>
          <li><b>dCBOR Codec for Rust:</b> <a
              href="https://github.com/BlockchainCommons/bc-dcbor-rust"
              moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/BlockchainCommons/bc-dcbor-rust</a><br>
          </li>
          <li><b>dCBOR Codec for Swift:</b> <a
              href="https://github.com/BlockchainCommons/BCSwiftDCBOR"
              moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/BlockchainCommons/BCSwiftDCBOR</a></li>
        </ul>
        We've also produced a CLI app using our Rust library, which can
        be used to test parsing and validation:<br>
        <ul>
          <li><b>dCBOR CLI:</b> <a
              href="https://github.com/BlockchainCommons/dcbor-cli"
              moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/BlockchainCommons/dcbor-cli</a></li>
        </ul>
        We focused on the deterministic flavor of CBOR per <a
href="https://www.rfc-editor.org/rfc/rfc8949.html#name-deterministically-encoded-c"
          moz-do-not-send="true">§4.2 of RFC-8949 </a>because of our
        specific need to produce deterministically repeatable hashes in
        the Merkle Tree underlying our <a
          href="https://www.blockchaincommons.com/introduction/Envelope-Intro/"
          moz-do-not-send="true">Gordian Envelope</a> data format. We
        suspect that there will be others with similar needs and hope
        these dCBOR libraries will prove useful for other specs &
        standards using CBOR!<br>
        <br>
        I'd love to get any advice, comments, or thoughts you have on
        our dCBOR libraries, as well as any requirements that the
        libraries may need to meet. I'd also appreciate to get any
        CCG-related CBOR test examples that we can use in documents and
        examples, such as mDL and COSE tests.<br>
        <br>
        I'm also happy to discuss <a
          href="https://www.blockchaincommons.com/introduction/Why-CBOR/"
          moz-do-not-send="true">why we picked CBOR</a> as a data format
        and why dCBOR is particularly advantageous, either here or in
        our <a
          href="https://github.com/orgs/BlockchainCommons/discussions/184"
          moz-do-not-send="true">discussion forums at GitHub</a>.<br>
        <br>
        Thanks!<br>
        <br>
        -- Christopher Allen<br>
           Blockchain Commons<br>
      </div>
    </div>
  </body>
</html>