If necessary (is it?) the final lad covers all the kids we see explicitly constrained in /imp/profiles but which we don't write out in this +deps arm, and any kids not explicitly constrained by /imp/profiles. For the developer, it’s only important to declare e.g. “it matters to me that my shrub knows the user’s date of birth, and that I know the user’s date of birth is a valid %time.”
The /imp/profiles UI will usually be an iframe within another shrub’s UI.
Shrubs may be aware of several of your profiles, but in practice I assume they’ll only ever want one, so the “select a profile” iframe need only grant the shrub access to one profile. We could have several behaviours within the same iframe, and have the developer specify which behaviour they want in the iframe’s attributes.
We may also gate specific pieces of data in each profile to each shrub. So we might ask the user to pick a profile then say “Allow this shrub to access your First name, Last name, Email, Phone number, Home Address?” The developer could request specific pieces of info in the iframe attributes and imp/profiles could grant acccess to those shrubs accordingly.
DevEx should look something like this.
Depending on full profiles spec
Depending on a subset of the profiles spec
If necessary (is it?) the final lad covers all the kids we see explicitly constrained in
/imp/profilesbut which we don't write out in this+depsarm, and any kids not explicitly constrained by/imp/profiles. For the developer, it’s only important to declare e.g. “it matters to me that my shrub knows the user’s date of birth, and that I know the user’s date of birth is a valid%time.”The
/imp/profilesUI will usually be an iframe within another shrub’s UI.Shrubs may be aware of several of your profiles, but in practice I assume they’ll only ever want one, so the “select a profile” iframe need only grant the shrub access to one profile. We could have several behaviours within the same iframe, and have the developer specify which behaviour they want in the iframe’s attributes.
We may also gate specific pieces of data in each profile to each shrub. So we might ask the user to pick a profile then say “Allow this shrub to access your First name, Last name, Email, Phone number, Home Address?” The developer could request specific pieces of info in the iframe attributes and
imp/profilescould grant acccess to those shrubs accordingly.