Browse Standards EIAIS108
Current STABILIZED 2016-06-15

CDIF - Transfer Format General Rules for Syntaxes and Encodings(STABILIZED Jul 2015) EIAIS108

The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories.
The standards which form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model.
The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards.
This document describes the way that CDIF meta-models are concretely represented during a transfer and the way that CDIF supports multiple exchange Syntaxes and Encodings. No specific exchange Syntaxes or Encodings are described in this document. EIA/IS-109 CDIF - Transfer Format - Syntax SYNTAX.1 and EIA/IS-110 CDIF - Transfer Format - Encoding ENCODING.1 describe one specific CDIF Syntax and one specific CDIF Encoding.
EIAIS108
2016-06-15
Latest
Stabilized

SAE MOBILUS

Subscribers can view annotate, and download all of SAE's content. Learn More »

Access SAE MOBILUS »

Members save up to 10% off list price.
Login to see discount.

Due to current capacity constraints, printed versions of our publications - including standards, technical papers, EDGE Reports, scholarly journal articles, books, and paint chips - may experience shipping delays of up to four to six weeks. We apologize for any inconvenience.

Get Involved

Want to participate in updating this standard?

X