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
Problem with termtype guessing #9
Comments
Yes. That's because In short: |
Yes but imagine tou have |
You provide a literal. If you want to provide an IRI for a resource description, then you provide
|
I see then the R2RML spec is missing one point:
|
The paragraph of the spec you are referring to is concerned with column-based term maps. rr:object (and rr:graph and rr:predicate, for that matter) are all shorthand for constant-based term maps. |
The spec is clear in my opinion:
When using rr:object, it is either an IRI or a literal, which is determined by "the syntax": <> vs. "" |
Actually they have a note I did not see:
Sorry, I think this can be closed :) thank you! |
R2RML spec says:
If the term map does not have a rr:termType property, then its term type is:
rr:Literal, if it is an object map and at least one of the following conditions is true:
It is a column-based term map.
It has a rr:language property (and thus a specified language tag).
It has a rr:datatype property (and thus a specified datatype).
rr:IRI, otherwise.
But when I have
rr:object
and I do not specify temtype the engines guesses it is a Literal even though none of the conditions abovce are met. E.g.:The text was updated successfully, but these errors were encountered: