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

support for "non-existing" properties #7

Open
EnnoMeijers opened this issue Aug 25, 2020 · 2 comments
Open

support for "non-existing" properties #7

EnnoMeijers opened this issue Aug 25, 2020 · 2 comments
Labels
UX An improvement to the user experience (UX).

Comments

@EnnoMeijers
Copy link
Contributor

The 'choose property' allows to enter "non-existing" properties like 'http://schema.org/work1' is that a bug or a feature?

@wouterbeek wouterbeek added the enhancement New feature or request label Aug 25, 2020
@wouterbeek
Copy link
Collaborator

wouterbeek commented Aug 25, 2020

IMO it would be a good usability improvement if non-existing IRIs cannot be defined within existing namespace (as in your example). It is easy to accidentally hit a key and use the wrong property/class as a result.

@wouterbeek wouterbeek added UX An improvement to the user experience (UX). and removed enhancement New feature or request labels Aug 25, 2020
@wouterbeek
Copy link
Collaborator

wouterbeek commented Aug 25, 2020

This may be implemented with an LDF query: if there are no results for {s} ?p ?o on the dataset that is used by the LD Wizard, then {s} does not exist. But this check must only be performed under some conditions: e.g., when {s} shares a predefined IRI prefix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX An improvement to the user experience (UX).
Projects
None yet
Development

No branches or pull requests

2 participants