L74 程序语言 标准查询与下载



共找到 1292 条与 程序语言 相关的标准,共 87

ISO/IEC 1539 is a multipart International Standard; the parts are published separately. This publication, ISO/IEC 1539-1, which is the first part, specifies the form and establishes the interpretation of programs expressed in the base Fortran language. The purpose of this part of ISO/IEC 1539 is to promote portability, liability, maintainability, and efficient execution of Fortran programs for use on a variety of computing systems.

Information Technology - Programming Languages - FORTRAN - Part 1: Base Language

ICS
35.060
CCS
L74
发布
2007
实施

The purpose of recommending SDL (Specification and Description Language) is to provide a language for unambiguous specification and description of the behaviour of telecommunication systems. The specifications and descriptions using SDL are intended to be formal in the sense that it is possible to analyse and interpret them unambiguously. The terms specification and description are used with the following meaning: a) a specification of a system is the description of its required behaviour; and b) a description of a system is the description of its actual behaviour; that is, its implementation. A system specification, in a broad sense, is the specification of both the behaviour and a set of general parameters of the system. However, SDL is intended to specify the behavioural aspects of a system; the general parameters describing properties like capacity and weight have to be described using different techniques. NOTE ? Since there is no distinction between use of SDL for specification and its use for description, the term specification is used in this Recommendation for both required behaviour and actual behaviour. The general objectives when defining SDL have been to provide a language that: a) is easy to learn, use and interpret; b) provides unambiguous specification for ordering, tendering and design, while also allowing some issues to be left open; c) may be extended to cover new developments; d) is able to support several methodologies of system specification and design.

Specification and Description Language (SDL) Study Group 17

ICS
CCS
L74
发布
2007
实施

Amends the existing IEEE 1076-2002 (VHDL) standard by adding a simulation runtime application interface (VHDL Programming Interface or VHPI).

VHDL Language reference manual - Amendment 1: Procedural language application interface

ICS
35.060
CCS
L74
发布
2007
实施

ISO/IEC 13249 defines a number of packages of generic data types common to various kinds of data used in multimedia and application areas, to enable that data to be stored and manipulated in an SQL database. The package in each subject area is defined as a part of ISO/IEC 13249. ISO/IEC 13249-1:2007 defines those concepts, notations and conventions that are common to two or more other parts of ISO/IEC 13249. In particular, it describes the way ISO/IEC 9075 is used in other parts of ISO/IEC 13249 to define the user-defined types and their behaviour appropriate to each subject area.

Information technology - Database languages - SQL multimedia and application packages - Part 1: Framework

ICS
35.060
CCS
L74
发布
2007
实施

? ??? ??? ??? ??(data model)? ????. ??? ??? ???? ?

Information technology-Topic Maps-Part 2:Data model

ICS
35.240.30
CCS
L74
发布
2006-12-29
实施
2006-12-29

이 코어 컴포넌트 기술규격은 개방된 세계적 환경에 있는 기업, 정부기관 또는 다른 조직간에

Electronic Business Extensible Markup Language(ebXML)-Part 5:ebXML Core Components Technical Specification,Version 2.01(ebCCTS)

ICS
35.040
CCS
L74
发布
2006-12-29
实施
2006-12-29

この規格は,データベース言語SQLをXMLと一緒に用いる方法を規定する。

Information technology -- Database languages -- SQL -- Part 14: XML-Related Specifications (SQL/XML)

ICS
35.060
CCS
L74
发布
2006-12-20
实施
2006-12-20

1.1 General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360-1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. ISO/IEC 23360-1, the LSB-generic document, should be used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document. The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed. The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification. 1.2 Module Specific Scope This is the Itanium™ architecture specific Core part of the Linux Standard Base (LSB). This part supplements the generic LSB Core module with those interfaces that differ between architectures. Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Linux Standard Base (LSB) core specification 3.1 - Part 3: Specification for IA64 architecture

ICS
35.080
CCS
L74
发布
2006-12
实施

1.1 General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360-1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. ISO/IEC 23360-1, the LSB-generic document, should be used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document. The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed. The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification. 1.2 Module Specific Scope This is the Core module of the Linux Standard Base (LSB), ISO/IEC 23360-1. This module provides the fundamental system interfaces, libraries, and runtime environment upon which all conforming applications and libraries depend. Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Linux Standard Base (LSB) core specification 3.1 - Part 1: Generic specification

ICS
35.080
CCS
L74
发布
2006-12
实施

