I just published "Vaccination Passport encoded as a W3C Verifiable Credential", which is exactly what it sounds like, plus some minor editorializing and bellyaching from moi.
#CCI
https://t.co/TzjkmIeuKB
My latest article: "Signing and Verifying JSON Documents with RSA Cryptography: ConsensasRSA2021"
Again, building on existing works and standards (IETF / W3C) but removing the need for JSON-LD … but playing nice with it, if that's your thing
https://t.co/B4N9r2VQlo
"A https://t.co/f1wBA8shLw description of a Health Condition like COVID-19"
Another quickie article, schema:HealthCondition to describe COVID using ICD-10
#COVID19#schema#semanticweb
https://t.co/yTCpqaxmUQ
Here's a bit more of a proposal: it's basically saying "write JSON-LD in a way such that you don't need to understand JSON-LD or use JSON-LD libraries"
#jsonld#json#semanticweb
https://t.co/V67XlDhYPx
"A https://t.co/f1wBA8shLw description of a Drug like Moderna"
A quickie article, basically just shows what the schema:Drug for Moderna would be.
#COVID19#vaccine#schema#semanticweb
https://t.co/71DW0ztKqe
@iotdb@wikidata Actually https://t.co/0rMBxWrs3A isn’t quite that; I did properties first, but it is similar to what you’re after - eg using bloodType, starSign instead of waiting years hoping schemaorg adds them?
@danbri@wikidata Certainly indicating type equivalence to a large vocabulary (I guess owl:sameAs) is a great idea. However, from a "human looking at it" POV, there's something unsatisfying with wdt:Q83307
@timdesjardins thanks - so basically what I see is that @WalletPasses has cloned the functionality, which is a solid idea though adds a separate step on Android.
https://t.co/p2ONbCJvwe
"Much of the data currently exchanging hands can be viewed as human-centric. We are not the only consumers of the web though, and someday that data may be made easier to read by those non-human consumers"