Message Instance Identifier Sample Clauses

Message Instance Identifier. The instance identifier shall uniquely identify every instance of a message of a given type. Instance identifiers are used by the system to keep streaming data coordinated, and to identify dropped messages of a given type at the application level. Instance identifier numbers shall not be reused unless other provisions for avoiding identifier ambiguity are provided in the message body.
AutoNDA by SimpleDocs

Related to Message Instance Identifier

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Act Identifier Title Shoulder note Iron Ore (Robe River) Agreement Xxx 0000 First Schedule Iron Ore (Robe River) Agreement Second Schedule First variation agreement Third Schedule Second variation agreement [s. 3B] Fourth Schedule Third variation agreement [s. 2] Fifth Schedule Fourth variation agreement Sixth Schedule Fifth variation agreement

  • Product Identification Before removal from Sale Area, unless Contracting Officer determines that circumstances warrant a written waiver or adjustment, Purchaser shall:

  • Client identification 9.1. The Company has the right to require the Client to confirm his/her registration information specified when opening a trading account. To do so, the Company may ask the Client at its own discretion and at any time to provide a notarized electronic copy of his/her identification document, bank statement or public utilities xxxx as a proof of residence. In particular cases, the Company may ask the Client to provide a photo of him/her holding his/her ID near his/her face. The detailed client identification requirements are set out in the “AML policies” section on the Company’s official site.

  • User Identification 6.2.5.1 Access to each Party’s corporate resources will be based on identifying and authenticating individual users in order to maintain clear and personal accountability for each user’s actions.

  • Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Your Member Identification Card Your BCBSRI member ID card is your key to getting healthcare coverage. It shows your healthcare provider that you’re part of the nation’s most trusted health plan. All BCBSRI members receive ID cards, which provide important information about your coverage. This card is for identification only, and you must show it whenever you receive healthcare services. Please note you must be a current member to receive covered services. Tips for keeping your card safe: • Carry it with you at all times. • Keep it in a safe location, just as you would with a credit card or money. • Let BCBSRI know right away if it is lost or stolen.

  • User ID and Password You will be assigned a personal User ID and a Password that you will use to obtain access to the Online Banking. You authorize us to follow any instructions entered through the Service using your User ID and Password. Because your User ID and Password can be used to access your Accounts and to access information about these Accounts, you should treat your User ID and Password with the same degree of care and secrecy that you use to protect your ATM security code and other sensitive financial data. We may ask you to change your User ID and Password from time to time for security reasons. You agree not to use any language that is abusive, harassing, libelous, defamatory, obscene, or threatening when defining your Password or any other personalization of your Accounts.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

Time is Money Join Law Insider Premium to draft better contracts faster.