Tobias Langer

Results 10 issues of Tobias Langer

With org-ref version 3.0 (according to the version statement in org-ref.el) I experience slowdowns on typing to the point of unusability, when I have more than just a few acronyms...

With the introduction of AAS spec v3.0 the additional SubmodelElementList type was introduced, that covers most, if all, cases of collection types. To my understanding, this introduces some ambiguity with...

transfer
acknowledged

Affected version: 9.0.4. OS: Linux Minimal example: ``` omnect-cli dep 0.0.2 ``` Exception: ``` org.cyclonedx.exception.ParseException: com.fasterxml.jackson.databind.JsonMappingException: Cannot deserialize value of type `java.util.ArrayList` from Object value (token `JsonToken.START_OBJECT`) at [Source: UNKNOWN;...

bug

[As of now](https://github.com/CycloneDX/cyclonedx-rust-cargo/blob/7596551f4caeb368e500c501b5a28f80d5347aa0/cargo-cyclonedx/src/generator.rs#L251-L252), cargo-cyclonedx explicitly creates sub-components for the component entry in the metadata for the respective compilation targets. This appears to contradict with the suggestions in the [Authoritative Guide...

I hope this is the right place for a suggestion like this. If not, please forward me. **Is your feature request related to a problem? Please describe.** The qualifiers `SMT/AllowedIdShort`...

According to meta model, submodel element lists may have a value = null, as value has a cardinality of 0..* (https://industrialdigitaltwin.io/aas-specifications/IDTA-01001/v3.1/spec-metamodel/submodel-elements.html#submodel-element-list-attributes) and the spec additionally forbids e.g. [empty json lists](https://github.com/admin-shell-io/aas-specs-metamodel/blob/0be69759372d8cd50f98850f9cc9ea8ce200455d/documentation/IDTA-01001/modules/ROOT/pages/mappings/formats/json.adoc)....

requires workstream approval

## **Is your feature request related to a problem? Please describe.** `ReferenceElement` currently behaves like an untyped pointer: it may reference *any* `Referable`, without any machine-readable indication of what type...

requires workstream approval

In [Format "Value" (Value-Only Serialization) in JSON ](https://industrialdigitaltwin.io/aas-specifications/IDTA-01001/v3.1.1/mappings/mappings.html#json-schema-value-only) it says: > SubmodelElements without a value are not serialized. Further below in the section about Ranges, it details more specifically: >...

requires workstream approval

In the bugfix release Digital Nameplate 3.0.1 (see [issue #123](https://github.com/admin-shell-io/submodel-templates/issues/123)), the semantic ID of a submodel element was modified. This change raises the question of how submodel instances remain valid...

**Describe the bug** The links to the RDF, XML, and JSON schemata descriptions are broken and lead to 404 pages. **Where** - https://github.com/admin-shell-io/aas-specs-metamodel/tree/master/schemas/rdf - https://github.com/admin-shell-io/aas-specs-metamodel/tree/master/schemas/json - https://github.com/admin-shell-io/aas-specs-metamodel/tree/master/schemas/xml

bug