solid / solid/specification

Proposal: Containment chain auxiliary resource

Open
#399 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

topic: auxiliary resources
Dominant language
HTML
Stars
563
Forks
108
Avg merge
4d 13h
Merged PRs (30d)
3

Description

In many cases, There exists natural requirement of knowing and or showing containment chain, like in breadcrumbs, etc.

Currently it is not possible, in single request. Though uri semantics can give hint, they are only necessary condition, rather than sufficient to establish containment fact (As we cannot know at which slash storage root starts, and whether given resource is auxiliary).

On file systems, it is possible to show such, as root is known, and no non-contained resources exist there.

Proposal is to have a hierarchy chain resource or a prov-chain resource as auxiliary resource to every resource, whose content is purely server managed.

It will return entire hierarchy chain, (aux chain too?), in single request. It will be inline with linked data principles too to derive hierarchy from links, rather than uri string manipulation. And enables getting better navigation and context about any solid resource.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Issue #399 is a proposal for a server-managed hierarchy-chain or prov-chain auxiliary resource for Solid resources. Start by reviewing the stated URI-semantics and linked-data constraints, then determine the resource shape, whether auxiliary chains are included, and how a single request returns the containment chain. Done requires an agreed specification rather than an implementation.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.