zilongwang/ReadingBank huggingface dataset:
Invariable All single bit Periodic modified checksum; or H.2.19.3.1 memory faults multiple checksum, or H.2.19.3.2 word protection with single bit redundancy H.2.19.8.2 Table R.1 (continued) Component 1) Acceptable measures 2) 3) 4) Definitions Document reference Document reference Verdict for applied measure For applied test 4.2 Variable DC fault Periodic static memory test, or H.2.19.6 memory word protection with single bit redundancy H.2.19.8.2 4.3 Addressing Stuck at Word protection with single bit parity H.2.19.18.2 (relevant to including the address, or variable and invariable memory) 5. Internal data Stuck at Word protection with single bit redundancy H.2.19.8.2 path DC fault Comparison of redundant CPUs by either: – reciprocal comparison H.2.18.15 – independent hardware comparator, or H.2.18.3 5.1 Void 5.2 Addressing Wrong address Word protection with single bit redundancy including the address H.2.19.8.2 Table R.1 (continued) Component Fault/error Acceptable measures Definitions Document reference Document reference Verdict for applied measure For applied test 6 External 6.1 Data Data corruption Word protection with multi-bit redundancy, or CRC – single word , or transfer redundancy, or protocol test H.2.19.8.1 H.2.19.4.1 H.2.18.2.2 H.2.18.14
6.2 Void 6.3 Timing Wrong point in time Time-slot monitoring, or scheduled transmission H.2.18.10.4 H.2.18.18 Time-slot and logical monitoring, or H.2.18.10.3 comparison of redundant communication channels by either: – reciprocal comparison H.2.18.15 – independent hardware comparator H.2.18.3 Logical monitoring, or H.2.18.10.2 sequence time-slot monitoring, or H.2.18.10.4 scheduled transmission H.2.18.18 (same options as for wrong point in time) 7. Input/output Fault Plausibility check H.2.18.13 periphery conditions specified in Comparison of redundant CPUs by either: 19.11.2 – reciprocal comparison H.2.18.15 – independent hardware comparator, or H.2.18.3 7.1 Void Table R.1 (continued) Component Fault/error Acceptable measures Definitions Document reference Document reference Verdict for applied measure For applied test 7.2 Analog I/O 7.2.1 A/D- and Fault conditions Plausibility check H.2.18.13 D/A- converter specified in 19.11.2 7.2.2 Analog multiplexer Wrong addressing Plausibility check H.2.18.13 8. Void 9. Custom Any output Periodic self test H.2.16.6 chips 5) outside the e.g. ASIC, static and GAL, Gate dynamic array functional specification When applicable in the specific Part 2 the software may be analysed with Table R2 Table R.2 – Specific fault/error conditions Component Fault/error Acceptable measures Definitions Document reference Document reference Verdict for applied measure For applied test
Certificate name Reference (entity completing test and document reference number) Date Resolution of findings Certificate for design of the PV system according to IEC 62548 (or IEC/TS 62738 if applicable).* * Results of the design are summarized in next table. Documentation of Findings for Design Review Finding (non conformity or concern identified during IEC audit) Severity (Serious = lead to failure; Moderate = severity unknown; Cosmetic = unlikely to affect product function) Date of finding Date of resolution Comment Documentation of System Quality Management - Installation and O&M Provider Certificate name Reference (entity completing test and document reference number) Date Resolution of findings QMS audit certificate of installation process according to IEC 63049* QMS certificate of O&M process according to IEC 63049 * Results of the QMS audit(s) are summarized in next table. Documentation of Audit Findings for System Quality Management - Installation Finding (non conformity identified during subsequent (renewal of certificate) IEC 63049 audit) Severity (Serious = could lead to failure; Moderate = severity unknown; Cosmetic = unlikely to affect product function) Date of finding Date of resolution Comment Certificate for Commissioning of PV System
Applicable standard Reference (entity completing test and document reference number) Date IEC 62446-1 Documentation of Audit Findings for Commissioning Finding (issues or concerns identified during IEC 62446-1) Severity (Serious = could lead to failure; Moderate = severity unknown; Cosmetic = unlikely to affect product function) Date of finding Date of resolution Comment PV System Performance Test Results Test or measurement Result End date of test period Reference conditions Output Power according to IEC 61724-2, section 8, item 15, including uncertainty of measurement kW + kW W/m2 °C Performance index for power generated at TRC as defined in IEC section 8, item 15 % W/m2 °C
Digital Template for Conditional PV Project Certificate The following provides a consistent format for data reporting to facilitate data base creation. Field name Example Units Certificate_number IECREPV458976.1 N Certificate_type F Milestone Name_of_System Hypothetical Ground-mount System #1 Certificate_holder PG&E Authorized_viewer1 Wells Fargo Authorized_viewer2 Authorized_viewer3 Authorized_viewer4 System-type U1L1 usage,architecture Geo_Location deg/deg System_Capacity_contract 100000 kW 998000 kW System_Capacity_ppi .995 Ratio Uncertainty_sc 1.5 % Timestamp 2015.05.21.08.05.01 yyyy.mm.dd.hh.mm.ss Availability_contract 99 % Certifier TUVR Name
Parameters associated with plant performance data MeasuredEnergyInclParasitics Active (real) energy measured for the indicated time period according to IEC 61724-3 sec 6.7 including adjustment for parasitic losses kWh 1000 MeasuredEnergyAvailability Measured Energy Availability for the indicated time period calculated from the measured weather data and observed availability according to IEC section 6.8. may be obtained by dividing by dimensionless 1 Actual Energy Availability For the Year excluding time of external or other outage causes per IEC 61724-3 section 6.8.1 ratio, dimensionless 0.99 AllInEnergyPerformanceIndex Active (real) energy performance index including times when the system is not functioning as in IEC 61724-3 section 6.8. ratio, dimensionless 0.9 InServiceEnergyPerformanceIndex Active (real) Energy Performance Index during times when the system is functioning (offline times removed) as in IEC 61724-3 section 6.8 ratio, dimensionless 0.9 ParasiticLossMeasured Are parasitic losses measured in the test? Yes/No No MeasurementProcedureDeviations Test Procedure pertains to IEC 61724-3 Yes/No No CapacityFactorIEC Active (Real) energy generation of plant relative to energy that would have been generated if the plant was operating continuously at its AC rated power, per IEC 61724-3 section 6.8.2 dimensionless 0.25 MeasurementUncertainityBasis Standard method used to calculate Uncertainity of measurement Method Used ISO/IE Guide StatedUncertaintyValueExpectedEnergy Uncertainty in expected energy arising from uncertainty in the measured weather data Percentage ±3 StatedUncertainityValueEnergyMeasured Value Quantification of Total Uncertainity (including bias and precision)of Energy Measured Percentage ±3 ExpectedO&MCost Cost of ownership for system based on the Predicted_O&M_Cost, but with the expected value for the particular time period used for this test. currency/W 1 MeasuredO&MCost Cost of ownership for system based on documented expenses for the particular time period used for this test. currency/W 1
Template for Annual PV Project Performance Certificate Annual PV Project Performance Certificate Certificate Type: U1 Client Installation Address Lat., Long. Altitude System Integrator Site Construction Firm Site Climate per IEC 60721 Test date O&M Contractor Description of Installation Rated power – kW DC Rated power – kW AC Location Module type Number of modules Inverter type Number of inverters Tilt Azimuth Tracker Type I / we being the person(s) responsible for the issuance of the Final PV Project Certificate for the electrical installation (as indicated by the signature(s) below), particulars of which are described above, having exercised reasonable skill and care when carrying out the design construction, inspection and testing, hereby certify that the said work for which I/we have been responsible is, to the best of my/our knowledge and belief, in accordance with ……… Signature(s): Name(s): Date: (The extent of liability of the signatory(s) is limited to the work described above) COMMENTS:
*This column is completed using Table 2; it may require interpolation if the test period does not align exactly with the years of the original prediction. The measurement point for electrical generation should match that of the prediction. Table A5. PV System Performance Test Results (Optional) Test or measurement Result End date of test period Reference conditions Output Power according to IEC 61724-2, section 8, item 15, including uncertainty of measurement kW W/m2 °C performance index for power generated at TRC as defined in IEC 61724-2, section 8, item 15 % W/m2 °C Table A6. Documentation of Significant Events Event description Root cause Action taken to resolve issue Electrical generation loss associated with event* Date of finding Date of resolution *List events causing loss of more than 0.1% of annual yield and any events reported to impact safety or attract need for regulatory review
Number of people involved with the Inspection activity within the scope of this assessment Responsible Managers for Inspection Name Position (title) and field of expertise of relevant Experience checked & appropriate To whom do they report? Yes No Principal involved in Inspection Name Position (title) and field of expertise Years of relevant Experience checked & appropriate To whom do they report? Yes No Staff involved in the Quality Management System of the Inspection Body Name Position (title) and field of expertise Years of relevant Experience checked & appropriate To whom does the quality management system staff report? Yes No Assessment of competence Briefly describe how the competence was assessed e.g. interview, CV check, demonstration of Inspection decisions, knowledge of the standard, reviewing of the Test Reports, etc.
Date Morning Afternoon Monday 23rd October 2017 The Disney Pumpkin Carving challenge… Who can carve their pumpkin into their favourite Disney character! Bonkers with Conkers! Paint rolling, modelling, necklace making and the great conker challenge….who will win! Tuesday 24th October 2017 Disney Princess and Prince for a day! Make your own princess headbands and handbags, princes’s swords or crowns. Make Beauty and the Beast candy apples, Disney princess button art, Castle building competition and much more! Come in fancy dress! Wednesday 25th October 2017 Cookie Creations! Make your own gingerbread Autumn leaf cookie or Mickey Oreo Cookies. Disney Autumn Scavenger Hunt! Take your Autumn sticky wall and see what you can find in the forest at Wallsend Park. Find Shrek for a treat! Thursday 26th October 2017 Disney Mask Making and Stone Painting Shrek, Beauty and the Beast, Mickey Disney Candy Apples Design and make your own candy Will you choose a
TESTING AND MEASURING EQUIPMENT/ALLOWED SUBCONTRACTING “R” Required “S” May be subcontracted, see OD 2012 “SPTL” Specialized Facility, see IECEE 02-2 “W” Witness testing in the categories “MED” and “MEAS” “3PPS” Three Phase Power Supply required Clause Measurement/testing Testing / measuring equipment / material needed Subcontracting
Voltage regulation loaded Reg Vld = [MAX(Vld,max -Vnom; Vnom - Vld, min)/Vnom ] x 100% Frequency regulation open circuit Reg Foc = [MAX(Foc,max -Fnom; Fnom - Foc, min)/Fnom ] x 100% Frequency regulation loaded Reg F ld = [MAX(Fld,max -Fnom; Fnom- Fld, min)/Fnom] x 100% Note: Function MAX(value 1; value 2) returns the maximum of value 1 and value 2. Example: In the calculation MAX(Voc max-Vnom; Vnom -Voc min) use the maximum value of either upper (Voc max-Vnom) or the lower (Vnom-Voc min).” Total Harmonic Distortion THD = SQRT(sum of all squares of amplitude of all harmonic voltages/square of the amplitude of the fundamental voltage) x 100% Responsibility of the laboratory 5.1 Laboratory power source measurements shall be performed upon initial installation, modification and repair of the laboratory power source(s) to confirm that appropriate power quality exists at the test connection locations. 5.2 In accordance with ISO/IEC clause 5.3.2, it is the responsibility of the laboratory to monitor, control and record characteristics of the laboratory power source to ensure continued conformance with the requirements. Considerations to be taken into account include changes in characteristics of the power as supplied by the electric utility (or other source), changes in load conditions on the power source substation due to power consumption of neighboring businesses and effects of other testing being conducted in the laboratory. General Instructions given in this document are to be followed to assure test consistency and repeatability. Equipment 7.1 Instruments: 7.1.1 Voltmeter 7.1.2 Ammeter 7.1.3 Frequency meter 7.1.4 Total harmonic distortion analyzer 7.1.5 Resistive loads 7.1.6 Accuracy of meters shall conform to the most recent version of CTL DSH-251. 7.1.7 calibrations are to be traceable to SI units. Note 1: Other types of equipment providing equivalent functionality may be used. Requirements 8.1 When not otherwise specified in the testing standard, the test connection location shall meet the following requirements:
Lightning protection system (protection level): Earthquake model and parameters (standard and key parameters e.g. spectrum, model, seismic zone, soil class, etc.): Other design conditions (such as sand-storm): Electrical network conditions: Normal supply voltage and Normal supply frequency and range: Voltage imbalance: Maximum duration of electrical power network outages: Number of electrical network outages: Total duration of network outages during project lifetime: Rotor nacelle assembly (RNA-machine) parameter Rated power: Type of regulation: Rated wind speed Vr: Rotor diameter: Hub height MSL): Hub height operating wind speed range Vin – Vout: Design lifetime: Operational weight: Corrosion protection (description): Support structure parameters Description of foundation including scour protection: Design water depth:* Resonant frequencies at normal operating conditions: Resonant frequencies at extreme operating conditions: Corrosion protection (description): Height of access platform (above MSL):*
Personnel Structure Employees >67% of the technical staff is own employees Yes No Responsible for Certification Decision Name Position and field of expertise Years of relevant experience Experience checked & found appropriate Reports to Yes No Principal staff and/or experts involved in Certification When the declared years of experience is low, the assessment team should make a professional judgment based upon interviews on the awareness and knowledge of the standards as well as CV information e.g. previous employments and function, training programmes completed. There shall be minimum 2 experts available in each critical technical area. Name Position (title) and field of expertise Years of relevant experience Experience checked & found appropriate Reports to Yes No Quality Manager(s) of the Certification Body Name Position (title) and field of expertise Years of relevant experience Experience checked & found appropriate Reports to Yes No
h) Any changes made to the test turbine during the test period; Test requirements # Reference to section in standard Requirement from standard Checks & expert guidance Reported / Inspected Finding 6 Test requirements 6.1 General In Clause 6 the requirements for the test are described. These include requirements for The test site, The MLCs and the amount of data required for each, The quantities to be measured, and Changes in the turbine configuration. Have there been specific test conditions worth mentioning, such as snow and ice (which may affect turbine and sensors), freezing weather (affecting the sensors and cup classification), strong hail To the extent these are measured, also information regarding shear, veer and upflow is to be reported alongside turbulence 6.2 Test site requirements Reporting clause 12.3) The terrain and wind conditions shall be capable of fulfilling the requirements of the capture matrix. Is there an evaluation for the test campaign prior to the test? An obstacle assessment and terrain assessment shall be completed per IEC 61400- 12-1. The measurement sector can be expanded beyond the one found using the methods in IEC 61400-12-1 if it can be shown that the wind speed and TI measured at the meteorological mast are representative of those seen by the wind turbine (e.g. turbine and meteorological mast on ridge). Check relating to the measurement sector shall be on the basis of OD-551-12 If the measurement sector is expanded, that evidence showing such representativeness is provided and reported. If the test site does not meet the requirements of IEC a site calibration should be performed. Checks relating to the assessment of the test site shall be on the basis of OD-551-12 If no site calibration is performed in complex terrain, is the extra uncertainty considered and reported? A description of the test site, including Photographs of all measurement sectors preferable taken from the wind turbine at hub height Geographical location with sufficiently detailed information to allow the reader to locate the test machine. Test site map showing the surrounding area covering a radial distance of at 20 times the wind turbine rotor diameter and indicating the topography, location of the wind turbine, meteorological mast, Check that all points mentioned in 12.3) have been included in the report
Signals used to control the blade test (applied loads, deflections, accelerations, strains) Functionality of sensors shall be verified throughout the test. Critical sensors shall be fixed or replaced when the fail. Stiffness of the blade shall be checked and documented several times throughout the test. Review what the lab does when various sensor types fail. How is the data processed and reported when a sensor (e.g. a strain gauge) failed for a portion of the test? 34 9.4 Fatigue load testing Typically the customer defines the Miner summation slope factor. The test lab may be responsible for determining the total damage equivalent load applied during the test. 35 Repairs during fatigue testing If any repairs were performed during fatigue testing how were they documented? Had the repaired area already achieved the target damage level? 10.4 Other blade property tests 36 10.4.1 mass and CG shall be determined. How was the mass/cg measurement obtained? Are the uncertainty estimates reasonable for these results? Is any additional hardware noted? Are any tare loads appropriately accounted for? 37 10.4.2 Natural frequencies. Minimum of 1st and 2nd flatwise Review how natural frequency measurements are conducted. Is
6.3.5 6.3.3 Are switching operations reported for turbine start-up at rated or higher wind speed? 6.3.6 6.3.3 Is the case of switching between generators reported? * *Only for turbines with multiple windings or more than one generator 6.3.7 6.3.3 Is the maximum number of the switching operation within a 10 min period and a 2 h period reported? 6.3.8 6.3.3 Are the flicker step and voltage change factors for the network impedance phase angles 30°, 50°, 70° and 85°, reported? 6.3.9 7.3.2 Is the selected short circuit ratio Sk,fic/Sn between 20 and 50? 6.3.10 7.3.2 Is the accuracy of the evaluated Pst values better than 5%?
Response to voltage drops (section 6.5, 7.5 of IEC61400-21 Rev. 2) # Reference to section in standard Requirement from standard Reported / Inspected Finding 6.5.1 6.5 Are the tests regarding response to voltage drops performed on the complete wind turbine? 6.5.2 6.5 &7.5 Is the response of the wind turbine to temporary voltage stated for the wind turbine operating at a) between 0,1 Pn and 0,3 Pn and b) above 0,9 Pn ? 6.5.3 6.5 Does the stated response include results from 2 consecutive tests of each case (VD1-VD6 in Table 1)? 6.5.4 6.5 & 7.5 Does the stated response include time-series of active power, reactive power, active current, reactive current and voltage at wind turbine terminals? 6.5.5 6.5 & 7.5 Do the time-series of active power, reactive power, active current, reactive current and voltage at wind turbine terminals correspond to the time shortly prior to the voltage drop and until the effect of the voltage drop has abated?
Empathy (understand the feelings and attitudes of others and is able to put oneself in others' shoes). Innovation (is change-oriented and able to generate and/or recognize creative solutions in varying work-related situations). Integrity (maintains and promotes organisational, social, and ethical standards and values in the conduct of internal as well as external business activities) Listening (draws out opinions and information from others in face-to-face interaction) Communication (is proficient in both written and verbal communication) Core Competencies Put our customers first Strive for excellence Be accountable Think and act as ‘one team’ Demonstrate respect Achieve work/life balance
Jan 24 Staining I LECTURE TEST 1: Ch. 1; 3-5 Genetics – Ch. 9 Jan 31 Feb 7 Staining II, Test review and Quizzes (TBD) Genetic Engineering – Ch. 10 Feb 14 Physical Growth Factors for Bacterial Growth Controlling Microbes – Ch. 11 Antibiotics – Ch. 12 Feb 21 Introduction to Biochemical Test Media, Test review LECTURE TEST 2: Ch. 9-12 Feb 28 MIDTERM LAB PRACTICAL TEST WEEK Materials come from laboratory experiments performed during weeks 1-5 Infection and Disease – Ch. 13 Nonspecific Defenses – Ch. 14 Mar 7 Culture and Sensitivity (C&S) read page 455 Specific Defenses – Ch. 15 Disorders in Immunity – Ch. 16 March 12- 17 Spring break LECTURE TEST 3: Ch. 13-16 Diagnosing Infections – Ch. 17 Mar 21 C&S: Unknown Identification Lab and Antibiotic Selection Diseases of the Skin/Eyes – Ch. 18 Mar 28 DNA Lab Nervous System Disease – Ch. 19 Apr 4 Immunology lab, Assign presentation topics Cardio/Lymph Disease –Ch. 20 (Quiz) Apr 11 Human Microbiology/Epidemiology Simulation Lab Analysis, Test review Presentations (Ch. 20 – 23) LECTURE TEST 4: Ch. 17-19 Respiratory Disease - Ch. 21 Apr 18 Presentations (Ch. 20 – 23) Digestive System Disease– Ch. 22 Genitourinary Diseases – Ch. 23 Apr 25 FINAL LAB TEST Test on lab experiments performed during 6-12. Place and time will be confirmed later Genitourinary Diseases – Ch. 23 MICROBIOLOGY (MCB 2010C) LABORATORY EXERCISES Valencia College – Spring 2018 Week 1. Lab Introduction - Safety and laboratory Guidelines: students read pp. 1-6 - “Scavenger hunt” (introduce students to location of lab’s safety equipment) - Exercise 1-1 Glo-Germ™ Hand Wash Education System (optional) - Exercise 2-1 Ubiquity of Microbes - Exercise 3-1 Introduction to the Light Microscope - learn parts, use, care and storage of the microscope; crossed thread and letter“e” prepared slides, - Exercise 3-3 Examination of Eukaryotic Microbes (begin observing prepared slides)
Jan 9 Introduction to the Microbiology Lab No Quiz Introduction – Ch. 1 Tools of the Lab – Ch. 3 Jan 16 Culturing Bacteria and Using the Microscope Bacteria and Archaea – Ch. 4 Eukaryotes – Ch. 5 Viruses – Ch. 6; Quiz in Chap 6 Jan 23 Staining I LECTURE TEST 1: Ch. 1; 3-5 Genetics – Ch. 9 Jan 30 Feb 6- Staining II, Test review and Quizzes (TBD) Genetic Engineering – Ch. 10 Feb 13 Physical Growth Factors for Bacterial Growth Controlling Microbes – Ch. 11 Antibiotics – Ch. 12 Feb 20 Introduction to Biochemical Test Media, Test review LECTURE TEST 2: Ch. 9-12 Feb 27 MIDTERM LAB PRACTICAL TEST WEEK Materials come from laboratory experiments performed during weeks 1-5 Infection and Disease – Ch. 13 Nonspecific Defenses – Ch. 14 Mar 6 Culture and Sensitivity (C&S) read page 455 Specific Defenses – Ch. 15 Disorders in Immunity – Ch. 16 March 12- 17 Spring LECTURE TEST 3: Ch. 13-16 Diagnosing Infections – Ch. 17 Mar 20 C&S: Unknown Identification Lab and Antibiotic Selection Diseases of the Skin/Eyes – Ch. 18 Mar 27 DNA Lab Nervous System Disease – Ch. 19 Apr 3 Immunology lab, Assign presentation topics Cardio/Lymph Disease –Ch. 20 (Quiz) Apr 10 Human Microbiology/Epidemiology Simulation Lab Analysis, Test review Presentations (Ch. 20 – 23) LECTURE TEST 4: Ch. 17-19 Respiratory Disease - Ch. 21 Apr 17 Presentations (Ch. 20 – 23) Digestive System Disease– Ch. 22 Genitourinary Diseases – Ch. 23 Apr 24 FINAL LAB TEST Test on lab experiments performed during weeks 6-12. Place and time will be confirmed later Genitourinary Diseases – Ch. 23 MICROBIOLOGY (MCB LABORATORY EXERCISES Valencia College – Spring 2018 Week 1. Lab Introduction - Safety and laboratory Guidelines: students read pp. 1-6 - “Scavenger hunt” (introduce students to location of lab’s safety equipment) - Exercise 1-1 Glo-Germ™ Hand Wash Education System (optional) - Exercise 2-1 Ubiquity of Microbes - Exercise 3-1 Introduction to the Microscope
HTTP/1.1 200 Ok 4.0 Content-Length: #### Content-Type: multipart/mixed; boundary=b_243234_25424_ef_892u748 --b_243234_25424_ef_892u748 Content-Type: application/http Content-Transfer-Encoding: binary HTTP/1.1 200 Ok Content-Type: application/atom+xml;type=entry Content-Length: ### <AtomPub representation of the Customer entity with EntityKey ALFKI> --b_243234_25424_ef_892u748 Content-Type: multipart/mixed; boundary=cs_12u7hdkin252452345eknd_383673037 Content-Length: ### --cs_12u7hdkin252452345eknd_383673037 Content-Type: application/http Content-Transfer-Encoding: binary Content-ID: 1 HTTP/1.1 201 Created Content-Type: application/atom+xml;type=entry Location: http://host/service.svc/Customer('POIUY') Content-Length: ### <AtomPub representation of a new Customer entity> Content-ID: 2 --cs_12u7hdkin252452345eknd_383673037 Content-Type: application/http Content-Transfer-Encoding: binary HTTP/1.1 204 No Content Host: host --cs_12u7hdkin252452345eknd_383673037-- --b_243234_25424_ef_892u748 Content-Type: application/http Content-Transfer-Encoding: binary HTTP/1.1 404 Not Found Content-Type: application/xml Content-Length: ### <Error message> --b_243234_25424_ef_892u748--
(Requests all products with a Price of 2.55). (Requests all products with a Price of 2.55). (Requests all products with a Rating exactly divisible by 5). Grouping Operator The Grouping Operator (open and close parenthesis "( )") controls the evaluation order of an expression. The Grouping Operator evaluates to the expression grouped inside the parenthesis. For example: Requests all products, because 9 mod 3 is 0. Canonical Functions In addition to operators, a set of functions is also defined for use with the filter or orderby query options. The following table lists the available functions. Note: ISNULL or COALESCE operators are not defined. Instead, there is a null literal that can be used in comparisons. The syntax for all canonical functions are defined in [OData-ABNF]. substringof The substringof canonical function has the following signature: Edm.Boolean substringof(Edm.String,Edm.String) If implemented the substringof canonical function MUST return true if, and only if, the parameter string value is a substring of the second parameter string value. The substringOfMethodCallExpr syntax rule defines how the substringof function is invoked. For example: Returns all customers with a CompanyName that contains 'Alfreds'. endswith The endswith canonical function has the following signature: Edm.Boolean endswith(Edm.String,Edm.String) If implemented the endswith canonical function MUST returns true if, and only if, the parameter string value ends with the second parameter string value. The endsWithMethodCallExpr syntax rule defines how the endswith function is invoked. For example: Returns all customers with a CompanyName that end with 'Futterkiste'. startswith The startswith canonical function has the following signature: Edm.Boolean startswith(Edm.String,Edm.String)
Revision History Revision Date Editor Changes Made Working Draft 01 2016-11-16 Ralf Handl Initial version Committee Specification 01 2017-06-08 Michael Pizzo Ralf Integrated 4.01 features Committee Specification Draft 02 2017-09-22 Michael Pizzo Ralf Incorporated review feedback Changed defaults of $Nullable, and $Precision Committee Specification Draft 03 2017-11-10 Michael Pizzo Ralf Handl Incorporated review feedback Stable order of action and function parameters Committee Specification 01 2017-12-19 Michael Ralf Handl Non-Material Changes
} } Action Import Action imports sets are top-level resources that are never included in the service document. An action import is identified by its name, a that MUST be unique within its entity container. An action import MUST specify the name of an unbound action in If the imported action returns an entity or a collection of entities, a or value MAY be specified to identify the entity set that contains the returned entities. If a is specified, it MUST resolve to an entity set defined in the same entity container. If a is specified, it MUST resolve to an entity set in scope. Action Import Object An action import is represented as a member of the entity container object whose name is the name of the action import and whose value is an object. The action import object MUST contain the member $Kind with a string of ActionImport, and the member $Action. It MAY contain the member $EntitySet. It MAY also contain . $Action The value of $Action is a string containing the qualified name of an unbound action. $EntitySet The value of $EntitySet is a string containing either the unqualified name of an entity set in the same entity container or a path to an entity set in a different entity container. Function Import Function imports sets are top-level resources. A function import is identified by its name, a that MUST be unique within its entity container. A function import MUST specify the name of an unbound function in scope. All of the imported function can be invoked from the entity container. If the imported function returns an entity or a collection of entities, a or value MAY be specified to identify the entity set that contains the returned entities. If a is specified, it MUST resolve to an entity set defined in the same entity container. If a is specified, it MUST resolve to an entity set in scope. A function import for a parameterless function MAY indicate whether it is included in the service document. If not explicitly indicated, it is not included. Function Import Object A function import is represented as a member of the entity container object name is the name of the function import and whose value is an object. The function import object MUST contain the member $Kind with a string value of FunctionImport, and the member $Function. It MAY contain the members $EntitySet and $IncludeInServiceDocument. It MAY also contain . $Function The value of $Function is a string containing the qualified name of an unbound function.
References Revision Date Editor Changes Made Working Draft 01 2016-11-16 Ralf Initial version Committee Specification Draft 01 2017-06-08 Michael Pizzo Ralf Handl Integrated 4.01 features Committee Specification Draft 02 2017-09-22 Michael Ralf Handl Incorporated review feedback Changed defaults of $Nullable, $Scale, and $Precision
Revision History Revision Date Editor Changes Made Working Draft 01 2016-11-16 Ralf Handl Initial version Committee Specification Draft 01 2017-06-08 Michael Pizzo Ralf Handl Integrated 4.01 features Committee Specification Draft 02 2017-09-22 Michael Ralf Handl Incorporated review feedback Changed defaults of $Nullable, $Scale, and $Precision Committee Specification 03 2017-11-10 Michael Pizzo Ralf Handl Incorporated review feedback Stable order of action and function parameters
Entity Type An entity type is represented as a member of the document object whose name is the name of the entity type and whose value is an object. The value object MUST contain the member $kind with a string value of EntityType. It MAY contain the members , , , , and . It also MAY contain members representing and as well as . Example : a simple entity type "org.example.Employee": { "$kind": "EntityType", "$Key": [ "ID" ], "ID": { "$Nullable": false }, "FirstName": { "$Nullable": false }, "LastName": { "$Nullable": false }, "Manager": { "$kind": "NavigationProperty", "$Type": "org.example.Manager" } } Example : a derived entity type based on the previous example "org.example.Manager": { "$kind": "EntityType", "$BaseType": "org.example.Employee", "AnnualBudget": { "$Type": "Edm.Decimal" }, "Employees": { "$kind": "NavigationProperty", "$isCollection": true, "$Type": "org.example.Employee" } } Member $Key The of $Key is an array with one item per key property. Key properties without a key are represented as strings containing the property name. Key properties with a key alias are represented as objects with one member whose name is the key alias and whose value is a string containing the path to the property.
Schema One or more schemas describe the entity model exposed by an OData service. The schema acts as a namespace for elements of the entity model such as entity types, complex types, enumerations and terms. A schema is identified by a . Schema namespaces MUST be unique within the document, and SHOULD be globally unique. A schema cannot span more than one document. The schema’s namespace is combined with the name of elements in the schema to create unique , so identifiers that are used to name types MUST be unique within a namespace to prevent ambiguity. See for more details. The namespace MUST NOT be one of the reserved values Edm, odata, System, or Transient. Schema Object A schema is represented as a member of the document object name is the schema namespace. Its value is an object that MUST contain a member and MAY contain a member . The schema object MAY contain members representing , , , , , , , and an . The schema object MAY also contain that apply to the schema itself. Alias A schema an alias which MUST be a . he alias used . Aliases are document-global, so all schemas defined within or included into a document MUST have different aliases. Aliases defined by a schema can be used throughout the containing document and are not restricted to the schema that defines them. The alias MUST NOT be one of the reserved values Edm, odata, System, or Transient. $Alias The value of $Alias is a string containing the alias for the schema. Example : document defining a schema org.example with an alias and a description for the schema { "$Version": "4.01", "org.example": { "$Alias": "self", "@Core.Description": "Example schema", … }, … } Annotations with External Targeting $Annotations The value of $Annotations is an object with one member per . The member name is a path identifying the , the member value is an object containing for that target. Example 7: annotations targeting the Person type with qualifier Tablet "org.example": {
Typographical Conventions Keywords defined by this specification use this monospaced font. Normative source code uses this paragraph style. Some sections of this specification are illustrated with non-normative examples. Example : text describing an example uses this paragraph style Non-normative examples use this paragraph All examples in this document are non-normative and informative only. Representation-specific text is indented and marked with vertical Representation-Specific Headline Normative representation-specific text All text is normative unless otherwise labeled.
} Entity Set Entity sets are top-level collection-valued resources. An entity set is identified by its name, a that MUST be unique within its entity container. An entity set MUST specify a type that MUST be an entity type in scope. An entity set MUST contain only instances of its specified entity type or its subtypes. The entity type MAY be but MUST have a defined. An entity set MAY indicate whether it is included in the service document. If not explicitly indicated, it is included. Entity sets that cannot be queried without specifying additional query options SHOULD NOT be included in the service document. Entity Set Object An entity set is represented as a member of the entity container object whose name is the name of the entity set and whose value is an object. The entity set object MUST contain the member $Kind with a string value of EntitySet, and the member $Type whose string value is the qualified name of an entity type. It MAY contain the members $IncludeInServiceDocument and as well as . $IncludeInServiceDocument The value of $IncludeInServiceDocument is one of the Boolean literals true or false. Absence of the member means true. Singleton Singletons are single-valued resources. A singleton is identified by its name, a that MUST be unique within its entity container. A singleton MUST specify a type that MUST be an entity type in scope. A singleton MUST reference an instance its entity type. Singleton Object A singleton is represented as a member of the entity container object whose name is the name of the singleton and whose value is an object. The singleton object MUST contain the member $Kind with a string value of Singleton, and the member $Type whose string value is the qualified name of an entity type. It MAY contain the member as well as . Navigation Property Binding If the entity type of an entity set or singleton declares navigation properties, a navigation property binding allows describing which entity set or singleton will contain the related entities. An or a SHOULD specify a navigation property binding for each of its entity type, including navigation properties defined on complex typed properties or derived types. If omitted, clients MUST assume that the target entity set or singleton can vary per related entity. Binding Path A navigation property binding MUST specify a path to a navigation property of the entity set’s or singleton's declared entity type, or a navigation property reached through a of type casts, complex
Revision History Revision Date Editor Changes Made Working Draft 01 2016-09-07 Michael Pizzo Ralf Imported content from 4.0 Errata 3 specification and integrated initial 4.01 features Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Committee Specification Draft 02 2017-06-08 Michael Ralf Handl Incorporated normative text from former OData Part 3: CSDL Committee Specification 03 2017-09-22 Michael Pizzo Ralf Handl Incorporated review feedback Committee Specification Draft 04 2017-11-10 Michael Pizzo Ralf Incorporated review feedback Stable order of action and function parameters
Schema One or more schemas describe the entity model exposed by an OData service. The schema acts as a namespace for elements of the entity model such as entity types, complex types, enumerations and terms. Element edm:Schema The edm:Schema element contains one or more of the following elements: edm:Term Values of the Name attribute MUST be unique across all direct child elements of a schema, with the sole exception of overloads for an action and overloads for a function. The names are local to the schema; they need not be unique within a document. Attribute Namespace A schema is identified by a . All edm:Schema elements MUST have a namespace defined through a Namespace attribute which MUST be unique within the document, and SHOULD be globally unique. A schema cannot span more than one document. The schema’s namespace is combined with the name of elements in the entity model to create unique , so identifiers that are used to name types MUST be unique within a namespace to prevent ambiguity. See for more detail. The Namespace attribute MUST NOT use the reserved values Edm, odata, System, or Transient. Attribute Alias A schema MAY define an alias by providing a value for the Alias attribute. An alias allows nominal types to be qualified with a short string rather than a long namespace. Aliases are document-global, so all and elements within a document MUST specify different values for the attribute. Aliases defined by an element can be used throughout the containing document and are not restricted to the schema that defines them. The Alias attribute MUST NOT use the reserved values Edm, odata, System, or Transient.
Revision History Revision Date Editor Changes Made Working Draft 01 2016-09-07 Michael Ralf Imported content from 4.0 Errata 3 specification and integrated initial 4.01 features Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Committee Specification Draft 02 2017-06-08 Michael Ralf Handl Incorporated normative text from former OData Part 3: CSDL Committee Specification Draft 03 2017-09-22 Michael Ralf Handl Incorporated review feedback Committee Specification 04 2017-11-10 Michael Ralf Incorporated review feedback Stable of action and function parameters Committee Specification 01 2017-12-19 Michael Pizzo Ralf Handl Non-Material Changes
Revision History Revision Date Editor Changes Made Working Draft 01 2012-11-12 Ralf Handl Translated contribution into OASIS format Committee Specification 01 2013-07-25 Ralf Handl Hubert Heijkers Gerald Krause Michael Pizzo Martin Zurmuehl Switched to pipe-and-filter-style query language based on composable set transformations Fleshed out examples and addressed numerous editorial and technical issues processed through the TC Added Conformance section Committee Specification Draft 02 2014-01-09 Ralf Handl Hubert Heijkers Gerald Krause Michael Pizzo Martin Zurmuehl Dynamic properties used all aggregated values.either via aliases or via custom aggregates Refactored annotations
Revision History Revision Date Editor Changes Made Working 01 2012-11-12 Ralf Handl Translated contribution into OASIS format Committee Specification Draft 01 2013-07-25 Ralf Hubert Heijkers Gerald Krause Michael Pizzo Martin Zurmuehl Switched to pipe-and-filter-style query language based on composable set transformations Fleshed out examples and addressed numerous editorial and technical issues processed through the TC Added Conformance section Committee Specification 02 2014-01-09 Ralf Hubert Heijkers Gerald Krause Michael Martin Zurmuehl Dynamic properties used all aggregated values.either via aliases or via custom aggregates Refactored annotations
Revision History Revision Date Editor Changes Made Working Draft 01 2012-11-12 Ralf Handl Translated contribution into OASIS format Committee Specification 01 2013-07-25 Ralf Handl Hubert Heijkers Gerald Krause Michael Pizzo Martin Zurmuehl Switched to pipe-and-filter-style query language based on composable set transformations Fleshed out examples and addressed numerous editorial and technical issues processed through the TC Added Conformance section Committee Specification Draft 02 2014-01-09 Ralf Handl Hubert Heijkers Gerald Krause Michael Pizzo Martin Zurmuehl Dynamic properties used all aggregated values. either via aliases or via custom aggregates Refactored annotations Committee Specification Draft 03 2015-07-16 Ralf Handl Hubert Heijkers Gerald Krause Michael Martin Zurmuehl Added compute transformation Minor clean-up
References The value of the references property is an object with one property per referenced CDSL document. The name of the property is the URI of the CSDL document. Its value is an object that may contain the properties includes and includeAnnotations. It also may contain . "references" : { "http://tinyurl.com/Org-OData-Measures-V1" : { "includes" : …, "@Some.Term" : … }, "http://somewhere/Vocabulary/V1" : { "includeAnnotations" : … } }, Includes The value of the includes property is an object with one property per included namespace. The name of the property is the namespace. Its value is an object that may have an alias property whose value is the alias of the included namespace. If no alias is defined, the object is empty. "includes" : { "Org.OData.Measures.V1" : { "alias" : "Core" }, "Another.Namespace" : {} }, IncludeAnnotations The value of the includeAnnotations property is an array of objects. Each object has a termNamespace property and may have a targetNamespace property or a qualifier property. The values of these properties are strings. "includeAnnotations" : [ { "termNamespace" : "Name.Space", "targetNamespace" : "Target.Space" }, { "termNamespace" : "Name.Space", "targetNamespace" : "qualifier" : "SomeName" }, { "termNamespace" : "NameSpace", "qualifier" : "SomeName" }, { "termNamespace" : "Name.Space" } ] Entity Types and Complex Types Each entity type and complex type is represented as a name/value pair of the standard JSON Schema definitions object. The name of the property is the qualified name of the entity type or
complex type. The value is a JSON Schema object. In addition to the standard properties it may contain the properties abstract, baseType, openType, properties, and navigationProperties. The object for an entity type may in addition contain the properties keys and hasStream. The properties abstract, openType, and hasStream have Boolean values. If not present, their value is false. The property baseType has a string value which is the qualified name of the base type. The object may contain . "definitions" : { "Customer" : { "abstract" : true, "keys" : …, "properties" : …, "@Some.Term" : … }, … }, Properties and Navigation Properties Each property and navigation property is represented as a pair of the standard JSON Schema properties object. … "properties" : { "ID" : { "type" : "string", }, "Description" : { "type" : ["string", "null"], "@Core.IsLanguageDependent" : {} }, "ReleaseDate" : { "type" : ["string", "null"], "odataType" : "Edm.Date" }, "DiscontinuedDate" : { "type" : ["string", "null"], "odataType" : "Edm.Date" }, "Rating" : { "type" : ["integer", "null"], "odataType" : "Edm.Int32" }, "Price" : { "type" : ["number", "null"], "odataType" : "Edm.Decimal", "@Org.OData.Measures.V1.ISOCurrency" : { "path" : "Currency" } },
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Ralf Transferred content from OData 4.0 Part 2 – URL Conventions Errata 3 Committee Specification 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Alternate keys Key-as-segment convention Operators in and divby $expand with stream properties $compute system query option system query option Committee Specification Draft 02 2017-06-08 Michael Pizzo Ralf More 4.01 features operations $expand, $select, $filter with POST and Instance annotations in query options $schemaversion system query option Committee Specification Draft 03 2017-09-28 Michael Pizzo Ralf Handl Incorporated review feedback nested query options within $select Added nested alias value assignments within $expand and $select
Core Vocabulary The Core vocabulary contains a set of basic annotation terms describing behavioral aspects along with annotation terms that can be used to define other vocabularies. Vocabulary Namespace: Term Name Term Description Lists the MIME types acceptable for the annotated entity type marked with HasStream="true" or the annotated stream property Instances of this type may contain properties in addition to those declared in $metadata If specified as false clients can assume that instances will not contain dynamic properties, irrespective of the value of the OpenType attribute. Communicates available alternate keys The service will automatically expand this navigation property even if not requested with $expand The service will automatically expand this navigation property as entity references even if not requested with $expand=.../$ref A value for this property is generated on both insert and update A unique identifier for nested entities within a request. Entity-ids follow OData URL conventions Functions, actions and types in this namespace can be referenced in URLs with or without namespace- or alias- qualification. Data Modelers should ensure uniqueness of schema children across all default namespaces, and should avoid naming bound functions, actions, or derived types with the same name as a structural or navigational property of the type. Entity-ids are URLs that locate the identified entity A description of a model element A value for this non-key property can be provided on insert and remains unchanged on update Properties and terms annotated with this term are Properties and terms annotated with this term MUST contain a valid MIME type Properties and terms annotated with this term MUST contain a valid URL A lengthy description of a model element A collection of qualified type names outside of the type hierarchy that instances of this type might be addressable as by using a type segment. The media type of a binary resource Instance annotation for warning and info messages