gunnar-mb

Datatypes 

IFEX -- VAFmodel

uint8    --  uint8_t
int8     --  int8_t
uint16   --  uint16_t
int16    --  int16_t
uint32   --  uint32_t
int32    --  int32_t

gunnar-mb

Current structure

├── docker
│   ├── <IFEX tools in a self-contained container format, for repeatable testing, or end-user use>
│   ├── Dockerfile, Makefile, README
├── docs
│   ├── MD-formatted documents, both templates (document structure) and some content
│   ├── README.md = when viewing docs directory in GitHub, the README is rendered
├── helpers
│   ├── <integrations to associated ecosystems and tools>

gunnar-mb

# Brainstorming Layer Types

# Example of E2E layer instance

TODO: - include a file defining list of profiles - how?  format?

namespaces:
  - name: this.a.b.c.mynamespace
  interface:

gunnar-mb

OpenAPI - IFEX, feature comparison and comments

• Introduction and Purpose

  • The purpose of analyzing other interface description formats and making a detailed comparison is:
    • Ensure interoperability with this technology so that the [[IFEX Principle]] can be fulfilled, and translate to/from this technology. This analysis is the first step of the [[Concept Mapping]] that is needed for implementing translators to/from any format.
    • Ensure general feature parity of IFEX compared to other approaches, picking up good ideas if something has been missed so far.
    • If anything is deliberately unsupported in IFEX, explain the rationale.
  • At this point we may proactively note that IFEX is not a simple "competitor" or "alternative". That is not the primary purpose of these comparisons. You may refer to for example the IFEX to Web Deployment using OpenAPI chapter for further understanding.

• Terminology

  • OAS = OpenAPI Specification
  • IFEX = Interface Exchange Framework. This typically