Kevux Systems and Software - Documentation
Author: Kevin Day
Description: Documentation of numerous Kevux Systems projects and software.
Keywords: Featureless, FLL, Kevin Day, Kevux, Linux, Library, Make, Fake, Controller, UTF-8, Open-Source, Documentation

# Documentation

## Projects

Documentation for the following projects are provided within their own sub-pages.

Byte Dump
Control
Controller
Featureless Make
Firewall
FSS Identify
FSS Basic Read
FSS Basic Write
FSS Basic List Read
FSS Basic List Write
FSS Embedded List Read
FSS Embedded List Write
FSS Extended Read
FSS Extended Write
FSS Extended List Read
FSS Extended List Write
FSS Payload Read
FSS Payload Write
FSS Status Code
Status Code
IKI Read
IKI Write
UTF8

## Specifications

Projects like the Featureless Linux Library are focused entirely around provided standards for every aspect of the project. Numerous specifications are available describing these standards. At this time, the specifications have not been transcribed into a format for the web. They are stored in plain text within the source code repositories.

Many of these specifications may be found here:

- https://sourceforge.net/p/fll/git/ci/development/tree/specifications/
- https://sourceforge.net/p/fll/git/ci/development/tree/level_3/control/specifications/
- https://sourceforge.net/p/fll/git/ci/development/tree/level_3/controller/specifications/
- https://sourceforge.net/p/fll/git/ci/development/tree/level_3/fake/specifications/
- https://sourceforge.net/p/fll/git/ci/development/tree/level_3/utf8/specifications/

## APIs

The APIs have not yet been generated and are not available in an easy to consume form outside of the source code itself.

The API can be viewed by navigating the source code for the FLL here:

- https://sourceforge.net/p/fll/git/ci/development/tree/

## Terminology

One of the biggest problems with an API is the misuse or misunderstanding of the meaning and purpose of one. The term itself is not the most accurate and is also not ideal. A more appropriate term would be a Library Interface or a Software Interface.

### Standard

A set of rules and guidelines.

### Specification

A specific interpretation, clarification, or description of a Standard, such as the documentation that describes how to use or follow a Standard.

### Implementation

The applying of some Standard or Specification.

### Application Programming Interface (API)

The API term is commonly mis-represented as Services or Protocols (such as "Web API"). An API instructs a programmer how to use a dependency when programming some software that utilizes said dependency. An API is a Specification of some Implementation of a Standard be it a formally defined standard or an informally defined standard. An API may be an Implementation of a Standard or a part of an Implementation of a Standard. An API is, in effect, documentation.

### Application Binary Interface (ABI)

The ABI term refers to an Application Binary Interface and represents the compiled implementation of some API. An ABI may not always exist for some API, such as for pure scripting languages. An ABI is neither a Specification nor a Standard. An ABI is an Implementation of an API making it an Implementation of a Standard or Specification.

### Service

Any action or labor performed by one party for another party (such as one person helping another person).

### Protocol

In the context of computers and software, this is a Standard focused on communication between two parties (often referring to Internet communication).