IT-tillämpningar
- +Ämnesområden
- +Informationsteknik, kontorsutrustning (17)
- Informationsteknik: allmänt (3)
- IT-säkerhet (0)
- +Kodning av information (5)
- Programspråk (1)
- Programutveckling och systemdokumentation (2)
- +Öppna system (OSI) (0)
- Nätarkitekturer (0)
- Datorgrafik (0)
- Mikroprocessorsystem (0)
- Terminalutrustning och övrig kringutrustning (0)
- Gränssnitt och anslutningsutrustning (0)
- Molnbaserade datortjänster (0)
- +Datalagringsmedier (0)
- +IT-tillämpningar (6)
- IT-tillämpningar: allmänt (0)
- Datorstödd design (1)
- Identifieringskort och tillhörande läsarenheter (1)
- IT-tillämpningar i kontorsarbete (1)
- IT- tillämpningar inom information, dokumentation och förlagsverksamhet (1)
- IT- tillämpningar inom finansiella system (0)
- IT- tillämpningar inom industrin (0)
- IT- tillämpningar inom transport (1)
- IT-tillämpningar inom handel (1)
- IT- tillämpningar inom bygg- och anläggningsindustri (0)
- IT-tillämpningar inom jordbruk (0)
- IT- tillämpningar inom posttjänster (0)
- IT- tillämpningar inom vetenskap (1)
- Hälso- och sjukvårdsinformatik (1)
- IT- tillämpningar inom utbildning (0)
- Internettillämpningar (0)
- IT- tillämpningar inom övriga områden (0)
- Kontorsutrustning (0)
This document specifies the data structure and content of an interface that permits communication between position-providing device(s) and position-using device(s) enabling the position-using device(s) to obtain and unambiguously interpret position information and determine, based on a measure of the degree of reliability, whether the resulting position information meets the requirements of the intended use. A standardized interface for positioning allows the integration of reliable position information obtained from non-specific positioning technologies and is useful in various location-focused information applications, such as surveying, navigation, intelligent transportation systems (ITS), and location-based services (LBS).
1.1 Introduction This document defines common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the "fundamentals and concepts" of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models. Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features. The EN 9300-1XX family is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX family. As technology matures, additional parts will be released in order to support new requirements within the aerospace community. 1.2 In scope The present part describes: - the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information; - the document structure of the EN 9300-1XX family, and the links between all these parts; - the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file; - specifications for the preservation planning of archived CAD information; - specific functions for administration and monitoring of CAD archived mechanical models; - the definition of archive information packages for CAD data. 1.3 Out of scope The following are out of scope for this part: - long-term archiving of CAD 2D drawings; - other CAD specialization disciplines, such as electrical harnesses, composite.
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:
— ASN.1 (data) types within the fields of EFC;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
This document describes the transaction information requirements of the transactions used in the basic collaborations described in EN 17015-1 Electronic Public Procurement – Catalogue – Choreographies. For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements. The document describes the following transactions: 1) Catalogue; 2) Catalogue Response 3) Pre-award Catalogue Request 4) Pre-award Catalogue 5) Shopping Cart How to claim compliance to a transaction is described in paragraph 6. How to claim conformance to a transaction is described in paragraph 6.
This standard defines an object-oriented abstract information model to represent a PHD and the observations generated by a PHD. It specifies what information needs to be present and the relationships between the informational elements in the model. It models observations in a generic way by focusing on the information content contained in the presentation of health measurements. The modeling follows the practice of ISO/IEEE 11073-20601 [B12] where Unified Modeling Language (UML) is used to describe a set of objects and the relationship between the objects.7 Tables provide descriptions of the attributes in the objects. IEEE 11073-10101™ nomenclature terms are used to express clinical content. This standard provides guidance as to what an exchange protocols needs to communicate to properly represent health observations, but is not, in itself, sufficient to be an exchange protocol. However, the content model defined herein does have sufficient detail to help organizations validate that there is no loss of the semantic content induced by data exchanges in a protocol adhering to this standard. This standard does not define a security framework.