Home

  UN DESA | DPAD | UN System Task Team on the Post-2015 Development Agenda

UN DESA | DPAD | UN System Task Team on the Post-2015 Development Agenda Skip to main navigation Skip to content Skip to resources [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] Report of the UN System Task Team on the Post-2015 Development Agenda Realizing the Future We Want for All In its report  Realizing the Future We Want for All , the UN System Task Team on the Post-2015 UN Development Agenda lays out its main findings and recommendations for a development agenda beyond 2015. (...) Presentation Frequently Asked Questions Report: Arabic , Chinese , English , French , Russian , Spanish Executive Summary: Chinese , English , Russian , Spanish Key Recommendations: Chinese , English , Russian , Spanish <directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive]

Score: 419407.1 - https://www.un.org/en/developm...y/untaskteam_undf/report.shtml

  ____________________

Perišić of aiding and abetting the VRS crimes in Sarajevo and Srebrenica. 1. Specific Direction (a) Specific Direction as a Component of Aiding and Abetting Liability The Appeals Chamber recalls that the Trial Chamber concluded that specific direction is not an element of the actus reus of aiding and abetting. (...) Perišić was specifically directed aid to the VRS Crimes in Sarajevo and Srebrenica. (...) Perišić was directed towards the VRS’s general war effort rather than VRS crimes.

Score: 419278.9 - https://www.icty.org/x/cases/p...ic/acjug/en/130228_summary.pdf

  Microsoft Word - WP6.doc

Rep. of Congo ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Bukavu TWR Circuit Bukavu/Kigali 1996 Not implemented DR Congo, Rwanda A ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Kinshasa Circuit Brazzaville/Kinshasa DRC ASECNA A ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Gbadolite TWR Circuit Gbadolite/Bangui 2002 Not implemented Could be implemented via Brazzaville if a circuit Kinshasa/Gbadolite is available. DR Congo, ASECNA A ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Goma APP Circuit Goma/Bujumbura 1998 Not implemented DR Congo, Burundi A ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Goma APP Circuit Goma/Kigali 1998 Not implemented DR Congo, Rwanda A Eritrea ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Asmara ACC Circuit Asmara/ Addis Ababa 1998 The circuit has been disconnected To be restored. (...) NAFISAT Ethiopia, Eritrea 2007 U CNS/SG/3 – WP/6 5 State Name Requirements Facilities or Services Description of Deficiency Date first reported Comments on Deficiency Description of Corrective action Executing Body Target date for implementation Priority Ghana ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Accra ACC Circuit Accra/Kano 2009 Unserviceable To be restored AFISNET Ghana Nigeria A Congo ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Brazzaville ACC Circuit Accra/Brazzaville Unserviceable To be restored AFISNET GHANA ASECNA A Gabon ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Libreville ACC Accra/Libreville Unserviceable To be restored AFISNET Ghana ASECNA A Rwanda ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Kigali ACC Kigali/Kinshasa Unserviceable To be restored AFISNET Rwanda, DR Congo A Somalia ATS Direct Speech Circuits Plan, AFI/7 Rec. 9/9 Hargeisa APP Circuit Hargeisa/Djibouti 1998 Not implemented Implement LTF circuit Somalia, Djibouti A -------------------------------

Score: 419137.3 - https://www.icao.int/WACAF/Doc...G/SG/2010/CNS_SG3/Docs/wp6.pdf

  Présentation PowerPoint

