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

Improve handling around usage of prefixed vs full URIs #1159

Open
elpoelma opened this issue Mar 12, 2024 · 0 comments
Open

Improve handling around usage of prefixed vs full URIs #1159

elpoelma opened this issue Mar 12, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@elpoelma
Copy link
Contributor

A plugin/feature may fail due to the usage of prefixed vs non-prefixed predicates.

The problem
rdfaAware plugins/features may currently fail due to the usage of prefixed vs non-prefixed predicates/uris.
When adding a property/backlink to a node, we currently allow the usage of prefixed URIs.
The problem is that these URIs do not (always) get directly expanded:

  • This may be due to the fact that the prefix they use is not defined
  • Sometimes, the prefix only gets expanded after a reload of the document

This can be a pain, as we need to take the prefixed, as well as the full version of URIs when writing plugins/features.

Solutions

  • Short-term: when inserting a predicate/property, we should always use the 'long' version of the URI, and not the prefixed one
  • Long-term: only allow inserting prefixed predicates/uris when those prefixes have been defined in the document. Automatically expand URIs when reading/inserting them.
@elpoelma elpoelma added the bug Something isn't working label Mar 12, 2024
@elpoelma elpoelma pinned this issue Mar 12, 2024
@brenner-company brenner-company unpinned this issue May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant