Specify WebID Profile format for Groups / Organizations

[dmitrizagidulin]

Our current WebID Profile spec covers the format of a profile for an individual person/user.

This issue is to specify the profile format of a Group / Organization / Company, to include items like:

• The group's WebID
• Link to an acl-protected Group Listing of members
• Cryptographic key material (for signing and encryption)
• Other relevant metadata

[jeff-zucker]

While profiles for organizations and individuals are, of course, very important topics, they are quite specifically excluded from this specification and have been since the very first README which says

Profiles contain two major types of information: 1) identifying information such as a person or organization's name, purpose, contacts, etc. and 2) infrastructure information such as what types of data the user has, where it is stored, and who has access to it. This document will focus on the latter - the information that an app can use to learn how to interact with the data associated with the Social Agent's WebID.

This repo will eventually contain three documents -

• this one on infrastructure discovery,
• one on personal profile information,
• and one on organizational profiles.

These may be combined into a single document in the future.

Our intention is to get this first document out soon and not delay it by adding the additional parts yet. It's true that the WebID spec covers much of this ground for individuals, however the fact that it is not specific to Solid means that servers and clients are diverging and introducing such things as a WebID Document that can't be edited with the Solid Protocol (this is what ESS does currently) and calls for abandonment of single document under the user's control at the top of the profile tree, calls to not mention permissions in the spec and other sorts of pressing issues. We need to get those basic issues ironed out before we can tackle individuals and organizations.