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

Extension of the AssetKind class by a further entry #294

Closed
JulianRahm opened this issue Oct 18, 2023 · 1 comment
Closed

Extension of the AssetKind class by a further entry #294

JulianRahm opened this issue Oct 18, 2023 · 1 comment
Labels
accepted accepted in principle to be fixed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Milestone
V3.1

Comments

@JulianRahm
Copy link

Extension of the AssetKind class by a further entry "Role" or "TechnicalPlaceholder".

Background: In the context of engineering, resources are specified. At a later point in time, these are assigned an article (type) that fulfils the requirements of the equipment. The "TechnicalPlaceholder" is therefore a form of requirement definition that is indispensable in engineering. This workflow is typical for engineering, which is an essential starting point for a new asset administration shells on machine or plant level.
Especially during the life cycle of a machine, types can be exchanged. As a rule, the equipment definition ("TechnicalPlaceholder") is kept more general, so that different types from different manufacturers can be used for the defined equipment at a later date.

image

Relation between TechnicalPlaceholder, Type and Instance:
image
@BirgitBoss BirgitBoss added specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally V3.1 labels Nov 8, 2023
@BirgitBoss
Copy link
Collaborator

The issue was discussed in the AAS specification meeting on 25th October 2023: The extension of the enumeration AssetKind with the value "Role!" was accepted for V3.1.

@BirgitBoss BirgitBoss added this to the V3.1 milestone Nov 16, 2023
@BirgitBoss BirgitBoss added accepted accepted in principle to be fixed and removed V3.1 labels Nov 16, 2023
BirgitBoss added a commit that referenced this issue Dec 15, 2023
@BirgitBoss
New value "Role" in Enumeration AssetKind (#294)
894c320
BirgitBoss added a commit that referenced this issue Dec 15, 2023
@BirgitBoss
add new value "AssetKind" enumeration "Role" #294
6c3e2df 
Change PathType to allow not only file:  #299
@BirgitBoss BirgitBoss mentioned this issue Dec 15, 2023
Closed
@BirgitBoss BirgitBoss linked a pull request Dec 15, 2023 that will close this issue
Resolve issues, focus specification/schemata #315
Closed
@BirgitBoss BirgitBoss mentioned this issue Dec 21, 2023
Merged
BirgitBoss added a commit that referenced this issue Jan 29, 2024
@BirgitBoss
Resolve Issues V3.1 (#317)
e484be0 
* * (Editorial) MultiLanguageNameType inconsistent description, maxLength=128 (schemata were correct) ([#313](#313))
* (Editorial) HasKind/kind explanataroy text: use template, not type ([#313](#313))
* (Editorial) DataTypeDefXsd links now correctly to xmlschema11-2, not to xsd V1.1 ([#312](#312))
+ minor editorial changes

* New value "Role" in Enumeration AssetKind (#294)

* add new value "AssetKind" enumeration "Role"  #294
Change PathType to allow not only file:  #299

* Identifier: change length from 2000 to 2024 characters #299

* allow hyphens in idShort of Referables #295

* make Entity/entityType optional #287

* editorial change, add missing link to issue #295

* Update Constraint AASd-014 (part 2 of #287)

* EmbeddedDataSpecification/dataSpecification now mandatory #296

* Update Change Appendix w.r.t. EmbeddedDataSpecifcation/dataSpecification (now mandatory) #296

* #296 update Changes Section

* Editorial changes
#313

* semanticId of specificAssetId with name "globalAssetId"
#298

* Correct AASd-002

see #295 
for backward compatibility reasons idShort can end with an underscore. Additionally also 1 char idShorts are allowed.

* path .Specification.pdf

remove \

* fix typo
@s-heppner s-heppner mentioned this issue Feb 2, 2024
Closed
s-heppner added a commit to aas-core-works/aas-core-meta that referenced this issue Feb 15, 2024
@s-heppner
V3.1: Add Role value to Asset_kind enumeration
05d14a1 
A new enumeration value has been added to class `Asset_kind`, see
[aas-specs#294](admin-shell-io/aas-specs#294)

Fixes #302
@s-heppner s-heppner mentioned this issue Feb 15, 2024
Merged
s-heppner added a commit to aas-core-works/aas-core-meta that referenced this issue Feb 19, 2024
@s-heppner
V3.1: Add Role value to Asset_kind enumeration
ebd6931 
A new enumeration value has been added to class `Asset_kind`, see
[aas-specs#294](admin-shell-io/aas-specs#294)

Fixes #302
s-heppner added a commit to aas-core-works/aas-core-meta that referenced this issue Feb 19, 2024
@s-heppner
V3.1: Add Role value to Asset_kind enumeration
8b7fa18 
A new enumeration value has been added to class `Asset_kind`, see
[aas-specs#294](admin-shell-io/aas-specs#294)

Fixes #302
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted accepted in principle to be fixed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Projects
None yet
Milestone
V3.1
Development

Successfully merging a pull request may close this issue.

Resolve issues, focus specification/schemata admin-shell-io/aas-specs
2 participants
@BirgitBoss @JulianRahm