Standardizing Domain Models on @Platform

[objectiser]

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

[objectiser]

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]

Hi @objectiser - Great to meet you. Pardon our tardiness in getting back to you. We were hosting an event last week and we are just coming back up for air.

Thanks for reaching out - we appreciate such feedback and inputs. Would you like to talk on a call sometime this week ? I have some Qs for you.

[objectiser]

Hi @anthonyvprakash, this week is a bit difficult but next week any day is fine (UK timezone).

[gkc]

@anthonyvprakash If it's feasible I'd love to participate in the call since I'm also in the UK timezone and have been discussing ideas related to / adjacent to @objectiser's proposal. Would have to be Tue-Fri next week as my Monday will be entirely spent travelling home from EMF Camp. If it doesn't work out then that's fine, I'll catch up afterwards.

[objectiser]

@anthonyvprakash, @gkc - any thoughts on a date/time to schedule the call? Next week is quite flexible for me.

[anthonyvprakash]

Am sorry @objectiser - Can you pick a time that works for you? https://calendly.com/atanthony

[objectiser]

@anthonyvprakash thanks. @gkc call scheduled for 14th at 2.30pm, hopefully you can make that day/time?

[anthonyvprakash]

@gkc & @objectiser - Please go ahead with the scheduled call. I will try my best to join.

[gkc]

Hi folks - 2:30pm tomorrow works fine for me however I do not see anything in my calendar ...

[objectiser]

@gkc Hopefully @anthonyvprakash can add you to the event.

[gkc]

2:30 on the 14th works just fine . However, I’ve not received an invitation / can’t see in my calendar …

…

On Thu, Jun 9, 2022 at 20:21 Gary Brown ***@***.***> wrote: @anthonyvprakash <https://github.com/anthonyvprakash> thanks. @gkc <https://github.com/gkc> call scheduled for 14th at 2.30pm, hopefully you can make that day/time? — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABXNZOOCYYTNSJBAW2BS2DVOI735ANCNFSM5WWUETFA> . You are receiving this because you were mentioned.Message ID: ***@***.***>