The goal of the proposed modification is to streamline the existing Provider and Consumer model.
All elements of the Profile package are presented (or will be presented) by a single class, and for consistency's sake, the Provider and Consumer classes should be presented similarly.
Therefore:
Accordingly, the Organization class can be presented outside the Profile model, along with the classes Document, and Taxonomy, in some TBD package, e.g., Utility.
Note, in this version of the Organization class, the attribute Web Page is replaced with the attribute id. It is safe to assume that every organization has a URI, which is almost always the URL of the organization's web page.
Something to consider: every POC can be uniquely identified (and usually does) by email.
The goal of the proposed modification is to streamline the existing Provider and Consumer model.
All elements of the Profile package are presented (or will be presented) by a single class, and for consistency's sake, the Provider and Consumer classes should be presented similarly.
Therefore:
Accordingly, the Organization class can be presented outside the Profile model, along with the classes Document, and Taxonomy, in some TBD package, e.g., Utility.
Note, in this version of the Organization class, the attribute Web Page is replaced with the attribute id. It is safe to assume that every organization has a URI, which is almost always the URL of the organization's web page.
Something to consider: every POC can be uniquely identified (and usually does) by email.