-
Notifications
You must be signed in to change notification settings - Fork 26
Issues: admin-shell-io/aas-specs
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Clarification request regarding usage of SubmodelElementList and cardinality qualifiers
acknowledged
in work
#435
opened May 28, 2024 by
empwilli
Remove abstract Class HasKind and incorporate directly in class Subclass
requires workstream approval
strategic decision in spec team needed
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Relax Constraint AASD-120 for SMT allow idShort in SML
requires workstream approval
strategic decision in spec team needed
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
ECLASS RDF Representation
RDF
impact to RDF
requires workstream approval
strategic decision in spec team needed
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#422
opened Apr 26, 2024 by
VladimirAlexiev
Improve SHACL schema
bug
Something isn't working
RDF
impact to RDF
#421
opened Apr 23, 2024 by
VladimirAlexiev
8 tasks
Introduce ContainerElement as SubmodelElement interface
ready for approval
TF proposes how to resolve the issue. Needs final approval my Workstream
requires workstream approval
strategic decision in spec team needed
Handling of optional sets if elements in serializations
ready for approval
TF proposes how to resolve the issue. Needs final approval my Workstream
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Optional values for all SubmodelElements
ready for approval
TF proposes how to resolve the issue. Needs final approval my Workstream
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Cardinality > 1, distinguish between Map / Array
documentation
Improvements or additions to documentation
requires workstream approval
strategic decision in spec team needed
Do not change Value-Only type for Range: stay with number
ready for approval
TF proposes how to resolve the issue. Needs final approval my Workstream
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Revisit Events <<Experimental>>
requires workstream approval
strategic decision in spec team needed
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
What is the Value-Only of a List of Operations or Capabilities
requires workstream approval
strategic decision in spec team needed
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
add constraint: for Submodel with kind=Instance Property/value and MultiLanguageProperty shall be defined.
requires workstream approval
strategic decision in spec team needed
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Update infos for OPC UA and AML
documentation
Improvements or additions to documentation
requires workstream approval
strategic decision in spec team needed
Handle valueId and isCaseOf like semanticId
requires workstream approval
strategic decision in spec team needed
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
XSD datatype version mismatch
bug
Something isn't working
ready for approval
TF proposes how to resolve the issue. Needs final approval my Workstream
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
rename repository to aas-specs-metamodel
ready for approval
TF proposes how to resolve the issue. Needs final approval my Workstream
requires workstream approval
strategic decision in spec team needed
Proposal for MultiLanguageFile Support
requires workstream approval
strategic decision in spec team needed
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#392
opened Apr 5, 2024 by
alaettindogan
Clarify Handling of globalAssetId and specificAssetId (Constraint AASd-116)
accepted
accepted in principle to be fixed
documentation
Improvements or additions to documentation
ready for approval
TF proposes how to resolve the issue. Needs final approval my Workstream
[BUG] Reference/type is underspecified
documentation
Improvements or additions to documentation
requires workstream approval
strategic decision in spec team needed
Definition of Cardinality seems to be wrong (01001-3-0, p. 134)
bug
Something isn't working
documentation
Improvements or additions to documentation
[BUG] The spelling of ID-Short-Path should be uniform
accepted
accepted in principle to be fixed
bug
Something isn't working
documentation
Improvements or additions to documentation
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-04-30.