Birgit Boss

Matching Strategy for Reference: what about referredSemanticId?

2

A Reference has a type, a referredSemanticId and a list of keys. In the chapter "Matching Strategies - Matching Algorithm for References" the referredSemanticId is not mentioned. Which impact does...

**Is your feature request related to a problem? Please describe.** There is a statement `The following types defined by the XSD and RDF specifications are explicitly omitted for serialization: xs:language,...

ValueOnly-Serialization: add information how to deal with optional elements

1

# What? in https://github.com/admin-shell-io/submodel-templates/issues/24 the qeustion arises how to deal with optional elements in the serialization. # How? Add sentence in chap. 11.4.2 ValueOnly-Serialization in JSON (V3.0) `Optional submodel elements...

JSON Schema for ValueOnly-Serialization. Exception also for SubmodelElementList?

3

# What? Question: In cha. 11.4.3 of IDTA-01002-3-0 it is written, that only SubmodelElementCollections are not considered in the serialization. It seems that this is also true for SubmodelElementList. Only...

asciidoc references

2

so far references to figures and chapters are hard-coded. Use references. Bibliography references should also be updated.

see https://github.com/admin-shell-io/aas-specs-iec61360/issues/10 Holds for Part 3a and for Part 1

Support IRDI-Path from ECLASS

1

**Is your feature request related to a problem? Please describe.** In some cases IRDI path need to be added as semanticId to SubmodelElements Example: absolute path: `0173-1---ADVANCED_1_1#01-ADO063#012/0173-1#01-AHF601#001/0173-1#02-ABI555#001/0173-1#01-AHF842#001*1/0173-1#02-ABI115#001 ` relative path...

Submodel ID and Administrative Information: too restrict?

1

Context: Administrative Information Attributes, Notes ``` Note 1: two submodels with the same semanticId but different administrative information shall have different IDs (Submodel/id), since they denote that the submodel is...

**Is your feature request related to a problem? Please describe.** The default in the current specificaiton V3.0 is that a specificAssetId is relevant for all. However, there are scenarios where...

Permalink to chapter JSON Mapping Rules in `schemas/json/README.md`

6

https://github.com/admin-shell-io/aas-specs/tree/master/schemas/json#json-mapping-rules does not link to chapter JSON Mapping rule but is identical to https://github.com/admin-shell-io/aas-specs/tree/master/schemas/json Used in Spec Part 1 for referencing to mapping rules