QVMC Spec Implementation Changes adn visual fixes#63
Merged
Conversation
…aQuery components
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.
This PR modernizes the application UI and refactors the query cache toward closer alignment with the Query View Materialization Containers (QVMC) specification.
On the UI side, the main user-facing pages now share a more consistent card-based design language, tighter typography, better responsive behavior, and clearer task flows. LandingPage, PodUpload, PodBrowser, DataQuery, ContainerNav, PodRegistration, and PodLogin were all updated to feel more polished and easier to understand for non-technical users. Navigation and selection flows were simplified, container browsing was made more intuitive, upload/query/browser layouts were made more cohesive, and several compact expandable controls were added to reduce visual clutter.
On the query cache side, the implementation was refactored to move closer to the QVMC spec while preserving the existing .json results-file approach for Solid SDK compatibility. Cache entries now use deterministic 10-character hashes, richer queries.ttl metadata, better RDF list handling for sources, safer write ordering, and improved deletion cleanup. The cache UI also gained per-entry rename and WebID sharing actions, cached-query filtering/search/sort, and a compact YASR-based cached-results preview with clearer handling for loading, empty, missing, and error states.