-
Notifications
You must be signed in to change notification settings - Fork 154
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
contribute section on the basic profile. [2] #785
Comments
This action was created in today's meeting. |
cc/ @rob-metalinkage |
@rob-metalinkage: any update on this action to report for tomorrow's meeting? |
Having looked at the draft yaml-ld spec I have created an initial PR I think we first need to decide how we introduce this (i.e. do we need a separate specification document or is this sufficient) - then we can look at listing the syntactical elements supported by JSON-LD. - can the WG decide where and how this should be included and if it needs further explanation - or just delegation to the relevant experts to fill in the details? |
We shouldn’t need any extra documents to do this, and fundamentally need to decide what is compatible, and if something incompatible is even in scope. |
I'm calling this action complete, as json-ld/yaml-ld#70 has been created. Thanks @rob-metalinkage. |
due 27 Jul 2022 (@rob-metalinkage)
The text was updated successfully, but these errors were encountered: