-
Notifications
You must be signed in to change notification settings - Fork 8
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
parent and child terminology #59
Comments
I believe it's called parent column and child column right now. I think we should change this to parent expression and child expression. I think this matches well with the proposal in #53 |
To fully match with #53, I'd suggest to use the names If we don't do that I assume the most simple join will be of form below, as an expression means that the object should be an ExpressionMap? ex:po rml:joincondition [
rml:child [
rml:reference "foreignId"
] ;
rml:parent [
rml:reference "Id"
]
] . |
If I combine #59 and #53 I would think that there is no problem if we call them cc/ @anaigmo |
Oki, then summing up the proposed changes in this issue:
Then instead of:
We would have without shortcuts: ex:po rml:joincondition [
rml:childMap [
rml:reference "foreignId"
] ;
rml:parentMap [
rml:reference "Id"
]
] . And with shortcuts: ex:po rml:joincondition [
rml:child "foreignId";
rml:parent "Id"
] . |
This issue had a proposal and is done. Closing. |
R2RML specification names the
rr:parent
andrr:child
as parent query and child query, would we keep this terminology?Or should we skip the query part and keep them only parent and child? I have the impression when we talk we typically use these terms.
or something else? if so, what?
The text was updated successfully, but these errors were encountered: