o-development / ldo

Monorepo for Linked Data Objects (ldo)
MIT License
23 stars 5 forks source link

LDO is making up quads #42

Open pchampin opened 2 months ago

pchampin commented 2 months ago

When I load https://h.champin.net/test.ttl with getResource, the global LDO dataset contains the following quads:

https://h.champin.net/          ldp:contains  https://h.champin.net/test.ttl  https://h.champin.net/
https://h.champin.net/test.ttl  rdf:type      ldp:Resource                    https://h.champin.net/
https://h.champin.net/test.ttl  rdf:type      schema:CreativeWork             https://h.champin.net/test.ttl

The first two quads (allegedly from the source https://h.champin.net/) are made up. https://h.champin.net/ is not a Solid container, so arguing that it ldp:contains anything is questionable. The 2nd one is equally questionable because test.ttl does not comply with the Solid nor the LDP specification (not sure if it makes a difference, but still).

This becomes worse when I load, e.g. https://id.inrupt.com/timbl, which results in the following made up quads:

https://id.inrupt.com/       ldp:contains  https://id.inrupt.com/timbl  https://id.inrupt.com/
https://id.inrupt.com/timbl  rdf:type      ldp:Resource                 https://id.inrupt.com/

https://id.inrupt.com/timbl identifies a real world object; this is confirmed by following the link (and the redirection) which says that it has type foaf:Agent. So it is not an ldp:Resource, and can not be contained in an LDP container (which, by the way, https://id.inrupt.com is not, either).

I would argue for simply not generating those quads. Are they required by LDO to work properly?