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

Tracking Issue: JSON-LD concerns #633

Closed
burnburn opened this issue May 17, 2019 · 1 comment
Closed

Tracking Issue: JSON-LD concerns #633

burnburn opened this issue May 17, 2019 · 1 comment
Milestone

Comments

@burnburn
Copy link
Contributor

This is a tracking issue to make sure a particular concern is clearly recorded. Duplicates will be closed.

@nadalin has raised a concern with JSON-LD as a supported syntax in the specification [1][2][3] and has asserted that non-JSON-LD users will be forced in some way to do JSON-LD processing. The specification makes clear that there is no expectation that all implementers of the specification must implement all of the syntactic representations. Additionally, the Working Group has clearly identified an intent to ensure that only users of JSON-LD are required to do any JSON-LD processing, while all other formats have only syntax constraints that may appear to be JSON-LD but in fact require absolutely no JSON-LD processing. We believe the specification reflects this intent.

[1] #525
[2] #557
[3] #489

This was referenced May 17, 2019
@burnburn burnburn added this to the CR-Exit milestone May 17, 2019
@burnburn
Copy link
Contributor Author

In the 16 July 2019 VCWG call:

RESOLVED: The Working Group has addressed all concerns outlined in issues #633 and #634 to the best of their ability, these are architectural decisions made by the group, and asserts that the specification reflects the consensus position of the Working Group and thus the issues should be closed.

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

No branches or pull requests

2 participants