add Implementations.md#171
Open
elf-pavlik wants to merge 3 commits into
Open
Conversation
3a19301 to
de3a762
Compare
de3a762 to
0b1ce5f
Compare
77e4ba9 to
fae74a4
Compare
TallTed
reviewed
Jun 9, 2026
Member
|
Much better! |
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
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.
closes #170
A lightweight way to track implementations per feature. Starting with
LWS currently doesn't clearly distinguish different classes of products. This may be needed for the test suite / test manifests as
spec:requriementSubject.Eventually I would aim for something more detailed as this old experiment (conformance numbers are random)
https://elf-pavlik.github.io/solid-efforts/#/implementation?id=https://solidproject.solidcommunity.net/catalog/data%23CSS