|
| 1 | +id;Subject;Type;Description;Changes in I4AAS/V3;Status;Comment |
| 2 | +1;Referable;V3 Feature;displayName and description were added as optional LangStringSet;new mapping rule - gets mapped to UANode native DisplayName and Description if present, otherwhise idShort is used;ok; |
| 3 | +2;LangStringSet;Bugfix;modeling insufficient, LocalizedText must be of ValueRank OneDimensional and not Scalar;changes for all LocalizedText Attributes;ok; |
| 4 | +3;Asset;Bugfix;"in I4AAS, Asset is a mandatory component of AAS with name ""Asset"" but should be prefixed ""Asset:{shortId}"". This does not work according to the definition of AASAssetAdministrationShellType.";no changes since V3 handles Assets now completely different;ok; |
| 5 | +4;Rules for Identifiables, Environment for Identifiables;Bugfix + Adjustments for V3;some Identifiables (Asset, Submodel) are modelled as component of the AAS. This is contradictory to some concepts of the AAS Meta Model, e.g. Submodels and Assets can be referenced by multiples AAS's.;"Removed Submodel and Asset Component from AAS. |
| 6 | +new rule: Submodel, AAS and Asset can be placed anywhere in the OPC UA Addressspace, but a basic FolderType (""AASEnvironmentType"") has been introduced which should be instantiated and used as parent folder. |
| 7 | +note: SubmodelReferences and AssetReferences can contain the optional and native OPC UA References ""AASReference"".";ok; |
| 8 | +5;Referable and Identifiable;Enhancement;Referable and Identifiabla in I4AAS are Interfaces, but in AAS are modelled as abstract classes. Referable and Identifiable are core concepts and contain mandatory fields. It can be modelled as abstract classes in I4AAS because it does not introduce problems of multiple inheritance. This also avoids the mismodelling by missing the mandatory fields. HasInterface was also not implemented!;"introduced abstract classes as top level classes which uses HasInterface Reference to the existing Interface. Only the ConceptDictionary already inherits DictionaryEntryType thus can not reuse the abstract class. Also HasInterface is just a ""hint"", you still need to model the attributes. This was missing has been done as well.";ok; |
| 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; |
| 10 | +7;AssetInformation;V3 Change;introduced;AASAssetInformationType introduced;ok; |
| 11 | +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; |
| 13 | +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 | +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 | +11;AASKeyDataType;V3 Change;"""local"" Attribute has been removed";"removed ""local"" attribute";ok; |
| 16 | +12;Asset;V3 Change;Asset is now only identifiable and hasDataSpecification, other attributes are now in AssetInformation;altered AASAssetType;ok; |
| 17 | +13;ValueListType;Bugfix;This type definition is not used anymore.;removed;ok; |
| 18 | +14;AASBlobType;Bugfix;does not represent a blob, but a file. Misses MimeType and Value Attribute;removed File Component, added MimeType and Value. Value is of Type ByteString;ok; |
| 19 | +15;AASFileType;Bugfix;Value is not of Type PathType, File is added as Component, should be HasAddIn since it is not part of the AAS Spec but an enhancement of I4AAS;"changed Value Type Definition |
| 20 | +changed File Reference Type |
| 21 | +changed Modeling Rule for Value";ok; |
| 22 | +16;Entity;Bugfix + Adjustments for V3;"added globalAssetId |
| 23 | +added specificAssetId |
| 24 | +removed ""Asset""";;ok; |
| 25 | +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 | +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 | +20;HasExtension / Extension;added in V3;new Class and Type Defintion;;; |
| 29 | +21;AssetAdministrationShell/conceptDictionaries;changed in V3;;removed;ok; |
| 30 | +22;View;changed in V3;is now deprecated;removed AASViewType FolderType;ok; |
| 31 | +23;SecurityPart;?;not in scope?;no further action;;should be considered in an updated version |
| 32 | +24;Operation;?;"AAS defined attributes are missing. I4AAS says it uses native Method as ""Operation"" Object and the modelling rule (btw spec and model are contradictory) allows for the inclusion of arguments. But still, OperationVariable as in AAS are not the argument but just their definitions and thus are missing in I4AAS.";should be redefined, considered for further changes;; |
| 33 | +25;DictionaryEntry;Bugfix;"https://reference.opcfoundation.org/v104/Core/docs/Amendment5/G.4/#TableG.6 |
| 34 | + |
| 35 | +""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 | +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 | +AssetInformation/specificAssetId |
| 40 | +HasDataSpecification/dataSpecification |
| 41 | +AnnotatedRelationshipElement/annotation |
| 42 | +Entity/statement |
| 43 | +ConceptDescription/isCaseOf |
| 44 | +Qualifiable/qualifier |
| 45 | +AssetAdministrationShell/Submodel |
| 46 | + |
| 47 | +not affected: |
| 48 | +SubmodelElementCollection (because itself is alredy a collection) |
| 49 | +Lists of Variables, e.g. LangString, Reference,... |
| 50 | + |
| 51 | +fix by using introducing a (mandatory) folder which contains the list element (as placeholders) and can be names according to AAS specification";ok; |
| 52 | +27;predefined dictionary entries;Clean Up;Due to the type definition and naming convention of the NodeId.csv export, names are duplicated. This causes issues for some SDKs. Also, due to the refactoring accoring to V3, the entries or not valid anymore.;removed all entries.;ok;Entries should be added in an updated version. |
| 53 | +28;IdShort;Clean Up;IdShort is mapped to BrowseName, but a few IdShort legacy objects were still present;removed legacy entries;ok; |
| 54 | +29;AASDataSpecificationIEC61360Type;Bugfix;contains Administraton and Category;must be removed;ok; |
| 55 | +30;Qualifiable;Bugfix;not implemented in I4AAS;introduce Interface?;; |
| 56 | +31;AASQualifierType;Bugfix;some attribute types do not fit;changed according to AAS V4;ok; |
| 57 | +;;;;;; |
| 58 | +;;;;;; |
| 59 | +;;;;;; |
0 commit comments