SIST EN 21539:1997/AC2:1997
(Amendment)Information technology - Programming languages - Fortran (ISO/IEC 1539:1991)
Information technology - Programming languages - Fortran (ISO/IEC 1539:1991)
Informationstechnik - Programmiersprachen - Fortran (ISO/IEC 1539:1991)
Technologies de l'information - Langages de programmation - Fortran (ISO/IEC 1539:1991)
Information technology - Programming languages - FORTRAN (ISO/IEC 1539:1991)
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Information technology - Programming languages - FORTRAN (ISO/IEC 1539:1991)Informationstechnik - Programmiersprachen - Fortran (ISO/IEC 1539:1991)Technologies de l'information - Langages de programmation - Fortran (ISO/IEC 1539:1991)Information technology - Programming languag
...
This May Also Interest You
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 for×1 day
Basically OML is the data exchanging format that is designed to facilitate exchanging the
omics data around the world without forcing to change any database schema.
- From Informatics side of view, OML is the data exchanging format based on XML. Here the
data exchanging format in the messaging and communication is in the scope, but the
database schema itself is out of the scope of this document.
- From biological side of view, all kinds of omics are in consideration and are in the scope of
this document, the genomic sequence variations and the whole genomic sequence are out of
the scope of this document.
- In otherwise, the annotations as clinical concerns and the relation with other omics concerns
are in the scope of this document.
- Though omics exist in various biological species, the scope of this document is in the
human health associated species as human, cell line, and preclinical animals. The other
biological species are out of the scope of this document.
- The clinical field is in the scope of this document, but the basic research fields and other
scientific fields are out of the scope of this document.
- Here the clinical trials including drug discovery is in the scope of this document. As for
supposed application fields, our main focus is in human health including clinical practice,
preventive medicine, translational research, and clinical researches.
- Standard55 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft93 pagesEnglish languagesale 10% offe-Library read for×1 day
The main purpose of ClaML is to formally represent the content and hierarchical structure of healthcare
classification systems in a markup language for the safe exchange and distribution of data and structure
between organizations and dissimilar software products.
The scope of healthcare classification systems covered by this document encompasses terminologies,
and is constrained to traditional paper-based systems (like ICD-10) and systems built according to
categorial structures and a cross thesaurus (like ICNP)[2]. ClaML is intended for representation of
healthcare classification systems in which classes have textual definitions, hierarchical ordering,
named hierarchical levels (such as “chapter”, “section”), inclusion and exclusion criteria, and codes. It
is not intended to cover any formal representation, neither for definition or composition of concepts,
nor for specification of classification rules. Systems with such formal specifications can at best be
partially represented using ClaML, and are hence out of scope. Most of the notes and examples in this
document relate to ICD. This is because ICD is the most common classification system in the scope of
this document. As a highly complex classification system it is an inexhaustible source for examples of
nearly any kind. But all these notes and examples represent also other similar classification systems,
if applicable, which are usually less complex. An overview of currently known classification systems
using ClaML is provided in a separate document which is electronically available (see 7.3).
This document is not intended to:
a) provide a normative syntax on how a healthcare classification system is to be constructed;
b) define link types between elements in a healthcare classification system (this is left to the
developers of healthcare classification systems);
c) provide a representation for direct viewing or printing.
- Standard67 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft64 pagesEnglish languagesale 10% offe-Library read for×1 day
ISO/IEC 8652:2012 specifies the form and meaning of programs written in the programming language Ada. Its purpose is to promote the portability of Ada programs to a variety of computing systems.
This third edition of ISO/IEC 8652 focuses on improvements in those user domains where safety and criticality are prime concerns. It enhances the functionality of containers, improves the ability to write and enforce contracts for Ada entities (for instance, via preconditions), and adds to the capabilities of Ada to perform on multicore and multithreaded architectures.
Ada is designed to support the construction of longâ€lived, highly reliable software systems. The language includes facilities to define packages of related types, objects, and operations. The packages may be parameterized and the types may be extended to support the construction of libraries of reusable, adaptable software components. The operations may be implemented as subprograms using conventional sequential control structures, or as entries that include synchronization of concurrent threads of control as part of their invocation. Ada supports objectâ€oriented programming by providing classes and interfaces, inheritance, polymorphism of variables and methods, and generic units. The language treats modularity in the physical sense as well, with a facility to support separate compilation.
The language provides rich support for realâ€time, concurrent programming, and includes facilities for multicore and multiprocessor programming. Errors can be signaled as exceptions and handled explicitly. The language also covers systems programming; this requires precise control over the representation of data and access to systemâ€dependent properties. Finally, a predefined environment of standard packages is provided, including facilities for, among others, inputâ€output, string manipulation, numeric elementary functions, random number generation, and definition and use of containers.
Foremost in the design of Ada is the intent to increase the reliability of programs by compiletime checking and rejection of unsafe programs.
- Standard1048 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 for×1 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 for×1 day
- Draft60 pagesEnglish languagesale 10% offe-Library read for×1 day
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 for×1 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 for×1 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 for×1 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 for×1 day
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.