-
Notifications
You must be signed in to change notification settings - Fork 12
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
add rml:languageMap #9
Comments
@VladimirAlexiev thanks for the recommendation! we encountered the same issue long time ago and we approached it by introducing the The See this test case https://github.com/RMLio/RML-Processor/tree/05266b836857f3c528db7a134fa0b84559a34432/src/test/resources/exampleLanguageMap As a Term Map is combined with FnO.io for transformations, it is also possible to modify the value from the original data, e.g. if the original data value is "engish", a function can be used to change it to a valid language tag, e.g. "en". As far as I see, |
Agree, this sounds better. |
Hi @andimou, I've tried to use the test cases you mentioned above. In my opinion they shouldn't work because of |
prefixes:
ex: "http://example.com/"
mappings:
person:
sources:
- ['persons.json~jsonpath', '$.persons[*]']
s: http://example.com/person/$(firstname)
po:
- [a, foaf:Person]
- [ex:lastName, $(lastname), $(lang)~lang]
- [ex:score, $(num), $(dt)] Data: {
"persons": [
{
"firstname": "John",
"lastname": "Doe",
"lang": "en",
"num": 3,
"dt": "xsd:integer",
},
{
"firstname": "Jane",
"lastname": "Smith",
"lang": "fr",
"num": "3.14",
"dt": "xsd:decimal",
},
]
} RML:
|
This issue is about http://rml.io/spec.html but I couldn't find a repo for that spec. If this is the wrong repo for this issue, please let me know and I'll move it.
There is no standard way to take the lang tag of a literal from a data field.
Back in Sep 2013 I proposed an extension
rrx:languageColumn
that does this (and uses the standardrr:language
as fallback in case of missing value).Please add this feature to RML.
It uses a namespace rrx: http://purl.org/r2rml-ext/ but if you want, we can re-host it under the RML namespace to increase standardization/uptake.
Thanks!
The text was updated successfully, but these errors were encountered: