Home

Results 21 - 30 of 295,784 for pointers. Search took 1.052 seconds.  
Sort by date/Sort by relevance
ETIR WEB SERVICES – MESSAGE I7 - RECORD DECLARATION DATA
Additional resources • eTIR XML schemas: wiki.unece.org/display/ED/Technical+artefacts • eTIR code lists: www.unece.org/fileadmin/DAM/trans/bcf/eTIR/documents/CodeLists0_4.pdf ECE/TRANS/WP.30/GE.1/2021/7 3 • List of eTIR focal points: www.unece.org/trans/bcf/etir/focals.html III. (...) Field list eTIR field name Mapping to the XML element (XPATH) Mandatory Format Code lists Conditions Rules WCO ID MESSAGE 75B ├ Message function, coded FunctionCode R n..2 CL16 017 ├ Message identifier ID R an..70 D014 ├ Type, coded TypeCode R an..3 CL26 D013 └┬ ADVANCETIRDATA Declaration R ├ Message function, coded Declaration/FunctionCode R n..2 CL16 017 ├ Functional reference Declaration/FunctionalReferenceID D an..70 C008 D026 ├ Message Identifier Declaration/ID R an..70 D014 ├ Issuing date Declaration/IssueDateTime R an..35 D011 ├ Type, coded Declaration/TypeCode R an..3 CL26 D013 ├ Version Declaration/VersionID R an..9 383 ├ Total gross weight Declaration/TotalGrossMassMeasure O n..16,6 131 ├┬ ADDITIONALINFORMATION Declaration/AdditionalInformation D C008 03A │├ Heavy and bulky goods indicator Declaration/AdditionalInformation/StatementCode R an..17 CL14 226 │└ Remarks Declaration/AdditionalInformation/StatementDescription O an..512 225 ├┬ AGENT Declaration/Agent O 05A E C E /T R A N S /W P .3 0 /G E .1 /2 0 2 1 /7 9 eTIR field name Mapping to the XML element (XPATH) Mandatory Format Code lists Conditions Rules WCO ID │├ Name Declaration/Agent/Name D an..70 C001 R003 │├ Code Declaration/Agent/ID D an..35 C001 R004 │└ Role, coded Declaration/Agent/RoleCode R an..3 CL02 R005 ├┬ AMENDMENT Declaration/Amendment D C008 06A │├ Amendment code Declaration/Amendment/ChangeReasonCode R an..3 CL17 099 │└┬ POINTER Declaration/Amendment/Pointer R 97A │ ├ Sequence number Declaration/Amendment/Pointer/SequenceNumeric R n..5 006 │ └ Location Declaration/Amendment/Pointer/Location R an..512 512 ├┬ SUBCONTRACTOR Declaration/Carrier O 18A │├ Name Declaration/Carrier/Name D an..70 R011 │├ Code Declaration/Carrier/ID D an..35 R012 │└┬ ADDRESS Declaration/Carrier/Address D 04A │ ├ City name Declaration/Carrier/Address/CityName R an..35 241 │ ├ Country, coded Declaration/Carrier/Address/CountryCode R a2 CL04 242 │ ├ Street and number/P.O. (...) The value should be "1" if the goods are considered by the customs as "heavy or bulky" or "0" otherwise │└ Remarks Declaration/AdditionalInformation/StatementDescripti on Text used to allow for remarks to the declaration from the TIR Carnet holder The value contains the remarks to the declaration from the transporter, or remains blank if there are none ├┬ AGENT Declaration/Agent Class representing the potential agent which would declare the goods on behalf of the TIR Carnet holder │├ Name Declaration/Agent/Name Name of the agent The value should be the official company name, or the first and last name of the person in case of physical person, to allow for quick identification │├ Code Declaration/Agent/ID Unique identifier of the agent The value should be the unique identifier of the agent │└ Role, coded Declaration/Agent/RoleCode Code of the role of the agent The value should be the code matching the role of the agent from 4 www.unece.org/fileadmin/DAM/trans/bcf/eTIR/documents/CodeLists0_4.pdf#page=134 E C E /T R A N S /W P .3 0 /G E .1 /2 0 2 1 /7 2 0 eTIR field name Mapping to the XML element (XPATH) Description Usage the list Party role code (UN/EDIFACT 3035)5 ├┬ AMENDMENT Declaration/Amendment List of potential amendments to the declaration │├ Amendment code Declaration/Amendment/ChangeReasonCode Code describing the type of amendment The value should be the code matching the type of amendment from the list Amendment code (eTIR) (www.unece.org/fileadmin/DAM/tr ans/bcf/eTIR/documents/CodeLists 0_4.pdf#page=121) │└┬ POINTER Declaration/Amendment/Pointer Pointer to the part of the declaration to be amended │ ├ Sequence number Declaration/Amendment/Pointer/SequenceNumeric Index of the pointer in the list The value should be the index (1- based) of the pointer in the list │ └ Location Declaration/Amendment/Pointer/Location Referred message section to be amended The value should be the XPATH expression pointing towards the section of the message to the amended ├┬ SUBCONTRACTOR Declaration/Carrier Class representing the potential agent which undertakes or arranges transport of goods between named points │├ Name Declaration/Carrier/Name Name of the subcontractor The value should be the official company name, or the first and last name of the person in case of physical person, to allow for quick identification │├ Code Declaration/Carrier/ID Unique identifier of the subcontractor The value should be the unique identifier of the subcontractor 5 www.unece.org/fileadmin/DAM/trans/bcf/eTIR/documents/CodeLists0_4.pdf#page=4 E C E /T R A N S /W P .3 0 /G E .1 /2 0 2 1 /7 2 1 eTIR field name Mapping to the XML element (XPATH) Description Usage │└┬ ADDRESS Declaration/Carrier/Address Class representing the physical address of the subcontractor │ ├ City name Declaration/Carrier/Address/CityName City name of the physical address of the subcontractor The value should be the city name of the physical address of the subcontractor │ ├ Country, coded Declaration/Carrier/Address/CountryCode Code of the country of the physical address of the subcontractor The value should be the code of the country of the physical address of the subcontractor from the list Country name code (ISO 3166-1- alpha-2)6 │ ├ Street and number/P.O.
Language:English
Score: 1095779.5 - https://daccess-ods.un.org/acc...TRANS/WP.30/GE.1/2021/7&Lang=E
Data Source: ods
DIALOGUE ON URBAN REALITIES: INNOVATIVE URBAN POLICIES AND LEGISLATION IN IMPLEMENTING THE HABITAT AGENDA AND ATTAINING THE MILLENNIUM DEVELOPMENT GOALS
Lessons learnt....................................................................................................................8 B. Pointers for the future........................................................................................................9 Discussion points ? (...) Section III brings together a number of lessons learnt and pointers for the future. II. Assessing effective urban policies and enabling legislation A. (...) III. Lessons learnt and pointers for the future A. Lessons learnt 30.
Language:English
Score: 1095701.1 - daccess-ods.un.org/acce...get?open&DS=HSP/WUF/2/3&Lang=E
Data Source: ods
CONCRETE AMENDMENT PROPOSALS
The first prerequisite to allow such notification mechanism, is to ensure that the information on adjacent border crossing points is adequately registered in ITDB for all countries having enabled the eTIR procedure on their territory. 9. (...) TRN). (c) The class Pointer would be included (with cardinality 0..1) to allow the translation to point as the element which is translated. Its status would be dependant (D) and the following condition should be added: IF statementType,coded =”TRN THEN NOT EMPTY (POINTER) 13. As an example, if the description of the goods of the first consignment item of the first consignment is provided in English as “Apples”, its translation in French could be provided as follows: AditionalInformation Sequence = 1 Remark Text.Content = “Pommes” Language identifier = “FR” statementType,coded = “TRN” Pointer Location = “Message/Consignement[1]/ConsignementItem[1]/Goods/Decription 14.
Language:English
Score: 1095528.6 - https://daccess-ods.un.org/acc.../WP.30/AC.2/TIB/2022/12&Lang=E
Data Source: ods
ETIR REFERENCE MODEL V.4.1A
The Reference Model will be expanded and refined as the work progresses and as feedback is received from modelling work carried out by the Informal ad hoc Expert Group on Conceptual and Technical Aspects of Computerization of the TIR Procedure (GE.1) and the network of eTIR focal points. United Nations ECE/TRANS/WP.30/2011/4/Rev.1 Economic and Social Council Distr.: General 25 November 2014 Original: English ECE/TRANS/WP.30/2011/4/Rev.1 2 Contents Page Introduction............................................................................................................................................... 12 a. (...) Analysis workflow ........................................................................................................................... 124 3.1 Activity Analysis ..................................................................................................................... 124 3.1.1 Sequence diagrams .................................................................................................... 124 3.1.1.1 Management by Customs of data on guarantees ....................................... 125 3.1.1.1.1 Register/update guarantee chain information ........................ 125 3.1.1.1.2 Register guarantee ................................................................. 126 3.1.1.1.3 Cancel guarantee ................................................................... 127 3.1.1.1.4 Accept guarantee ................................................................... 128 3.1.1.1.5 Get holder information .......................................................... 128 3.1.1.1.6 Get guarantee information ..................................................... 129 3.1.1.1.7 Query guarantee .................................................................... 129 ECE/TRANS/WP.30/2011/4/Rev.1 7 3.1.1.2 Data exchange ........................................................................................... 130 3.1.1.2.1 Record consignment information .......................................... 130 3.1.1.2.2 Update consignment information .......................................... 132 3.1.1.2.3 Start of TIR operation ............................................................ 133 3.1.1.2.4 Terminate TIR operation ....................................................... 134 3.1.1.2.5 Discharge TIR operation ....................................................... 135 3.1.1.2.6 Notify guarantee chain .......................................................... 136 3.1.1.2.7 Notify subsequent countries .................................................. 136 3.1.1.2.8 Advance cargo information ................................................... 137 3.1.2 Fall-back scenarios .................................................................................................... 137 3.1.2.1 Management by Customs of data on guarantees ....................................... 138 3.1.2.1.1 Register guarantee ................................................................. 138 3.1.2.1.2 Cancel guarantee ................................................................... 138 3.1.2.1.3 Accept guarantee ................................................................... 139 3.1.2.1.4 Get holder information .......................................................... 139 3.1.2.1.5 Query guarantee .................................................................... 140 3.1.2.2 Data exchange ........................................................................................... 141 3.1.2.2.1 Record consignment information .......................................... 141 3.1.2.2.2 Update consignment information .......................................... 142 3.1.2.2.3 Start of TIR operation ............................................................ 142 3.1.2.2.4 Terminate TIR operation ....................................................... 143 3.1.2.2.5 Discharge TIR operation ....................................................... 144 3.1.2.2.6 Notify guarantee chain .......................................................... 144 3.1.2.2.7 Notify subsequent countries .................................................. 144 3.1.2.2.8 Advance cargo information ................................................... 145 3.2 Data Analysis ........................................................................................................................... 145 3.2.1 Management by Customs of data on guarantees class diagram ................................ 145 3.2.2 Declaration class diagram ......................................................................................... 146 3.2.3 TIR operations class diagram .................................................................................... 147 3.2.4 Lists of electronic messages ...................................................................................... 149 3.2.4.1 External messages ..................................................................................... 149 3.2.4.2 Internal messages ...................................................................................... 150 3.2.5 Electronic messages data elements ........................................................................... 151 3.2.5.1 Classes (English Only) .............................................................................. 151 3.2.5.1.1 External messages ................................................................. 151 3.2.5.1.2 Internal messages .................................................................. 154 3.2.5.2 Classes and attributes (English Only) ....................................................... 159 3.2.5.2.1 External messages ................................................................. 159 3.2.5.2.2 Internal messages .................................................................. 177 ECE/TRANS/WP.30/2011/4/Rev.1 8 3.2.5.3 Message details (English Only) ................................................................. 210 3.2.5.3.1 External messages ................................................................. 210 3.2.5.3.2 Internal messages .................................................................. 259 3.2.6 Conditions and rules .................................................................................................. 340 3.2.6.1 Conditions ................................................................................................. 340 3.2.6.2 Rules ......................................................................................................... 341 3.2.7 Overview of Changes ................................................................................................ 341 3.2.7.1 E1 – Register guarantee............................................................................. 341 3.2.7.2 E2 – Register results .................................................................................. 342 3.2.7.3 E3 – Cancel guarantee ............................................................................... 342 3.2.7.4 E4 – Cancellation results ........................................................................... 342 3.2.7.5 E5 – Query guarantee ................................................................................ 343 3.2.7.6 E6 – Query results ..................................................................................... 343 3.2.7.7 E7 – Notify guarantee chain ...................................................................... 344 3.2.7.8 E8 – Notification confirmation ................................................................. 345 3.2.7.9 E9 – Advanced cargo information............................................................. 345 3.2.7.10 E10 – Advanced Cargo Information Results ............................................. 346 3.2.7.11 I1 – Accept guarantee ................................................................................ 347 3.2.7.12 I2 – Acceptance results ............................................................................. 347 3.2.7.13 I3 – Get holder information ....................................................................... 347 3.2.7.14 I4 – Holder information............................................................................. 347 3.2.7.15 I5 – Query guarantee ................................................................................. 348 3.2.7.16 I6 – Query results ...................................................................................... 348 3.2.7.17 I7 – Record advanced cargo Information .................................................. 351 3.2.7.18 I8 – Record advanced cargo information results ....................................... 353 3.2.7.19 I9 – Start TIR operation ............................................................................ 353 3.2.7.20 I10 – Start results ...................................................................................... 354 3.2.7.21 I11 – Terminate TIR operation .................................................................. 355 3.2.7.22 I12 – Termination results .......................................................................... 356 3.2.7.23 I13 – Discharge TIR operation .................................................................. 356 3.2.7.24 I14 – Discharge results .............................................................................. 357 3.2.7.25 I15 – Notify Customs ................................................................................ 357 3.2.7.26 I16 – Notification confirmation ................................................................. 359 3.2.8 Code lists ................................................................................................................... 359 3.2.8.1 List of code lists ........................................................................................ 359 3.2.8.2 CL01 – Equipment size and type description code ................................... 362 3.2.8.3 CL02 – Party role code ............................................................................. 365 3.2.8.4 CL03 – Item type identification code ........................................................ 405 3.2.8.5 CL04 – Country name code ...................................................................... 413 ECE/TRANS/WP.30/2011/4/Rev.1 9 3.2.8.6 CL05 – Transport means description code ................................................ 421 3.2.8.7 CL06 – Document name code ................................................................... 439 3.2.8.8 CL07 – Package type description code ..................................................... 501 3.2.8.9 CL08 – Seal type code .............................................................................. 512 3.2.8.10 CL09 – Message sub types ........................................................................ 513 3.2.8.11 CL10 ......................................................................................................... 513 3.2.8.12 CL11 ......................................................................................................... 513 3.2.8.13 CL12 – Guarantee type code ..................................................................... 513 3.2.8.14 CL13 – Customs offices database ............................................................. 513 3.2.8.15 CL14 – Indicator ....................................................................................... 514 3.2.8.16 CL15 – International TIR database ........................................................... 514 3.2.8.17 CL16 – Message function code ................................................................. 514 3.2.8.18 CL17 – Amendment code ......................................................................... 519 3.2.8.19 CL18 – Message section code ................................................................... 519 3.2.8.20 CL19 – Pointer code .................................................................................. 519 3.2.8.21 CL20 – Language name code .................................................................... 519 3.2.8.22 CL21 – Measurement unit code ................................................................ 531 3.2.8.23 CL22 – Guarantee status ........................................................................... 599 3.2.8.24 CL23 – Holder status ................................................................................ 599 3.2.8.25 CL24 – Control result code ....................................................................... 599 3.2.8.26 CL25 – Control type code ......................................................................... 599 3.2.8.27 CL26 – Message types (eTIR) .................................................................. 599 3.2.8.28 CL99 – Error code ..................................................................................... 600 4. (...) Methodological aspects ........................................................................................ 765 VII.3.3.1. Function point analysis ............................................................................. 765 VII.3.3.2.
Language:English
Score: 1093509.2 - daccess-ods.un.org/acce...RANS/WP.30/2011/4/REV.1&Lang=E
Data Source: ods
When instantiated in an AN, they will be set to NULL unless they point to connection termination points within the transmission part of the AN. (...) The assocV5TimeSlot attribute points to the associated V5 time slot object instance. (...) The value of the unreliableResourcePointer points to a v5TimeSlot object instance. In the 'protected' case, the value of the v5ReliableResourcePointer points to a commChannel object instance.
Language:English
Score: 1090035.3 - https://www.itu.int/wftp3/Publ...tu-t/q/q824.5/1997/q824.5.html
Data Source: un
TECHNICAL DETAILS OF MESSAGE PAIR E9/E10
The following diagram summarizes this logic, that must be implemented in the holder system, for any need to update the advance data or the declaration data, in order to be properly processed by the national customs system: Figure II Update the advance TIR data or the declaration data (c) Communication of advance TIR data for a TIR Transport with multiple loading points 12. In case a holder plans to execute a TIR transport with multiple loading points, possibly in multiple customs territories (countries), advance TIR data must be communicated using an eTIR message (or any other electronic means authorized by the relevant customs authorities) to each and every of the customs authorities of the countries where goods will be loaded. 13. It is important to note that the “E9 – Advance TIR data” message is only intended for the initial customs office of departure and that this message should only contain consignments loaded at that first loading point. Consequently, the holder must then send an “E11 – Advance amendment data” message to each customs authority where additional ECE/TRANS/WP.30/GE.1/2021/46 4 loading points are located, to communicate the advance TIR data related to the consignments to be loaded at the corresponding additional loading points. 14. The following diagram illustrates the example of a TIR transport with three loading points happening in two different customs territories and the “E9 – Advance TIR data” and “E11 – Advance amendment data” messages required: Figure III Advance TIR data for multiple loading points 15.
Language:English
Score: 1083360.1 - https://daccess-ods.un.org/acc...RANS/WP.30/GE.1/2021/46&Lang=E
Data Source: ods
ETIR FUNCTIONAL SPECIFICATIONS, VERSION 4.3
Annex III contains the sequence of messages from the point of view of countries of departure, transit and destination. 1.1.1 Management by customs of data on guarantees 1.1.1.1 Register/update guarantee chain information Figure 1.1 Register/update guarantee chain information sequence diagram eTIR package::AC2 gc : Guarantee Chain New(guarantee chain) gt : GuaranteeType Update() eTIR Intranet [in case of new guarantee chain]: AddGuaranteeChain [in case of existing guarantee chain]: UpdateGuaranteeChain eTIR DB Call(NewGuaranteeChain) Results Confirmation Call(UpdateGuranteeChain) Results Confirmation & guaranteeTypes New(GuaranteeType) *[for each new guarantee type]: CreateGuaranteeType Call(AddGuaranteeType) Confirmation GetGuaranteeTypes() ReturnGuaranteeTypes Call(GetGuaranteeTypes) Results LinkGuaranteeType(GuaranteeType.Code) *[for each guarantee chain's new guarantee type]: LinkGuaranteeType Call(LinkGuaranteeType) Confirmation Insert() Update() Select() Insert() UnLinkGuaranteeType(GuaranteeType.Code) *[for each guarantee chain's removed guarantee type]: UnlinkGuaranteeType Call(UnlinkGuaranteeType) Insert() Delete() eTIR package::eTIR Admin Register/update guarantee chain info.
Language:English
Score: 1080894.3 - https://daccess-ods.un.org/acc...S/WP.30/AC.2/TIB/2022/4&Lang=E
Data Source: ods
-- Module ASN1CMLETypeModule (Q.824.5:10/1997) ASN1CMLETypeModule {itu-t(0) recommendation(0) q(17) ca(824) dot(127) v5interface(5) informationModel(0) asn1Module(2) cAV5LEModule(0)} DEFINITIONS IMPLICIT TAGS ::= BEGIN -- EXPORTS everything IMPORTS -- Recommendation M.3100 Failed, NameType, PointerOrNull, UserLabel FROM ASN1DefinedTypesModule {ccitt recommendation m gnm(3100) informationModel(0) asn1Modules(2) asn1DefinedTypesModule(0)} -- Recommendation X.711 AttributeId, ObjectClass, ObjectInstance FROM CMIP-1 {joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3)}; informationModel OBJECT IDENTIFIER ::= {itu-t(0) recommendation(0) q(17) ca(824) dot(127) v5interface(5) informationModel(0)} standardSpecificExtension OBJECT IDENTIFIER ::= {informationModel standardSpecificExtension(0)} managedObjectClass OBJECT IDENTIFIER ::= {informationModel managedObjectClass(3)} package OBJECT IDENTIFIER ::= {informationModel package(4)} nameBinding OBJECT IDENTIFIER ::= {informationModel nameBinding(6)} attribute OBJECT IDENTIFIER ::= {informationModel attribute(7)} action OBJECT IDENTIFIER ::= {informationModel action(9)} notification OBJECT IDENTIFIER ::= {informationModel notification(10)} initialPointer Pointer ::= null:NULL initialPointerS SET OF Pointer ::= {} ActingRole ::= ENUMERATED {balanced(0), master(1), slave(2), ... } AssocInstances ::= SET OF ObjectInstance BcReserved ::= SET OF OCTET STRING(SIZE (2)) BlockStatus ::= ENUMERATED {none(0), local(1), remote(2), both(3), ... } DataType ::= ENUMERATED {dsType(0), pType(1), fType(2), ... } D-ChannelActivation ::= ENUMERATED { deact(0), -- link deactivated act1(1), -- layer 1 maintained act2(2), -- layer 1 and 2 maintained ... } EnvelopeFunctionAddress ::= INTEGER(0..8191) Layer3PortAddress ::= INTEGER(0..65535) LinkId ::= OCTET STRING(SIZE (1)) LineSignalling ::= INTEGER {dtmf(0), -- push button pulse(1), -- rotary both(2)} LinkIdCheckResult ::= ENUMERATED { linkIdOk(0), linkIdNotOk(1), linkIdRejected(2), ... } NoOf ::= INTEGER ObjectPointer ::= SEQUENCE { objectClass [0] ObjectClass, objectInstance [1] ObjectInstance } Origin ::= ENUMERATED {localResource(0), remoteResource(1), manual(2), ... } OriginalPointer ::= Pointer OriginalPointerInfo ::= SEQUENCE { originalPointer1 OriginalPointer, originalPointer2 OriginalPointer } Pointer ::= PointerOrNull V5SupportedProtocolVersion ::= ENUMERATED {v5dot1(1), v5dot2(2), ... } ProvVariant ::= BIT STRING(SIZE (7)) ReciprocalPointersInfo ::= SEQUENCE { objectClass1 ObjectClass, objectInstance1 ObjectInstance, attribute1 AttributeId, objectClass2 ObjectClass, objectInstance2 ObjectInstance, attribute2 AttributeId } RejectedProvVariant ::= SEQUENCE { provVariant [0] ProvVariant, rejectionCause [1] RejectionCause } RejectionCause ::= ENUMERATED { variantUnknown(0), variantKnownNotReady(1), reprovisioningInProgress(2), ... } ReleaseReciprocalPointersResult ::= SEQUENCE { originalPointerInfo OriginalPointerInfo, result CHOICE {failed [0] Failed, released [1] NULL} } RequestRemoteProvVariantResult ::= SEQUENCE { remoteProvVariant [1] ProvVariant, remoteInterfaceId [2] OCTET STRING(SIZE (3)) } SetReciprocalPointersResult ::= SEQUENCE { originalPointerInfo OriginalPointerInfo, result CHOICE {failed [0] Failed, set [1] NULL} } SwitchOverToNewVariantResult ::= CHOICE { reprovisioningStarted [0] ProvVariant, cannotReprovision [1] RejectedProvVariant } Success ::= ENUMERATED {successful(0), unsuccessful(1), ... } SwitchType ::= ENUMERATED {manual(0), forced(1), automatic(2), ... } VerifyRemoteProvVariantInfo ::= ProvVariant VerifyRemoteProvVariantResult ::= CHOICE { readyForReprovisioning [0] ProvVariant, notReadyForReprovisioning [1] RejectedProvVariant } V5ChannelType ::= ENUMERATED {bearerChannel(0), commChannel(1), ... } V5Identification ::= OCTET STRING(SIZE (3)) V5ProtectionFailedSwitchInfo ::= ENUMERATED { noStandByCChannelsAvailable(0), targetCChannelNotOperational(1), targetCChannelNotProvisioned(2), protectionSwitchImpossible(3), protectionGroupMismatch(4), requestedAllocationExisting(5), targetCChannelActive(6), ... } V5ProtectionGroupNumber ::= ENUMERATED {group1(0), group2(1), ... } V5ProtectionGroupType ::= ENUMERATED {plus(0), colon(1), ... } V5ProtectionNoSwitchInfo ::= SEQUENCE { failedSwitchInfo [0] V5ProtectionFailedSwitchInfo, v5ProtectionSwitchInfo [1] V5ProtectionSwitchInfo } V5ProtectionSwitchInfo ::= SEQUENCE { origin Origin, switchType SwitchType, switchFrom ObjectInstance, switchTo ObjectInstance } V5ProtectionSwitchReportingInfo ::= CHOICE { switched [0] V5ProtectionSwitchInfo, failed [1] V5ProtectionNoSwitchInfo } V5UserPortAddress ::= CHOICE { single [0] Layer3PortAddress, multiple [1] EnvelopeFunctionAddress } YesNo ::= BOOLEAN END -- of ASN1CMLETypeModule -- Generated by Asnp, the ASN.1 pretty-printer of France Telecom R&D
Language:English
Score: 1079671 - https://www.itu.int/wftp3/Publ...997-TC1/ASN1CMLETypeModule.asn
Data Source: un
REFERENCE MODEL OF THE TIR PROCEDURE. CHAPTER 3, ANALYSIS : NOTE / BY THE SECRETARIAT
The eTIR website database replica becomes the main source of information for all Customs administrations until the eTIR international system is restored. At that point, the eTIR international database and the eTIR website database replica will be synchronized. 3.1.3.1.2. (...) The eTIR website database replica becomes the main source of information for all Customs administrations until the eTIR international system is restored. At that point, the eTIR international database and the eTIR website database replica will be synchronized. 3.1.3.1.4. (...) R Error 0 1 .. D Pointer 1 unbounded .. R Guarantee 1 1 .. R c.
Language:English
Score: 1078977.5 - daccess-ods.un.org/acce...TRANS/WP.30/GE.1/2010/2&Lang=E
Data Source: ods
In the CCA, acts such as unauthorized access, modification of contents and wrongful communication is addressed www.cmc.gov.my © Malaysian Communications and Multimedia Commission 11 Pointers for Slide # 4 Presently, approaches to network security has a “jurisdiction” flavor to it. (...) All complaints relating to network security matters will be passed to either the MCMC or/and the Police. www.cmc.gov.my © Malaysian Communications and Multimedia Commission 14 Pointers for Slide # 5 As it is, organizations in Malaysia lack the coordination process. This is a point of concern as it slows the development with regards to implementation of policies, information-sharing and creating awareness.
Language:English
Score: 1077223.3 - https://www.itu.int/osg/spu/ni...kshop/presentations/cni.19.pdf
Data Source: un