Developing a Syntax for Conditional Rights Statements Sample Clauses

Developing a Syntax for Conditional Rights Statements. A syntax to express the conditions for access and reuse of a conditional rights statement needs to be developed. ● This syntax needs to be flexible to allow the modeling of various types of access conditions. ● In addition, the rights statement needs to be able to express the conditions under which an authorised user may reuse the Digital Object. Both elements need to be encoded in the conditional rights statement in a way that allows users to clearly understand under which conditions they can access and reuse a Digital Object. And that allows storage providers4 that host these Digital Objects to determine if access should be granted to a particular user. The conditional rights statement is not intended to let a storage provider or the data provider enforce the reuse conditions (they are not intended to be used as DRM/TPM).
Sample 1
AutoNDA by SimpleDocs

Related to Developing a Syntax for Conditional Rights Statements

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Inspection Testing Authorization and Right of Access 2.1 Equipment Testing and Inspection 2.2 Authorization Required Prior to Parallel Operation

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Schedule for Completing Agreement Closeout Activities Provide All Draft and Final Written Products on a CD-ROM or USB memory stick, organized by the tasks in the Agreement. Products: • Final Meeting Agreement Summary (if applicable) • Schedule for Completing Agreement Closeout Activities • All Draft and Final Written Products

  • Ownership, Use and Return of Offering Materials The Offering Materials shall continue to be the property of the Owner and HFF. The Offering Materials will be used by the Potential Investor solely for the purpose of evaluating the possible acquisition of the Property and not for any purpose unrelated to the possible acquisition of the Property. The Offering Materials may not be copied or duplicated without the Owner's and HFF’s prior written consent, and must be returned to HFF (or with HFF’s permission, destroyed by Potential Investor and any Related Party, and in such instance Potential Investor shall certify in writing to HFF and Owner that such information has been so destroyed) immediately upon request or when the Potential Investor declines to make an offer for the Property or terminates any discussions or negotiations with respect to the Property.

  • Access Rights for implementation Access Rights to Results and Background Needed for the performance of the own work of a Party under the Project shall be granted on a royalty-free basis, unless otherwise agreed for Background in Attachment 1.

  • Requirements Pertaining Only to Federal Grants and Subrecipient Agreements If this Agreement is a grant that is funded in whole or in part by Federal funds:

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Additional Information for Product Development Projects Outcome of product development efforts, such copyrights and license agreements. • Units sold or projected to be sold in California and outside of California. • Total annual sales or projected annual sales (in dollars) of products developed under the Agreement. • Investment dollars/follow-on private funding as a result of Energy Commission funding. • Patent numbers and applications, along with dates and brief descriptions.  Additional Information for Product Demonstrations: • Outcome of demonstrations and status of technology. • Number of similar installations. • Jobs created/retained as a result of the Agreement.

  • Additional Rights Our rights under this Clause shall be in addition and without prejudice to other rights of disclosures available pursuant to the Banking Act, Chapter 19 of Singapore (as may be amended and substituted from time to time) or any other statutory provision and in law and nothing herein is to be construed as limiting any of these other rights.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!