zilongwang/ReadingBank huggingface dataset:
int16 Edm.Int16 OData-specific format Edm.Int32 Swagger format int64 Edm.Int64 Swagger format int8 Edm.SByte OData-specific format single Edm.Single OData-specific format time Edm.TimeOfDay OData-specific format, was part of JSON Schema Draft 03 uint8 Edm.Byte OData-specific format uuid Edm.Guid OData-specific format
{ "@odata.path":"Address/CountryName" } ] } }, { "target":"ODataDemo.Product", "@Self.Tags":[ "MasterData" ] } ] } } }
the of the related resource. The link-entry MAY include an optional when attribute specifying when the link was created. Deleted Link Deleted links within a delta response are represented as deleted-link-entry objects. responses MUST contain a deleted-link-entry for each deleted link that corresponds to a $expand path in the initial request, unless either of the following is true: The source or target entity has been deleted The maximum cardinality of the related entity is one and there is a subsequent that specifies the same source and relationship. The deleted-link-entry has the following properties: – The property MUST be the first property and MUST be "deletedLinkEntry" source – The id of the entity from which the relationship is defined relationship - the name of the relationship property on the parent object target – The id of the related entity when – An optional datetime value indicating when the link was created The deleted-link-entry MUST contain a property specifying the of the entity from which the link was deleted, a property specifying the name of the navigation property for which the link was specified, and a attribute containing the of the related resource. The deleted-link-entry MAY include an optional when attribute specifying when the link was created.
FALL SEMESTER 2014-2015 Monday Tuesday Wednesday Thursday Friday Date Class Periods Date Class Periods Date Class Periods Date Class Periods Date Class Periods Week 1 8/11 8/12 ALL 8/13 ODD 8/14 EVEN 8/15 ODD Week 2 8/18 EVEN 8/19 ODD 8/20 EVEN 8/21 ODD 8/22 EVEN Week 3 8/25 ODD 8/26 EVEN 8/27 ODD 8/28 EVEN 8/29 Week 4 9/1 9/2 ODD 9/3 EVEN 9/4 ODD 9/5 EVEN Week 5 9/8 ODD 9/9 EVEN 9/10 ODD 9/11 EVEN 9/12 ODD Week 6 9/15 EVEN 9/16 ODD 9/17 EVEN 9/18 ODD 9/19 EVEN Week 7 9/22 ODD 9/23 EVEN 9/24 ODD 9/25 9/26 EVEN Week 8 9/29 ODD 9/30 EVEN 10/1 ODD 10/2 EVEN 10/3 ODD Week 9 10/6 EVEN 10/7 ODD 10/8 EVEN 10/9 ODD 10/10 EVEN Week 10 10/13 ODD 10/14 EVEN 10/15 ODD 10/16 EVEN 10/17 ODD Week 11 10/20 EVEN 10/21 ODD 10/22 EVEN 10/23 ODD 10/24 EVEN Week 12 10/27 ODD 10/28 EVEN 10/29 ODD 10/30 EVEN 10/31 ODD Week 13 11/3 EVEN 11/4 ODD 11/5 EVEN 11/6 ODD 11/7 EVEN Week 14 11/10 ODD 11/11 11/12 EVEN 11/13 ODD 11/14 EVEN Week 15 11/17 ODD 11/18 EVEN 11/19 ODD 11/20 EVEN 11/21 ODD Week 16 11/24 11/25 11/26 11/27 11/28 Week 17 12/1 EVEN 12/2 ODD 12/3 EVEN 12/4 ODD 12/5 EVEN Week 18 12/8 ODD 12/9 EVEN 12/10 ODD 12/11 EVEN 12/12 ODD Week 19 12/15 Finals Per 3 & 5 12/16 Finals Per 4 & 6 12/17 Finals Per 1 & 7 12/18 Final Per 2 12/19 MINIMUM DAY
Considerations This specification raises no security issues. This section is provided as a service to the application developers, information providers, and users of OData version 4.0 giving some references to starting points for securing OData services as specified. OData is a REST-full multi-format service that depends on other services and thus inherits both sides of the coin, security enhancements and concerns alike from the latter. For JSON-relevant security implications please cf. at the relevant subsections of [RFC4627] as starting point.
ODE TO THE INDIAN DUKAWALA ON EAST AFRICAN PLAINS ******** Done the Kisumu rail, And of all the Indian rail men, Many to in dhows sailed, But some majur the workers, And suthar the carpenters, As well luhar the smithy and tin workers, Stone masons and builders, In the country they had laboured, To commence a life new they remained, Then soon a fresh and new Indian breed, Of bold pioneering trading Sailed in the creaky wooden dhows, Along with the Indian crows, If lost at sea to guide them ashore, Towards ventures new to commence. Hara Ambe, Hara Ambe, An Indian dukawala, On the East African plains
Chapter 3: Cohort professional development Improving teacher development and management at all levels: STRIVE is the best example of successfully supporting teacher development while strengthening leadership and management of teachers. Strengthening Implementation of Basic Education in Selected Provinces of Visayas, Philippines Programs in the Pacific (Kiribati, Samoa, Vanuatu) and Nepal also used teacher professional development frameworks. Professional development outside government systems: these alternative delivery models reported some of the best outcomes among teacher development investments. However, they were not sustainable or scalable. Empowerment through Education for Afghanistan (CARE) Early Childhood Care and Education in Khyber Pakhtunkhwa, Pakistan (SCF) Basic Education Assistance for Mindanao in ARMM, Philippines (BRAC) Chapter 4: In-service qualification Qualification-directed teacher development: This was the least-used but potentially approach. In-service development for a qualification—as distinct from general professional development—demands a high quality curriculum and trainers. It needs the right study load, appropriate content for working teachers, and long-term government willingness, capacity and resources to sustain quality improvements. Education for All Fast Track Initiative, Laos Third Primary Education Development Program, Bangladesh Chapter 5: School-based professional development Improving leadership from school-level upwards: while yet to demonstrate school-level outcomes, ProDEP is working with government to strengthen how principals, supervisors and district managers lead and manage teachers at all levels. Professional Development of Education Personnel (ProDEP), Indonesia Many programs support and school-based management approaches. Cases not discussed in detail. promising
organisations that are shown to be most effective at leading to a sustained, integrated health response encompassing sexual and reproductive health, HIV and maternal health. funding and support for HIV mainstreaming where it facilitates greater Papua New Guinea ownership of HIV mainstreaming, by focusing resources where government departments and other partners have already demonstrated leadership. Was AusAID’s contribution efficiently managed? The decision to keep the management of the HIV Program ‘in house’ within AusAID was intended to provide continuity of leadership, high level engagement with the response, ensure greater flexibility to adapt to the context, and lighten the load of reporting. This management model has had benefits and drawbacks. The Program Director, a senior technical expert, has been in a position to advocate for HIV with the government and partners, and has helped drive the response. This feature of the model is very important and much appreciated by stakeholders. However, the HIV Program has had to take an increasing role in facilitating coordination due to low national capacity. As a consequence, the respective roles and responsibilities of the Papua New Guinea Government and Australian assistance in the response have become blurred. Another drawback is that, although managed in-house, in some respects the HIV Program continues to have the characteristics of a ‘contracted’ operational program, and its complexity places a significant management burden on AusAID’s staff. At the same time program reporting is less detailed than might be the case under a contractor, and not sufficiently detailed to give senior managers, or the evaluation team, a clear sense of efficiency or value for money. Recommendations Move to a program management model that combines strategic technical HIV capacity within AusAID and implementation through a managing contractor (international non-governmental organisation, national organisation or private sector). Full Report The full report, Responding to Crisis: Evaluation of the Australian aid program’s contribution to the national HIV response in PNG, 2006–2010, is available at www.ode.ausaid.gov.au A management response to the evaluation is included in the evaluation report. OFFICE DEVELOPMENT EFFECTIVENESS The Office of Development Effectiveness (ODE) monitors the performance of the Australian aid program, evaluates its impact and contributes to international evidence and debate about aid and development effectiveness. ODE Briefs are short, focused pieces of research and analysis on key findings and emerging themes on aid effectiveness. ode@ausaid.gov.au www.ode.ausaid.gov.au
Wilber I. Odem, Jr., Ph.D., P.E. Education Ph.D. Civil Engineering, Environmental Engineering Emphasis University of Arizona 1991 M.S. Civil Engineering, Environmental Engineering Emphasis University of Arizona 1985 B.A. Geosciences and Geography University of Texas, Austin 1981 Academic Experience Northern Arizona University Professor, Department of Engineering, Construction Management, and Environmental Engineering 2002 – present Full Time Interim Chair, Department of Construction Management 2009 Department of Civil and Environmental Engineering 2008 – 2009 Associate Professor, Department of and Environmental Engineering 1997 – 2002 Full Time Assistant Professor, Department of Civil and Environmental Engineering 1992 – 1997 Full Time University of Colorado, Boulder Research Associate 1991 – 1992 Full Time University of Arizona Research Associate 1988 – 1991 Full Time Research Assistant 1984 – 1985 Part Time Non-academic Experience Los Alamos National Laboratory Research Fellow Research Engineer Summer, 1993 Full Time HDR Engineering, Cameron Park, CA Environmental Engineer Environmental Engineer 1987 – 1988 Full Time Radian Corporation, Sacramento, CA Environmental Engineer Environmental Engineer 1986 – 1987 Full Time HydorGeoChem, Tucson, AZ Hydrogeological Technician Research Technician 1984 Part Time Certifications or Professional Registrations Civil Engineer, State of Arizona. Registration # 28114; State of Montana, Civil, Reg. # 21148
Delta Payload The non-format specific aspects of the delta handling are described in the section “Requesting Changes” in . Responses Responses from a delta request are returned as a JSON object. The JSON object MUST contain an array-valued property named value containing all , , or , as well as or between entities, and MAY contain additional, unchanged entities. If the response contains a partial list of changes, it MUST include a for the client to retrieve the next set of changes. The last page of a delta response SHOULD contain a for retrieving subsequent changes once the current set of changes has been applied to the initial set. If the response from the delta link contains a count annotation, the returned number MUST include all added, changed, or deleted entities to be returned, as well as added or deleted links. Example : a 4.01 response with five changes, in order of occurrence ContactName for customer was changed to "Susan Halvenstern" Order 10643 was removed from customer 'ALFKI' Order 10645 was added to customer 'BOTTM' The shipping information for order 10643 was updated Customer 'ANTON' was deleted { "@context":"http://host/service/$metadata#Customers/$delta", "@count":5, "value": [ { "@id":"Customers('BOTTM')", "ContactName":"Susan Halvenstern" }, { "@context":"#Customers/$deletedLink", "source":"Customers('ALFKI')", "relationship":"Orders", "target":"Orders(10643)" }, { "@context":"#Customers/$link", "source":"Customers('BOTTM')", "relationship":"Orders", "target":"Orders(10645)" }, { "@context":"#Orders/$entity", "@id":"Orders(10643)", "ShippingAddress":{ "Street":"23 Tsawassen Blvd.", "City":"Tsawassen", "Region":"BC", "PostalCode":"T2F 8M4" }, }, { "@context":"#Customers/$deletedEntity", "@removed": {
Revision History Revision Date Editor Changes Made Working 01 2016-06-22 Michael Ralf Handl Import material from OData 4.0 Errata 3 JSON document and initial application of 4.01 features Committee Specification Draft 01 2016-12-08 Michael Ralf Handl Integrated 4.01 features Committee Specification Draft 02 2017-06-08 Michael Pizzo Ralf Handl Integrated more 4.01 features, especially: Update of a collection of entities JSON Batch format Committee Specification Draft 03 2017-09-22 Michael Pizzo Ralf Handl Incorporated review feedback Committee Specification Draft 04 2017-11-10 Michael Ralf Handl Incorporated review feedback Changed default of continue-on-error Committee Specification 01 2017-12-19 Michael Pizzo Ralf Handl Non-Material Changes
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Ralf Import material from OData 4.0 Errata 3 JSON document and initial application of 4.01 features Committee Specification 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features
Extensibility Implementations can add of the form @namespace.termname or property@namespace.termname to any JSON object, property MAY or MAY NOT match the name of a name/value pair within the JSON object. However, the namespace MUST NOT start with odata and SHOULD NOT be required to be understood by the receiving party in order to correctly interpret the rest of the payload as the receiving party MUST ignore unknown annotations not defined in this version of the OData JSON Specification.
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Ralf Handl Import material from OData 4.0 Errata 3 JSON document and initial application of 4.01 features Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features Committee Specification 02 2017-06-08 Michael Pizzo Ralf Handl Integrated more 4.01 features, especially: Update of a collection of entities JSON Batch format Committee Specification Draft 03 2017-09-22 Michael Ralf Handl Incorporated review feedback Committee Specification Draft 04 2017-11-10 Michael Pizzo Ralf Handl Incorporated review feedback Changed default of continue-on-error
to keep data for each fish clearly associated with its scale sample, from collection in the field through scale analyses and data dissemination. Assign a Scale ID Number to each sample prior to OR at the time of scale collection. The Scale ID Number should be written on the scale sample envelope and be included in any field data collected at the time the scale is taken. Follow the protocol of your project. Data for each scale sample includes associated location and biological data. Follow the protocol manuals of our project (e.g., OASIS or CCRMP training manuals or other). Scale Collection Scale collection is often done in less than ideal field conditions. Most salmon species are coming in river during cold and wet weather. Even with difficult conditions, the FLHAP is better able to serve the needs of the project providing the scales if care is taken in collecting scales. The “key area” or anatomical location for cool water fish like salmonids is based upon where sockeye 1st generate their scales during development (Figure 1). The correct 5-step procedure for obtaining scale samples is as follows: Locate key area (Figure 1). Scrape slime off with non-serrated portion of knife. Pluck 4-5 scales with forceps and place in scale envelope, using care to not stack scales. Repeat on other side of fish. Allow scale envelopes to dry and organize in a well-ventilated container Figure 1. The key area is where scales first form on juvenile fish. These scales contain the most complete life history information. The key area is located above the lateral
For payloads with an OData-Version header equal to 4.0 the ExponentialDecimals=true format parameter indicates that the service MAY serialize Edm.Decimal numbers (including the , if requested) in exponential notation (e.g. 1e-6 instead of 0.000001). The sender of a request MUST specify ExponentialDecimals=true in the Content-Type header if the request body contains Edm.Decimal values in exponential notation. If not specified, or specified as ExponentialDecimals=false, all Edm.Decimal values MUST be serialized in long notation, using only an optional sign, digits, and an optional decimal point followed by digits. Payloads with an OData-Version header equal to 4.01 or greater always allow exponential notation for numbers and the ExponentialNotation format parameter is not needed or used.
Revision History Revision Date Editor Changes Made Working 01 2016-06-22 Michael Ralf Handl Import material from OData 4.0 Errata 3 JSON document and initial application of 4.01 features Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Handl Integrated 4.01 features
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Ralf Handl Import material from 4.0 Errata 3 JSON document and initial application of 4.01 features Committee Specification Draft 01 2016-12-08 Michael Ralf Handl Integrated 4.01 features
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Ralf Handl Import material from OData 4.0 Errata 3 JSON document and initial application of 4.01 features Committee Specification Draft 01 2016-12-08 Michael Pizzo Ralf Integrated 4.01 features Committee Specification 02 2017-06-08 Michael Pizzo Ralf Handl Integrated more 4.01 features, especially: Update of a collection of entities JSON format
Individual Property or Operation Response An individual property or operation response is represented as a JSON object. A single-valued property or operation response that has the null value does not have a representation; see . A property or operation response that is of a primitive type is represented as an object with a single name/value pair, whose name is value and whose value is a . A property or operation response that is of complex type is represented as a . A property or operation response that is of a collection type is represented as an object with a single name/value pair whose name is value. Its value is the JSON representation of a or . Example 22: primitive value { "@context": "http://host/service/$metadata#Edm.String", "value": "Pilar Ackerman" } Example 23: collection of primitive values { "@context": "http://host/service/$metadata#Collection(Edm.String)", "value": ["small", "medium", "extra large"] } Example 24: empty collection of primitive values { "@context": "http://host/service/$metadata#Collection(Edm.String)", "value": [] } Example 25: complex value { "@context": "http://host/service/$metadata#Model.Address", "Street": "12345 Grant Street", "City": "Taft", "Region": "Ohio", "PostalCode": "OH 98052", "Country@navigationLink": "Countries('US')" } Example 26: empty collection of complex values { "@context":"http://host/service/$metadata#Collection(Model.Address)", "value": [] } Note: the context URL is optional in requests.
Example 45: a batch request that contains the following individual requests in the order listed A query request An atomicity group that contains the following requests: Insert entity Update entity A second query request Note: For brevity, in the example, request bodies are excluded in of English descriptions inside <> brackets and OData-Version headers are omitted. POST /service/$batch HTTP/1.1 Host: host OData-Version: 4.01 Content-Type: application/json Content-Length: ### { "requests": [ { "id": "0", "method": "get", "url": "/service/Customers('ALFKI')" }, { "id": "1", "atomicityGroup": "group1", "dependsOn": ["0" ], "method": "patch", "url": "/service/Customers('ALFKI')", "headers": { "Prefer": "return=minimal" }, "body": <JSON representation of changes to Customer ALFKI> }, { "id": "2", "atomicityGroup": "group1", "method": "post", "url": "/service/Customers", "body": <JSON representation of a new Customer entity> }, { "id": "3", "dependsOn": [ "group1" ], "method": "get", "url": "/service/Products" } ] }
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Ralf Import material from OData 4.0 Errata 3 JSON document and initial application of 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 Integrated more 4.01 features, especially: Update of a collection of entities JSON Batch format Committee Specification Draft 03 2017-09-22 Michael Pizzo Ralf Incorporated review feedback Committee Specification 04 2017-11-10 Michael Pizzo Ralf Handl Incorporated review feedback Changed default of continue-on-error
Action Invocation Action parameter values are encoded in a single JSON object in the request body. Each non-binding parameter value is encoded as a separate name/value pair in this JSON object. The name is the name of the parameter. The value is the parameter value in the JSON representation appropriate for its type. Entity typed parameter values MAY include a subset of the properties, or just the , as appropriate to the action. Any parameter values not specified in the JSON object are assumed to have the null value. Example 44: { "param1": 42, "param2": { "Street": "One Microsoft Way", "Zip": }, "param3": [ 1, 42, 99 ], "param4": null } In order to invoke an action with no non-binding parameters, the client passes an empty JSON object in the body of the request. 4.01 Services MUST also support clients passing an empty request body for this case.
Revision History Revision Date Editor Changes Made Working Draft 01 2016-06-22 Michael Pizzo Ralf Handl Import material from OData 4.0 Errata 3 JSON document and initial application of 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 Pizzo Ralf Integrated more 4.01 features, especially: Update of a collection of entities JSON Batch format Committee Specification Draft 03 2017-09-22 Michael Ralf Handl Incorporated review feedback Committee Specification Draft 04 2017-11-10 Michael Pizzo Ralf Handl Incorporated review feedback Changed default of continue-on-error Committee Specification 01 2017-12-19 Michael Pizzo Ralf Handl Non-Material Changes
Usual Industry Duration Entry [observation: identifier (open)] A Usual Industry Duration Entry is a clinical statement about the quantity of time a person spent in a particular industry in which they worked for the longest over the course of their life. SHALL contain exactly one [1..1] @classCode="OBS" (CodeSystem: HL7ActClass urn:oid:2.16.840.1.113883.5.6). contain exactly one [1..1] @moodCode="EVN" Event (CodeSystem: ActMood urn:oid:2.16.840.1.113883.5.1001) . contain exactly one [1..1] templateId such that it SHALL contain exactly one [1..1] @root="1.3.6.1.4.1.19376.1.5.3.1.4.20.10". SHALL contain at least one [1..*] id . SHALL contain exactly one [1..1] code. This code SHall contain exactly one [1..1] @code="74162-9" (Usual Industry Duration). This code SHall contain exactly one [1..1] @codesystem="2.16.840.1.113883.6.1" LOINC (CodeSystem: LOINC urn:oid:2.16.840.1.113883.6.1). SHALL contain exactly one [1..1] statusCode="completed" Completed (CodeSystem: ActStatus urn:oid:2.16.840.1.113883.5.14) . SHALL contain exactly one [1..1] value with @xsi:type="PQ". This value SHALL contain exactly one [1..1] @unit, which SHALL include duration-related units from value set UCUM urn:oid:2.16.840.1.113883.1.11.12839.
"@custom.ItemIsA":"X.Movie" }, "SomeThing":{ "": "Y.SomeThingType" } } Annotations Annotations can appear inline within a element, or externally as a block that targets a model element. Annotations with external targeting are represented as an annotations name/value pair whose value is an array of JSON objects. Each of these objects contains a target name/value pair whose value is a string with a path expression identifying the annotated model element. In addition, each object contains at least one annotation in the same format that is used for inline annotations and specified in the remaining part of this section. Example : Annotations with external targeting "annotations":[ { "target":"Some.EntityType/SomeProperty", "@X.Y":…, … }, { "target":"Another.EntityType", "@X.Y":…, … }, … ] Annotations are represented similar to instance annotations in , chapter 18. Annotations for JSON objects are name/value pairs placed within the object, the name is an at (@) sign followed by the namespace-qualified name of the term, optionally followed by a hash (#) sign and the qualifier of the annotation. Annotations for JSON arrays or primitives are pairs placed next to the name/value pair whose value is the annotated array or primitive value. The name is the name of the annotated name/value pair followed by the namespace-qualified name of the term, optionally followed by a hash (#) sign and the qualifier of the annotation. The value of the annotation is either a plain JSON value or a JSON object. Example : annotation within an object, annotation of a non-object and annotation of an annotation "@Some.Term" : …, "Hugo@Some.Term" : …, "@Some.Term#SomeQualifier@Some.Term": … Annotations without Explicit Annotations that don't specify an explicit value are represented with an empty object as their value. The actual value is the default value of the term.
164. Π. Δαγτόγλου, Γενικό Διοικητικό Δίκαιο, 2004, σ. 467. Αντιστρόφως, πρέπει να θεωρούνται αντισυνταγματικές διατάξεις που απαγορεύουν τη χορήγηση αναστολής από το δικαστήριο. Ν. Χατζητζανή, Κώδιξ Διοικητικής Δικονομίας, 2004, σ. 1183 165. Ν. Χατζητζανή, Κώδιξ Διοικητικής Δικονομίας, 2004, σ. 1195 166. Ν. Χατζητζανή, Διοικητικής Δικονομίας, 2004, σ. 1200
OAS Document Structure OAS documents are represented as JSON objects and conform to [RFC7159]. [YAML], being a superset of JSON, can be used as well to represent an OAS document. An OAS document consists of a single , see [OpenAPI]. It is represented as a JSON object. How to construct each of its name/value pairs (“fields” in OpenAPI terminology) is described in the following sections. Example : Structure of an OAS document { "swagger":"2.0", "info": …, "schemes": …, "host": …, "basepath": …, "consumes": …, "produces": …, "tags": …, "paths": …, "definitions": …, "parameters": …, "responses": … } Field swagger The value of swagger is the string "2.0". Field info The of info is an , see [OpenAPI]. It contains the fields title and version, and it contains the keyword description. Example : Info Object – note that description accepts Markdown format "info":{ "title":"OData Service for namespace ODataDemo", "version":"0.1.0", "description":"This OData service is located at http://localhost/service-root/\n\n## References\n- } Field title The of title is the value of the unqualified annotation Core.Description of the main schema or the entity container of the OData service.
], The parameters array contains for system query options allowed for this t does not list system query options not allowed for this , , , , and in . Example : GET operation for an entity set - parameters "parameters": [ { "$ref": "#/parameters/top" }, { "$ref": "#/parameters/skip" }, { "$ref": "#/parameters/search" }, { "$ref": "#/parameters/filter" }, { "$ref": }, Note: the syntax of the system options , , and is too flexible to be formally described with OpenAPI Specification means, yet the typical use cases of just providing a comma-separated list of properties can be expressed via an array-valued parameter with an enum constraint, as shown in the following example. This makes it easy to try out these system query options in OpenAPI tools. Example : GET operation for an entity set – more specific parameters { "name": "$expand", "in": "query", "description": "Expand related entities, see [OData Expand]()", "type": "array", "uniqueItems": true, "items": { "type": "string" , "enum": [ "*", "Category", "Supplier" ] }, { "name": "$select", "in": "query", "description": "Select properties to be returned, see [OData Select]()",
Works offline No No No No Yes No Platform fully free of charge or are there costs related to various plans? Yes Hosted and supported by UN OCHA Yes Internal costs Google Engine pricing structure Yes No (from $99 to $199 per Degree of technical knowledge to set the platform None None IT or ODK expert needed IT or ODK expert needed Advanced None XLSForms can be loaded directly Yes Yes No (first convert XLSForm to XForm) No (first convert XLSForm to XForm) No (first convert XLSForm to XForm) Yes Limits on the number of submissions and Gb of storage space (per week, month, year)? Unlimited Unlimited Limited to server’s size Limited by the related Limited by computer size Yes (500 submissions per calendar month with 15 private forms, 1 private project and unlimited public projects) Quick visualisation of data on a map (without GIS manipulations)? Yes To be verified No No No Yes Platform compatible with the “pulldata” function enabling to preload data into forms? Yes No To be verified To be verified To be verified Yes Can the platform accept several administrators for a same form? No, but possible to clone a form To be verified Yes Yes No, because the form is on 1 PC only Yes In case of an existing Internet connexion, Kobo Toolbox is recommended as it enables: a quick deployment and easy maintenance of tools a secure storage of data all that at no cost In case of the absence of Internet connexion, ODK Aggregate VM will be recommended. Follow the steps below when choosing this solution: Download and install VirtualBox () to run the VM. Download ODK Aggregate VM . Follow the readme.txt instructions (“# Usage” section) Convert the XLSForm (.xls format) to an XForm (.xml format). We recommend . Use ODK Aggregate, all instructions available in the following link: NB: All tools here above are available in the ODK Resources folder. Design the Several open source software options for mobile data collection by humanitarian organizations exist. The solution selected by IFRC is Open Data Kit (ODK), with ODK Collect app for Android devices. Two important links exist to dig in further into ODK:
ValidTo → ??? Both → do not allow Precedence: URL wins over body $from/$to wins over key values because client demonstrated knowledge of Temporal annotation wins over property because client demonstrated knowledge of Temporal and we don’t want Bad Requests POST PATCH PUT DELETE from and to specified (as key part or otherwise) Treated identical to PUT, only exception are key properties Existing slices before/after truncated Existing fully covered slices changed, optionally compacted Non-existing slices created Same as PATCH, setting unspecified properties to default values (normal PUT behavior) Existing slices truncated Existing fully covered slices deleted/shadowed Only from specified, only as key part →assume client is unaware of Temporal to defaults to start of next time slice, or max if no next time slice exists to defaults to start of next time slice, or max if no next slice exists to defaults to start of next time slice, or max if no next time slice exists Only from specified, not as key part → client is aware of Temporal to defaults to max to defaults to max to defaults to max to defaults to max Only to specified, only as key part →assume client is unaware of Temporal from defaults to of time slice Only to specified (as key part or otherwise) from defaults to min from defaults to min from defaults to min from defaults to min Neither specified → not part of key →assume client is unaware of Temporal Treated identical to PUT, only exception are key properties from defaults to now, to defaults to max Rationale: change is visible immediately afterwards and remains as Same as PATCH, setting unspecified properties to default values (normal PUT behavior) from defaults to now, to defaults to max Rationale: same as for PATCH
ABNF Construction Rules Line Change Issue lambdaPredicateExpr = boolCommonExpr ; containing at one lambdaVariablePredicatePrefixExpr day = ( "0" / "1" / "2" ) oneToNine / ( "1" / "2" ) DIGIT / "3" ( "0" / "1" )
EDM Type JSON Schema Comment Type Format Keywords Edm.Binary string base64url maxlength byteLength OData-specific format maxLength is maximum length of string representation, i.e. 4*ceil(MaxLength/3) byteLength is the maximum length of the binary in octets Edm.Boolean boolean Edm.Byte integer uint8 OData-specific format Edm.Date string date Swagger format Edm.DateTimeOffset string date-time precision OData-specific keyword Edm.Decimal number, string decimal minimum maximum multipleOf precision scale OData-specific format string is needed for IEEE754Compatible mode OData-specific keywords precision and scale Edm.Double double Swagger format with extended meaning string is needed for -INF, INF, and NaN Edm.Duration string duration OData-specific format Edm.Guid string uuid OData-specific format Edm.Int16 integer int16 OData-specific format integer int32 Swagger format Edm.Int64 integer, string int64 Swagger format string is needed for IEEE754Compatible mode Edm.SByte integer int8 OData-specific format Edm.Single single OData-specific format string is needed for -INF, INF, and NaN Edm.String string maxlength Sequence of UTF-8 characters Edm.TimeOfDay string time precision OData-specific format OData-specific keyword Properties of type Edm.Decimal and Edm.Int64 are represented as JSON strings if the format option IEEE754Compatible=true is specified, so they have to be declared with both number and string.
Revision History Revision Date Editor Changes Made Working Draft 01 2012-08-22 Michael Pizzo Translated Contribution to OASIS format/template Committee Specification Draft 01 2013-04-26 Michael Ralf Handl, Martin Zurmuehl Simplified annotations, relationships, added containment, singletons Added Type Definitions, Edm.Date, Edm.TimeOfDay, Edm.Duration datatypes. Retired Edm.DateTime, Edm.Time. Enhanced ComplexType support Expanded Service Document Fleshed out descriptions and examples and addressed numerous editorial and technical issues processed through the TC Added Conformance section Committee Specification Draft 02 2013-07-01 Michael Ralf Handl, Martin Zurmuehl Restricted services to exactly one entity container Simplified function and action overloads Rounded off annotaitons Fleshed out containment Simplified rules for implicit enum member values Clarified intention of Partner and NavigationPropertyBinding Simplified and completed CSDL for Metadata Service, added description of behavior Committee Specification 01 2013-07-30 Michael Pizzo, Ralf Handl, Martin Zurmuehl Non-Material Changes
Acknowledgments The following individuals were members of the OASIS OData Technical Committee during the creation of this specification and their contributions are gratefully acknowledged: Howard Abrams (CA Technologies) Ken Baclawski (Northeastern University) Jay Balunas (Red Hat) Mark Biamonte (Progress Software) Matthew Borges (SAP AG) Edmond Bourne (BlackBerry) Joseph Boyle (Planetwork, Inc.) Peter Brown (Individual) Antonio Campanile (Bank of America) Pablo Castro (Microsoft) Axel Conrad (BlackBerry) Cover (OASIS) Erik de Voogd (SDL) Diane Downie (Citrix Systems) Stefan Drees (Individual) Patrick Durusau (Individual) Andrew Eisenberg (IBM) Chet Ensign Davina Erasmus (SDL) Colleen Evans (Microsoft) Senaka Fernando (WSO2) Brent Gross (IBM) Zhun Guo (Individual) Anila Kumar GVN (CA Technologies) Ralf Handl (SAP AG) Barbara Hartel (SAP AG) Hubert Heijkers (IBM) Jens Hüsken (SAP AG) Evan Ireland (SAP AG) Gershon Janssen (Individual) Ram Jeyaraman (Microsoft) Ted (Red Hat) Diane Jordan (IBM) Stephan Klevenz (SAP AG) Gerald Krause (SAP AG) Nuno Linhares (SDL) Paul Lipton (CA Technologies) Malaika (IBM) Ramanjaneyulu Malisetti (CA Technologies) Neil McEvoy (iFOSSF – International Free and Open Source Solutions Foundation) Stan Mitranic (CA Technologies) Dale Moberg (Axway Software) Graham (BrightstarDB Ltd.) Farrukh Najmi (Individual) Shishir Pardikar (Citrix Systems) Sanjay Patil (SAP AG) Nuccio Piscopo (iFOSSF – International Free and Open Source Solutions Foundation) Michael Pizzo (Microsoft) Robert Richards (Mashery) Sumedha Rubasinghe (WSO2) James Snell (IBM) Jeffrey Turpin Software) John Willson (Individual) John Wilmes (Individual) Christopher Woodruff (Perficient, Inc.) Martin Zurmuehl (SAP AG)
Acknowledgments The following individuals were members of the OASIS OData Technical Committee during the creation of this specification and their contributions are gratefully acknowledged: Howard Abrams (CA Technologies) Ken Baclawski (Northeastern University) Jay Balunas (Red Hat) Mark Biamonte (Progress Software) Matthew Borges (SAP AG) Edmond Bourne (BlackBerry) Joseph Boyle (Planetwork, Inc.) Brown (Individual) Antonio Campanile (Bank of America) Pablo Castro (Microsoft) Axel Conrad (BlackBerry) Robin Cover (OASIS) Erik de Voogd (SDL) Diane Downie (Citrix Systems) Stefan Drees (Individual) Patrick Durusau (Individual) Andrew Eisenberg (IBM) Chet Ensign Davina Erasmus (SDL) Colleen (Microsoft) Senaka Fernando (WSO2) Brent Gross (IBM) Zhun Guo (Individual) Anila Kumar GVN (CA Technologies) Ralf Handl (SAP AG) Barbara Hartel (SAP AG) Hubert Heijkers (IBM) Jens Hüsken (SAP AG) Evan Ireland (SAP AG) Gershon Janssen (Individual) Ram Jeyaraman (Microsoft) Ted (Red Hat) Diane Jordan (IBM) Stephan Klevenz (SAP AG) Gerald Krause (SAP AG) Nuno Linhares (SDL) Paul Lipton (CA Technologies) Susan Malaika (IBM) Ramanjaneyulu Malisetti (CA Technologies) Neil McEvoy (iFOSSF – International Free and Open Source Solutions Foundation) Stan Mitranic (CA Technologies) Dale Moberg (Axway Software) Graham Moore (BrightstarDB Ltd.) Farrukh Najmi (Individual) Shishir Pardikar (Citrix Systems) Sanjay Patil (SAP AG) Nuccio Piscopo (iFOSSF – International Free and Open Source Solutions Foundation) Michael (Microsoft) Robert Richards (Mashery) Sumedha Rubasinghe (WSO2) James Snell (IBM) Jeffrey Turpin (Axway Software) John Willson (Individual) John Wilmes (Individual) Christopher Woodruff (Perficient, Inc.) Martin Zurmuehl (SAP AG)
Revision History Revision Date Editor Changes Made Working Draft 01 2012-08-22 Michael Translated Contribution to OASIS format/template Committee Specification Draft 01 2013-04-26 Michael Pizzo, Ralf Handl, Martin Zurmuehl Added Delta support, Asynchronous processing, Upsert Aligned and expanded Prefer header preferences Simplified data model Defined rules and semantics around distributed metadata Fleshed out descriptions and examples and addressed numerous editorial and technical issues processed through the TC Added Conformance section Committee Specification Draft 02 2013-07-01 Michael Pizzo, Ralf Handl, Martin Zurmuehl Cleaned up action and function overloads and binding, removed old-style function parameter syntax Improved asynchronous processing and added callback notifications Improved context URL (formerly: metadata URL) Improved handling of empty results Improved description of rules for processing PUT and POST requests, especially deep inserts Harmonized and $inlinecount Committee Specification 01 2013-07-30 Michael Pizzo, Ralf Handl, Martin Zurmuehl Non-Material Changes Committee Specification Draft 03 2013-10-03 Michael Ralf Handl, Martin Zurmuehl Improved description of type-cast rules
Acknowledgments The following individuals were members of the OASIS OData Technical Committee during the creation of this specification and their contributions are gratefully acknowledged: Howard Abrams (CA Technologies) Ken Baclawski (Northeastern University) Jay Balunas (Red Hat) Mark Biamonte (Progress Software) Matthew Borges (SAP AG) Edmond Bourne (BlackBerry) Joseph Boyle (Planetwork, Inc.) Brown (Individual) Antonio Campanile (Bank of America) Pablo Castro (Microsoft) Axel Conrad (BlackBerry) Robin Cover (OASIS) Erik de Voogd (SDL) Diane Downie (Citrix Systems) Stefan Drees (Individual) Patrick Durusau (Individual) Andrew Eisenberg (IBM) Chet Ensign Davina Erasmus (SDL) Colleen Evans (Microsoft) Senaka Fernando (WSO2) Brent Gross (IBM) Zhun Guo (Individual) Kumar GVN (CA Technologies) Ralf Handl (SAP AG) Barbara Hartel (SAP AG) Hubert Heijkers (IBM) Jens Hüsken (SAP AG) Evan Ireland (SAP AG) Gershon Janssen (Individual) Ram Jeyaraman (Microsoft) Ted Jones (Red Hat) Diane Jordan (IBM) Stephan Klevenz (SAP AG) Gerald Krause (SAP AG) Nuno Linhares (SDL) Paul Lipton (CA Technologies) Malaika (IBM) Ramanjaneyulu Malisetti (CA Technologies) Neil McEvoy (iFOSSF – International Free and Open Source Solutions Foundation) Stan Mitranic (CA Technologies) Dale Moberg (Axway Software) Graham Moore (BrightstarDB Ltd.) Farrukh Najmi (Individual) Shishir Pardikar (Citrix Systems) Sanjay Patil (SAP AG) Nuccio Piscopo (iFOSSF – International Free and Open Source Solutions Foundation) Michael Pizzo (Microsoft) Robert Richards (Mashery) Sumedha Rubasinghe (WSO2) James Snell (IBM) Jeffrey Turpin (Axway Software) John Willson (Individual) John Wilmes (Individual) Christopher Woodruff (Perficient, Inc.) Martin Zurmuehl (SAP AG)
Revision History Revision Date Editor Changes Made Working Draft 01 2012-08-22 Michael Pizzo Translated Contribution to format/template Committee Specification Draft 01 2013-04-26 Ralf Handl Michael Pizzo Martin Zurmuehl Added Full-Text Search, modified expand syntax, expand options, crosstabs, enumerations Fleshed out descriptions and examples and addressed numerous editorial and technical issues processed through the TC Added Conformance section Committee Specification Draft 02 2013-07-01 Ralf Handl Michael Martin Zurmuehl Described which query options are applicable to which resource types and HTTP methods Simplified URL syntax Extended expand with a STAR operator Added special resources for cross-service search, cross joins, resolution of entity-ids Described handling of null values, division by zero, and overflow in arithmetic operations Added filtering for collections of complex and primitive types Committee Specification 01 2013-07-30 Michael Pizzo, Ralf Handl, Martin Zurmuehl Non-Material Changes Committee Specification Draft 03 2013-10-03 Michael Pizzo, Ralf Handl, Martin Zurmuehl Accessing properties of derived types Examples for primitive literals Precedence of has operator Committee Specification 02 2013-11-04 Michael Pizzo, Ralf Handl, Martin Zurmuehl Non-Material Changes OASIS Specification 2014-02-24 Michael Pizzo, Ralf Handl, Martin Zurmuehl Non-Material Changes Errata 01 2014-07-24 Michael Ralf Handl, Martin Zurmuehl Minor changes and improvements Errata 02 2014-10-29 Michael Pizzo, Ralf Handl, Martin Zurmuehl Repaired mechanical in the editable source
and Function Element edm:Action The edm:Action element represents an action in an entity Actions MAY have observable side effects and MAY return a single instance or a collection of instances of any type. Actions cannot be composed with additional path segments. The action MAY specify a return type using the element. The return type must be a primitive, entity or complex type, or a collection of primitive, entity or complex types. The action may also define zero or more elements to be used during the execution of the action. Attribute Name The edm:Action element MUST include a Name attribute whose value is a . Action Overload Rules actions support overloading (multiple actions having the same name within the same namespace) by binding parameter type. The combination of action name and the binding parameter type MUST be unique within a namespace. actions do not support overloads. The of all unbound actions MUST be unique within a namespace. An unbound action MAY have the same name as a bound action. Attribute IsBound An action element MAY specify a value for the IsBound attribute. Actions whose IsBound attribute is false or not specified are considered unbound. Unbound actions are invoked through an . Actions IsBound attribute is true are considered bound. Bound actions are invoked by appending a segment containing the qualified action name to a segment of the appropriate binding parameter type within the resource path. Bound actions MUST contain at least one element, and the first parameter is the binding parameter. The binding parameter can be of any type, and it MAY be . Attribute EntitySetPath actions that return an entity or a collection of entities MAY specify a value for the EntitySetPath attribute if determination of the entity set for the return type is contingent on the binding parameter. The value for the EntitySetPath attribute consists of a series of segments joined together with forward slashes. The first segment of the entity set path MUST be the name of the binding parameter. The remaining segments of the entity set path MUST represent navigation segments or type casts. A navigation segment names the of the to be traversed. A type cast segment names the of the entity type that should be returned from the type cast. Element edm:Function The edm:Function element represents a function in an entity Functions MUST NOT have observable side effects and MUST return a single instance or a collection of instances of any type. Functions MAY be composable.
Collection of Entity References Context URL template: {context-url}#Collection($ref) If a response is a collection of entity references, the context URL does not contain the type of the referenced entities. Example 23: resource URL and corresponding context URL for a collection of entity references http://host/service/Customers('ALFKI')/Orders/$ref http://host/service/$metadata#Collection($ref) Entity Reference Context URL template: {context-url}#$ref If a response is a single entity reference, $ref is the context URL fragment. Example 24: resource URL and corresponding context URL for a single entity reference http://host/service/Orders(10643)/Customer/$ref http://host/service/$metadata#$ref Property Value Context URL templates: {context-url}#{entity}/{property-path}{select-list} {context-url}#{type-name}{select-list} If a response represents an of an entity with a canonical URL, the context URL specifies the canonical URL of the entity and the path to the structural property of that entity. The path MUST include cast segments for properties defined on types derived from the expected type of the previous segment. If the property value does not contain explicitly or implicitly selected navigation properties or operations, OData 4.01 responses MAY use the less specific second template. Example 25: resource URL and corresponding context URL http://host/service/Customers(1)/Addresses http://host/service/$metadata#Customers(1)/Addresses Collection of Complex or Primitive Context URL template: {context-url}#Collection({type-name}){select-list} If a response is a collection of complex types or primitive types that do not represent an individual property of an entity with a canonical URL, the context URL specifies the fully qualified type of the collection. Example 26: resource URL and corresponding context URL http://host/service/TopFiveHobbies() http://host/service/$metadata#Collection(Edm.String)
Panelist Favorite Founder(s) OD Area Resources Julie Benesh Harrison Owen Open Dick Axelrod Barbara Bunker T-Groups, conflict resolution, Gender, Trust Future Search, Don’t just Do Something Marv Weisbord Self-directed work teams, 6 box model Kendra M. Coleman Elaine Kepner Gestalt OSD Group Process Bruce Mabee Fritz Steele Design, Innovation & OD The Physical Setting and OD Arrogant Leaders Margaret Posig Kurt Lewin Change Model, Action research Eric Sanders Mary Parker Follet Participative Management Peter Sorensen Douglas McGregor Intervening variables, Theory X- Y Rensis Likert Surveys – "5-Point Likert Scale" Blake & Mouton Managerial Grid: Task/People Marv Weisbord 6-box Productive Workplaces Therese Yaeger Dick Beckhard Formula for Change Organizational Transitions: Managing Complex Change Group’s Additional Favorite Founders Martin Seligman Frank Burns Fred Miller Steve Piersanti Dick Byrd (‘Big Bird’) Peter Koestenbaum Robert Keegan Kathie Dannemiller Eugene Gendlin Lisa Kimball Lisa Bill Gellerman Calvin Pava Jay Galbraith Thomas Gordon Roland Sullivan Barry Johnson Judith Katz Observations. What bubbles up for you from this discussion? OD practitioners build and divide on each other built on history and connections OD heritage chart, tree of your own OD heritage or genealogy Challenge each other on sources Generosity about them – Schein (seeks feedback / input) Work is done at different levels Trust the process Where to? Future of OD Can you do OD in text? Can algorithms capture all the ideas? Complexity Interconnectedness (all over the world) in a disconnected world, the meaning of meaning, are we falling behind? Facebook in OD (Intervention?) Democratization What can we do in the community (e.g. Ferguson) Digital OD – hubs in Chicago- Bring in Techy People We’re getting pushed out – deal with tough subjects – what’s the core? What is OD now? Why are we still not getting in? – Millennials can help Value and relevance of OD