You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On this ticket we want to collect ideas sparked in conversations or implementations... feel free to add yours.
This repo is, for now, only documenting the 'as-is', however, we should not forget 'might-become' ideas too.
Please explain your idea in the comment. No discussion should be made here -> for that please open a new ticket with the title of your idea and label it with discussion and future idea.
I propose this process for these ideas in order to open up for brainstorming - no rating or judgment should be made here on this ideas.
The text was updated successfully, but these errors were encountered:
💡 -> the profile name available via the standard discovery mechanisms, for example via the Type Indexes (instead of having it in the Solid WebId profile directly).
as mentioned on the webId-profile gitter chat
💡-> have type indices separated per pod. For instance, if I have a Pod for all of my financial data and a separate Pod for my fitness tracking, I wouldn't want the type index for the first pod inside the second pod -- I'd want two separate type indices, based on two separate Solid Profiles
as mentioned on the webId-profile gitter chat. and also here
On this ticket we want to collect ideas sparked in conversations or implementations... feel free to add yours.
This repo is, for now, only documenting the 'as-is', however, we should not forget 'might-become' ideas too.
Please explain your idea in the comment. No discussion should be made here -> for that please open a new ticket with the title of your idea and label it with
discussion
andfuture idea
.I propose this process for these ideas in order to open up for brainstorming - no rating or judgment should be made here on this ideas.
The text was updated successfully, but these errors were encountered: