You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
RESOLVED: JSON-LD Processors MAY issue validation warnings for malformed IRIs and BCP47 language strings, but they MUST NOT attempt to correct validation errors.
I think we should discuss whether JSON-LD processors should validate IRIs and language tags or just assume they are valid.
The text was updated successfully, but these errors were encountered: