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
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.
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.
The 'choose property' allows to enter "non-existing" properties like 'http://schema.org/work1' is that a bug or a feature?
The text was updated successfully, but these errors were encountered: