-
Notifications
You must be signed in to change notification settings - Fork 9
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
clarify in the spec that BN are allowed without reference to data #52
Comments
let's discuss this on a call, it's a difficult one |
The way we've written the container/collections specification is in line with this assumption, that is, the generation of a new blank node (that therefore cannot be named anywhere else) when there is no rml:reference of rr:template. I'm closing this issue. |
I'll open it again and transfer to the core spec |
There was a clarification added for this issue in this commit 552a485 |
There are still objections: should we include a clarification that it should be distinct? Enrique and Davide are in favor of keeping it distinct. @DylanVanAssche suggests to mention that it should be distinct but optionally can do it without guaranting it will be distinct but then they need a template. |
rr:template
or rml:reference
In Section 4.1 Identifying collections is stated:
I think there is a general issue that we need to decide on here which is: Do we allow the generation of blank nodes without an explicit expression (
rr:template
,rml:reference
, or other)?Generating a random blank node id has impact on how you can implement joins on those terms, because there is no way to make the id generation repeatable. The R2RML spec does not allow blank node generation without an
rr:template
orrr:column
, I assume for this reason.So if we would want to allow this we would either have to:
The text was updated successfully, but these errors were encountered: