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

Escaping for URL-as-ID is inconsistent with IRIs #149

Open
althonos opened this issue Feb 29, 2024 · 1 comment
Open

Escaping for URL-as-ID is inconsistent with IRIs #149

althonos opened this issue Feb 29, 2024 · 1 comment
Labels
1.4 major issues issues that are priority to address in 1.6

Comments

@althonos
Copy link
Member

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.

@althonos althonos added the 1.4 major issues issues that are priority to address in 1.6 label Feb 29, 2024
@althonos
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.4 major issues issues that are priority to address in 1.6
Projects
None yet
Development

No branches or pull requests

1 participant