Skip to content

Refactor: renaming proposalsΒ #82

@tangrammer

Description

@tangrammer

Following a few ideas trying to easy the understanding of DRP design

To use business instead of covered-business. IMO under the umbrella of DRP, a business could be considered automatically covered thus we don't need to be redundant here.
To not use AuthorizedAgent but just UserAgent that can exercise authorized DRR. So, considering authorization as a compulsory property to exercise DRRs. Then as compulsory one we don't need to be explicit about it .
To use BusinessAgent(BA) instead of PIP, that way we can derive that the role of UA with the User is almost identical than the role of Business with PIP/BA. Then we could simplify the desing as U <--> UA <--> BA <--> B. Making a bit generic .... A DataRightsAgent (DRA) is encharged of recieving DRR state changes, track and dispatch them.

thanks for reading and ... looking forward your thoughts πŸ˜„

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions