Home

  Microsoft Word - taxation-exchange of information

Microsoft Word - taxation-exchange of information United Nations E/C.18/2006/6/Add.1 Economic and Social Council Distr.: General 1 September 2006 Original: English Committee of Experts on International Cooperation Advance copy in Tax Matters Second session Geneva, 30 October-3 November 2006 Work on exchange of information and conclusion* Summary This paper provides a brief presentation of the work done by other international organisations in respect of exchange of information in tax matters and some possible future work for the UN Committee in this field. (...) This document presents some conclusions of the work done on exchange of information by other international organisations and possible future work for the UN in that field. (...) In the context of exchange of information achieving a level playing field means the convergence of existing practices to the same high standards for effective exchange of information on both criminal and civil taxation matters within an acceptable timeline for implementation with the aim of achieving equity and fair competition.

Score: 856687.9 - https://www.un.org/esa/ffd/wp-...information_EC1820066Add.1.pdf

  CNS SG/6-WP/27 Inter

Letter of Agreement 5(6) Identity Date Version Status File 1.0 Draft 6 AIDC MESSAGES CONTENT The table below specifies the fields to be included in the AIDC messages: Field Nr Field name ABI ACT LAM 3a Message Type X X X 3b Message Number X X X 3c Message Reference - - X 7a Aircraft Identification X X - 7b SSR Mode X*) X***) - 7c SSR Code X*) X***) - 13a Departure Aerodrome X X - 14a Boundary Point, COP X**) X**) - 14b ETO Boundary Point X X - 14c Cleared Level X X - 16a Destination Aerodrome X X - 22/8 Flight rules and Type of flight X X - 22/9a Number of Aircraft X****) X****) - 22/9b Type of Aircraft X X - 22/9c Wake Turbulence Category X X - 22/10 Equipment X X - “X” – shall be included “- “ – shall not be included *) Only if available. **) Only agreed COPs are allowed. ***) The field is not used for aircraft without transponder. ****) Only if other then 1. The field format shall be the ICAO format. Format and syntax of the individual fields shall comply with PANS ATM 4444 for AIDC. 7 COMMUNICATION The communication facility for flight data exchange is specified in [ICD_AIDC]. 8 INTEGRATION TESTING A test programme shall be mutually developed. (...) The field format shall be the ICAO format. Format and syntax of the individual fields shall comply with Eurocontrol OLDI]. 7 COMMUNICATION The communication facility for flight data exchange is specified in ICD_OLDI. 8 INTEGRATION TESTING A test programme shall be mutually developed.

Score: 829994.9 - https://www.icao.int/MID/Docum...-%20OLDI%20AIDC%20-%20Oman.pdf

  SeseAPDUs (X.832:04/1995)

&sE-Identifier ({ ValidSEs }) , -- This identifies one of the security- -- exchanges supported by the particular SESE -- abstract syntax itemIdentifier SECURITY-EXCHANGE . (...) &itemId ({ ValidSEs }{@seIdentifier}) , -- This identifies one of the security- -- exchange-items of the security exchange -- indicated by "seIdentifier" seItem SECURITY-EXCHANGE . (...) &ItemType ({ ValidSEs }{@seIdentifier, @itemIdentifier}) , invocationId InvocationId ( InvocationIdSet ) ( CONSTRAINED BY { -- Must be the same as the-- -- invocationId on an active security exchange-- -- if start flag is not true -- }) DEFAULT noInvocationId , startFlag BOOLEAN DEFAULT FALSE , -- This field is set only as the first security- -- exchange-item of a security-exchange is -- transferred. endFlag BOOLEAN DEFAULT FALSE -- This field is set as the last security-exchange- -- item of a security-exchange is transferred.

Score: 823112.5 - https://www.itu.int/wftp3/Publ...u-t/x/x832/1995/SeseAPDUs.html

  -- Module SeseAPDUs

&sE-Identifier({ValidSEs}), -- This identifies one of the security- -- exchanges supported by the particular SESE -- abstract syntax itemIdentifier SECURITY-EXCHANGE. (...) &itemId({ValidSEs}{@seIdentifier}), -- This identifies one of the security- -- exchange-items of the security exchange -- indicated by "seIdentifier" seItem SECURITY-EXCHANGE. (...) &ItemType ({ValidSEs}{@seIdentifier, @itemIdentifier}), invocationId InvocationId(InvocationIdSet) (CONSTRAINED BY {-- Must be the same as the---- invocationId on an active security exchange-- -- if start flag is not true -- }) DEFAULT noInvocationId, startFlag BOOLEAN DEFAULT FALSE, -- This field is set only as the first security- -- exchange-item of a security-exchange is -- transferred. endFlag BOOLEAN DEFAULT FALSE-- This field is set as the last security-exchange- -- item of a security-exchange is transferred.

