Skip to content
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

JSON-LD Vocabulary #435

Open
davidbarratt opened this issue Apr 17, 2022 · 0 comments
Open

JSON-LD Vocabulary #435

davidbarratt opened this issue Apr 17, 2022 · 0 comments
Labels

Comments

@davidbarratt
Copy link

davidbarratt commented Apr 17, 2022

I understand that you have previously rejected the idea of using Schema.org's JSON-LD vocabulary.

Would you be willing to host/maintain a custom vocabulary?

This could be as simple as having a URI for basics as https://jsonresume.org/basics.
That URI doesn't need to even resolve, it just needs to be agreed upon.

This would be documented in a JSON-LD context file and hosted at say:
https://jsonresume.org/jsonldcontext.jsonld

Then you would add a Link to the context like so:

Link: </jsonldcontext.jsonld>; rel="alternate"; type="application/ld+json"

Doing so would provide an agreed upon machine-readable vocabulary for resume data, which seems to be the goal of this project? If folks want to map the existing properties/types to existing vocabularies, they are free to do that or they can exist in the context I suppose with http://www.w3.org/2004/02/skos/core#exactMatch or https://schema.org/sameAs (see https://www.wikidata.org/wiki/Property:P1628).

Creating your own vocabulary is basically what Wikidata did and I think it's totally fine to do that. Having a custom vocabulary is way better than no vocabulary at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants