Changes between Version 4 and Version 5 of CommonFederationAPIv2

Timestamp:

04/09/14 14:30:58 (11 years ago)

Author:

Aaron Helsinger

Comment:

--

CommonFederationAPIv2

@@ -666 +666 @@
 Slices may have a set of members associated with them in particular roles. Certain SA may have policies that require certain types of membership requirements (exactly one lead, never empty, no more than a certain number of members, etc.). To that end, we provide a single omnibus method for updating slice membership in a single transaction, allowing any authorization or assurance logic to be supported at a single point in SA implementations.
 
-The set of recognized role types (e.g. LEAD, ADMIN, MEMBER, OPERATOR, AUDITOR) are to be listed in the get_version for a given Slice Authority.
-
-The following methods are written generically (with type arguments) to support the Slice Member Service as well as the Project Member Service (below). 
+The set of recognized role types (e.g. `LEAD`, `ADMIN`, `MEMBER`, `OPERATOR`, `AUDITOR`) are to be listed in the get_version for a given Slice Authority.
+
+The following methods are written generically (with type arguments) to support the Slice Member Service as well as the [#ProjectMemberServiceMethods Project Member Service (below)]. 
 
 {{{
@@ -724 +724 @@
 #
 # Arguments:
-#   Member_urn: The member for whom to find slices to which it belongs
+#   type: type of object for whom to lookup membership 
+#          (in the case of Slice Member Service, "SLICE", 
+#           in the case of Project Member Service, "PROJECT")
+#   member_urn: The member for whom to find slices to which it belongs
 #
 # Return:
@@ -789 +792 @@
 == Project Member Service Methods ==
 
-Projects may have members associated with them in particular roles and thus supports the same methods for member management as described above for the Slice Member Service. The differences are that the type provide is "PROJECT", the urn provided is a project URN and the membership information returned is tagged with "PROJECT_URN' and 'PROJECT_ROLE' as appropriate.
+Projects may have members associated with them in particular roles and thus supports the same methods for member management as described above for the [#SliceMemberServiceMethods Slice Member Service]. The differences are that the type provide is "PROJECT", the urn provided is a project URN and the membership information returned is tagged with "PROJECT_URN' and 'PROJECT_ROLE' as appropriate.
+
+For method signatures, see the listing under the [#SliceMemberServiceMethods Slice Member Service].
 
 || ''' Method ''' || ''' Description ''' ||