Re: JSON-LD contexts for a Membership VC

schema.org includes an @vocab so that JSON-LD errors don't happen and
instead terms are automatically mapped to URLs.

This is also what the V2 context does in verifiable credentials.

Just because a term has a URL doesn't mean the URL is resolvable or useful.

Issuers should review the full N-Quads of credentials and ensure all terms
resolve to human readable definitions.

Regards,

OS

On Mon, Mar 27, 2023, 9:19 PM Snorre Lothar von Gohren Edwin <
snorre@diwala.io> wrote:

> Hey just wanted to follow up on this and hear if anyone had any good
> examples of credentials that has used schema.org.
> As im experimenting with Schema.org as a context, I dont get any strict
> validation on things that are not registered with them.
>
> See this example from json ld playground
> <https://streaklinks.com/Bcfz5lx4eH7OH_H7fgF0aNlY/https%3A%2F%2Fjson-ld.org%2Fplayground%2F%23startTab%3Dtab-expanded%26json-ld%3D%257B%2522%2540context%2522%253A%255B%2522https%253A%252F%252Fwww.w3.org%252F2018%252Fcredentials%252Fv1%2522%252C%2522https%253A%252F%252Fschema.org%252Fdocs%252Fjsonldcontext.json%2522%255D%252C%2522type%2522%253A%255B%2522VerifiableCredential%2522%255D%252C%2522issuer%2522%253A%257B%2522id%2522%253A%2522did%253Aweb%253Adev.app.diwala.io%2522%257D%252C%2522issuanceDate%2522%253A%25222023-03-27T14%253A16%253A29Z%2522%252C%2522credentialSubject%2522%253A%257B%2522type%2522%253A%2522Person%2522%252C%2522id%2522%253A%2522did%253Akey%253Az6MkoatuG6vy6NNgvcxoiGs3X6U5MhRCkQ6c4zFL6u7gXzyU%2522%252C%2522birthDate%2522%253A%2522asda%2522%252C%2522nationality%2522%253A%2522Sweden%2522%252C%2522givenName%2522%253A%2522Test%2520Person%2522%252C%2522familyName%2522%253A%2522Last%2520Name%2522%252C%2522mumboJumbo%2522%253A%2522mumbo%2520jumbo%2522%257D%252C%2522id%2522%253A%2522urn%253Auuid%253A9ee6bb0f-b7d3-4c9d-8306-ff79de82fb8f%2522%252C%2522proof%2522%253A%257B%2522type%2522%253A%2522Ed25519Signature2018%2522%252C%2522created%2522%253A%25222023-03-27T12%253A16%253A30Z%2522%252C%2522verificationMethod%2522%253A%2522did%253Aweb%253Adev.app.diwala.io%2523key-1%2522%252C%2522proofPurpose%2522%253A%2522assertionMethod%2522%252C%2522jws%2522%253A%2522eyJhbGciOiJFZERTQSIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..mInvvzUw7hCN_RzT1379DrOMQbJcGG5LI9TRKAPw6YMEVEwYppYaNaChAEfFuozJtPbWKX6MI2e2j5LAwMGRBQ%2522%257D%257D%26frame%3D%257B%257D%26context%3D%257B%257D>(putting
> in the text to avoid long link, did not use shortener).
> Here you can see mumboJumbo attribute, and it seems to validate the
> JSON-LD, but the ref from schema.org returns 404.
>
> So just wondering what one can expect using schema.org types, and if we
> might be using it wrong?
> ᐧ
>
> On Tue, Jan 17, 2023 at 1:35 AM Orie Steele <orie@transmute.industries>
> wrote:
>
>> See what you can use from:
>>
>> https://schema.org/member
>>
>> https://schema.org/ProgramMembership
>>
>> OS
>>
>>
>>
>> On Mon, Jan 16, 2023, 6:26 PM Sanuja Wickramarathne <sanuja@diwala.io>
>> wrote:
>>
>>> Hi all!
>>>
>>> We are trying to create a *membership VC* with data props like *id
>>> number*, *name*, *year of admission* and would like to know which
>>> JSON-LD contexts can be used. Also, we will be happy if you have any
>>> examples that you can share with us?
>>>
>>
>
> --
>
> *Snorre Lothar von Gohren Edwin*
> Co-Founder & CTO, Diwala
> +47 411 611 94
> www.diwala.io
> <http://www.diwala.io/>
> *Stay on top of Diwala news on social media! **Facebook
> <https://www.facebook.com/diwalaorg>** / **LinkedIn
> <https://www.linkedin.com/company/diwala>** / **Instagram
> <https://www.instagram.com/diwala_/>** / **Twitter
> <https://twitter.com/Diwala>*
>