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).
User Content 13.1 The Site permits the submission and posting of questions and answers in connection with Evaluation Processes and may also permit the submission and posting of other text and/or other content submitted by you and other users (all of the foregoing, collectively, “User Submissions”), and the hosting, sharing, and/or publishing of such User Submissions. You understand that whether or not such User Submissions are published, the Company does not guarantee any confidentiality with respect to any User Submissions. You acknowledge that you shall not be due any remuneration in connection with your User Submissions from the Company or from any other User. 13.2 You shall be solely responsible for your own User Submissions and the consequences of posting or publishing them. In connection with your User Submissions, you affirm, represent, and/or warrant that: (i) your submission of User Submissions and the publication and use thereof by the Company does not violate the copyrights, trade secrets rights or other intellectual property rights of any third party, nor shall it constitute or result in a breach of any duty or obligation of confidentiality owed by you to any third party, and (ii) you have the written consent, release, and/or permission of each and every identifiable individual person in the User Submission to use the name or likeness of each and every such identifiable individual person to enable inclusion and use of the User Submissions in the manner contemplated by the Company and this Agreement. 13.3 By submitting User Submissions to the Site, you hereby grant to the Company a perpetual, irrevocable, worldwide, royalty-free, transferable, sublicensable right and license to use, reproduce, modify, distribute and exploit such User Submission in any manner and in any form of media, whether currently or hereafter existing. You represent and warrant that you have all necessary right, title and interest in and to each such User Submission to validly grant such license to the Company. 13.4 In connection with User Submissions and any other transmission of messages or material facilitated by the Site, you further agree that you will not: (i) submit or transmit material that is not authorized by the copyright owner, protected by trade secret or otherwise subject to third party proprietary rights, including privacy and publicity rights, unless you are the owner of such rights or have permission from their rightful owner to post the material and grant the rights granted to the Company in Section 13.3 above; (ii) publish or transmit falsehoods or misrepresentations that could damage the Company or any third party; (iii) submit or transmit material that is unlawful, defamatory, libelous, threatening, pornographic, harassing, hateful, racially or ethnically offensive or encourages conduct that would be considered a criminal offense, give rise to civil liability, violate any law or is otherwise inappropriate; (iv) post or transmit advertisements or solicitations of business; or (v) impersonate another person. If notified by a user or a content owner of a User Submission that allegedly does not conform to this Agreement, the Company may investigate the allegation and determine in good faith and in its sole discretion whether to remove the User Submission, which it reserves the right to do at any time. Additionally, the Company may, at any time, remove any User Submission that in the sole judgment of the Company violates this Agreement. 13.5 User Submissions may be provided by (without limitation) Users who are members of a Start-Up management team, contacts referred by Start-Ups (including without limitation customers, scientific advisors, background references, suppliers and distributors), external experts referred by the Company. The insights, recommendations, views and other content reflected in a User Submission should be taken as opinion rather than statements of facts. Investors should conduct their own diligence before making an investment. Nothing contained in a User Submission constitutes tax, legal, insurance or investment advice, or the recommendation of or an offer to sell, or the solicitation of an offer to buy or invest in, any investment product, vehicle, service or instrument. Such an offer or solicitation may only be made by delivery to a prospective investor of formal offering materials, including subscription or account documents or form, which should be reviewed carefully by any such investor before making the decision to invest in any particular company issuer listed, reviewed or discussed on the Propel(x) platform. To the maximum extent permitted under applicable law, you hereby release Propel(x) (and our officers, directors, agents, investors, subsidiaries, and employees) and each other User from any and all claims, demands, liabilities, losses or damages (whether direct, indirect, consequential, incidental or otherwise) of every kind and nature, known and unknown, suspected or unsuspected, arising out of or in any way related to User Submissions (including your reliance thereon). You acknowledge that, in connection with the foregoing release, you hereby irrevocably waive all rights granted to you under Section 1542 of the California Civil Code or any analogous applicable state or federal law or regulation. Said Section 1542 of the Civil Code of the State of California reads as follows:
Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.
Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.
Format and Content 51.2.1 Unless otherwise specified by CenturyLink, the forecasting forms located on the CenturyLink Wholesale Website will be used by CLEC for the requirements of this Section. 51.2.2 The joint planning process/negotiations should be completed within two (2) months of the initiation of such discussion. 51.2.3 Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 51.2.4 Parties shall meet to review and reconcile the forecasts if forecasts vary significantly. 51.2.5 CLEC shall provide an updated trunk forecast when ordering or requesting additional trunks from CenturyLink anytime after the initial trunk implementation.
Formatted Font: 12
Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
PARTY WEBSITES AND CONTENT The Site may contain (or you may be sent via the Site) links to other websites ("Third- Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software, and other content or items belonging to or originating from third parties ("Third-Party Content"). Such Third-Party Websites and Third-Party Content are not investigated, monitored, or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third-Party Websites accessed through the Site or any Third-Party Content posted on, available through, or installed from the Site, including the content, accuracy, offensiveness, opinions, reliability, privacy practices, or other policies of or contained in the Third-Party Websites or the Third-Party Content. Inclusion of, linking to, or permitting the use or installation of any Third-Party Websites or any Third-Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Site and access the Third-Party Websites or to use or install any Third-Party Content, you do so at your own risk, and you should be aware these Terms and Conditions no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Site or relating to any applications you use or install from the Site. Any purchases you make through Third- Party Websites will be through other websites and from other companies, and we take no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. You agree and acknowledge that we do not endorse the products or services offered on Third-Party Websites and you shall hold us harmless from any harm caused by your purchase of such products or services. Additionally, you shall hold us harmless from any losses sustained by you or harm caused to you relating to or resulting in any way from any Third-Party Content or any contact with Third-Party Websites.
Two-‐character labels All two-‐character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-‐character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-‐code manager of the string as specified in the ISO 3166-‐1 alpha-‐2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
List of Operator’s Subprocessors [Box 26] [Box 27] [Box 28] [Box 29]