Score: 821966.1 - https://www.itu.int/wftp3/Publ...tu-t/x/x832/1995/SeseAPDUs.asn

  Joint Video Team (MPEG+ITU) Document

This group of bitstreams exercises most of the major features of the standard, including: · CAVLC · CABAC · spatial direct · temporal direct · stored and non-stored B-pictures · non-stored P-pictures · field pictures · picture AFF · MB-AFF · loop filter disabling · implicit and explict weighted prediction · constrained intra prediction · multiple slice groups with all map types · reference index re-ordering · adaptive picture buffering mode · direct 8x8 inference · macroblock-level QP selection (all QP values) Details of the bitstreams and the combinations of the features that are exercised by each one are available in the accompanying spreadsheet, an updated version of which is being maintained in the bitstream exchange FTP area. (...) An issue related to the bS value to be applied for chroma filtering of the left MB edge when the current macroblock pair is a frame pair and the left macroblock pair is a field pair. At issue is whether the bS value for chroma is derived from the top field luma bS, or if the strength is derived from the strength of luma filtering in the field of the same parity. According to the 8.7.2, when the filtering of a macroblock is done in field mode, the strength of the filtering of the chroma is derived from the strength of the filtering of the luma in the same field, which seems to be the interpretation used in bitstreams CAMA1_TOSHIBA_A and CVMA1_TOSHIBA_A, and those who have verified it.

Score: 821869.5 - https://www.itu.int/wftp3/av-a.../2003_09_SanDiego/JVT-I006.doc

  Microsoft Word - DGCA MID2-WP34 -FPP-GACA-English

Legal framework and how to work in the field of flight procedures design was developed under GACA Regulation section 23. 2.6. (...) Given the importance and sensitivity of the flight procedures design to maintain safety and to gain time for airlines while preserving the environment and the follow-up of the global developments, there must be commitment to ensuring compliance with the rules and recommendations of the ICAO in this field, in addition to cooperate and exchange of experiences between the countries of the Middle East in the field of flight procedures design. (...) Saudi Arabia proposes to establish a working group to coordinate efforts in the field of flight procedures design and standardization of the regulation in the Middle East, especially in relation to the visibility (VIS/RVR) and the exchange of information and database. 4.2.

Score: 819950.8 - https://www.icao.int/MID/Docum...nts/2013/dgca_mid2/WP34_en.pdf

  Report on the measur

Report on the measures undertaken during 2017 in order to implement UN General Assembly Resolution 72/28 “Role of science and technology in the context of international security and disarmament” The Ministry of Defense (MoD) and the Armed Forces of Montenegro (MNEAF) use certain scientific achievements and primarily information and communication technologies which have a purpose and role in the field of improvement of both national and international security, and to a lesser extent to the processes of disarmament and arms control policies. (...) Cooperation will be accomplished through expert consultations, research projects, experimental fuel use, testing, evaluation and certification of use, as well as through continuous dialogue and exchange of information in this scientific field with the aim of future development and modernization of warships. Since MNEAF does not possess chemical, biological, nuclear weapons or conventional weapons whose application can cause enormous or indiscriminate casualties or harmful effects, there is no need for development, scientific research or the procurement of technologies used in this field. General scientific achievements or technologies are used in the field of disarmament and related technological processes, as well as in the field of safeguarding, storage, destruction and arms control and military equipment, whose application is laid down in internal instructions (Guidance on Warehouse Operations and the Instructions for Disposal of Lethal Means).

Score: 818541.26 - https://www.un.org/disarmament...uploads/2018/08/Montenegro.pdf

  MET SG/6-WP/02 15/02

MET SG/6-WP/02 15/02/2016 International Civil Aviation Organization MIDANPIRG Meteorology Sub-Group Sixth Meeting (MET SG/6) (Cairo, Egypt, 1 - 3 March 2016) Agenda Item 2: Follow-up on MIDANPIRG/15 Conclusions and Decisions relevant to the MET Field STATUS OF MIDANPIRG/15 CONCLUSIONS AND DECISIONS RELEVANT TO THE MET FIELD (Presented by the Secretariat) SUMMARY This paper provides a status of MIDANPIRG/15 Conclusions and Decisions relevant to the MET field. (...) INTRODUCTION 1.1 The meeting will recall MIDANPIRG/15 (8-11 June 2015, Bahrain) adopted 4 Conclusions and 3 Decisions that were at least in part related to the MET field. A status of these Conclusions and Decisions is provided at Appendix A. 2. (...) The status of implementation in detail will be provided in Agenda Item 4.3, Review of requirements for OPMET data and status of OPMET data exchange as well as the status of implementation of Regional OPMET Centre (ROC) Jeddah and back-up ROC Bahrain. 2.5 With reference to MIDANPIRG Conclusion 15/35, Air Navigation Deficiencies, deficiencies identified in the MET field will be addressed in Agenda Item 5, Review of air navigation deficiencies in the MET field. 3.