Présentation PowerPoint THE NEW CLASSIFICATION – AEROPLANE DESIGN GROUP (ADG) direction générale de l’Aviation civile 1 OLS SYMPOSIUM 1.Rationale of the new classification direction générale de l’Aviation civile 2 OLS SYMPOSIUM Limits Surfaces and aircraft direction générale de l’Aviation civile 3 OLS SYMPOSIUM Comparable aircraft may imply different OLS.Highly different aircraft may imply the same surfaces. Code number may be inconsistent with the performances and size of aircraft Objectives Consistency with the performances and size of aircraft Need to provide surfaces matching aircraft operations and size. direction générale de l’Aviation civile 4 OLS SYMPOSIUM Objectives Consistency with the criterion of instrument procedures OES intend to establish the airspace where obstacles can affect all the intended operations, including instrument operations. direction générale de l’Aviation civile 5 Impact of obstacles on instrument procedures Design consistent with instrument procedures Criteria related to approach speed OLS SYMPOSIUM In the 70’s, the Aerodrome Reference Code Panel: Runway length requirements and approach speed are related Objectives Consistency with code number Readability of the new classification for aerodromes of given code Today or Tomorrow direction générale de l’Aviation civile 6 OLS SYMPOSIUM Aerodromes of code number X Aerodromes of code number N Very different ADGs Homogeneous ADGs Objectives Consistency with code number Consistency with the existing dimensions direction générale de l’Aviation civile 7 OLS SYMPOSIUM 2.The proposal direction générale de l’Aviation civile 8 OLS SYMPOSIUM The proposal 1. (...) Wingspan allows to tailor the width of surfaces to the size of aircraft. direction générale de l’Aviation civile 11 0 20 40 60 80 100 120 140 160 0 10 20 30 40 50 60 70 80 In d ic a te d a ir s p e e d a t th re s h o ld ( k t) Wingspan (m) Aeroplane design groups ADG I ADG IIA ADG IIB ADG IIC ADG III ADG IV ADG V OLS SYMPOSIUM The proposal Consistency with code number direction générale de l’Aviation civile 12 0 20 40 60 80 100 Code nb 1 Code nb 2 Code nb 3 Code nb 4 ADG + ADG = ADG - OLS SYMPOSIUM 3.Application direction générale de l’Aviation civile 13 OLS SYMPOSIUM Application direction générale de l’Aviation civile 14 OLS SYMPOSIUM Aeroplane reference code Expected aeroplanes Reference field length of the demanding aircraft Local factors Aeroplane design group Indicated airspeed at threshold of the demanding aircraft Traffic planning Application direction générale de l’Aviation civile 15 OLS SYMPOSIUM Aircraft type IAS at THR (kt) Wingspan (m) ADG Airbus 320-200 121-141 35+ IIC Boeing 737-200 121-141 35+ IIC ATR-42-300 91-121 24+ IIB ATR-72-201 91-121 27+ IIB CRJ 100, 200, 440, 700 121-141 20+ / 23+ IIC Cessna 120, 152, 162 0-91 9+ / 10+ I Cessna Citation CJ2, CJ3, CJ4 91-121 15+ IIB Dash 6 0-91 19+ I Dash 7 0-91 28+ IIA Dash 8 91-121 25+ / 27+ IIB Learjet 23, 24, 25, 28… 121-141 10+ IIC PA-28 0-91 9+ / 10+ I

Score: 419137.3 - https://www.icao.int/Meetings/...roplane_Design_Group_(ADG).pdf

  European Commission evaluates the Directive on retention of telecommunications data

The Directive established data retention as a response to urgent security challenges, following major terrorist attacks in Madrid in 2004 and in London in 2005. (...) Also, the Directive does not guarantee that data are stored, retrieved and used in full compliance with the right to privacy and protection of personal data, and this has led courts to annul the legislation transposing the Directive in some EU Member States. (...) The data must be retained for a minimum of six months to a maximum of two years (to be decided by the Member State in transposing the Directive into national laws). Data protection authorities have criticized the directive on the grounds that it does not provide adequate safeguards on how data are stored, accessed and used.

Score: 419137.3 - https://www.itu.int/net/itunews/issues/2011/03/45.aspx

  ATM/CNS Meeting Luan

