> For the complete documentation index, see [llms.txt](https://map.universal.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://map.universal.id/analysis/efforts.md).

# Ongoing efforts

This topic covers the major efforts going on in the identity industry, and tries to cleanly differentiate between their areas of focus including use cases, harm cases (vulnerability and attack vectors), world views, motivations, and underlying technology assumptions.

## Web 3.0

### DID

The decentralized identity standards and ecosystem built on top of Decentralized Identifiers (DID) and related standards.

#### W3C standardization

* [DID core spec recommendation](https://www.w3.org/TR/did-core/)
* [Verifiable credentials spec recommendation](https://www.w3.org/TR/vc-data-model/)
* [JSON-LD spec recommendation](https://www.w3.org/TR/json-ld11/)
* [Credentials community](https://www.w3.org/community/credentials/)

#### DIF

* [Decentralized identity foundation](https://identity.foundation/)
* [Identity discovery (DID)](https://identity.foundation/working-groups/identifiers-discovery.html)
* [Claims and credentials (VC)](https://identity.foundation/working-groups/claims-credentials.html)

#### Misc

* [Web of trust reboot using DID/VC](https://github.com/WebOfTrustInfo/rwot5-boston/blob/master/final-documents/amira.md)
* [Privacy by design - Discussion paper - Danish Ministry of Science](https://blog.privacytrust.eu/public/Reports/NewDigitalSecurityModels.pdf)
* [Proposed VC flavors in Healthcare](https://www.lfph.io/2021/02/11/cci-verifiable-credentials-flavors-and-interoperability-paper/)
* [CitizenKey](http://citizenkey.dk/) - Focus on security and privacy, with goals of full digital privacy, using technologies such as zero knowledge cryptography, hardware security, and avoidance of correlatable identity roots at all layers.

### Ethereum identity

#### [Semaphore](https://semaphore.appliedzkp.org/)

Semaphore is an effort using Zero Knowledge (ZK) technology to enable fully anonymous identity interactions with the public blockchain in the context of community activity such as "private voting, whistle-blowing, mixers, and anonymous authentication". Here's [Vitalik's recent proposal](https://ethresear.ch/t/anonymous-reputation-risking-and-burning/3926) that offers to extend the concept into fully anonymous decentralized reputation.

## Privacy by design

A general effort has been forming as a push back to big tech's recent privacy abuses, primarily lead by nations other than the United States. Here are its [foundational principles](https://www.ipc.on.ca/wp-content/uploads/Resources/7foundationalprinciples.pdf). Legally, it advocates for holding responsible tech companies that handle user personal data for mishandling and abuses. Technically, it advocates for engineering systems that default to high privacy, and minimize the chances of persona data exposure outside of the user's expressed permissions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://map.universal.id/analysis/efforts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.