-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SemanticClarity/John Walker supports the W3C RCH WG #50
Comments
Thanks @jtwalker2000 |
Dear @jtwalker2000, We kindly ask you to review the new version, and either
Thanks in advance |
Dear 'Notifications'
I have reviewed the revised charter and I have continued interest in the
progress of the W3C LDS WG.
Please continue to include me in all relevant WG communications.
thx
-jw-
…On Tue, Feb 1, 2022 at 8:43 AM Pierre-Antoine Champin < ***@***.***> wrote:
Dear @jtwalker2000 <https://github.com/jtwalker2000>,
the proposed charter has been substantially changed since you submitted
your expression of support. More specifically, its scoped has been narrowed
down, to address some concerns raised in the Semantic Web community. See
also Ivan Herman's explanation of those changes on the SebWeb mailing list
<https://lists.w3.org/Archives/Public/semantic-web/2021Oct/0020.html>.
We kindly ask you to review the new version
<https://w3c.github.io/rch-wg-charter/>, and either
- renew your expression of interest (by a simple reply to this
thread), or
- to close this issue if you do not wish to renew it.
Thanks in advance
—
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZSWG5WVRBRNGZW5J6CPWTUZAEU5ANCNFSM43I6DVUA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
John Walker | Principal
SemanticClarity
510.393.3200
***@***.***
|
For the sake of clarity, editing the title to match the new name of the WG... |
@jtwalker2000 why closing the issue? Do you intend to retract your expression of support? |
No - my mistake, I thought my 'agreement' was complete ... my interest and
support continues. Please re-open if that is appropriate.
thx
-jw-
…On Thu, May 5, 2022 at 8:39 AM Pierre-Antoine Champin < ***@***.***> wrote:
@jtwalker2000 <https://github.com/jtwalker2000> why closing the issue? Do
you intend to retract your expression of support?
—
Reply to this email directly, view it on GitHub
<#50 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZSWG2E6U55VCZP54JCZW3VIPTUNANCNFSM43I6DVUA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
John Walker | Principal
SemanticClarity
510.393.3200
***@***.***
|
SemanticClarity would like to add its voice to supporting the creation of the W3C Linked Data Signatures Working Group.
Given Linked Data Signature adoption among governments around the world (for use in W3C Verifiable Credentials and W3C Decentralized Identifiers), as well as private industry (deployments to 152,000+ retail stores across the US)... and use in privacy-protecting digital signatures (BBS+) and other selective disclosure schemes... we think it's high time we cut an official standard that governments can use to move toward a more privacy-preserving future for their citizens.
The reasons above are in addition to all of the benefits that will be gained by verifiable data publishers -- there is a deep requirement to know where data came from on the Web today, misinformation is rampant, and this WG will standardize technologies that could be used to combat misinformation and gain trust in our Web-based data sources again.
For these reasons (and others), SemanticClarity is supportive of the LDS WG charter:
https://w3c.github.io/lds-wg-charter/
The text was updated successfully, but these errors were encountered: