Standards and Metadata Sample Clauses

Standards and Metadata. F6S maintains this data in an internal SQL database with the following schema. The following entities are modelled per each submission. ▪ Administrative Data (Name, Surname, Email address, Country) or SME information (Legal name, VAT number, incorporation year, address of the organization, webpage, contact person's name and surname, email address, phone number and company figures). ▪ Information about the EDI challenge selected. Selection of challenge, proposal summary, team interest in EDI ▪ Technical approach. Description of technical approach, architecture, additional datasets used and technical risks assessment. ▪ Business approach. Description of company and products already in the market, links to already existing solutions, existing customers. ▪ Market. Go-to market strategy, target market segmentation, business model. ▪ Competitors. List of your competitors and added value of your solution. ▪ Sales strategy. Plans for selling. ▪ Growth. Main partners and stakeholders, contacts with investors. ▪ Team. Details about components, how long you have been working together, profiles and dedication to the project of each member
Sample 1
AutoNDA by SimpleDocs
Standards and Metadata. XXXXXX maintains this data in a shared spreadsheet file with the following candidate fields: ▪ Incubator details, i.e. reference to EDI and incubation round within EDI ▪ Sector tackled ▪ Challenge details ▪ Incubation stage reached ▪ Logo and name of the project ▪ Type of beneficiary ▪ Name and surname of coordinator of team ▪ Company legal name ▪ Address full details (street, number, zipcode, city, country) ▪ Brief description of the solution ▪ Abstract ▪ URL of site of solution ▪ Funding received from EDI
Sample 1
Standards and Metadata. DEUSTO, as the data controller of this dataset, maintains this data in a shared spreadsheet file with the following candidate fields: ▪ Personal details for self-employees (name, surname, phone, email, ID, address country) or in case of experts working for a company (name of organization, VAT number, address, country, name, surname and ID of employee) ▪ Type of external collaborator (mentor or external evaluator) ▪ IBAN account ▪ Profile (expertise area) ▪ Description of activities carried out for EDI ▪ Payments issued for their work for EDI. This dataset will be for internal use exclusively, but non-confidential data about the external experts (such as their full names) might be shared with European Commission and sub-grantees, for transparency purposes. The dataset will be continuously updated in order to justify the XXX xxxxx amounts spent in evaluation and mentorship and clearly detail the activities executed on XXX’s behalf by those experts.
Sample 1
Standards and Metadata. 3.3.1 Which data standards will the data conform to? SlideWiki aims to be a long-lasting open-standard based incubator for the collaborative creation of OpenCourseWare in Europe. The evaluation of the quality of use, based on standards like ISO 25010, will also produce recommendations to improve SlideWiki user interfaces, novel interaction paradigms, information architecture components, etc. Furthermore, the distribution of the learning material to the following educational platforms • Massive Open Online Courses (MOOCs) • Learning Management Systems (LMSs) • Interactive eBooks • Social Networks will be facilitated by SlideWiki’s standard compliant HTML5, RDF/Linked Data and SCORM compatible content model, within the context of WP5. In the context of WP6, Secondary Education Trial, gold standards for the reconciliation of different open data sources of the city and of external organisations, such as the Spanish National Library or DBpedia will be generated. This activity is being also transferred into other cities, such as Madrid, and a similar expansion such as that of CoderDojo activities is expected.
Sample 1
Standards and Metadata. In most cases, the data are stored in common data formats such as FITS or MeasurementSets, which are data formats that include rich metadata describing the content and can be easily read by most astronomical data reduction packages. New standards for adaptive optics data are being defined in the Pilot, to complement FITS.
Sample 1
Standards and Metadata. 1/The standard code is not defined yet, as there is still some evolution on which languages maybe used. However, ORP WPLs commit to use a code formatted to improve readability and consistency among the project. 2/ Python software routines will follow the PEP-8 python coding standard.
Sample 1
Standards and Metadata. All material delivered as part of the programme will be stored in standard file formats – e.g. Word, PDF, power point for notes/slides, and MP4 (TBD) for training videos.
Sample 1
AutoNDA by SimpleDocs
Standards and Metadata. All the documents will be stored as PDF, word, or excel files.
Sample 1

Related to Standards and Metadata

  • Quality Standards Each Party agrees that the nature and quality of its products and services supplied in connection with the other Party's Marks will conform to quality standards set by the other Party. Each Party agrees to supply the other Party, upon request, with a reasonable number of samples of any Materials publicly disseminated by such Party which utilize the other Party's Marks. Each Party will comply with all applicable laws, regulations, and customs and obtain any required government approvals pertaining to use of the other Party's marks.

  • Safety Standards Performance of the Contract for all commodities or contractual services must comply with requirements of the Occupational Safety and Health Act and other applicable State of Florida and federal requirements.

  • Standards for Network Elements 1.8.1 BellSouth shall comply with the requirements set forth in the technical references, as well as any performance or other requirements identified in this Agreement, to the extent that they are consistent with the greater of BellSouth’s actual performance or applicable industry standards.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Contract Work Hours and Safety Standards Act The following clauses apply to any Federal-aid construction contract in an amount in excess of $100,000 and subject to the overtime provisions of the Contract Work Hours and Safety Standards Act. These clauses shall be inserted in addition to the clauses required by 29 CFR 5.5(a) or 29 CFR 4.6. As used in this paragraph, the terms laborers and mechanics include watchmen and guards.

  • CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

  • Contractor Work Hours and Safety Standards Contractor shall ensure compliance with all safety and hourly requirements for employees, in accordance with federal, state, and County safety and health regulations and laws.

  • Technical Standards The Generation System shall be installed and operated by the Interconnection Customer consistent with the requirements of this Agreement; the Technical Requirements; the applicable requirements located in the National Electrical Code (NEC); the applicable standards published by the American National Standards Institute (ANSI) and the Institute of Electrical and Electronic Engineers (IEEE); and local building and other applicable ordinances in effect at the time of the installation of the Generation System.

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