This is an interpretation of IEEE Std 1003.5 (1999 Edition). Interpretations are issued to explain and clarify the intent of a standard and are not intended to constitute an alteration to the original standard or to supply consulting information. Permission is hereby granted to download and print one copy of this document. Individuals seeking permission to reproduce and/or distribute this document in its entirety or portions of this document must contact the IEEE Standard Department for the appropriate license. Use of the information contained in this document is at your own risk.

IEEE Standards Interpretations for IEEE Std 1003.5 (1999 Edition)

ICS
CCS
L74
发布
2006-12
实施

1.1 General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360-1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. ISO/IEC 23360-1, the LSB-generic document, should be used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document. The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed. The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification. 1.2 Module Specific Scope This is the IA32 architecture specific Core part of the Linux Standard Base (LSB). This part supplements the generic LSB Core module with those interfaces that differ between architectures. Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Linux Standard Base (LSB) core specification 3.1 - Part 2: Specification for IA32 architecture

ICS
35.080
CCS
L74
发布
2006-12
实施

1.1 Overview This document provides the full reference for the Eiffel language. Eiffel is a method of software construction and a language applicable to the analysis, design, implementation and maintenance of software systems. This International Standard covers only the language, with an emphasis on the implementation aspects. As a consequence, the word “Eiffel” in the rest of this document is an abbreviation for “the Eiffel language”. 1.2 “The Standard” The language definition proper — “the Standard” — is contained in Clause 8 of this document, with the exception of text appearing between markers Informative text and End; such text only plays an explanatory role for human readers. 1.3 Aspects covered The Standard specifies: • the form of legal basic constituents of Eiffel texts, or lexical properties of the language; • the structure of legal Eiffel texts made of lexically legal constituents, or syntax properties; • supplementary restrictions imposed on syntactically legal Eiffel texts, or validity properties; • the computational effect of executing valid Eiffel texts, or semantic properties; and • some requirements on a conforming implementation of Eiffel, such as the ability to produce certain forms of automatic documentation. 1.4 Aspects not covered The Standard does not specify: • the requirements that a computing environment must meet to support the translation, execution and other handling of Eiffel texts; • the semantic properties of an Eiffel text if it or its data exceed the capacity of a particular computing environment; • the mechanisms for translating Eiffel texts into a form that can be executed in a computing environment; • the mechanisms for starting the execution of the result of such a translation; and • other mechanisms for handling Eiffel texts and interacting with users of the language. The specification of Clause 8 consists of precise specification elements, originating with the book Standard Eiffel where these elements are accompanied by extensive explanations and examples. The elements retained are: • definitions of technical terms and Eiffel concepts; Information technology — EiffeI: Analysis, Design and Programming Language • syntax specifications; • validity constraints (with their codes, such as VVBG); and • semantic specifications.

Information technology - Eiffel: Analysis, Design and Programming Language

ICS
35.060
CCS
L74
发布
2006-12
实施

1.1 General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360-1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. ISO/IEC 23360-1, the LSB-generic document, is used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document. The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed. The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification. 1.2 Module Specific Scope This is the S390 architecture-specific Core part of the Linux Standard Base (LSB). It supplements the generic LSB Core module with those interfaces that differ between architectures. Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Linux Standard Base (LSB) core specification 3.1 - Part 7: Specification for S390 architecture

ICS
35.080
CCS
L74
发布
2006-12
实施

1.1 General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360-1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. ISO/IEC 23360-1, the LSB-generic document, is used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document. The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed. The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification. 1.2 Module Specific Scope This is the S390X architecture-specific Core part of the Linux Standard Base (LSB). It supplements the generic LSB Core module with those interfaces that differ between architectures. Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Linux Standard Base (LSB) core specification 3.1 - Part 8: Specification for S390X architecture

ICS
35.080
CCS
L74
发布
2006-12
实施

1.1 General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360-1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. ISO/IEC 23360-1, the LSB-generic document, is be used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document. The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed. The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification. 1.2 Module Specific Scope This is the AMD64 architecture-specific Core part of the Linux Standard Base (LSB). It supplements the generic LSB Core module with those interfaces that differ between architectures. Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Linux Standard Base (LSB) core specification 3.1 - Part 4: Specification for AMD64 architecture

ICS
35.080
CCS
L74
发布
2006-12
实施

1.1 General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360-1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. ISO/IEC 23360-1, the LSB-generic document, is used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document. The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed. The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification. 1.2 Module Specific Scope This is the PPC32 architecture-specific Core part of the Linux Standard Base (LSB). It supplements the generic LSB Core module with those interfaces that differ between architectures. Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Linux Standard Base (LSB) core specification 3.1 - Part 5: Specification for PPC32 architecture

ICS
35.080
CCS
L74
发布
2006-12
实施

