Skip to content

Validate IRIs and language tags #203

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

Closed
lanthaler opened this issue Dec 11, 2012 · 4 comments
Closed

Validate IRIs and language tags #203

lanthaler opened this issue Dec 11, 2012 · 4 comments

Comments

@lanthaler
Copy link
Member

I think we should discuss whether JSON-LD processors should validate IRIs and language tags or just assume they are valid.

@niklasl
Copy link
Member

niklasl commented Dec 11, 2012

Yes. Many systems are lax about that. They should/must warn about the malformed value, but probably not drop it.

lanthaler added a commit that referenced this issue Dec 14, 2012
This addresses #185 as well as #203, #142 and #196.
@tidoust
Copy link

tidoust commented Dec 18, 2012

Unless it's really needed for other parts of the algorithms, I would not make IRI validation a MUST. A JSON-LD Implementation/Processor is not a JSON-LD validator and will not include validation code if that can be avoided, e.g. to keep the amount of code needed to a bare minimum for execution in constrained environments.

It may also be tough to include such validation code in an implementation. For instance, it may be hard to validate an IRI properly in a JavaScript implementation running client-side.

@lanthaler
Copy link
Member Author

RESOLVED: JSON-LD Processors MAY issue validation warnings for malformed IRIs and BCP47 language strings, but they MUST NOT attempt to correct validation errors.

lanthaler added a commit that referenced this issue Dec 18, 2012
…ST NOT be corrected

Updated the algorithms accordingly.

This addresses #203.
@lanthaler
Copy link
Member Author

I've updated the spec according the resolution. I will therefore close this issue in 24 hours unless I hear objections.

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

No branches or pull requests

3 participants