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

Add definitions for triples and triple patterns #350

Closed
wants to merge 2 commits into from

Conversation

kjetilk
Copy link
Member

@kjetilk kjetilk commented Nov 16, 2021

Addressing #348 .

I decided to paraphrase, as the formal definitions in particular for SPARQL, did not seem appropriate to put our document. Please check that out. I also decided to constrain to URIs, as we generally have done, but see #347 .

I'm not particularly confident this is the right thing to put in there, but the normative references are there for those who need them.

@kjetilk kjetilk added this to the Release 0.9 milestone Nov 16, 2021
@kjetilk kjetilk requested a review from a team November 16, 2021 23:54
@kjetilk kjetilk self-assigned this Nov 16, 2021
@damooo
Copy link

damooo commented Nov 17, 2021

URI restriction must be only about identifiers assigned to information-resources managed by solid server, independent of triple definition.
It must no way restrict general definition of triple to have it's terms to be only uris. Thus it just bars away much of linked-data.
According to spec, there cannot be triple <<dbpedia:rama> dbpedia:wikipage wikipedia:राम>>. in a resource <exampl.org/about-rama.ttl>.
It is contrary to rdf-spec. subject, predicate, object identifiers can be any iri in a triple.
Only identifiers we assign to solid-resources is constrainable, whether they are used in a triple in any position or not.

@kjetilk
Copy link
Member Author

kjetilk commented Nov 17, 2021

Yes, indeed. But if we defined it in terms of a IRI, we'd have to define IRI too. Perhaps we shouldn't introduce definitions in our document at all, but rather reference the relevant specifications in the places we use those terms?

@kjetilk
Copy link
Member Author

kjetilk commented Nov 17, 2021

Solid Editors resolved to close this and instead merge #351 .

@kjetilk kjetilk closed this Nov 17, 2021
@csarven csarven deleted the define/triples-patterns branch May 12, 2022 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Add references for "triple" (and "triple pattern") to the protocol document
2 participants