Score: 813825.1 - https://www.icao.int/MID/Documents/2016/MET%20SG6/WP%202.pdf

  Edition : 0.18

Edition : 0.23 Working Draft Page 3 SUR.ET1.ST05.2000-STD-12-01 Surveillance Data Exchange - Part 12 ADS-B Messages 3.2 Acronyms and Abbreviations For the purposes of this Eurocontrol Document, the following shall apply: ° Degree (angle) ADS-B Automatic Dependent Surveillance - Broadcast ASTERIX All Purpose STructured Eurocontrol suRveillance Information EXchange CAT Data Category EATMP European Air Traffic Management Programme FRN Field Reference Number FSPEC Field Specification FX Field Extension Indicator ICAO International Civil Aviation Organization LEN Length Indicator LSB Least Significant Bit PSR Primary Surveillance Radar RE Reserved Expansion Indicator REP Field Repetition Indicator s second, unit of time SAC System Area Code SDPS Surveillance Data Processing System SIC System Identification Code SP Special Purpose Indicator SSR Secondary Surveillance Radar STFRDE Surveillance Task Force on Radar Data Exchange SURT Surveillance Team (EATMP) UAP User Application Profile (see Definitions ) UTC Co-ordinated Universal Time WGS-84 World Geodetic System 84 Page 4 Working Draft Edition : 0.23 Surveillance Data Exchange - Part 12 ADS-B Messages SUR.ET1.ST05.2000-STD-12-01 4 GENERAL PRINCIPLES 4.1 General This document describes the application of ASTERIX to ADS-B target reports. 4.2 Time Management The time-stamping shall comply with ICAO Annex 5. 4.3 Unused Bits in Data Items Decoders of ASTERIX data shall never assume and rely on specific settings of spare or unused Bits. (...) Format : Compound data item consisting of a one byte primary sub-field, followed by up to four fixed length data fields. (...) Table 2 – ADS-B Messages UAP FRN Data Item Information Length 1 I021/010 Data Source Identification 2 2 I021/040 Target Report Descriptor 1+ 3 I021/030 Time of Day 3 4 I021/130 Position in WGS-84 co-ordinates 6 5 I021/080 Target Address 3 6 I021/140 Geometric Altitude 2 7 I021/090 Figure of Merit 2 FX - Field extension indicator - 8 I021/210 Link technology 1 9 I021/230 Roll Angle 2 10 I021/145 Flight Level 2 11 I021/150 Air Speed 2 12 I021/151 True Air Speed 2 13 I021/152 Magnetic Heading 2 14 I021/155 Barometric Vertical Rate 2 FX - Field extension indicator - 15 I021/157 Geometric Vertical Rate 2 16 I021/160 Ground Vector 4 17 I021/165 Rate of Turn 1+ 18 I021/170 Target Identification 6 19 I021/095 Velocity Accuracy 1 20 I021/032 Time of day accuracy 1 21 I021/200 Target Status 1 FX - Field extension indicator - 22 I021/020 Emitter Category 1 23 I021/220 Met report 1+ 24 I021/146 Intermediate State Selected Altitude 2 25 I021/148 Final State Selected Altitude 2 26 I021/110 Trajectory Intent 1+N*15 27 - Spare bits set to zero - 28 - Spare bits set to zero - FX - Field extension indicator - 29 - Spare bits set to zero - 30 - Spare bits set to zero - 31 - Spare bits set to zero - 32 - Spare bits set to zero - 33 - Spare bits set to zero - 34 RE Reserved Expansion Field 1+ 35 SP Special Purpose Field 1+ FX - Field extension indicator - In the above table Page 32 Working Draft Edition : 0.23 Surveillance Data Exchange - Part 12 ADS-B Messages SUR.ET1.ST05.2000-STD-12-01 • the first column indicates the Field Reference Number (FRN) associated to each Data Item used in the UAP; • the fourth column gives the format and the length of each item, a stand-alone figure indicates the octet-count of a fixed-length Data Item, 1+ indicates a variable-length Data Item comprising a first part of 1 octet followed by n-octets extents as necessary.

Score: 813487.9 - https://www.icao.int/NACC/Docu...0CAT%2021%20ADS%20Messages.pdf

  MET SG/4-WP/5 30/05/

For both types the WMO AHL shall be decomposed into the following fields. Each field shall be recorded in the corresponding field of the output file(s). (...) Each report shall be decomposed into the following fields. Each field shall be recorded in the corresponding field of the output file(s). (...) The Destination Address field is the last field does not have a fixed length.

Score: 813041.4 - https://www.icao.int/MID/Documents/2013/met%20sg4/WP05.pdf