You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 15, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: dataformat-uanodeset/nodeset/i4aas/changelog.csv
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,8 @@ note: SubmodelReferences and AssetReferences can contain the optional and native
9
9
6;ConceptDictionary;Bugfix;OPC UA Dictionary is used as ConceptDictionary,thus the dedicated Types AASConceptDictionaryType is not needed anymore. ;AASConceptDictionaryType removed. Also legacy references are removed;ok;
8;AASReference;Bugfix;"AASReference is non-hierarchical. Also See: https://reference.opcfoundation.org/v104/Core/docs/Part3/7.4/
12
-
""The semantic of NonHierarchicalReferences is to denote that its subtypes do not span a hierarchy and should not be followed when trying to present a hierarchy."" But this is the whole point of the AASReference,to follow the hierarchy which could be denoted by the AASReferenceType.";"removed AASReference and uses the hierachical reference HasAddIn to avoid confusion about ""a AASRerence Type which has a component referenced by a AASReference"". ";ok;
12
+
""The semantic of NonHierarchicalReferences is to denote that its subtypes do not span a hierarchy and should not be followed when trying to present a hierarchy."" But this is the whole point of the AASReference,to follow the hierarchy which could be denoted by the AASReferenceType.";"removed AASReference and uses the hierachical reference HasAddIn to avoid confusion about ""a AASRerence Type which has a component referenced by a AASReference"".
13
+
Also this can only happen for an object instance at runtime,when the referable exists. Thus it is not possible to add this with modeling rules because this will predefine some attribtues like browsename,which is IdShort of the actual Referable.";ok;
13
14
9;AASReferenceType;Bugfix;OptionalPlaceholder Referable is a BaseObjectType and as HasComponent defined,but it should be used the AASReference Type with Target AASReferableType.;using AASReference Type with Target AASReferableType. Removed legacy,non-hierachical Reference,see #8.;ok;
14
15
10;HasInterface;Bugfix;HasInterface already exists in OPC UA Standard but has been introduced within the I4AAS Namespace;removed proprietary HasInterface Reference Type;ok;
15
16
11;AASKeyDataType;V3 Change;"""local"" Attribute has been removed";"removed ""local"" attribute";ok;
@@ -23,7 +24,7 @@ changed Modeling Rule for Value";ok;
23
24
added specificAssetId
24
25
removed ""Asset""";;ok;
25
26
17;IdentifierKeyValuePair;added in V3;completely new type;added as AASIdentifierKeyValuePairType;ok;
26
-
18;AASDataTypeIEC62…;Bugfix;messed up,INTEGER_MEASURE missing;rearranged as in the AAS Meta Model Spec;ok;
27
+
18;AASDataTypeIEC62…;Bugfix;messed up,INTEGER_MEASURE missing;rearranged as in the AAS Meta Model Spec;ok;
27
28
19;Identifier;Enhancement;modeled as Type,but could be Structure;just proposed since issues with structures are known;;should be considered in an updated version
28
29
20;HasExtension / Extension;added in V3;new Class and Type Defintion;;;
29
30
21;AssetAdministrationShell/conceptDictionaries;changed in V3;;removed;ok;
@@ -35,7 +36,7 @@ removed ""Asset""";;ok;
35
36
""The identifier in the respective external dictionary shall be a unique URI string. This identifier is used for the NodeId and the BrowseName Attributes of instances of the DictionaryEntryType. The IdentifierType of the NodeId shall be STRING_1 with the identifier from the external dictionary as the value.""
36
37
37
38
Currently the NodeId does not follow this convention.";no action,see #27;ok;
38
-
26;General;Design Flaw;Many list are modeled as optional placeholder. Therefore,the attribute name of such a list given by the AAS Spec gets lost. It will lead to inconsistencies,e.g. when the order of such a list matters,if there are two list of the same type but with different attribute names,…;"affected attribtues:
39
+
26;General;Design Flaw;Many list are modeled as optional placeholder. Therefore,the attribute name of such a list given by the AAS Spec gets lost. It will lead to inconsistencies,e.g. when the order of such a list matters,if there are two list of the same type but with different attribute names,…;"affected attribtues:
39
40
AssetInformation/specificAssetId
40
41
HasDataSpecification/dataSpecification
41
42
AnnotatedRelationshipElement/annotation
@@ -54,6 +55,6 @@ fix by using introducing a (mandatory) folder which contains the list element (a
54
55
29;AASDataSpecificationIEC61360Type;Bugfix;contains Administraton and Category;must be removed;ok;
55
56
30;Qualifiable;Bugfix;not implemented in I4AAS;introduce Interface?;;
56
57
31;AASQualifierType;Bugfix;some attribute types do not fit;changed according to AAS V4;ok;
57
-
;;;;;;
58
+
32;BillOfMaterial;V3 Changes;The definition for BillOfMaterial was not that clear. It seems like BillOfMaterial is a List of References,no a single Reference.;should be solved by using a AASReferenceList;ok;
Copy file name to clipboardExpand all lines: dataformat-uanodeset/src/main/java/io/adminshell/aas/v3/dataformat/i4aas/mappers/AssetInformationMapper.java
0 commit comments