Home

Results 81 - 90 of 209,797 for elements. Search took 1.486 seconds.  
Sort by date/Sort by relevance
A.1 alphabetic character set: A character set that contains letters and may contain control characters and special characters but not digits (ISO 2382/4) A.2 alpha character set: A character set that contains both letters and digits and may contain control characters and special characters (ISO 2382/4) A.3 application message type: A basic message type adapted to suit a certain application area A.4 character set: A finite set of different characters that is considered complete for a given purpose (ISO 2382/4) A.5 common access reference: Key to relate all subsequent transfers of data to the same business file A.6 component data element: A simple data element which is a subordinate portion of a composite data element and in interchange identified by its position within the composite data element A.7 component data element separator: A character used to separate the component data elements in a composite data element A.8 composite data element: A data element containing two or more component data elements A.9 conditional: A statement in a segment or message directory of a condition for the use of a segment, a data element, a composite data element or a component data element (cf. mandatory) A.10 connection: An established link for transmission of data A.11 data: A representation of facts, concepts or instructions in a formalized manner suitable for communication, interpretation or processing by human beings or by automatic means (ISO 2382/1) A.12 data element: A unit of data which in a certain context is considered indivisible (ISO 2382/4) UN/EDIFACT: A unit of data for which the identification, description and value representation have been specified A.13 data elements directory: A listing of identified, named and described data element attributes, with specifications as to how the corresponding data element values shall be represented A.14 data element name: One or more words in a natural language identifying a data element concept A.15 data element separator: A character used to separate data elements in a segment A.16 data element tag: A unique identifier for a data element in a data elements directory A.17 data element value: The specific entry of an identified data element represented as specified in a data elements directory A.18 functional group: One or more messages of the same type headed by a functional group header service segment and ending with a functional group trailer service segment A.19 functional group header: The service segment heading and identifying the functional group A.20 functional group trailer: The service segment ending a functional group A.21 identifier: A character or group of characters used to identify or name an item of data and possibly to indicate certain properties of that data (ISO 2382/4) A.22 interchange: Communication between partners in the form of a structured set of messages and service segments starting with an interchange control header and ending with an interchange control trailer A.23 interchange control header: The service segment starting and identifying an interchange A.24 interchange control trailer: The service segment ending an interchange A.25 mandatory: A statement in a segment or message directory which specifies that a segment, a data element, a composite data element or a component data element must be used (cf. conditional) A.26 message: An ordered series of characters intended to convey information (ISO 2382/16) UN/EDIFACT: A set of segments in the order specified in a Message directory starting with the Message header and ending with the Message trailer A.27 message directory: A listing of identified, named, described and specified message types A.28 message header: The service segment starting and uniquely identifying a message A.29 message trailer: The service segment ending a message A.30 message type: An identified and structured set of data elements covering the requirements for a specified type of transaction, e.g. invoice. (...) It can be a service segment or a user data segment A.38 segment code: A code which uniquely identifies each segment as specified in a segment directory A.39 segment tag: A composite data element, in which the first component data element contains a code which uniquely identifies a segment as specified in the relevant segment directory. Additional component data elements can be conditionally used to indicate the hierarchical level and nesting relation in a message and the incidence of repetition of the segment A.40 segment terminator: A syntax character indicating the end of a segment A.41 segments directory: A listing of identified, named, described and specified segments A.42 separator character: A character used for syntactical separation of data A.43 service data element: A data element used in service segments A.44 service segment: A segment required to service the interchange of user data A.45 service string advice: A character string at the beginning of an interchange defining the syntactically delimiting characters and indicators used in the interchange A.46 simple data element: A data element containing a single value A.47 syntax rules: Rules governing the structure of an interchange and its functional groups, messages, segments and data elements A.48 transfer: A communication from one partner to another A.49 user data segment: A segment containing application data A PROPOS Mandat Secrétaire exécutif Structure de l’organisation OPPORTUNITÉS D’EMPLOI Postes vacants RECHERCHES Base de données statistique Évaluations SUIVEZ NOUS Facebook Twitter Contact us Flickr Rss Youtube Instagram @ Commission économique des Nations Unies pour l’Europe | Termes et conditions d'utilisation | Confidentialité de l'information Nous contacter
Language:English
Score: 615272.9 - https://unece.org/fr/node/9062
Data Source: un
A.1 alphabetic character set: A character set that contains letters and may contain control characters and special characters but not digits (ISO 2382/4) A.2 alpha character set: A character set that contains both letters and digits and may contain control characters and special characters (ISO 2382/4) A.3 application message type: A basic message type adapted to suit a certain application area A.4 character set: A finite set of different characters that is considered complete for a given purpose (ISO 2382/4) A.5 common access reference: Key to relate all subsequent transfers of data to the same business file A.6 component data element: A simple data element which is a subordinate portion of a composite data element and in interchange identified by its position within the composite data element A.7 component data element separator: A character used to separate the component data elements in a composite data element A.8 composite data element: A data element containing two or more component data elements A.9 conditional: A statement in a segment or message directory of a condition for the use of a segment, a data element, a composite data element or a component data element (cf. mandatory) A.10 connection: An established link for transmission of data A.11 data: A representation of facts, concepts or instructions in a formalized manner suitable for communication, interpretation or processing by human beings or by automatic means (ISO 2382/1) A.12 data element: A unit of data which in a certain context is considered indivisible (ISO 2382/4) UN/EDIFACT: A unit of data for which the identification, description and value representation have been specified A.13 data elements directory: A listing of identified, named and described data element attributes, with specifications as to how the corresponding data element values shall be represented A.14 data element name: One or more words in a natural language identifying a data element concept A.15 data element separator: A character used to separate data elements in a segment A.16 data element tag: A unique identifier for a data element in a data elements directory A.17 data element value: The specific entry of an identified data element represented as specified in a data elements directory A.18 functional group: One or more messages of the same type headed by a functional group header service segment and ending with a functional group trailer service segment A.19 functional group header: The service segment heading and identifying the functional group A.20 functional group trailer: The service segment ending a functional group A.21 identifier: A character or group of characters used to identify or name an item of data and possibly to indicate certain properties of that data (ISO 2382/4) A.22 interchange: Communication between partners in the form of a structured set of messages and service segments starting with an interchange control header and ending with an interchange control trailer A.23 interchange control header: The service segment starting and identifying an interchange A.24 interchange control trailer: The service segment ending an interchange A.25 mandatory: A statement in a segment or message directory which specifies that a segment, a data element, a composite data element or a component data element must be used (cf. conditional) A.26 message: An ordered series of characters intended to convey information (ISO 2382/16) UN/EDIFACT: A set of segments in the order specified in a Message directory starting with the Message header and ending with the Message trailer A.27 message directory: A listing of identified, named, described and specified message types A.28 message header: The service segment starting and uniquely identifying a message A.29 message trailer: The service segment ending a message A.30 message type: An identified and structured set of data elements covering the requirements for a specified type of transaction, e.g. invoice. (...) It can be a service segment or a user data segment A.38 segment code: A code which uniquely identifies each segment as specified in a segment directory A.39 segment tag: A composite data element, in which the first component data element contains a code which uniquely identifies a segment as specified in the relevant segment directory. Additional component data elements can be conditionally used to indicate the hierarchical level and nesting relation in a message and the incidence of repetition of the segment A.40 segment terminator: A syntax character indicating the end of a segment A.41 segments directory: A listing of identified, named, described and specified segments A.42 separator character: A character used for syntactical separation of data A.43 service data element: A data element used in service segments A.44 service segment: A segment required to service the interchange of user data A.45 service string advice: A character string at the beginning of an interchange defining the syntactically delimiting characters and indicators used in the interchange A.46 simple data element: A data element containing a single value A.47 syntax rules: Rules governing the structure of an interchange and its functional groups, messages, segments and data elements A.48 transfer: A communication from one partner to another A.49 user data segment: A segment containing application data ABOUT UNECE Mission Executive Secretary Organizational Structure OPPORTUNITIES Vacancies Internship Programme RESOURCES Statistical Database Evaluations Follow UNECE Facebook Twitter Contact us Flickr Rss Youtube Instagram © United Nations Economic Commission for Europe | Terms and Conditions of Use | Privacy Notice Contact us
Language:English
Score: 615272.9 - https://unece.org/ar/node/9062
Data Source: un
A paragraph element contains hidden text for a paragraph. A line element contains hidden text for a line. A word element contains hidden text for a word. A altword element contains hidden text for a alternative word. A char element contains a hidden text character. A altchar element contains a hidden text alternative character.
Language:English
Score: 615206.1 - https://www.itu.int/wftp3/Publ...t/fl/itu-t/t/t805/2012/htx.xsd
Data Source: un
This module includes elements which should be viewed as a subset of all available meteorological information that can be used to support enhanced operational efficiency and safety. (...) Element Implementation Status 1 Element Description: Standardized Aeronautical Information Exchange Model (AIXM) Date Planned/Implemented Before May 2017 Status Implemented Status Details Enter status details 2 Element Description: eAIP Date Planned/Implemented Enter date if applicable Status Implemented Status Details Enter status details 3 Element Description: Digital NOTAM Date Planned/Implemented Enter date if applicable Status Analysis not started Status Details Enter status details 4 Element Description: eTOD Date Planned/Implemented June 2018 Status Analysis in progress Status Details Work has started 5 Element Description: WGS-84 Date Planned/Implemented Before May 2010 Status Implemented Status Details Enter status details 6 Element Description: QMS for AIM Date Planned/Implemented DECEMBER 2018 Status Developing Status Details Work has started Achieved Benefits Access and Equity Capacity Efficiency: eAIP – Alignment with ICAO standards will ensure operators can find necessary data in the same manner as they do other ICAO compliant AIPs Environment: Moving away from print across sections of the business, including eAIP. (...) Element Implementation Status 1 Element Description: ADS-C over oceanic and remote areas Date Planned/Implemented Enter date if applicable Status N/A Status Details Enter status details 2 Element Description: CPDLC over continental areas Date Planned/Implemented Enter date if applicable Status N/A Status Details Enter status details 3 Element Description: CPDLC over oceanic and remote areas Date Planned/Implemented Enter date if applicable Status N/A Status Details Enter status details Achieved Benefits Access and Equity Capacity Efficiency Environment Safety Implementation Challenges Ground system Implementation Avionics Implementation Procedures Availability Operational Approvals Notes
Language:English
Score: 615069.73 - https://www.icao.int/NACC/Docu...Groups/ANIWG/ASBU/ASBU-BRB.pdf
Data Source: un
Element Implementation Status 1 Element Description: WAFS Date Planned/Implemented Status/Implemented Status Details 2 Element Description: Volcanic Ash IAVW Date Planned/Implemented Status/Implemented Status Details 3 Element Description: TCAC forecasts Date Planned/Implemented Status/Implemented Status Details 4 Element Description: Aerodrome warnings 30/06/17-In progress Status/Developing Status Details 5 Element Description: Wind shear warnings and alerts 30/06/17-In progress ed Status/Developing Status Details 6 Element Description: SIGMET NA Status/NA Status Details 7 Element Description: Other OPMET information (METAR, SPECI and/or TAF) Implemented Status/Implemented Status Details 8 Element Description: QMS for MET Implemented Status/Implemented 4 of 13 STATE Status Details Achieved Benefits Access and Equity Capacity Efficiency  Environment Safety Implementation Challenges Ground system Implementation  Avionics Implementation Procedures Availability Operational Approvals Notes Government has approved the purchase of a new AWOS system for met 5 of 13 STATE Antigua and Barbuda ASBU Air Navigation Reporting Form (ANRF) PIA 2 Block - Module B0 - DATM Date 19/10/, 2016 Module Description: The initial introduction of digital processing and management of information through, aeronautical information service (AIS)/aeronautical information management (AIM) implementation, use of aeronautical exchange model (AIXM), migration to electronic aeronautical information publication (AIP) and better quality and availability of data. Element Implementation Status 1 Element Description: Aeronautical Information Exchange Model (AIXM) 30/09/2018/Need Status/Planning Status Details 2 Element Description: eAIP Implemented Status/Implemented Status Details 3 Element Description: Digital NOTAM 30/03/2017 Status/Developing Status Details will be provided by Trinidad and Tobago should be ready by first quarter of next year 4 Element Description: eTOD 30/09/2018 Status/Planning Status Details 5 Element Description: (Identified by NACC) WGS-84 Implemented Status/Implemented Status Details was implemented at the end of 2014 6 Element Description: QMS for AIM 29/12/2017 Status/Partially implemented Status Details awaiting signed LOA with Trinidad and Tobago Achieved Benefits Access Capacity Efficiency  Environment Safety  Implementation Challenges Ground system Implementation  Avionics Implementation 6 of 13 STATE Procedures Availability Operational Approvals Notes All are internal changes 7 of 13 STATE Antigua and Barbuda ASBU Air Navigation Reporting Form (ANRF) PIA 3 Block - Module B0 - ACAS Date 19/10/2016 Module Description: Provides short-term improvements to existing airborne collision avoidance systems (ACAS) to reduce nuisance alerts while maintaining existing levels of safety. (...) This will optimize throughput, allow fuel efficient descent profiles, and increase capacity in terminal areas. Element Implementation Status 1 Element Description: Procedure changes to facilitate CDO 30/12/2017/In Progress Status/Developing Status Details 2 Element Description: Route changes to facilitate CDO 30/12/2017/In Progress Status/Developing Status Details 3 Element Description: PBN STARs 30/12/2017/In Progress Status/Developing Status Details Achieved Benefits Access and Equity Capacity Efficiency Environment Safety Implementation Challenges Ground system Implementation Avionics Implementation Procedures Availability  Operational Approvals  Notes
Language:English
Score: 615055.6 - https://www.icao.int/NACC/Docu...Groups/ANIWG/ASBU/ASBU-ATG.pdf
Data Source: un
Recommended fields are as follows: · Agency element number - A reference number for the data element. · Data element name - The name of the data element being defined. (...) “Capture Agency Data Elements” - The ITDS data team captured agency data elements from several sources. (...) “Identify Similar Data Elements” – The ITDS team identified similar data elements.
Language:English
Score: 614963.3 - https://unece.org/fileadmin/DA...34-PublicReviewDraft-Feb09.doc
Data Source: un
A.2 Control layer management functional component Figure A.2 shows the functional elements of the CLM functional component. Figure A.2 – Functional elements of the CLM functional component A.2.1 Control layer support functional element The CL support functional element provides an MMC reference point to the CL-MSO functional component (see clause 7.2.2) which is used for requesting and receiving management operations and associated information to/from the SDN-CL. A.2.2 Control layer resource discovery functional element The CL resource discovery functional element is responsible for discovering control resources in the SDN-CL. (...) The discovered resources are stored in the CL resource repository functional element. A.2.3 Control layer resource repository functional element The CL resource repository functional element is responsible for storing the contents discovered by the resource discovery and bootstrapping and managing the lifecycle of the contents in the repository.
Language:English
Score: 614102.5 - https://www.itu.int/en/publica.../files/basic-html/page185.html
Data Source: un
A.3.9 Resource layer security management functional element The RL security management is an optional functional element responsible for security management of the SDN-RL. (...) A.3.10 Resource layer resource accounting management functional element The RL accounting management functional element is responsible for accounting management of the SDN- RL. (...) A.4 Multi-layer management orchestration functional component Figure A.4 shows the functional elements of the MMO functional component. Figure A.4 – Functional elements of the MMO functional component A.4.1 Multi-layer orchestration support functional element The multi-layer orchestration support functional element provides an internal interface to the multi-layer orchestration support functional element in the ALM, CLM, RLM functional components for requesting and receiving management operations and associated information for multi-layer orchestration.
Language:English
Score: 614010.3 - https://www.itu.int/en/publica.../files/basic-html/page189.html
Data Source: un
Recommended fields are as follows: · Agency element number - A reference number for the data element. · Data element name - The name of the data element being defined. (...) “Capture Agency Data Elements” - The ITDS data team captured agency data elements from several sources. (...) “Identify Similar Data Elements” – The ITDS team identified similar data elements.
Language:English
Score: 613713.23 - https://unece.org/fileadmin/DA...licReview/Rec34v6_june2008.doc
Data Source: un
[ISO 9735] Component data element separator: a character used to separate component data elements in a composite data element. [ISO 9735] Composite data element: a data element containing two or more component data elements. (...) [ISO 9735] Data element tag: a unique identifier for a data element in a data element directory.
Language:English
Score: 613668.1 - https://unece.org/trade/uncefa...t/part-3-terms-and-definitions
Data Source: un