mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2025-05-02 06:16:25 -04:00
change - to •
This commit is contained in:
⧉ infominer
parent
d58af13c81
commit
bc2b1bd67a
23 changed files with 72 additions and 72 deletions
|
|
@ -15,7 +15,7 @@ header:
|
|||
last_modified_at: 2020-11-09
|
||||
---
|
||||
|
||||
**[World Wide Web Consortium(W3C)](https://www.w3.org/) - [Twitter](https://twitter.com/w3c) - [GitHub](https://github.com/w3c) - [LinkedIn](https://www.linkedin.com/company/w3c/)**
|
||||
**[World Wide Web Consortium(W3C)](https://www.w3.org/) • [Twitter](https://twitter.com/w3c) • [GitHub](https://github.com/w3c) • [LinkedIn](https://www.linkedin.com/company/w3c/)**
|
||||
|
||||
* [ICANN WIki](https://icannwiki.org/W3C)
|
||||
> First started as an IETF application area at the beginning of 1990, the Web standard stack, given its foreseen volume and applicative nature on top of the Internet protocols, quickly spun off its own forum. The W3C then laid the foundations of the Web with the development of HTML 4 and XML at the end of the last century. It still works closely with IETF today, on the HTTP or URL specifications and in other areas of common interest (e.g. crypto, security, video).
|
||||
|
|
@ -98,7 +98,7 @@ last_modified_at: 2020-11-09
|
|||
* [w3c/webauthn-pay](https://github.com/w3c/webauthn-pay) - Joint task force of Web Authentication WG and Web Payments WG
|
||||
|
||||
### JSON-LD WG
|
||||
- [w3c/json-ld-wg](https://github.com/w3c/json-ld-wg) - [website](https://www.w3.org/2018/json-ld-wg/)
|
||||
- [w3c/json-ld-wg](https://github.com/w3c/json-ld-wg) • [website](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
|
||||
|
|
@ -149,7 +149,7 @@ last_modified_at: 2020-11-09
|
|||
> Abstract: While decentralized, user-centric identity systems provide hope that useful, secure identity systems may be possible on the Internet, ensuring that user data is protected in these system requires more than a technical solution. In this paper, we describe a project underway at Identity Commons to create a framework within which users can express their protection preferences (called identity rights agreements). Part of this project will establish a reputation system for identity providers and relying parties that engenders trust and lowers user risk.
|
||||
* [W3C Workshop on Identity in the Browser](https://www.w3.org/2011/identity-ws/report.html) 24/25th May 2011, Mountain View (USA)
|
||||
> Over the last ten years, for most end-users there has been no visible progress beyond cookie-managed usernames and passwords entered via HTML forms. Current password-based logins offers little value to the end-user, as they are forced to bear the onerous responsibility of remembering too many passwords or simply re-using low-security passwords. As passwords and cookies are easily compromised, both web-site operators and users then expose themselves to massive security breaches. Despite the large amount of valuable standardization work on identity, it is unclear how user agents such as Web browsers can interact with both identity-consuming applications and server-side federated identity services, and many current identity specifications either assume or underspecify secure authentication in the browser. The key missing component to enable trusted identity on the Web is likely then to be found in user-centric cross-browser standards for secure authentication and session management.
|
||||
* [Position papers](https://www.w3.org/2011/identity-ws/papers.html) - [Download all papers](https://www.w3.org/2011/identity-ws/papers.zip) as a ZIP file.
|
||||
* [Position papers](https://www.w3.org/2011/identity-ws/papers.html) • [Download all papers](https://www.w3.org/2011/identity-ws/papers.zip) as a ZIP file.
|
||||
* [Identity in the Browser: Easy Wins and Guiding Principles](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_52.pdf) by Naveen Agarwal, Miranda Callahan, Tyler Close, Travis McCoy, Chris Messina, Glen Murphy, Dirk Pranke (Google)
|
||||
* [National Strategy for Trusted Identities in Cyberspace - Requirements and Potential Use Cases](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_21.pdf) by Peter Alterman (NIH)
|
||||
* [A Vision for Browser-Assisted Web Authentication](https://www.w3.org/2011/identity-ws/papers/idbrowser2011_submission_43.pdf) by Siddharth Bajaj, Slawek Ligier (Symantec)
|
||||
|
|
@ -212,5 +212,5 @@ last_modified_at: 2020-11-09
|
|||
> The W3C is still exploring better ways to do authentication, for example in the [2014 workshop on authentication](http://www.w3.org/2012/webcrypto/webcrypto-next-workshop/Overview.html). The WebID is a Community Group, and anyone can start a Community Group. A Community Group does not necessarily reflect the endorsement of the W3C, but we encourage grassroots communities to experiment with technology that may become a future standard.
|
||||
* [USER IDENTITY ON THE WEB COMMUNITY GROUP](https://www.w3.org/community/w3id/)
|
||||
> Currently, more and more services are created on the web and require information about you, me, all of us. Therefore, users have to give away a lot of information about themselves to many different services. The point is that the users lose control of their identity on the web, by filling a lot of forms (e.g., through subscriptions). Privacy on the Internet is extremely important and must remain. Personal information is used by services we, sometimes, don't even know about, and it is a real problem. The aim of this group would be to think about new ways to identify individuals over the internet using trusted web based identities embedded directly into the core protocols of the web. At the same time it is important to maintain equilibrium between total privacy and providing information when needed, which means, when the user wants to.
|
||||
* [The Story of Open SSI Standards - Drummond Reed/Evernym - Webinar 1](https://ssimeetup.org/story-open-ssi-standards-drummond-reed-evernym-webinar-1/) - [Youtube](https://www.youtube.com/watch?v=RllH91rcFdE) - [Slideshare](https://www.slideshare.net/SSIMeetup/self-sovereign-identity-ssi-open-standards-with-drummond-reed)
|
||||
* [The Story of Open SSI Standards - Drummond Reed/Evernym - Webinar 1](https://ssimeetup.org/story-open-ssi-standards-drummond-reed-evernym-webinar-1/) • [Youtube](https://www.youtube.com/watch?v=RllH91rcFdE) • [Slideshare](https://www.slideshare.net/SSIMeetup/self-sovereign-identity-ssi-open-standards-with-drummond-reed)
|
||||
> Drummond Reed, Chief Trust Officer at Evernym and Sovrin Foundation Trustee, features in our first Webinar "The Story of SSI Open Standards" by giving us the background on the foundation of Self Sovereign Identity.
|
||||
|
|
|
|||
|
|
@ -27,14 +27,14 @@ 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
|
||||
> 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)
|
||||
* [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)
|
||||
> 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](https://json-ld.org/learn.html) ([source](https://github.com/json-ld/json-ld.org))
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Not all verifiable credentials are created the same. This post examines the cate
|
|||
* [Blockstack and Verifiable Credentials - Paris P2P Festival](https://p2p.paris/gen/attADzQJ92rNIv6B3-Blockstack_and_Verifiable_Credentials_-_Paris_P2P_Festival_.pdf)
|
||||
* [Enabling Decentralised Identifiers and Verifiable Credentials for Constrained IoT Devices using OAuth-based Delegation](https://www.ndss-symposium.org/wp-content/uploads/diss2019_05_Lagutin_paper.pdf)
|
||||
> Abstract—Decentralised identifiers (DIDs) and verifiable credentials (VCs) are upcoming standards for self-sovereign privacypreserving identifiers and authorisation, respectively. This focus on privacy can help improve many services and open up new business models, but using DIDs and VCs directly on constrained IoT devices can be problematic due to the management and resource overhead. This paper presents an OAuth-based method to delegate the processing and access policy management to the Authorisation Server thus allowing also systems with constrained IoT devices to benefit from DIDs and VCs.
|
||||
* [W3C Verifiable Credentials - Kent Branch](https://www.bcs.org/events/2019/october/w3c-verifiable-credentials-kent-branch/) - [pdf](https://cdn.bcs.org/bcs-org-media/4653/kent-w3c-verifiable-credentials-031019.pdf)
|
||||
* [W3C Verifiable Credentials - Kent Branch](https://www.bcs.org/events/2019/october/w3c-verifiable-credentials-kent-branch/) • [pdf](https://cdn.bcs.org/bcs-org-media/4653/kent-w3c-verifiable-credentials-031019.pdf)
|
||||
> The speaker will introduce the W3C Verifiable Credentials Data Model, which was published as a Proposed Recommendation in September 2019. Verifiable Credentials are the latest development in identity management and are fundamentally different from today's federated identity management systems such as SAML and OpenID Connect.
|
||||
>
|
||||
> David will describe the VC ecosystem and data model. He will then describe the prototype implementation which was built with colleagues from the University of Toulouse. They built a prototype system, which uses Fast Identity Online (FIDO) for user authentication, meaning that usernames and passwords are no longer needed. A pilot application was tested with a small sample of NHS patients and the speaker will present the results of this trial.
|
||||
|
|
@ -80,7 +80,7 @@ Not all verifiable credentials are created the same. This post examines the cate
|
|||
|
||||
### CCG
|
||||
|
||||
* [Credentials Community Group](https://www.w3.org/community/credentials/) - [Website](https://w3c-ccg.github.io/) - [Mail archive](http://lists.w3.org/Archives/Public/public-credentials/)
|
||||
* [Credentials Community Group](https://www.w3.org/community/credentials/) • [Website](https://w3c-ccg.github.io/) • [Mail archive](http://lists.w3.org/Archives/Public/public-credentials/)
|
||||
> The mission of the Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.
|
||||
* [w3c-ccg/vc-extension-registry](https://github.com/w3c-ccg/vc-extension-registry)
|
||||
REGISTRY: The Verifiable Credentials Extension Registry - w3c-ccg/vc-extension-registry
|
||||
|
|
@ -91,7 +91,7 @@ WORK ITEM: Verifiable Credentials Examples.
|
|||
|
||||
### VC-WG
|
||||
|
||||
* [W3C Verifiable Claims Working Group](https://www.w3.org/2017/vc/WG/) - [Mail Archives](https://lists.w3.org/Archives/Public/public-vc-wg/) - Technical discussion and public announcements for the Verifiable Claims Working Group
|
||||
* [W3C Verifiable Claims Working Group](https://www.w3.org/2017/vc/WG/) • [Mail Archives](https://lists.w3.org/Archives/Public/public-vc-wg/) - Technical discussion and public announcements for the Verifiable Claims Working Group
|
||||
> The mission of the Verifiable Claims Working Group (VCWG) is to make expressing and exchanging credentials that have been verified by a third party easier and more secure on the Web.
|
||||
* [w3c/verifiable-claims](https://github.com/w3c/verifiable-claims)
|
||||
W3C Verifiable Claims Working Group.
|
||||
|
|
@ -99,7 +99,7 @@ W3C Verifiable Claims Working Group.
|
|||
> Verifiable Claims Data Model and Representations specification.
|
||||
* [w3c/vc-use-cases](https://github.com/w3c/vc-use-cases)
|
||||
Verifiable Claims Use Cases.
|
||||
* [Verifiable Credentials Implementation Guidelines 1.0](https://www.w3.org/TR/vc-imp-guide/) - [w3c/vc-imp-guide](https://github.com/w3c/vc-imp-guide)
|
||||
* [Verifiable Credentials Implementation Guidelines 1.0](https://www.w3.org/TR/vc-imp-guide/) • [w3c/vc-imp-guide](https://github.com/w3c/vc-imp-guide)
|
||||
> Verifiable Claims WG - Verifiable Credentials Implementation Guidelines - w3c/vc-imp-guide
|
||||
* [w3c/vc-test-suite](https://github.com/w3c/vc-test-suite)
|
||||
Verifiable Claims WG Test Suite.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ redirect_from:
|
|||
last_modified_at: 2020-11-09
|
||||
---
|
||||
|
||||
**[Webpage](https://w3c.github.io/webauthn/) [GitHub](https://github.com/w3c/webauthn) - [Blog](https://www.w3.org/blog/webauthn/)**
|
||||
**[Webpage](https://w3c.github.io/webauthn/) • [GitHub](https://github.com/w3c/webauthn) • [Blog](https://www.w3.org/blog/webauthn/)**
|
||||
|
||||
* [Charter](https://www.w3.org/2019/10/webauthn-wg-charter.html)
|
||||
> The Web Authentication Working Group will develop recommendation-track specifications defining an API, as well as signature and attestation formats which provide an asymmetric cryptography-based foundation for authentication of users to Web Applications.
|
||||
|
|
@ -37,7 +37,7 @@ last_modified_at: 2020-11-09
|
|||
|
||||
<iframe src="https://slides.com/fidoalliance/webauthn-overview/embed" width="576" height="420" scrolling="no" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>
|
||||
|
||||
[Web Authentication: An API for accessing Public Key Credentials Level 1](https://www.w3.org/TR/webauthn/) - [WebAuthN-WG](https://www.w3.org/Webauthn/)
|
||||
[Web Authentication: An API for accessing Public Key Credentials Level 1](https://www.w3.org/TR/webauthn/) • [WebAuthN-WG](https://www.w3.org/Webauthn/)
|
||||
* [WebAuthn Awesome Awesome](https://github.com/herrjemand/awesome-webauthn) - A curated list of awesome WebAuthn/FIDO2 resources
|
||||
* [webauthn - npmjs.com](https://www.npmjs.com/package/webauthn)
|
||||
> WebAuthn is a W3C standard that enables web developers to replace passwords in their applications with FIDO authentication. This repository implements a NPM package for use in Node.js services. This package is in active development and not yet ready for production use. You can use it to kick the tires on WebAuthn. Please file issues to ask questions or provide feedback.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue