Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature #17 eclass application classification classes #33

Closed
wants to merge 3 commits into from
Closed

Feature #17 eclass application classification classes #33

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
149f39c
Merge pull request #2 from admin-shell-io/master
BirgitBoss Aug 25, 2020
edc80e0
Merge pull request #4 from admin-shell-io/master
BirgitBoss Jan 11, 2021
d66cff4
New #17 ECLASS ApplicationsClasses
BirgitBoss Jan 11, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 36 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,8 +162,42 @@ Via display names (introduced in V3.0RC01 Referable/displayName, it is also poss

Note: It is requested that the idShort of a non-identifiable is unique in its name space (for example in a Submodel or in a SubmodelElementCollection). This is not requested for the display names!



**[How to reference an ECLASS application or classification class](#id45)** <a id="id45"></a>

Referencing of application and classification classes is no different to referencing the ECLASS property definition.
Since classification and application classes correspond to a set of properties they can be used to describe the semantics of a complete submodel or of an SubmodelElementCollection.

Please be aware: to be completeley unambiguous it is either necessary to model the complete hierarchy in the submodel or by using a semanticId with more than one IRDI. The keys in the reference are ordered.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In ECLASS a classification class can only be contained in exactly another classification class. IEC61360 would also allow that a classification class is member of more than one other classification class. So for ECLASS property together with its parent classification class is sufficient for a unique semanticId. ==> change example


Example:

* Application Class: 0173-1#01-AAB572#006 Electric engineering, automation, process control engineering
* Classification Level 1: 0173-1#01-AAB583#008 Electrical drive
* Classification Level 2: 0173-1#01-AJZ695#008 Servo motor
* Classification Level 3: 0173-1#01-AJZ696#015 Servo asynchronous motor

For example the semanticId of a submodel containing the properties for the asynchronous servo motor without any further hierarchical modelling would be:


<aas:semanticId>
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

formatting not correct, should be aas:semanticId


<aas:keys>

<aas:key idType="IRDI" type="GlobalReference">0173-1#01-AAB572#006</aas:key>

<aas:key idType="IRDI" type="GlobalReference">0173-1#01-AAB583#008</aas:key>

<aas:key idType="IRDI" type="GlobalReference">0173-1#01-AJZ695#008</aas:key>

<aas:key idType="IRDI" type="GlobalReference">0173-1#01-AJZ696#015</aas:key>

</aas:keys>

</aas:semanticId>



(Answered: 2021-01-11)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a reference to the screencast #53 of https://admin-shell-io.com/screencasts/


## Asset Administration Shell in Detail Series

Expand Down