Changes between Version 2 and Version 3 of GAPI_AM_API_V3_DELTAS

Timestamp:

05/07/12 10:15:55 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

GAPI_AM_API_V3_DELTAS

@@ -83 +83 @@
  2. Some methods that take {{{slice_urn}}} now take a {{{urn}}} that may be a slice or sliver:
   - E.G. `Renew`, `Delete`, `Status`
-  - AMs are responsible for distinguishing whether the request operates on a slice or a sliver (see [#ChangeSetK:Standardizecertificatesandcredentials Change Set K] which defines how slice and sliver URNs differ).
+  - AMs are responsible for distinguishing whether the request operates on a slice or a sliver (see [#Adopted:ChangeSetK:Standardizecertificatesandcredentials Change Set K] which defines how slice and sliver URNs differ).
   - AMs are free to refuse to `Renew`, `Delete`, or provide status on an individual sliver, if the local AM or that resource type does not support it.
    - AMs should return an error message if the operation is not supported.
@@ -565 +565 @@
 
 Aggregates are expected to combine the manifests of all requested slivers into a single manifest RSpec. Note that a manifest returned here for only some of the slivers in a slice at this aggregate, may contain references to resources not described in this manifest (they are in other slivers). As a result, such manifests may not be directly usable as a subsequent request.
-