Verifiable-Credentials.md

@@ -15,6 +15,12 @@
 }
 ```
 
+`id` is the organisation ID and can be any DID.  Here a mock kvk namespace is used, but it can also be an anonymous one (uuid) or something entirely third (e.g., a zinl or cibg namespace).  In the context used here, it should be considered to have no structure and only used for linking.
+
+`organisationType` is an extensible type identifying the organisation type.  There should be other types than hospitals, and third parties are free to include their own too (hence the use of an URI).
+
+`organisationSize` is an extensible type identifying the rough organisation size in intervals.  Some intervals should be predefined.  15 is an important cut-off size.
+
 ## VC 4: Organisation Membership
 
 ```json
@@ -31,6 +37,10 @@
 }
 ```
 
+`id` is a user id and should be a DID corresponding to user id's otherwise used in the system.  Here, a mock bsn namespace is used, but in practise it would be something issues using NUTS, the beheerorganisatie, or the individual organisation.
+
+`organisationId` is a DID and the same as used in VC 4.
+
 ## VC 3: Vetted Organisation membership (assuming VC 2 is a thing)
 
 ```json
@@ -65,6 +75,14 @@
 }
 ```
 
+Here, VC 3 extends VC 2, so both are included in the context/type.
+
+`capabilities` indicate permissions of the user within the network.  Each capability links to a `context`, a type indicating whether the credential is valid for production network, test network or an internal network (the type can be extended by third parties).  Individual `roles` indicate capabilities within the network and the type is extensible for special third party needs.
+
+`vettedBy` indicated the id of another user.  It is possible to include their VC 3 in the VP to provide a full chain of trust.  It is allowed that `vettedBy` is equal to `id` for anchors of trust.  It is also possible for applications to explicitly trust specific ids.
+
+The `vettingProcedure` is a type indicating how the user was vetted.  This type is extensible.
+
 ## VC 3: Vetted Organisation membership (assuming VC 2 is removed)
 
 ```json
@@ -96,4 +114,6 @@
 "
         }
 }
-```
\ No newline at end of file
+```
+
+This is identical to the previous VC 3, but does not extend VC 2.
\ No newline at end of file