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.
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 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 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 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 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 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 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
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
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-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
- Standard307 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
- Standard1715 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
- Standard269 pagesEnglish languagesale 15% off
- Standard437 pagesEnglish languagesale 15% off
- Standard158 pagesEnglish languagesale 15% off
- Standard74 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
This document defines ways in which Database Language SQL can be used in conjunction with multidimensional arrays.
- Standard149 pagesEnglish languagesale 15% off
The present document specifies the rules to define schemas for JSON data structures in TTCN-3, to enable testing of
JSON-based systems, interfaces and protocols, and the conversion rules between TTCN-3 [1] and JSON [2] to enable
exchanging TTCN-3 data in JSON format between different systems.
- Standard36 pagesEnglish languagesale 15% off
- Standard36 pagesEnglish languagesale 15% off
- Standardization document36 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the form and meaning of programs written in Ada. Its purpose is to promote the portability of Ada programs to a variety of computing systems. This document specifies: — The form of a program written in Ada; — The effect of translating and executing such a program; — The manner in which program units can be combined to form Ada programs; — The language-defined library units that a conforming implementation is required to supply; — The permissible variations in conformance to the rules of this document, and the manner in which they are to be documented; — Those violations of the requirements of this document that a conforming implementation is required to detect, and the effect of attempting to translate or execute a program containing such violations; — Those violations of the requirements of this document that a conforming implementation is not required to detect. This document does not specify: — The means whereby a program written in Ada is transformed into object code executable by a processor; — The means whereby translation or execution of programs is invoked and the executing units are controlled; — The size or speed of the object code, or the relative execution speed of different language constructs; — The form or contents of any listings produced by implementations; in particular, the form or contents of error or warning messages; — The effect of unspecified execution; — The size of a program or program unit that will exceed the capacity of a particular conforming implementation.
- Standard1048 pagesEnglish languagesale 15% off
- Standard6 pagesEnglish languagesale 15% off
- Standard6 pagesEnglish languagesale 15% off
This document specifies the syntax and semantics of COBOL. Its purpose is to promote a high degree of machine independence to permit the use of COBOL on a variety of data processing systems. This document specifies: The form of a compilation group written in COBOL. The effect of compiling a compilation group. The effect of executing run units. The elements of the language for which a conforming implementation is required to supply a definition. The elements of the language for which meaning is explicitly undefined. The elements of the language that are dependent on the capabilities of the processor. This document does not specify: The means whereby a compilation group written in COBOL is compiled into code executable by a processor. The time at which method, function, or program runtime modules are linked or bound to an activating statement, except that runtime binding occurs of necessity when the identification of the appropriate program or method is not known at compile time. The time at which parameterized classes and interfaces are expanded. The mechanism by which locales are defined and made available on a processor. The form or content of error, flagging, or warning messages. The form and content of listings produced during compilation, if any. The form of documentation produced by an implementor of products conforming to this document. The sharing of objects and resources other than files among run units.
- Standard1229 pagesEnglish languagesale 15% off
IEC 61636-2:2023 (E) provides the definition of an exchange format, utilizing XML, for exchanging maintenance action information (MAI) associated with the removal, repair, and replacement of system components to maintain/support an operational system. This standard is published as a double log IEC-IEEE standard.
- Standard25 pagesEnglish languagesale 15% off
The IEC 62714 series specifies an engineering data exchange format for use in industrial automation systems.
This part of IEC 62714 specifies normative as well as informative AML libraries for the modelling of engineering information for the exchange between engineering tools in the plant automation area by means of AML. Moreover, it presents additional user defined libraries as an example. Its provisions apply to the export/import applications of related tools.
This part of IEC 62714 specifies AML role class libraries and AML attribute type libraries. Role classes provide semantics to AML objects, attribute types provide semantics to AML attributes. The association of role classes to AML objects or attribute types to AML attributes represent the possibility to add (also external) semantic to it. By associating a role class to an AML object or an attribute type to an AML attribute,it gets a semantic.This part of IEC 62714 does not define details of the data exchange procedure or implementation requirements for the import/export tools.
- Standard61 pagesEnglish languagesale 10% offe-Library read for1 day
The IEC 62714 series specifies an engineering data exchange format for use in industrial automation systems. This part of IEC 62714 specifies normative as well as informative AML libraries for the modelling of engineering information for the exchange between engineering tools in the plant automation area by means of AML. Moreover, it presents additional user defined libraries as an example. Its provisions apply to the export/import applications of related tools. This part of IEC 62714 specifies AML role class libraries and AML attribute type libraries. Role classes provide semantics to AML objects, attribute types provide semantics to AML attributes. The association of role classes to AML objects or attribute types to AML attributes represent the possibility to add (also external) semantic to it. By associating a role class to an AML object or an attribute type to an AML attribute,it gets a semantic.This part of IEC 62714 does not define details of the data exchange procedure or implementation requirements for the import/export tools.
- Standard61 pagesEnglish languagesale 10% offe-Library read for1 day
IEC 62714-2:2022 specifies normative as well as informative AML libraries for the modelling of engineering information for the exchange between engineering tools in the plant automation area by means of AML. Moreover, it presents additional user-defined libraries as an example. Its provisions apply to the export/import applications of related tools.
This part of IEC 62714 specifies AML role class libraries and the usage of AML attributes to represent semantic information. Role classes provide semantics to AML objects, attribute types provide semantics to AML attributes. The association of role classes to AML objects or attribute types to AML attributes represent the possibility to add (also external) semantic information to it. By associating a role class to an AML object or an attribute type to an AML attribute, it gets semantic information. This part of IEC 62714 does not define details of the data exchange procedure or implementation requirements for the import/export tools.
- Standard117 pagesEnglish and French languagesale 15% off
This document discusses the syntax and semantics for including online analytic processing (OLAP) capabilities in SQL, as defined in ISO/IEC 9075-2. It discusses the following features regarding OLAP capabilities of the SQL language: — Feature T611, “Elementary OLAP operations”, — Feature T612, “Advanced OLAP operations”, — Feature T614, “NTILE function”, — Feature T615, “LEAD and LAG functions”, — Feature T616, “Null treatment option for LEAD and LAG functions”, — Feature T617, “FIRST_VALUE and LAST_VALUE functions”, — Feature T618, “NTH_VALUE function”, — Feature T619, “Nested window functions”, — Feature T620, “WINDOW clause: GROUPS option”, — Feature T621, “Enhanced numeric functions”
- Standard49 pagesEnglish languagesale 15% off
This specification defines constructs for a Service Modelling Language (SML) for Virtual
Manufacturing Enterprises (VMEs). There is no language standard in ISO or CEN for the
modelling of service systems. Existing service modelling languages mainly focus on IT–
related services or web services. Most existing enterprise modelling languages have some
relevance for services for a VME and can be reused to model part of a service system in this context. However the concepts of those modelling languages need to be integrated and mapped one to another in order to cover the whole modelling requirements for service system engineering.
A standardized Service Modelling Language (SML) and its associated meta-model is seen as an important issue to avoid costly and fragmented development in this domain. SML is focusing on modelling of manufacturing services that a company can develop to support its
products. Compared to ISO 19440-2, SML employs less constructs and a simpler structure. The SML can be considered a specialization of the more general modelling language proposed in ISO 19440-2 .
The modelling constructs of this Technical Specification are complementary to
those constructs and support the design and implementation of future enterprise systems
providing extended products (products + services) to the market.
This Technical Specification specifies:
a) a Model Driven Service Engineering Architecture (MDSEA),
b) a set of constructs for a Service Modelling Language for (Virtual) Manufacturing
Enterprises developed under MDSEA.
Five annexes are provided addressing the basics concepts of service modelling, service
modelling languages, tools and MDSEA and industrial pilots to validate the SML, Annex
D and Annex E.
The MDSEA architecture is derived from MDA [1] and MDI [2] with necessary adaptation and extension to cover the modelling of service (and its system) in its most general forms.
The modelling language addressed in this Technical Specification is specified only at the Business Service Modelling (BSM) level of MDSEA. This specification applies to manufacturing enterprises but can also apply to other classes of enterprises. It is intended for use by system engineers, IT and research specialists who are concerned with developing and deploying product related services in VMEs and Ecosystems.
The constructs specified in this document are also intended to be used by those business
users who are making decisions based on business rather than technical concerns. For this reason, many of the details are simplified or omitted compared to their equivalents (where they exist) in IS 19440:2.
The main added value of the proposed SML will be threefold:
i) Identification of the language constructs needed to define services needed by the
business user.
ii) Integration of existing modelling languages constructs into one coherent meta-model.
iii) Definition of an MDSEA framework based on MDI/MDA to host the language and offer
methods of model transformation between the modelling levels.
- Technical report45 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
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®, 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.
- Standard65 pagesEnglish languagesale 15% off
- Standard65 pagesEnglish languagesale 15% off
- Standardization document65 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies an extension of the Test Description Language (TDL) enabling the specification of
structured test objectives. The extension covers the necessary additional constructs in the abstract syntax, their
semantics, as well as the concrete graphical syntactic notation for the added constructs. In addition textual syntax
examples of the TDL Structured Test Objectives extensions as well as BNF rules for a textual syntax for TDL with the
Structured Test Objectives extensions are provided. The intended use of the present document is to serve both as a
foundation for TDL tools implementing support for the specification of structured test objectives, as well as a reference
for end users applying the standardized syntax for the specification of structured test objectives with TDL.
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.
- Standard78 pagesEnglish languagesale 15% off
- Standard78 pagesEnglish languagesale 15% off
- Standardization document78 pagesEnglish languagesale 10% offe-Library read for1 day
The present document defines the real time and performance testing support 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 OMG 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 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.
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 of and guidelines for this package in combination with other packages
is outside the scope of the present document.
- Standard37 pagesEnglish languagesale 15% off
- Standard37 pagesEnglish languagesale 15% off
- Standardization document37 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies how the elements of the Test Description Language (TDL) should be mapped to Testing
and Test Control Notation version 3 (TTCN-3) [2]. The intended use of the present document is to serve as the basis for
the development of TDL tools. The meta-model of TDL and the meanings of the meta-classes are described in ETSI
ES 203 119-1 [1].
- Standard69 pagesEnglish languagesale 15% off
- Standard69 pagesEnglish languagesale 15% off
- Standardization document69 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies the exchange format of the Test Description Language (TDL) in the form of an XML
Schema derived from the TDL meta-model [1]. The intended use of the present document is to serve as the specification
of the format used for exchange of model instances and tool interoperability between TDL-compliant tools.
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.
- Standard21 pagesEnglish languagesale 15% off
- Standard21 pagesEnglish languagesale 15% off
- Standardization document21 pagesEnglish languagesale 10% offe-Library read for1 day
The present document defines extensions to the Test Description Language (TDL) to support the re-use of test
configurations.
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.
- Standard23 pagesEnglish languagesale 15% off
- Standard23 pagesEnglish languagesale 15% off
- Standardization document23 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard2 pagesEnglish languagesale 15% off
- Standard7 pagesEnglish languagesale 15% off
- Standard4 pagesEnglish languagesale 15% off