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

clarify in the spec that BN are allowed without reference to data #52

Open
pmaria opened this issue Sep 22, 2022 · 7 comments
Open

clarify in the spec that BN are allowed without reference to data #52

pmaria opened this issue Sep 22, 2022 · 7 comments
Labels
pending Waiting for another spec or issue to be ready proposal issue has a proposal to be solved

Comments

@pmaria
Copy link
Collaborator

pmaria commented Sep 22, 2022

In Section 4.1 Identifying collections is stated:

If no rr:template or rml:reference is provided for generating blank node IDs (rr:BlankNode) or IRIs (rr:IRI), then each iteration generates a new blank node identifier for the collection or container.

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 or rr:column, I assume for this reason.

So if we would want to allow this we would either have to:

  • Force processors into a way of implementing joins.
  • Have processors issue warnings when such a mapping is encountered, but it cannot guarantee correct results.
  • ?
@andimou
Copy link
Contributor

andimou commented Sep 26, 2022

let's discuss this on a call, it's a difficult one

@dachafra dachafra added the RML-core issue related to the core part of the RML vocab label Sep 28, 2022
@dachafra
Copy link
Member

During the meeting (28/09/2022), we have decided to allow the generation of BN without reference to the data.

Does this issue have any impact on collections/containers spec then? @chrdebru @frmichel
If yes, we will leave it open. If not, we can close or transfer it to the core spec

@frmichel
Copy link

During the meeting (28/09/2022), we have decided to allow the generation of BN without reference to the data.

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.

@dachafra
Copy link
Member

dachafra commented Oct 27, 2022

I'll open it again and transfer to the core spec

@dachafra dachafra reopened this Oct 27, 2022
@dachafra dachafra transferred this issue from kg-construct/rml-cc Oct 27, 2022
@andimou
Copy link
Contributor

andimou commented Oct 25, 2023

There was a clarification added for this issue in this commit 552a485

@andimou
Copy link
Contributor

andimou commented Nov 22, 2023

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.

@dachafra dachafra added proposal issue has a proposal to be solved and removed RML-core issue related to the core part of the RML vocab labels Jul 3, 2024
@kg-construct kg-construct deleted a comment from DylanVanAssche Jul 3, 2024
@dachafra
Copy link
Member

dachafra commented Jul 3, 2024

There was a clarification added for this issue in this commit 552a485

@andimou I inspected the commit but didn't find any clarification about BN generation without data reference. Am I missing something?

@dachafra dachafra changed the title identifying blank nodes without an rr:template or rml:reference clarify in the spec that BN are allowed without reference to data Jul 3, 2024
@dachafra dachafra added the pending Waiting for another spec or issue to be ready label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending Waiting for another spec or issue to be ready proposal issue has a proposal to be solved
Projects
None yet
Development

No branches or pull requests

4 participants