objectiser
commented
2 years ago Just to be clear, this mechanism does not need to be too onerous initially. For example:
- Initially all of the domain models could be within a single github repo, just segmented
- The properties could be within a single namespace (e.g. ‘wavi’) - worth discussing pro/cons
- Fixed duration release cycles (if changes have been made within that cycle)
- Changes recommended via github issues
- Domain experts for the area of change would discuss on the github issue before approving/rejecting
- Meetings only scheduled on adhoc basis when issue(s) need more in depth discussion
anthonyvprakash
gkc
Is your feature request related to a problem? Please describe.
The @platform provides infrastructure to enable apps (within their own namespace) to associate information they require against a user’s atsign. This means that the information is siloed based on applications.
Although not currently policed, the future benefit of this approach could be that only the app (that owns the namespace) is able to modify that information.
The disadvantage of this approach is that apps that provide capabilities within the same domain/vertical would require the user to enter/maintain the same information in multiple namespaces. This seems counter to the “you own the data” message - as technically it may be true, but with duplication of details per app, it still seems like the apps have some control.
If we use the wavi app and profile data as an example. If an app needs the same common user details, contact info and social channels, it could either duplicate the same fields within the app’s namespace, or the fields from wavi could be read/viewed. However I believe the expected approach is that the wavi app would need to be used to create/edit this information - which impacts the user experience of the other app.
Describe the solution you'd like
Upon identification of a suitable domain that could benefit from having a common model shared between apps, create a github project (under the atsign-foundation org) to act as a collaborative area for domain experts and app developers to define the specification, model and associated (but optional) UI widget for viewing/editing the fields.
The first candidate would be the contact/social information currently managed within the wavi app. This should be separated out into a “user profile” project, which can create (at a minimum) editor widgets for the fields, which could then be integrated into the wavi (and other) app(s).
As many domains have further levels of specialization, it may eventually lead to a hierarchy of domain groups.
The @foundation could provide an oversight role for these domain projects, to ensure a good level of governance.
Describe alternatives you've considered
Additional context