RE: [PROPOSED WORK ITEM] Citizenship Vocabulary

> It seems we have a couple of options, we can keep making individual 
> repositories or we can make a single repository for all vocabularies 
> developed for DHS SVIP.

No. No. and ... ahem ... NO : -)

This would actually defeat the purpose of why SVIP is transparent about our work in this area, and why we are ensuring that the companies that we have contractual relationships with are required to work in the public and engage with and incorporate feedback from the global technical community on the work going on in the DID/VC ecosystem. 

By doing so, we ensure that the baseline of security, privacy and interoperability that we are *ALL* striving for is done with full, public, visibility and accountability and in the public interest.

Look ... I do understand Orie's frustration here and I have my own frustrations about how we do not have a good, single pointer to a complete set of resources that we can send to someone so that they can bootstrap, leverage, contribute and enhance the interop work artifacts and test suites that we are developing and using under the CCG umbrella. This email (https://lists.w3.org/Archives/Public/public-credentials/2020Jun/0100.html ) was a  short term bug fix for that in the absence of that single point / resource / narrative.

I have some ideas about how to make this better, but that is all based on a desire to provide an answer to >> "Can we provide a community web resource w/ some narrative around it that points to interop test artifacts that are developed and enhanced by the community in a manner that enables someone to get started WITHOUT either SVIP or any of the SVIP Portfolio Companies acting as any type of Gatekeeper?" 

> 1. Better SEO for DHS SVIP

Hard Pass! 
We have better things to spend our time, treasure and attention on! 

> Possibility to share some JSON Schema  / SHACL files for things like 
> physical address, postal address, and organizations.

>>Those are all schema.org terms. We should try to convince them to add JSON Schema/SHACL 
>>files for those terms as supplementary things for schema.org.

Ahem .. We don’t need convincing on this because we agree that re-inventing the wheel is a bad idea.  
Our challenge to date has been to get this upvoted as a priority to date by the cohort with all the other things that needed to be done. 
So WE are forcing this issue by making this a work item for the cohort  : -)
So there! <grumble> <grumble> 

Best Regards,

Anil

Anil John
Technical Director, Silicon Valley Innovation Program 
Science and Technology Directorate 
US Department of Homeland Security 
Washington, DC, USA 

Email Response Time – 24 Hours

Received on Friday, 25 September 2020 15:52:17 UTC