AMS AFI/7 Rec. 9/12 Kinshasa FIR HF poor quality. 1998 Improve installations DR Congo U Selcal not available ATS Direct Speech Bukavu TWR Circuit Bukavu/Kigali 1996 Not implemented DR Congo, Rwanda A Circuits Plan, AFI/7 Rec. 9/9 ATS Direct Speech Gbadolite TWR Circuit 2002 Not implemented Could be DR Congo, ASECNA A Circuits Plan, AFI/7 Gbadolite/Bangui implemented via Rec. 9/9 Brazzaville if a circuit Kinshasa/Gbadolite is available. ATS Direct Speech Goma APP Circuit 1998 Not implemented DR Congo, Burundi U Circuits Plan, AFI/7 Goma/Bujumbura Rec. 9/9 ATS Direct Speech Goma APP Circuit Goma/Kigali 1998 Not implemented DR Congo, Rwanda U Circuits Plan, AFI/7 Rec. 9/9 ATS Direct Speech Kinshasa FIC Circuit 2002 Not implemented VSAT being DR Congo, Burundi 2003 A Circuits Plan, AFI/7 Kinshasa/Bujumbura implemented in Rec. 9/9 Bujumbura ATS Direct Speech Kinshasa FIC Circuit 1996 Not implemented VSAT NAFISAT in DR Congo, Uganda U Circuits Plan, AFI/7 Kinshasa/Entebbe project Rec. 9/9 P:\ATM-CNS-Luanda\Appendices\App-D-WP8.doc ATM/CNS Meeting Luanda Appendix D WP/8 4 StateName Requirements Facilities or Description of Date Comments on Description of Executing Body Target Priority Services Deficiency first Deficiency Corrective action date for reported implement ation ATS Direct Speech Kinshasa FIC Circuit 1996 Inmarsat phone VSAT NAFISAT in DR Congo, Sudan U Circuits Plan, AFI/7 Kinshasa/Khartoum available at Kinshasa project Rec. 9/9 ATS Direct Speech Kinshasa FIC Circuit 1996 Not implemented VSAT SADC DR Congo, Rwanda U Circuits Plan, AFI/7 Kinshasa/Kigali operational in Rec. 9/9 Kinshasa, also in project in Rwanda Navaids AFI/7, Rec. (...) Dakar AFTN centre Circuit Dakar/Bissau 1998 Not implemented VSAT planned ASECNA, Guinea U 9/7 Bissau ATS Direct Speech Dakar ACC/FIC Circuit Dakar/Algiers 1998 PSTN in use VSAT planned ASECNA, Algeria 2002 A Circuits Plan, AFI/7 Rec. 9/9 ATS Direct Speech Dakar ACC/FIC Circuit 2003 Not implemented To implement ASECNA U Circuits Plan, AFI/7 Dakar/Rochambeau Rec. 9/9 ATS Direct Speech Dakar ACC/FIC Circuit Dakar/Bissau 1998 Not implemented VSAT being ASECNA, Guinea U Circuits Plan, AFI/7 considered Bissau Rec. 9/9 South Africa AFTN Plan, AFI Rec.

Score: 418952.83 - https://www.icao.int/WACAF/Doc...G/2003/ATM-CNS/wp08appd_en.pdf

  Decision on prosecution's motions for order striking appellant's notice of appeal and appeal brief a

IT-03-68-A, Decision on Prosecution's Motion for an Order Striking Defence Notice of Appeal and Requiring Refiling, 3 October 2006, p. 4. 13 See also Practice Direction on Procedure, para. 5. 14 See Appeal Brief, p. 93. 15 See Practice Direction on Procedure, para. 8, providing that Paragraph (C)(2) of the Practice Direction on Length afplieHo filings under Rule 77 of the Rules. 1 See Practice Direction on Length, para. 7. 17 Section III of the Practice Direction on Procedure including Paragraphs 4 and 5 applies to final decisions of a Trial Chamber under Rule 77. (...) Pursuant to Paragraph 5 of the Practice Direction on Procedure, the Appeal Brief was due on 2 September 2009. (...) However, due to its imprecise wording, it is not entirely clear whether Submission 280 refers to the latest version of the Practice Direction on Procedure or to the latest version of the Practice Direction on Length which is also dated 16 September 2005. 19 See also Practice Direction on Formal Requirements, para. 11. 20 See Rule 116 bis(A) of the Rules.

Score: 418868.1 - https://www.icty.org/x/cases/c...mpt_seselj/acdec/en/091216.pdf

  <i>Copyright in the Digital Single Market</i>: a taster

Article-by-Article Commentary to the Provisions of Directive 2019/790 (Oxford University Press, 2021). (...) This has been the case, among others, of the InfoSoc Directive 2001/29 and the Enforcement Directive 2004/48 . (...) In 2016, a proposal for a DSM Directive was unveiled. After three years of intense negotiations, the DSM Directive was adopted in spring 2019.

Score: 418868.1 - https://www.wipo.int/wipo_maga...e/en/2021/04/article_0009.html

  IN-CS-1-Operations (Q.1218:10/1995)

