Feat/fetch rdf metadata#203
Draft
angelo-v wants to merge 2 commits into
Draft
Conversation
llm: zai-org/glm-5.1 # Agent contributions - Proposed the task breakdown structure with dependency graph for the RDF metadata plan - Drafted four task files with goals, scope, verification criteria, and out-of-scope boundaries - Initially included rdflib upstream fix as Task 1; restructured to 4 tasks after human clarified it's assumed done # Human contributions - Clarified that the rdflib describedby fix is upstream and should be assumed, not tracked as a task - Requested the breakdown focus on smaller tasks without code details — steered away from implementation specifics - Directed creation of individual task files in the plan directory
The feature relies on an upstream fix and will not work yet. llm: zai-org/glm-5.1 blocked-by: linkeddata/rdflib.js#741 # Agent contributions - Identified that rdflib.js already parses `Link: rel="describedby"` HTTP headers, and implemented `Store.fetch()` auto-follow logic for describedby triples using the IANA URI - Wrote behavioural tests for the describedby auto-follow feature (tracer bullet, no describedby, graceful failure, seeAlso/alternate exclusion) - Rewrote tests to use real `Link` headers in mock responses instead of seeding fake describedby triples; fixed broken `dct:Image` assertion in failure test; fixed missing `it(` prefixes # Human contributions - Corrected that only the IANA `describedby` URI should be queried, not `rdfs:seeAlso` — rdflib conflates multiple link relations under it - Rejected the custom Link header parser, pointing out rdflib already does this; clarified tests should exercise the real Link header path - Directed that only a single describedby link should be supported (not multiple), simplifying the implementation to use `any()` instead of iterating - Insisted on no fake triple seeding — tests must pass real `Link` headers and let rdflib parse them; accepted that tests will fail until the upstream rdflib fix lands
angelo-v
force-pushed
the
feat/fetch-rdf-metadata
branch
from
9a9df7c to
6611fb0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.