Merge pull request #426 from admin-shell-io/SeBa/268-notes-for-aas-value-and-metadata

Add Note for Metadata and ValueOnly Representations of Asset Administration Shells

Author: BirgitBoss

documentation/IDTA-01002-3/modules/ROOT/pages/changelog.adoc

@@ -41,6 +41,7 @@ Minor Changes:
 * Clarification on how to handle duplicate query parameters
 * Replace "servers" clause in OpenAPI files
 * Add notes for base64url-encoded values and order of "assetIds" query parameters
+* xref:http-rest-api/http-rest-api.adoc#modifier-constraints[HTTP Modifier Constraints]: Adding note for metadata and value-only representations of Asset Administration Shells (https://github.com/admin-shell-io/aas-specs-api/issues/268[#268])
 
 === Interface Changes w.r.t. V3.0.3 to V3.1
 

documentation/IDTA-01002-3/modules/ROOT/pages/http-rest-api/http-rest-api.adoc

@@ -328,7 +328,7 @@ Additional classes needed for payload of the HTTP/REST API specification can be
 [#modifier-constraints]
 == Modifier Constraints
 
-// Previously pointing to Clause 12.5
+
 To use link:https://admin-shell-io.github.io/aas-specs-antora/IDTA-01001/v3.1/mappings/mappings.html#_format_metadata_metadata_serialization[metadata objects] as described in xref:bibliography.adoc#bib1[[1]]., modifiers are implemented as HTTP query parameters or path suffixes.
 For example, a request for a specific submodel may look like: +
 GET /submodel/$value?level=deep&extent=withBlobValue
@@ -350,6 +350,10 @@ In addition, the modifiers can also be used for PUT operations.
 They define how the request content is delivered and have the same semantics as in the related GET operation.
 Only Content=Reference and Content=Path are not possible for PUT.
 
+====
+Note: Although metadata and value-only representations of Asset Administration Shells are possible, they are not supported up to now.
+====
+
 == Mapping of Operations
 
 The following <<table-mapping-operations>> shows the mapping of the generic operations to the HTTP/REST API.