Classification
| Name |
Package
|
| Short Description |
Folder which contain OTX documents
|
| Class |
OTX Core
|
| Pre-Conditions |
-
|
| Specified by |
ISO 13209-2
|
Introduction
OTX documents can be stored in a file system or in a database. If stored in a file system, certain constraints on the organisation of files and folders allow a simple implementation to find OTX documents easily. The package name (in dotted notation) can simply be translated into a directory path or vice versa, whereas the OTX document name can be translated directly to the file name. It is an analogy to the file system organisation of packages and classes recommended the Java Language Specification.
| Java |
C# |
OTX |
File System
|
| Package |
Namespace |
Package |
Folder
|
| Document |
Document |
Document |
File
|
| Class |
Class |
document name |
File content
|
| Analogies between Java, C # and OTX
|
|
|
|
|
Important: OTX documents are unambiguously identified with the combination of package name and their own name. This allows for having equal document names in different OTX packages and avoiding ambiguity.
|
|
|
|
|
Important: Global entities (global constants, procedures, validities, etc.) contained in the OTX document are unambiguously identified with the combination of package- and document-name, and their name. This allows for having equal global names in different OTX files and avoiding ambiguity.
|
|
|
|
|
Important: Due to the fact that the package name of an document shall not be empty, a so called Root-Package (root folder) shall be exist.
|
|
| Package/Document Structure of OTX stored in a file system (package name: Bold, document name: Italic)
|
Semantics
No semantics available.
Checker rules
See also
Naming Conventions
OTX Documents
Imports