The operation initializes the specified -- counters in the SSF. activityTest OPERATION ::= {RETURN RESULT TRUE CODE op-activityTest } -- Direction: SCF -> SSF, Timer: Tat -- This operation is used to check for the continued existence of a relationship between the SCF -- and SSF. (...) Use of this operation by the SCF to gap queries and updates at the SDF is for further study. callInformationReport OPERATION ::= { ARGUMENT CallInformationReportArg RETURN RESULT FALSE CODE op-callInformationReport } -- Direction: SSF -> SCF, Timer: Tcirp -- This operation is used to send specific call information for a single call to the SCF as requested by the -- SCF in a previous CallInformationRequest. callInformationRequest OPERATION ::= { ARGUMENT CallInformationRequestArg RETURN RESULT FALSE ERRORS { missingParameter | parameterOutOfRange | requestedInfoError | systemFailure | taskRefused | unexpectedComponentSequence | unexpectedDataValue | unexpectedParameter } CODE op-callInformationRequest } -- Direction: SCF -> SSF, Timer: Tcirq -- This operation is used to request the SSF to record specific information about a single call and report it to -- the SCF (with a CallInformationReport operation). cancel OPERATION ::= { ARGUMENT CancelArg RETURN RESULT FALSE ERRORS { cancelFailed | missingParameter | taskRefused } CODE op-cancel } -- Direction: SCF -> SSF, or SCF -> SRF, Timer: Tcan -- This generic operation cancels the correlated previous operation or all previous requests. (...) Refer to clause 3 for a description of the procedures associated with this operation. eventNotificationCharging OPERATION ::= { ARGUMENT EventNotificationChargingArg RETURN RESULT FALSE CODE op-eventNotificationCharging } -- Direction: SSF -> SCF, Timer: Tenc -- This operation is used by the SSF to report to the SCF the occurrence of a specific charging event -- type as previously requested by the SCF in a RequestNotificationChargingEvent operation. eventReportBCSM OPERATION ::= { ARGUMENT EventReportBCSMArg RETURN RESULT FALSE CODE op-eventReportBCSM } -- Direction: SSF -> SCF, Timer: Terb -- This operation is used to notify the SCF of a call-related event (e.g.

Score: 418792 - https://www.itu.int/wftp3/Publ...8/1995/IN-CS-1-Operations.html

  -- Module IN-CS-1-Op

The operation initializes the specified -- counters in the SSF. activityTest OPERATION ::= {RETURN RESULT TRUE CODE op-activityTest } -- Direction: SCF -> SSF, Timer: Tat -- This operation is used to check for the continued existence of a relationship between the SCF -- and SSF. (...) Use of this operation by the SCF to gap queries and updates at the SDF is for further study. callInformationReport OPERATION ::= { ARGUMENT CallInformationReportArg RETURN RESULT FALSE CODE op-callInformationReport } -- Direction: SSF -> SCF, Timer: Tcirp -- This operation is used to send specific call information for a single call to the SCF as requested by the -- SCF in a previous CallInformationRequest. callInformationRequest OPERATION ::= { ARGUMENT CallInformationRequestArg RETURN RESULT FALSE ERRORS {missingParameter | parameterOutOfRange | requestedInfoError | systemFailure | taskRefused | unexpectedComponentSequence | unexpectedDataValue | unexpectedParameter} CODE op-callInformationRequest } -- Direction: SCF -> SSF, Timer: Tcirq -- This operation is used to request the SSF to record specific information about a single call and report it to -- the SCF (with a CallInformationReport operation). cancel OPERATION ::= { ARGUMENT CancelArg RETURN RESULT FALSE ERRORS {cancelFailed | missingParameter | taskRefused} CODE op-cancel } -- Direction: SCF -> SSF, or SCF -> SRF, Timer: Tcan -- This generic operation cancels the correlated previous operation or all previous requests. (...) Refer to clause 3 for a description of the procedures associated with this operation. eventNotificationCharging OPERATION ::= { ARGUMENT EventNotificationChargingArg RETURN RESULT FALSE CODE op-eventNotificationCharging } -- Direction: SSF -> SCF, Timer: Tenc -- This operation is used by the SSF to report to the SCF the occurrence of a specific charging event -- type as previously requested by the SCF in a RequestNotificationChargingEvent operation. eventReportBCSM OPERATION ::= { ARGUMENT EventReportBCSMArg RETURN RESULT FALSE CODE op-eventReportBCSM } -- Direction: SSF -> SCF, Timer: Terb -- This operation is used to notify the SCF of a call-related event (e.g.

Score: 418792 - https://www.itu.int/wftp3/Publ...18/1995/IN-CS-1-Operations.asn