mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-07-01 08:31:29 +00:00
update links
This commit is contained in:
Infominer
parent
7d96513b1d
commit
2d77bfcf66
|
|
@ -6,81 +6,32 @@ excerpt: >
|
|||
|
||||
Like the web of hypertext, the web of data is constructed with documents on the web. However, unlike the web of hypertext, where links are relationships anchors in hypertext documents written in HTML, for data they links between arbitrary things described by RDF,. The URIs identify any kind of object or concept.
|
||||
layout: single
|
||||
permalink: /specs-standards/JSON-LD/
|
||||
canonical_url: 'https://decentralized-id.com/specs-standards/JSON-LD/'
|
||||
permalink: /specs-standards/linked-data/JSON-LD/
|
||||
redirect_from: /specs-standards/JSON-LD/
|
||||
canonical_url: 'https://decentralized-id.com/specs-standards/linked-data/JSON-LD/'
|
||||
categories: ["Specs-Standards"]
|
||||
tags: ["Digital Bazaar","RDF","JSON-LD","Credentials Community Group","Veres One"]
|
||||
last_modified_at: 2020-01-07
|
||||
tags: ["Digital Bazaar","JSON-LD","Credentials Community Group","Veres One", "Linked Data"]
|
||||
last_modified_at: 2020-01-09
|
||||
---
|
||||
|
||||
[On JSON-LD and the semantics of Identity](https://medium.com/transmute-techtalk/on-json-ld-and-the-semantics-of-identity-42d051d3ce14) Orie Steele
|
||||
## 101
|
||||
|
||||
* [JSON-LD for Beginners](https://moz.com/blog/json-ld-for-beginners)
|
||||
* [Why JSON-LD](https://jsonld.com/why-json-ld/)
|
||||
> JSON-LD is able to accomplish the same thing, but does not require HTML. It can exist in and of itself. In short, JSON-LD can be inserted into your web page without disrupting the current content or HTML.
|
||||
|
||||
## NFO
|
||||
|
||||
* [On JSON-LD and the semantics of Identity](https://medium.com/transmute-techtalk/on-json-ld-and-the-semantics-of-identity-42d051d3ce14) Orie Steele
|
||||
> In this post, we’ll explore how JSON-LD is used in a number of contexts including decentralized identity and verifiable credentials. We’ll also cover the basics of what you should know before using JSON-LD and how you can contribute to software and standards that rely on it.
|
||||
|
||||
[Publishing JSON-LD for Developers](https://datalanguage.com/news/publishing-json-ld-for-developers) - [Hacker News](https://news.ycombinator.com/item?id=17021939)
|
||||
[JSON-LD and Why I Hate the Semantic Web](http://manu.sporny.org/2014/json-ld-origins-2/) - [Hacker News](https://news.ycombinator.com/item?id=14474222)
|
||||
|
||||
[WebOfTrustInfo/ld-signatures-java](https://github.com/WebOfTrustInfo/ld-signatures-java)
|
||||
[WebOfTrustInfo/ld-signatures-python](https://github.com/WebOfTrustInfo/ld-signatures-python)
|
||||
[w3c-ccg/ocap-ld](https://github.com/w3c-ccg/ocap-ld) - WORK ITEM: Linked Data Object Capabilities specification - w3c-ccg/ocap-ld
|
||||
[w3c-ccg/ld-cryptosuite-registry](https://github.com/w3c-ccg/ld-cryptosuite-registry) - REGISTRY: Linked Data Keys Registry (managed by W3C Credentials Community Group) - w3c-ccg/ld-cryptosuite-registry
|
||||
|
||||
[Design Issues - LinkedData](https://www.w3.org/DesignIssues/LinkedData.html) -w3.org
|
||||
> The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. With linked data, when you have some of it, you can find other, related, data.
|
||||
>
|
||||
> Like the web of hypertext, the web of data is constructed with documents on the web. However, unlike the web of hypertext, where links are relationships anchors in hypertext documents written in HTML, for data they links between arbitrary things described by RDF,. The URIs identify any kind of object or concept. But for HTML or RDF, the same expectations apply to make the web grow:
|
||||
>
|
||||
> - Use URIs as names for things
|
||||
> - Use HTTP URIs so that people can look up those names.
|
||||
> - When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)
|
||||
> - Include links to other URIs. so that they can discover more things.
|
||||
|
||||
[RDF.js: The new RDF and Linked Data JavaScript library](https://www.w3.org/community/rdfjs/2018/04/23/rdf-js-the-new-rdf-and-linked-data-javascript-library/)
|
||||
> A diverse web requires decentralized data storage and maintenance. According to MIT’s Tim Berners-Lee, “it is about making links, so that a person or machine can explore the web of data. With Linked Data, when you have some of it, you can find other, related, data”.
|
||||
>
|
||||
> Zazuko’s CTO Thomas Bergwinkl adds that “Linked Data is built on top of the web stack and the programming language of the web is JavaScript. It is crucial for Web Developers to have access to well-designed JavaScript libraries to work with RDF and Linked Data”.
|
||||
>
|
||||
> The RDFJS W3C Community Group did a tremendous job in defining a standard to represent Linked Data in JavaScript. Several individuals and groups started to implement the RDFJS specification.
|
||||
|
||||
[Comparison of RDFJS libraries](https://www.w3.org/community/rdfjs/wiki/Comparison_of_RDFJS_libraries)
|
||||
|
||||
[Linked Data Capabilities](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/lds-ocap.md) By Christopher Lemmer Webber and Mark S. Miller
|
||||
> Linked Data Signatures enable a method of asserting the integrity of linked data documents that are passed throughout the web. The object capability model is a powerful system for ensuring the security of computing systems. In this paper, we explore layering an object capability model on top of Linked Data Signatures via chains of signed proclamations. fn:1 We call this system "Linked Data Capabilities", or "ld-ocap" for short.
|
||||
|
||||
[Identity as Linked Data on Immutable Ledgers](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/identity-as-linked-data-on-immutable-ledgers.md)
|
||||
> Content creators on the Web are getting a raw deal. They get a fraction of a cent for an ad played on YouTube, and nothing on Facebook, for filling these sites with traffic-driving content. It’s hard to make a living when you’re a creative. Licensing is hard; the user experience is bad, so lawyers and middlemen extract the most value. In the music industry, more money flows into the pockets of distributors than creatives. Consumers are often happy to pay for their content. Instead, they're forced to sit through ads.
|
||||
|
||||
[Blockchain Extensions for Linked Data Signatures](https://github.com/WebOfTrustInfo/rwot3-sf/blob/master/topics-and-advance-readings/blockchain-extensions-for-linked-data-signatures.md) by Manu Sporny, Harlan Wood, Noah Thorp, Wayne Vaughn, Christopher Allen, Jason Bukowski, and Dave Longley
|
||||
> The term Linked Data is used to describe a recommended best practice for exposing, sharing, and connecting information on the Web using standards, such as URLs, to identify things and their properties. When information is presented as Linked Data, other related information can be easily discovered and new information can be easily linked to it. Linked Data is extensible in a decentralized way, greatly reducing barriers to large scale integration.
|
||||
>
|
||||
> With the increase in usage of Linked Data for a variety of applications, there is a need to be able to verify the authenticity and integrity of Linked Data documents. The Linked Data Signatures specification added authentication and integrity protection to linked data documents through the use of public/private key cryptography without sacrificing Linked Data features such as extensibility and composability.
|
||||
|
||||
[Resource Integrity Proofs](https://github.com/WebOfTrustInfo/rwot7-toronto/blob/master/final-documents/resource-integrity-proofs.md) by Ganesh Annan and Kim Hamilton Duffy
|
||||
> Cryptographic linking provides discoverability, integrity, and scheme agility
|
||||
> Contributors: Manu Sporny, Dave Longley, David Lehn, and Bohdan Andriyiv
|
||||
>
|
||||
> Currently, the Web provides a simple yet powerful mechanism for the dissemination of information via links. Unfortunately, there is no generalized mechanism that enables verifying that a fetched resource has been delivered without unexpected manipulation. Would it be possible to create an extensible and multipurpose cryptographic link that provides discoverability, integrity, and scheme agility?
|
||||
>
|
||||
> Cryptographic linking solutions today have yet to provide a generalized mechanism for creating tamper-evident links. The Subresource Integrity standard limits this guarantee to script and link resources loaded on Web pages via the use of HTML attributes. IPFS provides a verification mechanism that is constrained to hash-based, content-addressable links, with no ability to complete content negotiation. RFC6920 proposes another mechanism that cannot be applied to existing links: it recommends the use of named information hashes and a resolution method that creates a content addressable URL [1]. Resource Integrity Proofs incorporates ideas from these standards and solutions to provide a new data format for cryptographic links that is fit for the open world.
|
||||
|
||||
[Recent happenings with Linked Data Capabilities](https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/topics-and-advance-readings/ld-ocap-recent-happenings.md)
|
||||
> Veres One's architecture has been adjusted to take full advantage of Linked Data Capabilities as its primary mechanism for granting authority to perform operations on the ledger as well as on DID Documents. permission to update key materials can be conditionally handed out to an entity (or entities) and later revoked if deemed appropriate using Linked Data Capabilities' design.
|
||||
>
|
||||
> 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.
|
||||
|
||||
[Designing a Linked Data developer experience](https://ruben.verborgh.org/blog/2018/12/28/designing-a-linked-data-developer-experience/)
|
||||
> Making decentralized Web app development fun
|
||||
>
|
||||
> While the Semantic Web community was fighting its own internal battles, we failed to gain traction with the people who build apps that are actually used: front-end developers. Ironically, Semantic Web enthusiasts have failed to...
|
||||
|
||||
[What Is JSON-LD Markup and Why Is It Better than Schema.org?](https://sitechecker.pro/json-ld-markup/)
|
||||
* [Publishing JSON-LD for Developers](https://datalanguage.com/news/publishing-json-ld-for-developers) - [Hacker News](https://news.ycombinator.com/item?id=17021939)
|
||||
* [What Is JSON-LD Markup and Why Is It Better than Schema.org?](https://sitechecker.pro/json-ld-markup/)
|
||||
> If you understand how to use schema.org, but do not dare to mark pages up because of the complexity of the process, this article is for you. There is an effective and easy-to-use alternative - the JSON-LD format.
|
||||
|
||||
[Libre Lounge: Episode 17: ActivityPub Part 2 on Apple Podcasts](https://librelounge.org/episodes/episode-17-activitypub-part-2.html) - [Part 1](https://librelounge.org/episodes/episode-12-activitypub-part-1.html) - [Part 3](https://librelounge.org/episodes/episode-20-activitypub-part-3.html)
|
||||
* [Libre Lounge: Episode 17: ActivityPub Part 2 on Apple Podcasts](https://librelounge.org/episodes/episode-17-activitypub-part-2.html) - [Part 1](https://librelounge.org/episodes/episode-12-activitypub-part-1.html) - [Part 3](https://librelounge.org/episodes/episode-20-activitypub-part-3.html)
|
||||
> In our ongoing series about ActivityPub, Chris and Serge explore the world of JSON-LD and the ActivityStreams vocabulary.
|
||||
>
|
||||
> Links: [ActivityPub Specification (w3c)](https://www.w3.org/TR/activitypub/) - [ActivityStreams (w3c)](https://www.w3.org/TR/activitystreams-core/) - [JSON-LD (json-ld.org)](https://json-ld.org/) [JSON-LD Playground (json-ld.org)](https://json-ld.org/playground/) - [Cyc (wikipedia)](https://en.wikipedia.org/wiki/Cyc) - [RDF (w3c)](https://www.w3.org/RDF/)
|
||||
* [JSON-LD and Why I Hate the Semantic Web](http://manu.sporny.org/2014/json-ld-origins-2/) - [Hacker News](https://news.ycombinator.com/item?id=14474222)
|
||||
|
||||
|
||||
## [JSON-LD Articles and Presentations](json-ld.org/learn.html) ([source](https://github.com/json-ld/json-ld.org))
|
||||
|
|
@ -117,4 +68,54 @@ last_modified_at: 2020-01-07
|
|||
- [JSON-LD: Building Meaningful Data APIs](http://blog.codeship.com/json-ld-building-meaningful-data-apis/), [Benjamin Young](http://bigbluehat.com/).
|
||||
- [Webizing your database with Linked Data in JSON-LD on Cloudant](https://cloudant.com/blog/webizing-your-database-with-linked-data-in-json-ld/), [Benjamin Young](http://bigbluehat.com/).
|
||||
|
||||
Website content released under a [Creative Commons CC0 Public Domain Dedication](http://creativecommons.org/about/cc0) except where an alternate is specified. Part of the [PaySwarm](http://payswarm.com/) standardization initiative.
|
||||
Website content released under a [Creative Commons CC0 Public Domain Dedication](http://creativecommons.org/about/cc0) except where an alternate is specified. Part of the [PaySwarm](http://payswarm.com/) standardization initiative.
|
||||
|
||||
## GitHub Repositories
|
||||
|
||||
* [Torann/json-ld](https://github.com/Torann/json-ld) - Extremely simple JSON-LD Generator
|
||||
* [piprate/json-gold](https://github.com/piprate/json-gold) - JSON-goLD Documentations Travis CI results GoCover.io
|
||||
> This library is an implementation of the JSON-LD 1.1 specification in Go. It supports both URDNA2015 and URGNA2012 RDF dataset normalisation algorithms.
|
||||
* [JayHoltslander/Structured-Data-JSON-LD](https://github.com/JayHoltslander/Structured-Data-JSON-LD)
|
||||
> Collection of structured data snippets in Google preferred JSON-LD format. [codepen.io/collection/DNvPJE/](https://codepen.io/collection/DNvPJE/)
|
||||
* [codemeta/codemeta](https://github.com/codemeta/codemeta)
|
||||
> CodeMeta contributors are creating a minimal metadata schema for science software and code, in JSON and XML. The goal of CodeMeta is to create a concept vocabulary that can be used to standardize the exchange of software metadata across repositories and organizations. CodeMeta started by comparing the software metadata used across multiple repositories, which resulted in the CodeMeta Metadata Crosswalk. That crosswalk was then used to generate a set of software metadata concepts, which were arranged into a JSON-LD context for serialization.
|
||||
|
||||
### [JSON-LD WG](https://www.w3.org/2018/json-ld-wg/)
|
||||
- [w3c/json-ld-framing](https://github.com/w3c/json-ld-framing) - JSON-LD 1.1 Framing Specification
|
||||
- [w3c/json-ld-api](https://github.com/w3c/json-ld-api) - JSON-LD 1.1 Processing Algorithms and API Specification
|
||||
- [w3c/json-ld-syntax](https://github.com/w3c/json-ld-syntax) - JSON-LD 1.1 Specification
|
||||
* [w3c/json-ld-bp](https://github.com/w3c/json-ld-bp) JSON-LD 1.1 Best Practices Note [w3c.github.io/json-ld-bp](https://w3c.github.io/json-ld-bp/)
|
||||
* [w3c/json-ld-rc](https://github.com/w3c/json-ld-rc)
|
||||
|
||||
## JSON-LD Public Repositories
|
||||
* [json-ld/json-ld.org](https://github.com/json-ld/json-ld.org) - JSON for Linked Data
|
||||
* [json-ld/json-ld-patch](https://github.com/json-ld/json-ld-patch) - JSON-LD Patch
|
||||
* [json-ld/minutes](https://github.com/json-ld/minutes) - Teleconference minutes - text and audio logs
|
||||
* [json-ld/normalization](https://github.com/json-ld/normalization) - RDF Dataset Normalization
|
||||
* [json-ld/tests](https://github.com/json-ld/tests) Archived - [READ-ONLY] Subtree split of the JSON-LD tests – obsolete, please see WG test suites
|
||||
* [json-ld/scrawl.js](https://github.com/json-ld/scrawl.js)
|
||||
Scribe tool used by the JSON-LD Community Group
|
||||
* [json-ld/Charter](https://github.com/json-ld/Charter)
|
||||
Charter for JSON-LD WG
|
||||
|
||||
### Digital Bazaar
|
||||
- [json-ld](https://github.com/digitalbazaar/json-ld) - A Context-based JSON Serialization for Linked Data
|
||||
- [jsonld-cli](https://github.com/digitalbazaar/jsonld-cli) - JSON-LD command line interface tool
|
||||
- [pyld](https://github.com/digitalbazaar/pyld) - JSON-LD processor written in Python
|
||||
- [jsonld.js](https://github.com/digitalbazaar/jsonld.js) - A JSON-LD Processor and API implementation in JavaScript
|
||||
- [php-json-ld](https://github.com/digitalbazaar/php-json-ld) - PHP implementation of a JSON-LD Processor and API
|
||||
- [jsonld-signatures](https://github.com/digitalbazaar/jsonld-signatures) - An implementation of the Linked Data Signatures specification for JSON-LD. Works in the browser and Node.js.
|
||||
- [jsonld-request](https://github.com/digitalbazaar/jsonld-request) - LIbrary to load JSON-LD from stdin, URLs, or files.
|
||||
- [jsonld-patch](https://github.com/digitalbazaar/jsonld-patch) - JSON patch for JSON-LD
|
||||
- [crypto-ld](https://github.com/digitalbazaar/crypto-ld)
|
||||
- [ecdsa-koblitz-signature-2016](https://github.com/digitalbazaar/ecdsa-koblitz-signature-2016) - Provides EcdsaKoblitzSignature2016 LD proof suite
|
||||
- [bedrock-angular-jsonld](https://github.com/digitalbazaar/bedrock-angular-jsonld) - JSON-LD support for bedrock-angular apps
|
||||
- [cuckoo-ldp](https://github.com/digitalbazaar/cuckoo-ldp) - Cuckoo Cycle Based Linked Data Proofs
|
||||
- [proofs-ld](https://github.com/digitalbazaar/proofs-ld)
|
||||
- [ld-signature-demo](https://github.com/digitalbazaar/ld-signature-demo)
|
||||
- [bedrock-angular-ldn](https://github.com/digitalbazaar/bedrock-angular-ldn) - Bedrock AngularJS module for Linked Data Notification Sender+Consumer
|
||||
- [bedrock-ldn-inbox](https://github.com/digitalbazaar/bedrock-ldn-inbox) - Bedrock module for Linked Data Notification Inboxes
|
||||
- [bedrock-ldn-receiver](https://github.com/digitalbazaar/bedrock-ldn-receiver) - Bedrock module for Linked Data Notification Receiver
|
||||
- [x25519-key-pair](https://github.com/digitalbazaar/x25519-key-pair) - An X25519 (Curve25519) DH key implementation to work with the crypto-ld LDKeyPair API
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user