Search results

Inconsistent Length Restrictions for File/value and FileValue/value

bugSomething isn't workingSomething isn't working

Status: Open.

#540 In admin-shell-io/aas-specs;

· sebbader-sap opened on Mar 14, 2025

 ·  

V3.1

Clarification Request: can a derived submodel template redefine the semantic id of the "parent" template?

questionFurther information is requestedFurther information is requested

Status: Open.

#535 In admin-shell-io/aas-specs;

· DenisBiondic opened on Mar 6, 2025

Enhancing Property Requiredness: Introducing a "Recommended" Option

requires workstream approvalstrategic decision proposal needs to be prepared in TF spec teamstrategic decision proposal needs to be prepared in TF spec team

Status: Open.

#525 In admin-shell-io/aas-specs;

· Philipp-Liedl opened on Feb 13, 2025

CanonicalAAS: Define Ordering Rules and Canonical Representation for AAS

requires workstream approvalstrategic decision proposal needs to be prepared in TF spec teamstrategic decision proposal needs to be prepared in TF spec team

specificationimpact on specification and thus on xml, json etc., label "aas-core" not set additinallyimpact on specification and thus on xml, json etc., label "aas-core" not set additinally

Status: Open.

#521 In admin-shell-io/aas-specs;

· mhrimaz opened on Jan 17, 2025

Remove AASd-006

documentationImprovements or additions to documentationImprovements or additions to documentation

requires workstream approvalstrategic decision proposal needs to be prepared in TF spec teamstrategic decision proposal needs to be prepared in TF spec team

Status: Open.

#515 In admin-shell-io/aas-specs;

· BirgitBoss opened on Dec 15, 2024

use idShort instead of index in idShortPath for elements of SML

requires workstream approvalstrategic decision proposal needs to be prepared in TF spec teamstrategic decision proposal needs to be prepared in TF spec team

specificationimpact on specification and thus on xml, json etc., label "aas-core" not set additinallyimpact on specification and thus on xml, json etc., label "aas-core" not set additinally

Status: Open.

#507 In admin-shell-io/aas-specs;

· BirgitBoss opened on Dec 15, 2024

 ·  

V3.x

Preserve AAS-/SM-Id of original AAS/SM after cross enterprise AAS-/SM-transfer with modification of Ids

postponed for next version(s)

requires workstream approvalstrategic decision proposal needs to be prepared in TF spec teamstrategic decision proposal needs to be prepared in TF spec team

specificationimpact on specification and thus on xml, json etc., label "aas-core" not set additinallyimpact on specification and thus on xml, json etc., label "aas-core" not set additinally

Status: Open.

#497 In admin-shell-io/aas-specs;

· HeinrichChristian opened on Dec 10, 2024

[BUG] Reference to the not existing Complete_Example.ttl

acceptedaccepted as proposedaccepted as proposed

Status: Open.

#489 In admin-shell-io/aas-specs;

· zrgt opened on Nov 28, 2024

Clarify Handling of IRDI pathes

postponed for next version(s)

Status: Open.

#487 In admin-shell-io/aas-specs;

· BirgitBoss opened on Nov 27, 2024

AdministrativeInformation: add createdAt and updatedAt attributes

ready for approvalTF proposes how to resolve the issue. Needs final approval my WorkstreamTF proposes how to resolve the issue. Needs final approval my Workstream

specificationimpact on specification and thus on xml, json etc., label "aas-core" not set additinallyimpact on specification and thus on xml, json etc., label "aas-core" not set additinally

Status: Open.

#484 In admin-shell-io/aas-specs;

· BirgitBoss opened on Nov 15, 2024

 ·  

V3.x

AssetKind: add Batch besides Type and Instance?

ready for approvalTF proposes how to resolve the issue. Needs final approval my WorkstreamTF proposes how to resolve the issue. Needs final approval my Workstream

specificationimpact on specification and thus on xml, json etc., label "aas-core" not set additinallyimpact on specification and thus on xml, json etc., label "aas-core" not set additinally

Status: Open.

#483 In admin-shell-io/aas-specs;

· BirgitBoss opened on Nov 15, 2024

 ·  

V3.x

[BUG] Do not use keywords in the meta-model

bugSomething isn't workingSomething isn't working

specificationimpact on specification and thus on xml, json etc., label "aas-core" not set additinallyimpact on specification and thus on xml, json etc., label "aas-core" not set additinally

Status: Open.

#468 In admin-shell-io/aas-specs;

· mristin opened on Sep 12, 2024

 ·  

V4.x