mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-12-17 11:34:30 -05:00
sorting nft and ethereum
This commit is contained in:
parent
a11ac125cf
commit
4534149449
@ -46,167 +46,6 @@ The Ford Foundation paper attached provides the references. However, this thread
|
||||
|
||||
* [https://redecentralize.org/redigest/2021/08/](https://redecentralize.org/redigest/2021/08/) says: *Human rights are not a bug*
|
||||
|
||||
## NFT
|
||||
|
||||
* [New twist on Verifiable Capability Authorizations: Data NFTs in the Ocean Protocol V4](https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0069.html) Michael Herman (Trusted Digital Web) (Saturday, 9 April)
|
||||
|
||||
A data NFT represents the copyright (or exclusive license against copyright) for a data asset on the blockchain — we call this the “base IP”. When a user publishes a dataset in OceanOnda V4, they create a new NFT as part of the process. This data NFT is proof of your claim of base IP. Assuming a valid claim, you are entitled to the revenue from that asset, just like a title deed gives you the right to receive rent.
|
||||
|
||||
* [China is using #blockchain technology to manage #prisoners as if each #prisoner was an #NFT](https://lists.w3.org/Archives/Public/public-credentials/2021Dec/0147.html) Michael Herman (Trusted Digital Web) (Sunday, 26 December)
|
||||
|
||||
China is using #blockchain technology to manage #prisoners as if each #prisoner was an #NFT/token on the blockchain...
|
||||
|
||||
* [https://www.taiwannews.com.tw/en/news/4384071](https://www.taiwannews.com.tw/en/news/4384071)
|
||||
|
||||
## Legal Identification
|
||||
|
||||
* [Principal Authority – new article on Wyoming law defining Digital Identity](https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0083.html) Christopher Allen (Thursday, 16 September)
|
||||
|
||||
What we've found as a good framework is the concept of "Principal Authority" which comes from the Laws of Agency, which allows us to leverage fiduciary style Laws of Custom to define requirements for practices when digital identity is delegated to others (whether for authorization or for use of data).
|
||||
|
||||
I've written up a layman's article (as I am not a lawyer) introducing this topic at:
|
||||
|
||||
* [https://www.blockchaincommons.com/articles/Principal-Authority/](https://www.blockchaincommons.com/articles/Principal-Authority/)
|
||||
|
||||
* [On why revocation is important...](https://lists.w3.org/Archives/Public/public-credentials/2022May/0052.html) Mike Prorock (Tuesday, 24 May)
|
||||
>[https://arstechnica.com/information-technology/2022/05/digital-drivers-license-used-by-4m-australians-is-a-snap-to-forge/](https://arstechnica.com/information-technology/2022/05/digital-drivers-license-used-by-4m-australians-is-a-snap-to-forge/)
|
||||
|
||||
Yikes!
|
||||
|
||||
For those that didn't read the article, the TL;DR is:
|
||||
|
||||
Tough to forge digital driver’s license is… easy to forge... 4 million mobile driver's licenses in NSW Australia compromised in an unrecoverable way.
|
||||
|
||||
## Code
|
||||
|
||||
* [re: RAR resources?](https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0083.html) Justin Richer (Monday, 12 July)
|
||||
|
||||
* [RAR has been implemented and is available in Authlete (and supporting libraries):](https://www.authlete.com/developers/relnotes/2.2.8/)
|
||||
|
||||
* [And in Connect2ID (and supporting libraries)](https://connect2id.com/blog/connect2id-server-12):
|
||||
|
||||
I know there are others out there, too, but these I’ve worked with.
|
||||
|
||||
* [New Swift Library for Optimized QR-Code Generation](https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0381.html) Christopher Allen (Monday, 30 August)
|
||||
|
||||
interoperable specifications for QR-based air-gap cryptographic use cases that we call Universal Resources (aka "UR").
|
||||
|
||||
Our UR specifications are designed for the interoperable transmission and storage of a variety of kinds of information, but in particular cryptographic data, and we have an advanced QR and CBOR-based architecture. (For more information on this see [URs: An Overview](https://github.com/BlockchainCommons/crypto-commons/blob/master/Docs/ur-1-overview.md)
|
||||
|
||||
For make it easier to implement our specs we also make available open source reference libraries and demo apps in [our repos on Github](https://github.com/BlockchainCommons)
|
||||
|
||||
* [DIF Grant #1: JWS Test Suite .. with specific references to the JSON-JSON-LD Divide](https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0356.html) Michael Herman (Trusted Digital Web) (Monday, 23 August)
|
||||
|
||||
* [[link](https://link.medium.com/a0416tjJXib)]The kinds of signature suite definitions that define Linked Data Proofs made strange bedfellows with the in-built mechanisms of JWT, which were hardened and commoditized earlier. This results in a slightly “balkanized” landscape of VC-JWTs that make different concessions to the expectations of JSON-LD-native parsers and systems.
|
||||
|
||||
* [#didlang Language 0.2, a new language for working with DID Identifiers, DID Documents, DID Agents, and DID Objects](https://lists.w3.org/Archives/Public/public-credentials/2022Jan/0021.html) Michael Herman (Trusted Digital Web) (Wednesday, 5 January)
|
||||
|
||||
...with new capabilities for coercing the Agent serviceEndpoint selector and Agent interface method selector ([13 minutes](https://youtu.be/bJBzrPnpJVo).
|
||||
|
||||
* [DIDs and Vanilla JWS with GitHub Actions](https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0099.html) Orie Steele (Monday, 18 April)
|
||||
|
||||
I wanted to share another DID Web + JOSE + GitHub demo:
|
||||
|
||||
- [https://github.com/OR13/signor](https://github.com/OR13/signor)
|
||||
- [https://github.com/OR13/jose-actions](https://github.com/OR13/jose-actions)
|
||||
|
||||
TLDR - JWS linked to DIDs from a Github Action [...] this will also work for VCs.
|
||||
|
||||
* [GitHub DIDs & VCs for Supply Chain Traceability](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0027.html) Orie Steele (Monday, 7 March)
|
||||
|
||||
I wanted to share some very recent (experimental and unstable) work we've done to enable Decentralized Identifiers and Verifiable Credentials to assist with the software supply chain.
|
||||
|
||||
- [](https://github.com/transmute-industries/verifiable-actions)[https://github.com/transmute-industries/verifiable-actions](https://github.com/transmute-industries/verifiable-actions)
|
||||
- [https://github.com/transmute-industries/public-credential-registry-template](https://github.com/transmute-industries/public-credential-registry-template)
|
||||
|
||||
The key idea is to enable github actions to sign and verify credentials that conform to the W3C Verifiable Credentials standard (which in turn supports various envelope formats including JOSE, COSE and PGP).
|
||||
|
||||
* [GitHub Integrations for securing Container Registries with Decentralized Identifiers & Verifiable Credentials](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0157.html)
|
||||
|
||||
I wanted to share some updates I made to the github action we created for working with DIDs and VCs in GitHub Workflows.
|
||||
|
||||
* [https://github.com/transmute-industries/public-credential-registry-template/blob/main/docs/public-container-registry.md](https://github.com/transmute-industries/public-credential-registry-template/blob/main/docs/public-container-registry.md)
|
||||
|
||||
* [...] TLDR:
|
||||
|
||||
- Creating Container Revision VCs with DID Web in a GitHub Action
|
||||
- Uploading the VC-JWT for the signed revision as a label to GitHub Container Registry
|
||||
- Pulling the latest container registry tag and checking the vc for the revision.
|
||||
|
||||
## Standardization
|
||||
|
||||
* [FYI: What makes a standard ‘world class’?](https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0213.html) Michael Herman (Trusted Digital Web) (Saturday, 14 August)
|
||||
|
||||
* A world class standard should have well-defined objectives that respond to real needs in a timely manner.
|
||||
|
||||
* Its technical content should be complete and accurate.
|
||||
|
||||
* It should be easy to understand (or as easy as the subject matter allows!) and easy to implement.
|
||||
|
||||
* Its requirements should be expressed clearly and unambiguously.
|
||||
|
||||
* It should be validated.
|
||||
|
||||
* It should be well-maintained.
|
||||
|
||||
Reference: [A Guide To Writing World Class Standards](https://www.etsi.org/images/files/Brochures/AGuideToWritingWorldClassStandards.pdf)
|
||||
|
||||
* [Re: historical background regarding success of responses to formal objections](https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0076.html) Liam R. E. Quin (Monday, 13 September)
|
||||
|
||||
In the 17 years i worked at W3C, the formal objections were
|
||||
|
||||
(1) "we [the objector] wanted to be on record as saying this but go ahead and publish" (the most common);
|
||||
|
||||
(2) we [the objector] have a product, or are about to ship a product, and the feature(s) in this spec would cause problems in the short-term for our product, and that's more important to us than the Web (no-one will ever admit to this but it's not uncommon)
|
||||
|
||||
(3) we object to this spec, we prefer another approach, so here's a bunch of fake objections to slow things down because we can't share our actual business strategy
|
||||
|
||||
(4) we believe there's a technical problem with this spec, but we didn't notice it over the past four years despite a last call review (this one is actually rare but does happen)
|
||||
|
||||
* [We're not the only community with problems (Fwd: Open Letter to Debian election candidates about Debian vendettas)](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0127.html) Manu Sporny (Saturday, 19 March)
|
||||
|
||||
Just a reminder that these "politics" and "other-ing" isn't some weird by product of the "identity community", or DIF, or CCG, or OpenID... it's endemic in any long-lived community composed of human beings.
|
||||
|
||||
It's not something you're ever rid of... it's something you manage over time;
|
||||
|
||||
## Procedure \ CCG
|
||||
|
||||
* [IRC mailing list bridge](https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0117.html) Charles E. Lehner (Saturday, 23 April)
|
||||
|
||||
Notifications of messages to this mailing list (public-credentials) are now sent to our IRC channel (#ccg).
|
||||
|
||||
* [re: How to contribute to new standards work? (was:Re: RDF Dataset Canonicalization - Formal Proof)](https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0172.html) Manu Sporny (Tuesday, 10 August)
|
||||
|
||||
* [The CCG Work Item process is outlined here](https://docs.google.com/document/d/1vj811aUbs8GwZUNo-LIFBHafsz4rZTSnRtPv7RQaqNc/):
|
||||
|
||||
* [Here's how you get started:](https://docs.google.com/document/d/1vj811aUbs8GwZUNo-LIFBHafsz4rZTSnRtPv7RQaqNc/edit%23heading%3Dh.f28tyzjvad8g)
|
||||
|
||||
This process is open to anyone -- no W3C Membership dues, fees, etc. required to participate.
|
||||
|
||||
* [Reminder: You can present to the CCG](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0151.html)
|
||||
|
||||
This is a friendly reminder that anyone in the community that is doing something interesting that you think the community should know about whether that work is done here in the CCG or elsewhere, can email the chairs with what you want to share and we can get you on the calendar. It's best if you email all 3 chairs.
|
||||
|
||||
* [Clarity about the group charter](https://lists.w3.org/Archives/Public/public-credentials/2022Jun/0044.html) Manu Sporny (Wednesday, 22 June)
|
||||
|
||||
there are statements like: "Buy our products! We're the best!" (with nothing else that we can learn from) that is frowned upon... but, in general, even if it is a feature in one of your products, chances are that we want to hear about it if it has relevance to how we might interoperate on that feature (or use it to meet a goal of the community).
|
||||
|
||||
* [2022-2026 Verifiable Data Standards Roadmap [DRAFT]](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0068.html) Manu Sporny (Saturday, 12 March)
|
||||
|
||||
![https://www.notion.soimages/image1.png](https://www.notion.soimages/image1.png)
|
||||
|
||||
## W3C
|
||||
|
||||
* [does the CCG have any thoughts about possible changes to W3C itself?](https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0067.html) Daniel Hardman (Saturday, 9 April)
|
||||
|
||||
This major organizational overhaul to the W3C is also happening at a time of unprecedented activity and change for the internet. Will the web support crypto and Web3 industry proposals? How will the web support advertising? What should be the baseline web browser security standards?
|
||||
|
||||
* [Announcement: W3C to become a public-interest non-profit organization](https://lists.w3.org/Archives/Public/public-credentials/2022Jun/0063.html) Kimberly Wilson Linson (Tuesday, 28 June)
|
||||
|
||||
* [W3C to become a public-interest non-profit organization](https://www.w3.org/2022/06/pressrelease-w3c-le.html.en)
|
||||
|
||||
"We designed the W3C legal entity in a way that keeps our core unchanged," said Dr. Jeff Jaffe, W3C CEO. "Our values-driven work remains anchored in the royalty-free W3C Patent Policy, and the W3C Process Document where we enshrined dedication to security, privacy, internationalization and web accessibility. W3C and its Members will continue to play a fundamental role in making the web work for billions of people."
|
||||
|
||||
## Decentralized Identifiers (DID)
|
||||
|
||||
* [re: Defining load balanced, failover clusters for DID Document serviceEndpoints?](https://lists.w3.org/Archives/Public/public-credentials/2022Jan/0056.html) (Monday, 10 January)
|
||||
|
Loading…
Reference in New Issue
Block a user