-
Notifications
You must be signed in to change notification settings - Fork 8
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 compatible profile #70
Conversation
Initial statements about JSON-LD compatible profile
Thanks, we’ll try to discuss in the call tomorrow. |
This begs the question of what a profile that wasn't compatible with JSON-LD would look like, and how it could be processed. The only real features I could see as being useful are a multiple-document model (for which there are JSON analogs) and support for non-JSON tags (such as datetime, ...). I'm not sure we can make strong statements on a YAML-LD-JSON (or as I've called it "basic") profile without fleshing out what the goals of a more extended profile might be. |
This PR was discussed on the Aug 03 meeting where we decided to hold off until we had a better understanding of what an extended profile might do beyond a basic JSON-compatible profile. |
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
This issue was discussed in the August 17th meeting. General feel that it can be merged, but more detail is still necessary. |
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Replaced via #74. |
Initial statements about JSON-LD compatible profile
Preview | Diff