Remove annotations uplift from references API

descriptor.md

@@ -37,15 +37,6 @@ The following fields contain the primary properties that constitute an Artifact
 - **`artifactType`** *string*
 
   This OPTIONAL property defines the type or Artifact, differentiating artifacts that use the `application/vnd.oras.manifest`. When the descriptor is used for blobs, this property MUST be empty.
-
-- **`annotations`** *string-string map*
-
-  This OPTIONAL property contains the annotations from the annotations field in the artifact manifest for this
-  descriptor, if present. It does not include annotations from the blob descriptors. This property MUST use the
-  [annotation rules](https://github.com/opencontainers/image-spec/blob/main/annotations.md#rules) and various use cases
-  for references SHOULD define their own sets of annotations that clients can use to make decisions about which
-  artifacts need to be pulled.
-
 ## Digests
 
 The _digest_ property of a Descriptor acts as a content identifier, enabling [content addressability](http://en.wikipedia.org/wiki/Content-addressable_storage).

manifest-referrers-api.md

@@ -68,19 +68,13 @@ As an example, Notary v2 manifests use annotations to determine which Notary v2
       "digest": "sha256:3c3a4604a545cdc127456d94e421cd355bca5b528f4a9c1905b15da2eb4a4c6b",
       "mediaType": "application/vnd.oci.artifact.manifest.v1+json",
       "artifactType": "cncf.notary.v2",
-      "size": 312,
-      "annotations": {
-        "org.cncf.notary.v2.signature.subject": "wabbit-networks.io"
-      }
+      "size": 312
     },
     {
       "digest": "sha256:3c3a4604a545cdc127456d94e421cd355bca5b528f4a9c1905b15da2eb4a4c6b",
       "mediaType": "application/vnd.oci.artifact.manifest.v1+json",
       "artifactType": "example.sbom.v0",
-      "size": 237,
-      "annotations": {
-        "example.sbom.v0.author": "wabbit-networks.io"
-      }
+      "size": 237
     }
   ],
   "@nextLink": "{opaqueUrl}"