PDF Price
$60.00
ADD TO CART
Other Languages and Specifics includes standards relating to programming languages and their particular uses sometimes within certain fields. The programming languages include Full BASIC, EDDL, Ada and more.
Establishes the syntax of BASIC programs written using individual character input, or modules, or both; the semantic rules for interpreting the meaning of a BASIC program that uses individual character input, or modules, or both; the errors and exceptional circumstances that shall be detected; and also the manner in which such errors and exceptional circumstances shall be handled.
New IEEE Standard - Active.Reaffirmed 2008. The form and meaning of programs written in the Scheme programming language, in particular, their syntax, the semantic rules for interpreting them, and the representation of data to be input or output by them, are specified. The fundamental ideas of the language and the notational conventions used for describing and writing programs in the language are presented. The syntax and semantics of expressions, programs, and definitions are specified. Scheme's built-in procedures, which include all of the language's data manipulation and input/output primitives, are described, and a formal syntax for Scheme written in extended Backus-Naur form is provided. Formal denotational semantics for Scheme and some issues in the implementation of Scheme's arithmetic are covered in the appendixes.
IEC 62714-1:2018 is a solution for data exchange focusing on the domain of automation engineering. The data exchange format defined in the IEC 62714 series (Automation Markup Language, AML) is an XML schema based data format and has been developed in order to support the data exchange in a heterogeneous engineering tools landscape. The goal of AML is to interconnect engineering tools in their different disciplines, e.g. mechanical plant engineering, electrical design, process engineering, process control engineering, HMI development, PLC programming, robot programming, etc. This second edition cancels and replaces the first edition published in 2014. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) use of CAEX 3.0 according to IEC 62424:2016
b) improved modelling of references to documents outside of the scope of the present standard,
c) modelling of references between CAEX attributes and items in external documents,
d) revised role libraries,
e) modified Port concept,
f) modelling of multilingual expressions,
g) modelling of structured attribute lists or array,
h) a new AML container format,
i) a new standard AML attribute library
IEC 62714-4:2020 specifies the integration of logic information as part of an AML model for the data exchange in a heterogenous engineering tool landscape of production systems.
This document specifies three types of logic information: sequencing, behaviour, and interlocking information.
This document deals with the six following sequencing and behaviour logic models (covering the different phases of the engineering process of production systems) and how they are integrated in AML: Gantt chart, activity-on-node network, timing diagram, Sequential Function Chart (SFC), Function Block Diagram (FBD), and mathematical expression.
This document specifies how to model Gantt chart, activity-on-node network, and timing diagram and how they are stored in Intermediate Modelling Layer (IML).
This document specifies how interlocking information is modelled (as interlocking source and target groups) in AML. The interlocking logic model is stored in Function Block Diagram (FBD).
This document specifies the AML logic XML schema that stores the logic models by using IEC 61131-10.
This document specifies how to reference PLC programs stored in PLCopen XML documents.
This document does not define details of the data exchange procedure or implementation requirements for the import/export tools.
This standard is part of the POSIX series of standards. It defines an application program interface for controlling device drivers. Although it is based on the widely used ioctl() system call, the interface is type-safe and has a fixed number of parameters.
IEEE Std 1450-1999, which specifies the Standard Test Interface Language (STIL), is extended by this standard to provide an interface between test generation tools and test equipment with regard to the specification of the flow of execution of test program components. It defines structures so that test flows, sub-flows, and binning may be described in a manner that facilitates automated generation, modification, and/or manual maintenance and, although not yet a complete run-time test language, execution on automated test equipment (ATE). It also defines an interface between tester configurations (described by IEEE Std 1450-1999 and IEEE Std 1450.2-2002) and test program components. It also defines a hierarchy of flows, sub-flows, and test components as well as structures for defining flow-related variables and processing expressions involving those variables. It provides structures that support automatic test program generation (ATPRG) and translation and that support running it natively as an ATE programming language. As an adjunct, IEEE Std 1450.3-2007 may be used by ATPRG for tester rules checking.
The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.
A new specification language, named Fuzzy Markup Language (FML), is presented in this standard, exploiting the benefits offered by eXtensible Markup Language (XML) specifications and related tools in order to model a fuzzy logic system in a human-readable and hardware independent way. Therefore, designers of industrial fuzzy systems are provided with a unified and high-level methodology for describing interoperable fuzzy systems. The W3C XML Schema definition language is used by this standard to define the syntax and semantics of the FML programs.
This standard is part of the POSIX series of standards for applications and userinterfaces to open systems. It defines the Ada language bindings as package specificationsand accompanying textual descriptions of the application program interface (API).
This International Standard specifies the semantics and syntax of DXL. DXL is a language for exchanging tree-structured charts among CASE tools.
DXL is applicable to:
This International Standard does not specify:
ISO/IEC 18023-1:2005 addresses the concepts, syntax and semantics for the representation and interchange of environmental data. It specifies:
ISO/IEC 18023-1:2005 also specifies topological, rule-based, and other constraints that ensure appropriate data can be available for applications that rely on automatically generated behaviours when interacting with environmental data.
ISO/IEC 18024-4:2006 specifies a language-dependent layer for the C programming language.
ISO/IEC 18023-1 specifies a language-independent application program interface (API) for SEDRIS. For integration into a programming language, the SEDRIS API is embedded in a language-dependent layer obeying the particular conventions of that language.
**This document has been packaged as a zipped file. The zip file contains a Readme file and it is essential to consult this file to understand the way in which the document has been structured.
ISO/IEC 19501:2004 describes the Unified Modeling Language (UML), a graphical language for visualizing, specifying, constructing and documenting the artifacts of a software-intensive system. The UML offers a standard way to write a system's blueprints, including conceptual things such as business processes and system functions, as well as concrete things such as programming language statements, database schemas, and reusable software components.
This International Standard specifies the OMG Interface Definition Language (IDL). IDL is a descriptive language used to define data types and interfaces in a way that is independent of the programming language or operating system/processor platform.
The IDL specifies only the syntax used to define the data types and interfaces. It is normally used in connection with other standards that further define how these types/interfaces are utilized in specific contexts and platforms:
? Separate "language mapping" standards define how the IDL-defined constructs map to specific programming languages, such as, C/C++, Java, C#, etc.
? Separate "serialization" standards define how data objects and method invocations are serialized into a format suitable for network transmission.
? Separate "middleware" standards, such as, DDS or CORBA leverage the IDL to define data-types, services, and interfaces.
The description of IDL grammar uses a syntax notation that is similar to Extended Backus-Naur Format (EBNF).
This standard defines a set of system application program interfaces to operating system services. These interfaces provide access via the Ada programming language to the same operating system services for which C-language interfaces are specified in ISO/IEC 9945-1:1996 {2} 1)2)and IEEE P1003.1g {B14}.
The purpose of this standard is to support application portability at the Ada source code level. This standard is intended to be used by both application developers and system implementors.
This standard is intended to be compatible with implementations of the 1995 revision to the Ada language standard (ISO/IEC 8652:1995 {1}). Fall-back approaches compatible with implementations of the original Ada language standard (ISO/IEC 8652:1987 {B5}) are also provided (see 1.3).
This standard is intended to contain no specifications that conflict with “Year 2000” requirements.
This standard comprises three major components:
The following areas are outside the scope of this standard:
When the XTI Detailed Network Interface option and/or the Sockets Detailed Network Interface option are supported, then a set of DNI's (see 2.2.3.26) are also within the scope of this standard. A DNI is intended to provide access to protocol-specific features of the underlying network for highly portable applications that need access to sophisticated network features. The DNI's are based on the SPG4 XTI and 4.4 BSD socket specifications.
The following areas are outside of the scope of the DNI's:
This standard describes the external characteristics and facilities that are of importance to applications developers, rather than the implementation approaches that may be employed to achieve them. Special emphasis is placed on those facilities and capabilities needed for the broad spectrum of applications.
This standard has been defined exclusively at the source code level. The objective is that a Strictly Conforming POSIX.5 Application can be compiled to execute on any conforming implementation, within the portability of the application Ada code itself.
1) Plain numbers in curly braces correspond to those of the normative references in 1.2. Numbers preceded by a “B” in curly braces correspond to those of the bibliography in Annex A. See 2.1 for the description of this and the other typographical conventions followed in this document.
2) A language-independent definitions of this standard was once under development, but work on that project was suspended.
IEC 61131-3:2013 specifies the syntax and semantics of a unified suite of programming languages for programmable controllers (PCs). This suite consists of two textual languages, Instruction List (IL) and Structured Text (ST), and two graphical languages, Ladder Diagram (LD) and Function Block Diagram (FBD). This third edition cancels and replaces the second edition, published in 2003 and constitutes a technical revision. It includes the following significant technical changes: It is a compatible extension of the second edition. The main extensions are new data types and conversion functions, references, name spaces and the object oriented features of classes and function blocks.
IEC 61636-1:2021 (E) provides the definition of an exchange format, utilizing XML, for exchanging data resulting from executing tests of a unit under test (UUT) via a test program in an automatic test environment. This standard is published as a double logo IEC-IEEE standard.
This part of ISO/IEC 13719 defines the binding of the Portable Common Tool Environment (PCTE), as specified in ISO/IEC 13719-1, to the C programming language.
A number of features are not completely defined in ISO/IEC 13719-1, some freedom being allowed to the implementor. Some of these features are specified as implementation limits. Some constraints are placed on these implementation limits by this part of ISO/IEC 13719. These constraints are specified in clause 24, Implementation Limits.
PCTE is an interface to a set of facilities that forms the basis for constructing environments supporting systems engineering projects. These facilities are designed particularly to provide an infrastructure for programs which may be part of such environments. Such programs, which are used as aids to system development, are often referred to as tools.
This part of ISO/IEC 13719 defines the binding of the Portable Common Tool Environment (PCTE) interfaces, as specified in ISO/IEC 13719-1, to the Ada programming language.
A number of features are not completely defined in ISO/IEC 13719-1, some freedom being allowed to the implementor. Some of these features are specified as implementation limits. Some constraints are placed on these implementation limits by this part of ISO/IEC 13719. These constraints are specified in clause 24.
PCTE is an interface to a set of facilities that forms the basis for constructing environments supporting systems engineering projects. These facilities are designed particularly to provide an infrastructure for programs which may be part of such environments. Such programs, which are used as aids to system development, are often referred to as tools.
This part of ISO/IEC 13719 defines the standard binding of the Portable Common Tool Environment (PCTE), as specified in ISO/IEC 13719-1, to the CORBA Interface Definition Language (IDL) defined in ISO/IEC CD 14750.
A number of features are not completely defined in ISO/IEC 13719-1, some freedom being allowed to the implementer. Some of these features are specified as implementation limits. Some constraints are placed on these implementation limits by this IDL Binding Standard. These constraints are specified in clause 24, Implementation Limits.
PCTE is an interface to a set of facilities that forms the basis for constructing environments supporting systems engineering projects. These facilities are designed particularly to provide an infrastructure for programs which may be part of such environments. Such programs, which are used as aids to systems development, are often referred to as tools.
The 1671 bundle supports the development of Test Program Sets (TPSs) that will be used in an automatic test environment. It specifies an exchange format, utilizing XML, for identifying all of the hardware, software and documentation associated with a unit under test (UUT). It contains downloadable .xsd files from http://standards.ieee.org/downloads/1671/. This UUT may be tested and diagnosed using a test program set (TPS) on an automatic test system (ATS). This test station may be used as a component of a test program set to test and diagnose a unit under test. This bundle consists of IEEE 1671-2010, IEEE 1671.1-2017, IEEE 1671.2-2012, IEEE 1671.3-2017, IEEE 1671.4-2014, IEEE 1671.5-2015, IEEE 1671.6-2015.
An exchange format using extensible markup language (XML) for identifying all of the hardware, software, and documentation associated with a test adapter is specified in this document. This test adapter may be used as a component of a test program set to test and diagnose a unit under test.
An exchange format, using extensible markup language (XML), for identifying all of the hardware, software, and documentation associated with a test station is specified in this document. This test station may be used with a test program set to test and diagnose a unit under test.