1.1 General The Linux Standard Base (LSB) defines a system interface for compiled applications and a minimal environment for support of installation scripts. Its purpose is to enable a uniform industry standard environment for high-volume applications conforming to the LSB. These specifications are composed of two basic parts: A common specification ("LSB-generic" or "generic LSB"), ISO/IEC 23360-1, describing those parts of the interface that remain constant across all implementations of the LSB, and an architecture-specific part ("LSB-arch" or "archLSB") describing the parts of the interface that vary by processor architecture. Together, the LSB-generic and the relevant architecture-specific part of ISO/IEC 23360 for a single hardware architecture provide a complete interface specification for compiled application programs on systems that share a common hardware architecture. ISO/IEC 23360-1, the LSB-generic document, is used in conjunction with an architecture-specific part. Whenever a section of the LSB-generic specification is supplemented by architecture-specific information, the LSB-generic document includes a reference to the architecture part. Architecture-specific parts of ISO/IEC 23360 may also contain additional information that is not referenced in the LSB-generic document. The LSB contains both a set of Application Program Interfaces (APIs) and Application Binary Interfaces (ABIs). APIs may appear in the source code of portable applications, while the compiled binary of that application may use the larger set of ABIs. A conforming implementation provides all of the ABIs listed here. The compilation system may replace (e.g. by macro definition) certain APIs with calls to one or more of the underlying binary interfaces, and may insert calls to binary interfaces as needed. The LSB is primarily a binary interface definition. Not all of the source level APIs available to applications may be contained in this specification. 1.2 Module Specific Scope This is the PPC64 architecture-specific Core part of the Linux Standard Base (LSB). It supplements the generic LSB Core module with those interfaces that differ between architectures. Interfaces described in this part of ISO/IEC 23360 are mandatory except where explicitly listed otherwise. Core interfaces may be supplemented by other modules; all modules are built upon the core.

Linux Standard Base (LSB) core specification 3.1 - Part 6: Specification for PPC64 architecture

ICS
35.080
CCS
L74
发布
2006-12
实施

ISO/IEC 13249 defines a number of packages of generic data types common to various kinds of data used in multimedia and application areas, to enable that data to be stored and manipulated in an SQL database. This part of ISO/IEC 13249 a) introduces the data mining part of ISO/IEC 13249, b) gives the references necessary for this part of ISO/IEC 13249, c) defines notations and conventions specific to this part of ISO/IEC 13249, d) defines concepts specific to this part of ISO/IEC 13249, e) defines data mining user-defined types and their associated routines. The data mining user-defined types defined in this part adhere to the following. — A data mining user-defined type is generic to data mining data handling. It addresses the need to store, manage and retrieve information based on elements such as data mining models, data mining settings, and data mining test results. — A data mining user-defined type does not redefine the database language SQL directly or in combination with another data mining data type.

Information technology - Database languages - SQL multimedia and application packages - Data mining

ICS
35.060
CCS
L74
发布
2006-11-30
实施
2006-11-30

この規格は,異なるシステム環境で,それらの環境の独特な性質を考慮にいれた書換えを行うことなく,複数の高水準言語で書かれたアプリケーションを動作させることを可能とする共通言語基盤(CLI)を定義する。

CLI: Common Language Infrastructure

ICS
35.060
CCS
L74
发布
2006-11-20
实施

This part of ISO/IEC 13249 a) introduces the Spatial part of ISO/IEC 13249, b) gives the references necessary for this part of ISO/IEC 13249, c) defines notations and conventions specific to this part of ISO/IEC 13249, d) defines concepts specific to this part of ISO/IEC 13249, e) defines spatial user-defined types and their associated routines. The spatial user-defined types defined in this part of ISO/IEC 13249 adhere to the following. — A spatial user-defined type is generic to spatial data handling. It addresses the need to store, manage and retrieve information based on aspects of spatial data such as geometry, location and topology. — A spatial user-defined type does not redefine the database language SQL directly or in combination with another spatial data type. Implementations of this part of ISO/IEC 13249 may exist in environments that also support geographic information, decision support, data mining and data warehousing systems. Application areas addressed by implementations of this part of ISO/IEC 13249 include, but are not restricted to, automated mapping, desktop mapping, facilities management, geoengineering, graphics, location based services, multimedia and resource management applications.

Information technology - Database languages - SQL multimedia and application packages - Part 3: Spatial

ICS
35.060
CCS
L74
发布
2006-11-01
实施



Copyright ©2007-2022 ANTPEDIA, All Rights Reserved
京ICP备07018254号 京公网安备1101085018 电信与信息服务业务经营许可证:京ICP证110310号