SolidOS
Links to terms are broken
The links to terms lead to 404s even though the URIs are correct. For example if you use SolidOS to look at your webID profile, and click on "storage" you should go to http://www.w3.org/ns/pim/space#storage or "Person" should go to http://schema.org/Person. This works if you open the link in a new tab but if you directly click the link, you get a 404.
What exactly does one have to do to reproduce the problem? When you are using which pane to look at to look at which data? If I look at https://timbl.solidcommunity.net/profile/card with the default pane, the "Data" pane, then links to the predicates for storage and Person seem Ok like http://schema.org/Person and http://www.w3.org/ns/pim/space#storage for example.
What exactly does one have to do to reproduce the problem?
It happens for me on the default pane. I have the problem on both firefox and chrome and both logged in or not. Clicking on any term in the central column (e.g. type) or term-based items in the third column (e.g. Person) results in a 404.
What is the URI of the 404? If you extract the URI from the link with Control/click then Copy URL to clipbord then what is the URI you get?
The URI is the correct one. If I copy the link (or even just open in a new tab) it goes to the right place. See my first image above - it shows the correct URI but also mysteriously reports a 404.
On Fri, May 23, 2025 at 10:06 AM Tim Berners-Lee @.***> wrote:
timbl left a comment (SolidOS/solidos#218) https://github.com/SolidOS/solidos/issues/218#issuecomment-2905168161
What is the URI of the 404? If you extract the URI from the link with Control/click then Copy URL to clipbord then what is the URI you get?
— Reply to this email directly, view it on GitHub https://github.com/SolidOS/solidos/issues/218#issuecomment-2905168161, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKVJCJBXZIOACWWGJRQZNM3275ISXAVCNFSM6AAAAAB5WDPL2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBVGE3DQMJWGE . You are receiving this because you authored the thread.Message ID: @.***>