Standardised Event Reporting Syntax Sample Clauses

Standardised Event Reporting Syntax. In order to work across server software boundaries, a simple string is defined which needs to contain all the required information about a tick, and which can optionally contain more information if a federation wants to send that additional information. The basic format is: F-TICKS/eduroam/1.0#REALM=%R#VISCOUNTRY=LU# CSI=%{Calling-Station-Id}#RESULT=OK# The # character does not typically appear in eduroam realms or Calling-Station-Id information, and is suited as a field separator. The information contained in this string is not the absolute minimum required for logging in purposes. It exceeds the minimum in two ways: • The REALM field as used in the authentication (for example “@▇▇▇▇▇▇▇▇▇.▇▇”) contains the user’s country of origin and the institution of origin. • The Calling-Station-Id Field contains the full MAC address of a user’s device. This extra information may be considered privacy-invading by some national operators. In these cases, it is suggested that senders of the tick do the following: • Replace institution information with the string “undisclosed”. In the example above, “▇▇▇▇▇▇▇▇▇.▇▇” becomes “▇▇▇▇▇▇▇▇▇▇▇.▇▇”. • Garble the second half of the Calling-Station-Id by hashing it in a one-way manner. It is important that the same MAC address results in the same garbled string since the Calling-Station-Id field is used for extraction of the roaming days figure. The reason for suggesting that the first half of the MAC address is untouched is because that part of the MAC address can, in any case, be used to generate service-relevant data (the distribution of hardware vendors in the eduroam user base). With the information contained in the basic format, F-Ticks can collate the same statistics as the status quo system. This is sufficient for international roaming statistics. If a participant wants to generate more detailed statistics for his national branch, the participant can optionally let F-Ticks generate more detailed statistics by providing national roaming details as an optional parameter. The string then looks like the following: F-TICKS/eduroam/1.0#REALM=%R#VISCOUNTRY=LU#VISINST=SP-Name#CSI=%{Calling- Station-Id}#RESULT=OK# Note the additional parameter VISINST (visited institution). Also note that if a participant wants these fine-grained intra-country statistics, it makes less sense to obscure the realm, since the extra granularity of statistics requires the full user institution name to be present. The string format is considered to be suff...
View Source

Related to Standardised Event Reporting Syntax

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Adverse Events Subsequent to the date hereof, there shall not have occurred any of the following: (i) a suspension or material limitation in trading in securities generally on the New York Stock Exchange, the NASDAQ National Market or the NASDAQ Global Market, (ii) a general moratorium on commercial banking activities in the People’s Republic of China or New York, (iii) the outbreak or escalation of hostilities involving the United States or the People’s Republic of China or the declaration by the United States or the People’s Republic of China of a national emergency or war if the effect of any such event specified in this clause (iii) in your reasonable judgment makes it impracticable or inadvisable to proceed with the public offering or the delivery of the Shares on the terms and in the manner contemplated in the Prospectus, or (iv) such a material adverse change in general economic, political, financial or international conditions affecting financial markets in the United States or the People’s Republic of China having a material adverse impact on trading prices of securities in general, as, in your reasonable judgment, makes it impracticable or inadvisable to proceed with the public offering of the Shares or the delivery of the Shares on the terms and in the manner contemplated in the Prospectus.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Fund Valuation and Financial Reporting Services (1) Account for Fund share purchases, sales, exchanges, transfers, dividend reinvestments, and other Fund share activity as reported by the Fund’s transfer agent on a timely basis. (2) Apply equalization accounting as directed by the Fund. (3) Determine net investment income (earnings) for the Fund as of each valuation date. Account for periodic distributions of earnings to shareholders and maintain undistributed net investment income balances as of each valuation date. (4) Maintain a general ledger and other accounts, books, and financial records for the Fund in the form as agreed upon. (5) Determine the net asset value of the Fund according to the accounting policies and procedures set forth in the Fund’s current prospectus. (6) Calculate per share net asset value, per share net earnings, and other per share amounts reflective of Fund operations at such time as required by the nature and characteristics of the Fund. (7) Communicate to the Fund, at an agreed upon time, the per share net asset value for each valuation date. (8) Prepare monthly reports that document the adequacy of accounting detail to support month-end ledger balances. (9) Prepare monthly security transactions listings.

  • Progress Reporting a) RECIPIENT must satisfactorily demonstrate the timely use of funds by submitting payment requests and progress reports to ECOLOGY. ECOLOGY reserves the right to amend or terminate this Agreement if the RECIPIENT does not document timely use of funds. b) RECIPIENT must submit a progress report with each payment request. Payment requests will not be processed without a progress report. ECOLOGY will define the elements and frequency of progress reports. c) RECIPIENT shall use ECOLOGY’s provided progress report format. d) Quarterly progress reports will cover the periods from January 1 through March 31, April 1 through June 30, July 1 through September 30, and October 1 through December 31. Reports shall be submitted within thirty (30) days after the end of the quarter being reported. e) RECIPIENT must submit within thirty (30) days of the expiration date of the project, unless an extension has been approved by ECOLOGY, all financial, performance, and other reports required by the Agreement and funding program guidelines. RECIPIENT shall use the ECOLOGY provided closeout report format.