Closed rob-metalinkage closed 1 year ago
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.
This issue was discussed in the August 17th meeting.
General feel that it can be merged, but more detail is still necessary.
Replaced via #74.
Initial statements about JSON-LD compatible profile
Preview | Diff