Ascii1000D has a few basic goals
-
Component Authoring with as Little As Possible
Everything should work with as few keystrokes as possible, as few licenses as possible, as little setup as possible. Technical Publications systems are not multi-million dollar integration projects.
-
S1000D Architecture
Filenames (data module codes), file relationships, data flows, all non-markup related architecture from S1000D is used in Ascii1000D. The exception to this is where it violates the above rule: for example, CGM illustrations can’t be implemented on an open architecture, so we adopt SVG instead.
-
Business System Agnostic
The system will function regardless of the type or number of different business systems that contain engineering data.
-
Engineering Data Sources
The system assumes that engineering data must be integrated using the following formats as interchange: 3MF and/or STEP; CSV for engineering parts data, and CSV for Logistics.
