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

property values: option to force LD-R to recognize it as literal or URI #43

Open
mathib opened this issue May 4, 2018 · 0 comments
Open

Comments

@mathib
Copy link

mathib commented May 4, 2018

While entering new values for properties, LD-R checks the input and treats this input the same as the first input was treated. The first input value of a certain property of that resource, is classified behind the screens as 'literal' or 'URI', by looking for 'http://' or 'https://' I think.

This can give some strange results if the first value of e.g. a property 'foaf:name' was 'http://example.com/john' and thus classified by LD-R as being a URI. The property 'foaf:name' only points to literal values according its ontology. If someone enters "john" as a string, LD-R somehow also thinks this is a URI.

Would it be possible for LD-R to allow users to define in the configs if a certain property should have literals or URI's as object. Another approach could be to load this information from the ontology file(s) and looking if a certain property is an owl:ObjectProperty or an owl:DatatypeProperty. There could even be an option to highlight if a user wrongly entered a URI instead of a literal while the property is a DatatypeProperty (or the other way around: a literal for an ObjectProperty).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants