Skip to content

Commit 70141cb

Browse files
authored
Merge branch 'IDTA-01002-3-1_preparation' into SeBa/423-clarify-padding
2 parents 9ec736a + 4a7ac6e commit 70141cb

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,7 @@ Minor Changes:
4242
* Replace "servers" clause in OpenAPI files
4343
* Add notes for base64url-encoded values and order of "assetIds" query parameters
4444
* xref:http-rest-api/http-rest-api.adoc#design-decisions[Design Decisions for the HTTP API]: Clarify that padding is not allowed for base64url-encoded values (https://github.com/admin-shell-io/aas-specs-api/issues/423[#423])
45+
* 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])
4546

4647
=== Interface Changes w.r.t. V3.0.3 to V3.1
4748

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -330,7 +330,7 @@ Additional classes needed for payload of the HTTP/REST API specification can be
330330
[#modifier-constraints]
331331
== Modifier Constraints
332332

333-
// Previously pointing to Clause 12.5
333+
334334
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.
335335
For example, a request for a specific submodel may look like: +
336336
GET /submodel/$value?level=deep&extent=withBlobValue
@@ -352,6 +352,10 @@ In addition, the modifiers can also be used for PUT operations.
352352
They define how the request content is delivered and have the same semantics as in the related GET operation.
353353
Only Content=Reference and Content=Path are not possible for PUT.
354354

355+
====
356+
Note: Although metadata and value-only representations of Asset Administration Shells are possible, they are not supported up to now.
357+
====
358+
355359
== Mapping of Operations
356360

357361
The following <<table-mapping-operations>> shows the mapping of the generic operations to the HTTP/REST API.

0 commit comments

Comments
 (0)