35.060 - Languages used in information technology
ICS 35.060 Details
Languages used in information technology
Programmiersprachen
Langages utilisés dans les technologies de l'information
Jeziki, ki se uporabljajo v informacijski tehniki in tehnologiji
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.060 - Languages used in information technology
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document describes a JavaScript Object Notation (JSON) data model format and a Representational State Transfer (RESTful) Web Service Application Programming Interface (API) for communication between Activities experienced by an individual, group, or other entity and a Learning Record Store (LRS). The LRS is a system that exposes the xAPI RESTful Web Service API for the purpose of tracking and accessing experiential data, especially in learning and human performance.
- Standard109 pagesEnglish languagesale 15% off
The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [8]) to TTCN-3 as defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.
- Standard161 pagesEnglish languagesale 15% off
- Standard161 pagesEnglish languagesale 15% off
- Standardization document161 pagesEnglish languagesale 10% offe-Library read for1 day
The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA ® based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2]) defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the scope of the present document.
- Standard396 pagesEnglish languagesale 15% off
- Standard396 pagesEnglish languagesale 15% off
- Standardization document396 pagesEnglish languagesale 10% offe-Library read for1 day
Within the context of training data for Earth Observation (EO) Artificial Intelligence Machine Learning (AI/ML), this document specifies a conceptual model that:
— establishes a UML model with a target of maximizing the interoperability and usability of EO imagery training data;
— specifies different AI/ML tasks and labels in EO in terms of supervised learning, including scene level, object level and pixel level tasks;
— describes the permanent identifier, version, licence, training data size, measurement or imagery used for annotation;
— specifies a description of quality (e.g. training data errors, training data representativeness, quality measures) and provenance (e.g. agents who perform the labelling, labelling procedure).
- Standard57 pagesEnglish languagesale 10% offe-Library read for1 day
The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines types for behaviour definitions in TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages and guidelines for this package in combination with other packages is outside the scope of the present document
- Standard44 pagesEnglish languagesale 15% off
- Standard44 pagesEnglish languagesale 15% off
- Standardization document44 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the abstract syntax of the Test Description Language (TDL) in the form of a meta-model based on the OMG ® Meta Object Facility™ (MOF) [1]. It also specifies the semantics of the individual elements of the TDL meta-model. The intended use of the present document is to serve as the basis for the development of TDL concrete syntaxes aimed at TDL users and to enable TDL tools such as documentation generators, specification analysers and code generators.
The specification of concrete syntaxes for TDL is outside the scope of the present document. However, for illustrative purposes, an example of a possible textual syntax together with its application on some existing ETSI test descriptions are provided.
NOTE: OMG®, UML ®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named
- Standard108 pagesEnglish languagesale 15% off
- Standard108 pagesEnglish languagesale 15% off
- Standardization document108 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the architecture for the execution environment of TDL test descriptions and functional requirements for the components in the form of function declarations that will be provided by an implementation of the components and data types used as input and output parameters of the functions. The test executor component will interpret the elements of test descriptions according to operational semantics specified in [1]. The present document will be used for developing a code generator or interpreter for mapping abstract TDL constructs to code and the required test environment components that are specific to a chosen test execution platform.
- Standard23 pagesEnglish languagesale 15% off
- Standard23 pagesEnglish languagesale 15% off
- Standardization document23 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the concrete textual syntax of the Test Description Language (TDL). The intended use of the present document is to serve as the basis for the development of textual TDL tools and TDL specifications. The meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
NOTE: OMG®, UML ® and OCL™ are the trademarks of Object Management Group (OMG). Xtext™ is
trademark of the Eclipse ® Foundation. This information is given for the convenience of users of the present document and does not constitute an endorsement by ETSI of the products named.
- Standard67 pagesEnglish languagesale 15% off
- Standard67 pagesEnglish languagesale 15% off
- Standardization document67 pagesEnglish languagesale 10% offe-Library read for1 day
- Standardization document67 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 61967-7:2025 defines SystemC® with Transaction Level Modeling (TLM) as an ISO standard C++ class library for system and hardware design. SystemC®1 as an ANSI standard C++ class library for system and hardware design.
The general purpose of this standard is to provide a C++-based standard for designers and architects who need to address complex systems that are a hybrid between hardware and software. The specific purpose of this standard is to provide a precise and complete definition of the SystemC class library including a TLM library so that a SystemC implementation can be developed with reference to this standard alone. This standard is not intended to serve as a user’s guide or to provide an introduction to SystemC, but it does contain useful information for end users.
The changes with respect to the previous edition are provided in Annex D.
This standard is published as a double logo IEC-IEEE standard.
- Standard618 pagesEnglish languagesale 15% off
This document promotes the applicability and portability of Prolog grammar rules in data processing systems that support standard Prolog as defined in ISO/IEC 13211–1:1995/Cor 1:2007/Cor 2:2012/Cor 3:2017 and ISO/IEC 13211–2:2000. This document specifies: a) The representation, syntax, and constraints of Prolog grammar rules b) A logical expansion of grammar rules into Prolog clauses c) A set of built-in predicates for parsing with grammar rules
- Technical specification18 pagesEnglish languagesale 15% off
This document specifies the form and establishes the interpretation of programs written in the C programming language. It is not a complete specification of that language but builds upon ISO/IEC 9899:2018 by constraining and clarifying the Memory Object Model.
- Technical specification23 pagesEnglish languagesale 15% off
This document specifies extensions to programming language C to include functions corresponding to operations specified and recommended in ISO/IEC 60559, but not supported in ISO/IEC 9899:2024 (also referred to as C23).
- Technical specification13 pagesEnglish languagesale 15% off
This document specifies extensions to programming language C to include pragmas corresponding to attributes specified and recommended in ISO/IEC 60559 but not supported in ISO/IEC 9899:2024 (also referred to as C23).
- Technical specification20 pagesEnglish languagesale 15% off
This document provides a possible instantiation of the registry metamodel specified in ISO/IEC 11179-3, ISO/IEC 11179-31, ISO/IEC 11179-32 using the SQL database language as specified in ISO/IEC 9075-2.
- Technical report44 pagesEnglish languagesale 15% off
This document provides guidance on the use of the Ravenscar profile for concurrent Ada software intended for verification up to, and including, the very highest levels of integrity. To this end, this document provides a complete description of the motivations behind the Ravenscar profile, to show how conformant programs can be analysed, and to give examples of usage. This document is aimed at a broad audience, including application programmers, implementers of run-time systems, those responsible for defining company or project guidelines, and academics. Familiarity with the Ada language is assumed.
- Technical specification52 pagesEnglish languagesale 15% off
This document builds upon ISO/IEC 14882 by describing requirements for implementations of an interface that computer programs written in the C++ programming language could use to invoke algorithms with concurrent execution. The algorithms described by this document are realizable across a broad class of computer architectures. This document is written as a set of differences from the base standard. Some of the functionality described by this document might be considered for standardization in a future version of C++, but it is not currently part of ISO/IEC 14882:2020. Some of the functionality in this document might never be standardized, and other functionality might be standardized in a substantially different form. The goal of this document is to build widespread existing practice for concurrency in the ISO/IEC 14882:2020 algorithms library. It gives advice on extensions to those vendors who wish to provide them.
- Technical specification19 pagesEnglish languagesale 15% off
The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.
- Standard395 pagesEnglish languagesale 15% off
- Standard395 pagesEnglish languagesale 15% off
- Standardization document395 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the form and establishes the interpretation of programs written in the C programming language. It is designed to promote the portability of C programs among a variety of data-processing systems. It is intended for use by implementers and programmers. It specifies: — the representation of C programs; — the syntax and constraints of the C language; — the semantic rules for interpreting C programs; — the representation of input data to be processed by C programs; — the representation of output data produced by C programs; — the restrictions and limits imposed by a conforming implementation of C. This document does not specify: — the mechanism by which C programs are transformed for use by a data-processing system; — the mechanism by which C programs are invoked for use by a data-processing system; — the mechanism by which input data are transformed for use by a C program; — the mechanism by which output data are transformed after being produced by a C program; — the size or complexity of a program and its data that will exceed the capacity of any specific data-processing system or the capacity of a particular processor; — all minimal requirements of a data-processing system that is capable of supporting a conforming implementation. Annex J gives an overview of portability issues that a C program can encounter.
- Standard758 pagesEnglish languagesale 15% off
This document enumerates approaches and techniques to avoid software programming language vulnerabilities in the development of systems where assured behaviour is required for security, safety, mission-critical and business-critical software. In general, the description of the vulnerabilities and description of avoidance mechanisms are applicable to the software developed, reviewed, or maintained for any application. Vulnerabilities are described in a generic manner that is applicable to a broad range of programming languages.
- Standard153 pagesEnglish languagesale 15% off
This document specifies requirements for implementations of the C++ programming language. The first such requirement is that they implement the language, so this document also defines C++. Other requirements and relaxations of the first requirement appear at various places within this document. C++ is a general purpose programming language based on the C programming language as described in ISO/IEC 9899:2018 Programming languages — C (hereinafter referred to as the C standard). C++ provides many facilities beyond those provided by C, including additional data types, classes, templates, exceptions, namespaces, operator overloading, function name overloading, references, free store management operators, and additional library facilities.
- Standard2104 pagesEnglish languagesale 15% off
This document describes the model of database language SQL as defined in ISO/IEC 9075-1, ISO/IEC 9075-2, and ISO/IEC 9075-11. The meanings of and the relationships between various concepts of that model are described in text and illustrated graphically. Background in the form of some historical review and a brief overview of key SQL features is included. NOTE 2 — In spite of the fact that the names of the ISO/IEC 9075 series of standards contain the phrase “database language”, the standards do not use the word “database” to describe the thing that SQL creates and on which it operates. The word “database” is used in many different contexts and has meanings wholly unrelated to the intent of the ISO/IEC 9075 series. Consequently, a variety of other terms are defined and used by the ISO/IEC 9075 series. The word “database” is frequently used in this document informally to mean “a collection of data managed by an SQL-implementation at any given time.”
- Standard58 pagesEnglish languagesale 15% off
This document describes extensions to the C++ Standard Library (2). These extensions are classes and functions that are likely to be used widely within a program and/or on the interface boundaries between libraries written by different organizations. It is intended that some of the library components be considered for standardization in a future version of C++. At present, they are not part of any C++ standard. The goal of this document is to build more widespread existing practice for an expanded C++ standard library. It gives advice on extensions to those vendors who wish to provide them.
- Technical specification54 pagesEnglish languagesale 15% off
IEC 62529:2024 provides the means to define and describe signals used in testing. It provides a set of common basic signal definitions, built upon formal mathematical specifications, so that signals can be combined to form complex signals usable across all test platforms. The standard provides support for structural textual languages and programming language interfaces for interoperability. This second edition cancels and replaces the first edition, published in 2007, and constitutes a technical revision.
- Standard352 pagesEnglish languagesale 15% off
This document defines data structures and basic operations on property graphs. It provides capabilities for creating, accessing, querying, maintaining, and controlling property graphs and the data they comprise. This document specifies the syntax and semantics of a data management language for specifying and modifying the structure of property graphs and collections thereof. This document provides a vehicle for portability of data definitions and manipulation among GQL-implementations. Implementations of this document can exist in environments that also support application programming languages, end-user query facilities, and various tools for database design, data administration, and performance optimization.
- Standard610 pagesEnglish languagesale 15% off
- Standard206 pagesEnglish languagesale 15% off
IEC 61523-4:2023 defines the syntax and semantics of a format used to express power intent in energy-aware electronic system design. Power intent includes the concepts and information required for specification and validation, implementation and verification, and modeling and analysis of power-managed electronic systems. This standard also defines the relationship between the power intent captured in this format and design intent captured via other formats (e.g., standard hardware description languages and cell libraries). This is an IEC/IEEE dual logo standard.
- Standard10 pagesEnglish languagesale 15% off
The present document specifies the concrete textual syntax of the Test Description Language (TDL). The intended use
of the present document is to serve as the basis for the development of textual TDL tools and TDL specifications. The
meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
NOTE: OMG®, UML® and OCL™ are the trademarks of Object Management Group (OMG). Xtext™ is
trademark of the Eclipse® Foundation. This information is given for the convenience of users of the
present document and does not constitute an endorsement by ETSI of the products named.
- Standard66 pagesEnglish languagesale 15% off
- Standard66 pagesEnglish languagesale 15% off
- Standardization document66 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the abstract syntax of the Test Description Language (TDL) in the form of a
meta-model based on the OMG® Meta Object Facility™ (MOF) [1]. It also specifies the semantics of the individual
elements of the TDL meta-model. The intended use of the present document is to serve as the basis for the development
of TDL concrete syntaxes aimed at TDL users and to enable TDL tools such as documentation generators, specification
analysers and code generators.
The specification of concrete syntaxes for TDL is outside the scope of the present document. However, for illustrative
purposes, an example of a possible textual syntax together with its application on some existing ETSI test descriptions
are provided.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.
- Standard118 pagesEnglish languagesale 15% off
- Standard118 pagesEnglish languagesale 15% off
- Standardization document118 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard674 pagesEnglish languagesale 15% off
IEC 63504-2804:2023 defines an architecture description standard from the software design perspective - this provides a common interface that abstracts the hardware properties that are critical to enable multicore tools. The standard includes performance estimation accuracy for complex processors like Very Long Instruction Word (VLIW) core and complex contention scenarios, description of caches to include uncached memory regions and caches for subsets of memories, properties for coarse power consumption estimation, and reusability by separating eXtensible Markup Language (XML) files for processor description and other memory/communication-related information. This is an IEC/IEEE dual logo standard.
- Standard83 pagesEnglish languagesale 15% off
IEC 63501-2416:2023 describes a parameterized and abstracted power model enabling system, software, and hardware intellectual property (IP)-centric power analysis and optimization. It defines concepts for the development of parameterized, accurate, efficient, and complete power models for systems and hardware IP blocks usable for system power analysis and optimization. These concepts include, but are not limited to, process, voltage, and temperature (PVT) independence; power and thermal management interface; and workload and architecture parameterization. This standard also defines the necessary requirements for the information content of parameterized, accurate, efficient, and complete power models to help guide development and usage of other related power, workload, and functional modeling standards. This standard is published as a double logo IEC-IEEE standard.
- Standard62 pagesEnglish languagesale 15% off
IEC 61523-4:2023 defines the syntax and semantics of a format used to express power intent in energy-aware electronic system design. Power intent includes the concepts and information required for specification and validation, implementation and verification, and modeling and analysis of power-managed electronic systems. This standard also defines the relationship between the power intent captured in this format and design intent captured via other formats (e.g., standard hardware description languages and cell libraries). This is an IEC/IEEE dual logo standard.
The contents of the corrigendum 1 (2024-02) have been included in this copy.
- Standard547 pagesEnglish languagesale 15% off
IEC 62530-2:2023 establishes the Universal Verification Methodology (UVM), a set of application programming interfaces (APIs) that defines a base class library (BCL) definition used to develop modular, scalable, and reusable components for functional verification environments. The APIs and BCL are based on the IEEE standard for SystemVerilog, IEEE Std 1800™.1. This is an IEC/IEEE dual logo standard.
- Standard457 pagesEnglish languagesale 15% off
IEC 63055:2023 defines a common interoperable format that will be used for the design of a) large-scale integration (LSI), b) packages for such LSI, and c) printed circuit boards on which the packaged LSIs are interconnected. Collectively, such designs are referred to as LSI-Package-Board (LPB) designs. The format provides a common way to specify information/data about the project management, netlists, components, design rules, and geometries used in LPB designs. This is an IEC/IEEE dual logo standard.
- Standard292 pagesEnglish languagesale 15% off
IEC 61691-1-1:2023 defines the syntax and semantics of the VHSIC Hardware Description Language (VHDL). The acronym VHSIC (Very High Speed Integrated Circuits) in the language’s name comes from the U.S. government program that funded early work on the standard. This is an IEC/IEEE dual logo standard.
- Standard672 pagesEnglish languagesale 15% off
IEC 61523-1:2023 focuses on delay and power calculation for integrated circuit design with support for modeling logical behavior and signal integrity.
The standard specifications covered in this document are as follows:
- Description language for timing and power modeling, called the “delay calculation language” (DCL)
- Software procedural interface (PI) for communications between EDA applications and compiled libraries of DCL descriptions
- Standard file exchange format for parasitic information about the chip design: Standard Parasitic Exchange Format (SPEF)
- Informative usage examples
- Informative notes.
This is an IEC/IEEE dual logo standard.
- Standard640 pagesEnglish languagesale 15% off
This document describes TUpper as an ontology that is conformant to the requirements specified for top-level ontologies in ISO/IEC 21838-1. This document describes TUpper as a resource designed to support ontology design, ontology integration, automated reasoning, and semantic integration of heterogeneous information systems. The following are within the scope of this document: — definitions of classes and relations in the signature of TUpper; — axiomatizations of TUpper in OWL 2 and CL; — documentation of the conformity of TUpper to the requirements specified for top-level ontologies in ISO/IEC 21838-1; — documentation of the methodology for specifying domain ontologies that conform to TUpper. The following are outside the scope of this document: — specification of ontology languages, including the languages RDF, OWL and CL standardly used in ontology development; — specification of methods for reasoning with ontologies; — specification of translators between the notations of ontologies developed in different ontology languages.
- Standard7 pagesEnglish languagesale 15% off
This document describes descriptive ontology for finguistic and cognitive engineering (DOLCE) as an ontology that is conformant to the requirements specified for top-level ontologies in ISO/IEC 21838-1. This document describes DOLCE as a resource designed to support ontology design, ontology integration, and semantic integration of heterogeneous information systems. The following are within the scope of this document: — definitions of classes and relations in the signature of DOLCE; — axiomatizations of DOLCE in OWL 2 and CL; — documentation of the conformity of DOLCE to the requirements specified for top-level ontologies in ISO/IEC 21838-1; — documentation of the methodology for specifying domain ontologies that conform to DOLCE. The following are outside the scope of this document: — specification of ontology languages, including the languages RDF, OWL, and CL standardly used in ontology development; — specification of methods for reasoning with ontologies; — specification of translators between the notations of ontologies developed in different ontology languages.
- Standard7 pagesEnglish languagesale 15% off
- Standard3 pagesEnglish languagesale 15% off
ISO/IEC 9075-2 specifies embedded SQL for the programming languages: Ada, C, COBOL, Fortran, MUMPS, Pascal, and PL/I. ISO/IEC 9075-10:2016 defines similar features of Database language SQL that support embedding of SQL-statements into programs written in the Java? programming language (Java is a registered trademark of Sun Microsystems, Inc.). The embedding of SQL into Java is commonly known as "SQLJ". This part of ISO/IEC 9075 specifies the syntax and semantics of SQLJ, as well as mechanisms to ensure binary portability of resulting SQLJ applications. In addition, it specifies a number of Java packages and their contained classes (including methods). Throughout ISO/IEC 9075-10:2016, the terms "SQLJ" and "SQL/OLB" are used synonymously. NOTE Additional explanatory material (non-normative) about certain facilities defined in ISO/IEC 9075-2 can be found in ISO/IEC TR 19075-3.
- Standard317 pagesEnglish languagesale 15% off
ISO/IEC 9075-3:2016 defines the structures and procedures that can be used to execute statements of the database language SQL from within an application written in a programming language in such a way that procedures used are independent of the SQL statements to be executed.
- Standard371 pagesEnglish languagesale 15% off
- Standard269 pagesEnglish languagesale 15% off
- Standard307 pagesEnglish languagesale 15% off
- Standard158 pagesEnglish languagesale 15% off
This document defines ways in which Database Language SQL can be used in conjunction with multidimensional arrays.
- Standard149 pagesEnglish languagesale 15% off
- Standard437 pagesEnglish languagesale 15% off
ISO/IEC 9075-9:2016 defines extensions to Database Language SQL to support management of external data through the use of foreign-data wrappers and datalink types.
- Standard447 pagesEnglish languagesale 15% off
ISO/IEC 9075-13:2016 specifies the ability to invoke static methods written in the Java? programming language as SQL-invoked routines and to use classes defined in the Java programming language as SQL structured user-defined types. (Java is a registered trademark of Oracle Corporation and/or its affiliates.)
- Standard132 pagesEnglish languagesale 15% off
- Standard1715 pagesEnglish languagesale 15% off
- Standard74 pagesEnglish languagesale 15% off