Super simple #SolidProject CanIUse PoC

Follows links so Feature and App can document themselves

Feature feat:apps App
Feature feat:canUse SecondaryFeature
App feat:feature SecondaryFeature

Given that #LinkedData provides a directed graph across documents, construction of a UI can depend on data that cannot be reached by following links from our starting document.

It seems the common solution is to rely on out of band information from a third document, e.g. a type index in #SolidProject

Here, we want to display information about a and b, but we need our third document to make us aware that b exists - and that it has a backlink to a that we can use.

Probably not new #LinkedData ideas, but I've had two big realisations prompted by experimenting with #PodOS

1) I find it easier to build interfaces driven by components to which I have bound specific data rather than focusing on how I am navigating the knowledge graph

2) In an RDF world, this naturally happens by following predicates, and I want this level of control *in addition to* binding higher level shapes.

(Pls excuse rough diagrams)

#SolidProject

Unlocked achievement of too many apps available to open a #SolidProject resource

Probably need to favour user's preferred apps over others, and prefer more specific types/shapes over more general (here markdown vs LDP:Resource)