Labels

impact on aas-core but not on specification

accepted as proposed by the Workstream AAS Specifications

problem noted but solution differs from original proposal

in work

Something isn't working

Improvements or additions to documentation

This issue or pull request already exists. Typically closed with reference to the other issue.

New feature or request

Good for newcomers

Extra attention is needed

This doesn't seem right

impact on JSON schema only (not on specification)

not backward comptible, would require a major release

requirement accepted, solution open

postponed, no decision which version it will be contained in

not content related but related to process

Further information is requested

impact on RDF (not on specification)

TF proposes how to resolve the issue. Needs final approval my Workstream

strategic decision proposal needs to be prepared in TF spec team

generated schemata for xml, JSON and rdf or XMI

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

issue refers to other part of specification or other and will be transfered

Issues related to the schemas for V3RC02