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

Fixing the definition of instance of a graph to consider triple terms #71

Open
franconi opened this issue Jan 22, 2025 · 4 comments
Open
Labels
spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature

Comments

@franconi
Copy link

The definition of instance of a graph should be fixed to include triple terms as follows:

Suppose that M is a functional mapping from a set of blank nodes to some set of RDF terms. Any graph obtained from a graph G by replacing some or all of the blank nodes N in G by M(N) is an instance of G.

@franconi franconi added the spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature label Jan 22, 2025
@pfps
Copy link
Contributor

pfps commented Jan 22, 2025

What is the definition of "in" here?

@franconi
Copy link
Author

N in G if N appears in the parse tree of G.
I guess that the same sort of ambiguity happens also in the RDF 1.1 spec.

@pfps
Copy link
Contributor

pfps commented Jan 22, 2025

And what is the "parse tree"?

@franconi
Copy link
Author

Ok, so your issue is not about the change introduced by the new formulation, but about part of the formulation which was present before already; fair enough.

We could either mention the grammar (e.g., it appears as a RDF term in the graph) or explicitly write the inductive definition of "appears in", which is used elsewhere in the semantics document. Maybe this latter approach would be better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:substantive Change in the spec affecting its normative content (class 3) –see also spec:bug, spec:new-feature
Projects
None yet
Development

No branches or pull requests

2 participants