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
The way special characters are escaped is not consistent with IRIs, so it's hard to treat them equivalently: the URL-as-ID production rule uses backslash escaped characters, but escaping should use the URL/URI/IRI percent-encoding instead to be compatible with IRI syntax.
The text was updated successfully, but these errors were encountered:
This could be fixed by requiring the URL-as-ID to be following the URL production rule from the Uniform Resource Locator grammar, or by actually using actual IRIs as identifiers, similarly to the OWL2 Manchester syntax.
The way special characters are escaped is not consistent with IRIs, so it's hard to treat them equivalently: the URL-as-ID production rule uses backslash escaped characters, but escaping should use the URL/URI/IRI percent-encoding instead to be compatible with IRI syntax.
The text was updated successfully, but these errors were encountered: