links

_posts/blockchain/bitcoin/2019-03-11-bitcoin.md

@@ -49,7 +49,7 @@ last_modified_at: 2020-01-07
 
 * [BTCR DID Method](https://w3c-ccg.github.io/didm-btcr/) - [source](https://github.com/w3c-ccg/didm-btcr) - WORK ITEM: BTCR DID Method Spec did:btcr:      
   * The Bitcoin Reference DID method (did:btcr) supports DIDs on the public Bitcoin blockchain. The Bitcoin Reference method has minimal design goals: a DID trust anchor based on the Bitcoin blockchain, updates publicly visible and auditable via Bitcoin transactions, and optionally, additional DID Document information referenced in the transaction OP_RETURN data field. No other Personal Identifiable Information (PII) would be placed on the immutable blockchain.
-* [BTCR DID Resolver Specification](https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/topics-and-advance-readings/btcr_did_resolver.md)
+* [BTCR DID Resolver Specification](https://nbviewer.jupyter.org/github/WebOfTrustInfo/rebooting-the-web-of-trust-spring2018/blob/master/final-documents/btcr-resolver.pdf)
   > This describes the process of resolving a BTCR DID into a DID Document. The draft reference implementation is available at [https://github.com/WebOfTrustInfo/btcr-did-tools-js](https://github.com/WebOfTrustInfo/btcr-did-tools-js) (see didFormatter.js). Note not all steps described in this document are implemented yet.
   > 
   > See the [BTCR playground](https://weboftrustinfo.github.io/btcr-tx-playground.github.io/) for a live demonstration. The BTCR playground uses the draft reference implementation BTCR DID resolver.
@@ -59,7 +59,7 @@ last_modified_at: 2020-01-07
 * [WebOfTrustInfo/btcr-tx-playground.github.io](https://github.com/WebOfTrustInfo/btcr-tx-playground.github.io)
 * [WebOfTrustInfo/btcr-did-tools-js](https://github.com/WebOfTrustInfo/btcr-did-tools-js)
 * [WebOfTrustInfo/btcr-hackathon](https://github.com/WebOfTrustInfo/btcr-hackathon) - Virtual hackathon to create spec and code for Bitcoin-based Decentralized Identifiers (DIDs)
-* [BTCR v0.1 Decisions](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/btcr_0_1.md) by Kim Hamilton Duffy, Christopher Allen, Dan Pape (01/19)
+* [BTCR v0.1 Decisions](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/btcr_0_1.pdf) by Kim Hamilton Duffy, Christopher Allen, Dan Pape (01/19)
   > The Bitcoin Reference (BTCR) DID method supports DIDs using the Bitcoin blockchain. This method has been under development through Rebooting Web of Trust events and hackathons over the past year. The BTCR method's reliance on the Bitcoin blockchain presents both advantages and design challenges. During RWOT7, the authors made a number of design and implementation decisions -- largely scope-cutting in nature -- in order to lock down a Minimum Viable Product (MVP) version, which we'll refer to as v0.1. This paper documents those decisions, which will apply to the upcoming v0.1 BTCR method specification and associated v0.1 BTCR reference implementation.
 * [DIDs Demystified: A hands-on intro to DIDs via the BTCR DID Method – Kim Hamilton Duffy – Webinar 5](https://ssimeetup.org/dids-demystified-hands-intro-dids-btcr-did-method-kim-hamilton-duffy-webinar-5/)
   > This talk will demystify Decentralized Identifiers (DIDs) via the simple Bitcoin Reference (BTCR) DID Method. Kim will introduce the basics of DIDs and show how they work in action through demos of the creation/updating and resolution process in BTCR. We’ll build on this knowledge by discussing advanced features enabled by DIDs, along with a brief survey of other DID methods. By the end of the talk, you’ll be able to create and resolve your own BTCR DIDs through the live BTCR playground.

_posts/web-standards/2020-01-10-linked-data.md

@@ -56,6 +56,8 @@ last_modified_at: 2020-01-09
   > As for ledger updates, Accelerators also make use of Linked Data Capabilities. To prevent spamming the ledger, the costs of an update must somehow be accounted for. The traditional way to do this on a blockchain is to use proof of work, and this is also an option in Veres One, but for those use cases where expending time and energy on proof of work is less desirable users can use an "accelerator".
   > 
   > An accelerator is an entity that has been granted a capability to perform updates on the ledger more quickly. Accelerators may likewise take advantage of Linked Data Capabilities' support for delegation, with or without caveats.
+* [LD Signature Format Alignment](https://nbviewer.jupyter.org/github/WebOfTrustInfo/rebooting-the-web-of-trust-spring2017/blob/master/final-documents/ld-signatures.pdf)
+  > The goal of the "LD Signature Format Alignment" Working Group at Rebooting the Web of Trust IV was to investigate the feasibility and impact of the proposed 2017 RSA Signature Suite spec, which brings JSON-LD signatures into alignment with the JOSE JSON Web Signature (JWS) standards.The 2017 RSA Signature Suite is based on RFC 7797, the JSON Web Signature (JWS) Unencoded Payload Option specifcation. This approach avoids past concerns about JWT raised in the LD signature adopters, including:•Increased space consumption associated withbase-64 encoding.•Difculty of nesting or chaining signatures, leading to data duplication.•Use of a format that is not a JSON object, preventing ability to rely exclusively on a JSON document-based storage engine (whilepreserving the signature)
 
 ## GitHub Repos