diff --git a/.github/workflows/publish_to_production_slot.yml b/.github/workflows/publish_to_production_slot.yml index 5894f9e8..9ffbe9ab 100644 --- a/.github/workflows/publish_to_production_slot.yml +++ b/.github/workflows/publish_to_production_slot.yml @@ -25,7 +25,7 @@ jobs: run: | docker run \ -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \ - jekyll/builder:stable /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --future" + jekyll/builder:stable /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --config _config.yml --future" - name: Log in with Azure # Using Azure Service Principal uses: azure/login@v1 diff --git a/.github/workflows/publish_to_staging_slot.yml b/.github/workflows/publish_to_staging_slot.yml index 7d0e68ac..3f39370b 100644 --- a/.github/workflows/publish_to_staging_slot.yml +++ b/.github/workflows/publish_to_staging_slot.yml @@ -25,7 +25,7 @@ jobs: run: | docker run \ -v ${{ github.workspace }}:/srv/jekyll -v ${{ github.workspace }}/_site:/srv/jekyll/_site \ - jekyll/builder:stable /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --future" + jekyll/builder:stable /bin/bash -c "chmod -R 777 /srv/jekyll && jekyll build --config _config_staging.yml --future" - name: Log in with Azure # Using Azure Service Principal uses: azure/login@v1 diff --git a/_config_staging.yml b/_config_staging.yml new file mode 100644 index 00000000..b7d7b4c0 --- /dev/null +++ b/_config_staging.yml @@ -0,0 +1,31 @@ +# Site settings +title: OData - the Best Way to REST +email: odata-discussion@googlegroups.com +description: > # this means to ignore newlines until "baseurl:" + OData, short for Open Data Protocol, is an open protocol + to allow the creation and consumption of queryable and interoperable RESTful APIs + in a simple and standard way. +baseurl: "" # the subpath of your site, e.g. /blog/ +url: "https://odata-prod-stage.azurewebsites.net" # the base hostname & protocol for your site +twitter_username: odataorg +github_username: odataorg + +collections: + ecosys: + output: true + permalink: /ecosystem/:categories/:title/ + libraries: + output: true + tutorials: + output: true + permalink: /tutorials/:title/ + +permalink: /blog/:title/ + +# highlighter: pygments + +# Build settings +markdown: kramdown + +gems: + - jekyll-sitemap diff --git a/_ecosys/consumers/Client-Libraries.md b/_ecosys/consumers/Client-Libraries.md index 04e9c936..ce5dc7d5 100644 --- a/_ecosys/consumers/Client-Libraries.md +++ b/_ecosys/consumers/Client-Libraries.md @@ -2,6 +2,6 @@ layout: default category: consumers title: "Client Libraries" -link: "https://www.odata.org/libraries" +link: "/libraries" --- Client libraries are programming libraries that make it easy to consume OData services. We already have libraries that target: Javascript, PHP, Java, Windows Phone 7 Series, iPhone (Objective C) and .NET. For a complete list visit the OData SDK. diff --git a/_ecosys/sdk/Sample-Services.md b/_ecosys/sdk/Sample-Services.md index bf45ce77..508d3d16 100644 --- a/_ecosys/sdk/Sample-Services.md +++ b/_ecosys/sdk/Sample-Services.md @@ -4,4 +4,4 @@ category: sdk title: "Sample Services" github: "https://github.com/OData/ODataSamples" --- -Github repository of ODataSamples, including code used in [here](https://www.odata.org/odata-services/). +Github repository of ODataSamples, including code used in [here](/odata-services/). diff --git a/_includes/head.html b/_includes/head.html index 0b1fe7e1..22bd67dc 100644 --- a/_includes/head.html +++ b/_includes/head.html @@ -31,7 +31,7 @@ --> - + diff --git a/_posts/2010-04-13-odata-weekly-roundup-2.html b/_posts/2010-04-13-odata-weekly-roundup-2.html index 6cb76085..3fb3bfc0 100644 --- a/_posts/2010-04-13-odata-weekly-roundup-2.html +++ b/_posts/2010-04-13-odata-weekly-roundup-2.html @@ -19,8 +19,8 @@
Many exciting things have happened in the OData world since our last post.
In case you haven't heard already we are putting on an OData Roadshow.
+In case you haven't heard already we are putting on an OData Roadshow.
Douglas Purdy and Jonathan Carter will be presenting and guiding attendees through a free day's worth of OData goodness.
The Roadshow will visit each of these locations:
Chris (aka Woody) Woodruff has organized a series of OData workshops to compliment the official OData Roadshow.
-This is highly recommended. So if for whatever reason you can't make it to one of the OData Roadshow events, or you just can't get enough OData, see if you can get along to one of Chris' workshops.
+This is highly recommended. So if for whatever reason you can't make it to one of the OData Roadshow events, or you just can't get enough OData, see if you can get along to one of Chris' workshops.
The workshops start in Raleigh tomorrow and finish in NYC on June 28th.
Today we released an OData Mailing List. This is the list to use if you have OData questions, comments on OData or want to discuss how OData should evolve over time.
To sign up to the list go here and follow the instructions provided. The list is fully open so anyone can subscribe and participate. Be sure to read the terms of use on the signup page to understand how your feedback on the mailing list may be used to enhance OData over time.
-You can see a read only archive of all the messages from the mailing list here: /mailing-list
+You can see a read only archive of all the messages from the mailing list here: /mailing-list
We look forward to hearing your thoughts, comments and feedback!
diff --git a/_posts/2010-07-30-enhancing-odata-support-for-querying-derived-types.html b/_posts/2010-07-30-enhancing-odata-support-for-querying-derived-types.html index e6e87f6b..1c841bda 100644 --- a/_posts/2010-07-30-enhancing-odata-support-for-querying-derived-types.html +++ b/_posts/2010-07-30-enhancing-odata-support-for-querying-derived-types.html @@ -111,6 +111,6 @@
As you can see we've come up with two options to add better support for Derived types in OData queries.
Which do you prefer? And why? Perhaps you have another suggestion?
-Whatever you think, please tell us all about it on the OData Mailing List.
+Whatever you think, please tell us all about it on the OData Mailing List.
About a week ago we outlined some options for enhancing OData support for querying derived types.
+About a week ago we outlined some options for enhancing OData support for querying derived types.
From there the discussion moved to the OData Mailing list, where the community gave us very valuable feedback:
$expand will expand related results where possible. So this:
~/People/?$expand=HR.Employee/Manager
-Would include managers for each employee using the standard OData <link><m:Inline> approach, and non employees would have no Manager <link>.
+Would include managers for each employee using the standard OData <link><m:Inline> approach, and non employees would have no Manager <link>.
This query:
@@ -110,7 +110,7 @@You might expect people to have a NULL Manager/Firstname, but there is a real difference between having a NULL property value and having no property!
Today when inserting into a Collection that allows derived types you must specify the type using the entry's category's term.
+Today when inserting into a Collection that allows derived types you must specify the type using the entry's category's term.
However if you post to a type specialized uri like this:
~/People/HR.Employee
The server may be able to infer the exact type being created.
@@ -138,7 +138,7 @@Clearly adding better support for derived types to OData is valuable. And it seems like the proposal is starting to take shape - thanks in large part to your feedback!
What do you think?
-The best place to tell us is on the OData Mailing List.
+The best place to tell us is on the OData Mailing List.
Alex James
Program Manager
Microsoft
To enable modeling these type of situations easier in OData, this document outlines a proposal for the changes required to represent Entries with properties that are unordered homogenous sets of non-null primitive or complex values (aka "Bags").
Proposal:
Metadata
-As you know, OData services may expose a metadata document ($metadata endpoint) which describes the data model exposed by the service. Below is an example of the proposed extension of the metadata document to define Bag properties. In this case, the Customer Entry has a Bag of email addresses and apartment addresses.
+As you know, OData services may expose a metadata document ($metadata endpoint) which describes the data model exposed by the service. Below is an example of the proposed extension of the metadata document to define Bag properties. In this case, the Customer Entry has a Bag of email addresses and apartment addresses.
Uri Construction Rules
The optional, but recommended, URI path construction rules defined by OData will be extended as proposed below to support addressing Bag properties.
@@ -75,7 +75,7 @@Response:
Example 2: Representing Bag properties with Customizable Feed Mapping
-NOTE: When a Bag is represented outside of <atom:content> using Customizable Feed mappings we'll use the Atom collection representation semantics of repeating top level element. We'll do this both for properties mapped to Atom elements and properties mapped to arbitrary elements in a custom namespace. The Bag MAY still be represented in the <atom:content> section.
+NOTE: When a Bag is represented outside of <atom:content> using Customizable Feed mappings we'll use the Atom collection representation semantics of repeating top level element. We'll do this both for properties mapped to Atom elements and properties mapped to arbitrary elements in a custom namespace. The Bag MAY still be represented in the <atom:content> section.
Example 3: Response to a GET request to /Customers(1)/Addresses
@@ -85,7 +85,7 @@Additional Rules
Customizable feed mapping
-The following rules define the customizable feed mappings rules for Bags and are in addition to those already defined for entries here.
+The following rules define the customizable feed mappings rules for Bags and are in addition to those already defined for entries here.
We look forward to hearing what you think of this approach…
-Whatever you think, please tell us all about it on the OData Mailing List.
+Whatever you think, please tell us all about it on the OData Mailing List.
Ahmed Moustafa
The Data Services team has starting thinking about adding Any/All support to Data Services and we noticed a couple of things that I think warrant minor changes to the proposal. So as always I wanted to share and get your thoughts.
The original any/all proposal suggested using a ',' to separate the range variable from the predicate, e.g:
+The original any/all proposal suggested using a ',' to separate the range variable from the predicate, e.g:
~/Movies/?$filter=any(Actors a, a/Name eq 'John Belushi')
I think this has a problem. Usually ',' is used to separate similar things, like the parameters to a function, but in this case it separates a Lambda Parameter from a Predicate. Clearly these things are not the same, moreover using ',' would confuse things in the future if we ever allowed calling custom functions with multiple parameters in the filter.
I think this means we need something more lambda-ish, perhaps something like this:
diff --git a/_posts/2011-02-21-vocabularies.html b/_posts/2011-02-21-vocabularies.html index f9509c4b..fa6b6946 100644 --- a/_posts/2011-02-21-vocabularies.html +++ b/_posts/2011-02-21-vocabularies.html @@ -86,7 +86,7 @@In fact if you execute an OData request that just retrieves an instance of this complex type the response would look like this:
+In fact if you execute an OData request that just retrieves an instance of this complex type the response would look like this:
<Constraint
p1:type="Namespace.Constraint"
xmlns:p1="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"
@@ -95,8 +95,8 @@ OData values:
<ErrorMessage>Please enter a valid EmailAddress</ErrorMessage>
</Constraint>
And this is almost identical to our original annotation, the only differences being around the xml namespaces.
-Which means it is not too much of a stretch to say if your annotation can be modeled as a ComplexType which - of course allow nested complex types properties and multi-value properties too - then the Annotation is simply an OData value.
-This is very nice because it means when we do addressable metadata you can in theory write a query like this to retrieve the annotations for a specific property:
+Which means it is not too much of a stretch to say if your annotation can be modeled as a ComplexType which - of course allow nested complex types properties and multi-value properties too - then the Annotation is simply an OData value.
+This is very nice because it means when we do addressable metadata you can in theory write a query like this to retrieve the annotations for a specific property:
~/$metadata.svc/Properties('Namespace.Type.PropertyName')/Annotations
ISSUE: Actually this introduces a problem, since each annotation instance would have a different 'type' we would need to support either ComplexType inheritance (so we can define the annotation as an EntityType with a Value property of type AnnotationValue, but instances of Annotations would invariably have Values derived from the base AnnotationValue type) or mark Annotation as a OpenType or provide a way to specify a property without specifying the type.
Of course today annotations are allowed that can't be modeled as ComplexTypes, so we would need to be able to distinguish those. Perhaps the easiest way is like this:
diff --git a/_posts/2011-04-13-announcing-datajs-version-0-0-3.html b/_posts/2011-04-13-announcing-datajs-version-0-0-3.html index 75ac6475..787584d7 100644 --- a/_posts/2011-04-13-announcing-datajs-version-0-0-3.html +++ b/_posts/2011-04-13-announcing-datajs-version-0-0-3.html @@ -24,6 +24,6 @@ //display 'data' resultsFor more information checkout the announcement post.
-As always please share your thoughts on the Mailing List.
+As always please share your thoughts on the Mailing List.
-Alex
OData is released under the Microsoft Open Specification promise. This allows anyone to create OData services that implement the specification and to freely interoperate with OData implementations.
-Currently there are several OData service producers and server libraries including .Net Framework, Java, Rails and several client libraries across a range of platforms such as Objective-C, Javascript, PHP, and Java. The fact that an OData service can be consumed by a wide range of applications and libraries makes interoperability a key requirement.
+Currently there are several OData service producers and server libraries including .Net Framework, Java, Rails and several client libraries across a range of platforms such as Objective-C, Javascript, PHP, and Java. The fact that an OData service can be consumed by a wide range of applications and libraries makes interoperability a key requirement.
Today we are announcing the OData Service Validation Tool to address that requirement. The goal with this tool is to enable OData service authors ensure that their service interoperates well with any OData client. Consumers of the OData protocol can also benefit from this tool by testing OData service implementations that they are building an experience for to pinpoint potential issues.
The tool can currently validate the following types of OData endpoints:
The current (alpha) release of this tool runs a small representative set of rules derived from the specification. You can see a current list of rules here.
We are actively working on adding more rules to increase the coverage across the specification so that compliance can be determined with a much more exhaustive set of rules. The goal is to add new rules to the service on a regular cadence.
-Please go ahead and try the tool either with a service of your own or using one of many public OData services.
-Let us know if you have any questions or comments about this service or if there is a feature that you would like to see added. This tool is in the very early stages of development and you can help shape its evolution by providing feedback. Please join the OData mailing list to provide feedback or report issues.
+Please go ahead and try the tool either with a service of your own or using one of many public OData services.
+Let us know if you have any questions or comments about this service or if there is a feature that you would like to see added. This tool is in the very early stages of development and you can help shape its evolution by providing feedback. Please join the OData mailing list to provide feedback or report issues.
diff --git a/_posts/2011-04-13-reference-data-caching-walkthrough.html b/_posts/2011-04-13-reference-data-caching-walkthrough.html index d3cb28cc..86a4ebd3 100644 --- a/_posts/2011-04-13-reference-data-caching-walkthrough.html +++ b/_posts/2011-04-13-reference-data-caching-walkthrough.html @@ -13,5 +13,5 @@ ---Tim Laverty from the DataFX team at Microsoft just posted a walk-through showing how to setup reference data caching using the recently released ' Reference Data Caching CTP' (aka the 'Microsoft WCF Data Services For .NET March 2011 Community Technical Preview with Reference Data Caching Extensions').
-Take a look and as always let the OData community know what you think on the Mailing List.
+Take a look and as always let the OData community know what you think on the Mailing List.
We pointed out when we announced the OData Service Validation Tool at Mix the other week, we are actively working on it and would add more rules to the service on a regular cadence.
+We pointed out when we announced the OData Service Validation Tool at Mix the other week, we are actively working on it and would add more rules to the service on a regular cadence.
We just pushed an update to the service with the following:
Since the release of the tool, the feedback that we received has been great. Thank you all for trying it and providing feedback.
It's also great to hear that there is interest in the source of the tool and potentially being able to contribute new rules. We heard that feedback and are in the process of making the tool open source. We will update you when the process is completed and the source code is available.
-As always, please let us know what you think through the OData mailing list.
+As always, please let us know what you think through the OData mailing list.
This is a strawman proposal. Please challenge it in the OData mailing list.
+This is a strawman proposal. Please challenge it in the OData mailing list.
OData supports geospatial data types as a new set of primitives. They can be used just like any other primitives - passed in URLs as literals, as types and values for properties, projected in $select, and so on. Like other primitives, there is a set of canonical functions that can be used with them.
As always, please give it a try and let us know what you think using the OData Mailing List.
+As always, please give it a try and let us know what you think using the OData Mailing List.
In the meantime, we are also actively working towards open sourcing the tool. We are sorry for the lack of updates on this front but we are committed to making the tool open source and we are waiting for the legal process to be completed. We investigated our options and are currently working with the legal department to create the most appropriate contribution model so that it's also possible for the community to contribute rules.
There is no ETA for the release at the moment but we are in final stages of obtaining legal approvals. We will immediately announce when the source code is available.
-Thank you for your continued feedback and interest. We are all ears on the OData Mailing List. Please let us know if you have any feedback, questions and/or suggestions.
+Thank you for your continued feedback and interest. We are all ears on the OData Mailing List. Please let us know if you have any feedback, questions and/or suggestions.
That said I hope this is enough to whet your appetite.
-Please let me know what you think via the OData.org mailing list.
+Please let me know what you think via the OData.org mailing list.
Cheers
Alex
I’d like to highlight the new crawling feature. Since we launched one of the requests that we heard was to be able to hierarchically validate a service starting from a service document. We had added the capability to do that in the engine in the last release. In this release, we added UI support for the feature.
If you enter enter a URL to a service document and select the crawling checkbox, the validation engine will automatically validate the service doc, the metadata document (if available), the top feed in the service document and the top entry in the feed. In addition to those we also send a bad request to generate an OData error payload and validate that as well.
-As always we’d like to hear your feedback. Please check the new feature out and let us know what you think either on the mailing list or on the discussions page on the Codeplex site.
+As always we’d like to hear your feedback. Please check the new feature out and let us know what you think either on the mailing list or on the discussions page on the Codeplex site.
Turker Keskinpala
Program Manager
diff --git a/_posts/2011-11-08-odata-service-validation-tool-update-19-new-rules.html b/_posts/2011-11-08-odata-service-validation-tool-update-19-new-rules.html index b17f290a..b1d7e15e 100644 --- a/_posts/2011-11-08-odata-service-validation-tool-update-19-new-rules.html +++ b/_posts/2011-11-08-odata-service-validation-tool-update-19-new-rules.html @@ -20,5 +20,5 @@This rule update brings the total number of rules in the validation tool to 97.
OData Service Validation Codeplex project is also updated with all recent changes along with documentation on how to extend the validation service by authoring rules.
-Keep validating and let us know what you think either on the mailing list or on the discussions page on the Codeplex site.
+Keep validating and let us know what you think either on the mailing list or on the discussions page on the Codeplex site.
It took me longer than expected to write again about this, but I have another round of measurements and another proposal that goes with it. Since folks want to close on the next version of OData soon, it would be great to iterate quickly on this one so if we all agree we can include it in this version.
-Back then we started with some discussion about pros/cons of various options and about what to optimize for (see this thread and this post if you want to see some of the original content). I proposed a JSON-encoded-in-JSON approach that had some fans but also some folks were worried that we might be optimizing for the wrong thing. Based on that I started to look at alternate approaches so I could put more options on the table, and I ended up with something that I think has a lot of potential.
+Back then we started with some discussion about pros/cons of various options and about what to optimize for (see this thread and this post if you want to see some of the original content). I proposed a JSON-encoded-in-JSON approach that had some fans but also some folks were worried that we might be optimizing for the wrong thing. Based on that I started to look at alternate approaches so I could put more options on the table, and I ended up with something that I think has a lot of potential.
I showed a somewhat half-baked version of this at //BUILD back in September, you can see it by skipping to 00:41:55 in this video.
This time I started asking “what if we could serve really clean JSON, just the kind of JSON you'd have in a custom service, but still keep all the richness in semantics of OData?” Control information (particularly URLs) adds lots of bloat to existing JSON format payloads. If you remote it, how do things change? Check out the following chart for a typical OData feed:
@@ -139,7 +139,7 @@Note that an interesting side-effect of this approach is that removes any knowledge of the server URL namespace from clients. In the past OData clients had to choose between the higher coupling that came from knowing the URL conventions of the server and losing the query capabilities. Now that patterns are captured in metadata a client that knows about both data and metadata content types can derive all URLs from patterns. This removes the coupling and makes it possible for servers to have their own URL conventions as long as they can be represented with annotations (yes, it means you can have a server that uses “/” instead of “(“ and “)” if you want, for those that were always unhappy with parenthesis :) )
We discussed a JSON format that’s clean and lean and doesn’t need a special coding/decoding step and still preserves a lot of the compactness. We achieve this by moving control information that’s regular enough to metadata in the form of patterns, and by linking data and metadata so clients need no out-of-band knowledge. The approach also allows servers to have different URL conventions without causing OData clients to lose any functionality.
-That do you think? As usual, the OData mailing list is the best place for debate.
+That do you think? As usual, the OData mailing list is the best place for debate.
-pablo
[1] We had long debates with folks here about introducing “application/odata+json”. It seems that this will just cause things to break more for the majority of users, so staying with application/json is probably the right thing. More on this in a future post.
diff --git a/_posts/2012-02-28-odata-service-validation-tool-update-ground-work-for-v3-support.html b/_posts/2012-02-28-odata-service-validation-tool-update-ground-work-for-v3-support.html index f210cbfa..0e649406 100644 --- a/_posts/2012-02-28-odata-service-validation-tool-update-ground-work-for-v3-support.html +++ b/_posts/2012-02-28-odata-service-validation-tool-update-ground-work-for-v3-support.html @@ -24,5 +24,5 @@This update brings the total number of rules in the validation tool to 152. You can see the list of the active rules here and the list of rules that are under development here.
Moreover, with this update the validation tool is positioned to support rules for v3 services for OData V3 payload validation.
-Keep on validating and let us know what you think either on the mailing list or on the discussions page on the Codeplex site.
+Keep on validating and let us know what you think either on the mailing list or on the discussions page on the Codeplex site.
OASIS announced today the Call for Participation for the new OASIS OData Technical Committee tasked with the responsibility of producing the OData Standard.
In addition to the core OData version 3.0 protocol found here, the Technical Committee will be defining some key extensions in the first version of the OASIS Standard:
+In addition to the core OData version 3.0 protocol found here, the Technical Committee will be defining some key extensions in the first version of the OASIS Standard:
OData Extensions for Data Aggregation - Business Intelligence provides the ability to get the right set of aggregated results from large data warehouses. OData Extensions for Analytics enable OData to support Business Intelligence by allowing services to model data analytic "cubes" (dimensions, hierarchies, measures) and consumers to query aggregated data.
OData Extensions for Temporal Data – Temporal databases support querying data as of a particular time or time range. OData Extensions for Temporal data define temporal annotations, functions and semantics for describing and working with temporal data.
Working with XML and JSON Data in OData – Databases often store XML or JSON documents as streams. Extensions for XML and JSON Data define custom functions and annotations to enable those documents to be represented and queried using functions appropriate to each domain (for example, custom XQuery functions for XML).
diff --git a/_posts/2012-06-11-using-schema-org-vocabularies-with-odata.html b/_posts/2012-06-11-using-schema-org-vocabularies-with-odata.html index 1e19cbee..da3ddf80 100644 --- a/_posts/2012-06-11-using-schema-org-vocabularies-with-odata.html +++ b/_posts/2012-06-11-using-schema-org-vocabularies-with-odata.html @@ -17,7 +17,7 @@I am happy to share that, through ongoing discussions with the members of schema.org, we have agreed that defining common OData Vocabulary encodings of the schema.org schemas is a benefit to both technologies. Sharing a common vocabulary even across different encodings like OData, RDFa 1.1, and Microdata, facilitates a common understanding and even possible transformation of data across those encodings. Toward that end we have jointly posted a discussion paper on the Web Schemas wiki on the use of schema.org schemas within OData.
From Dan Brickley's blog post on new developments around schema.org:
"We are also pleased to announce today a discussion paper on the use of OData and Schema.org, posted in the Web Schemas wiki. OData defines a RESTful interface for working with data on the Web. The newest version of OData allows service developers and third parties to annotate data or metadata exposed by an OData Service. Defining common OData Vocabulary encodings of the schema.org schemas facilitates the understanding and even transformation of data across these different encodings."
-Feel free to add comments to Dan's post, or send us feedback on the odata.org mailing list.
+Feel free to add comments to Dan's post, or send us feedback on the odata.org mailing list.
Exciting times for OData!
-Mike
Developing such solutions in a scalable and robust manner through heterogeneous pre-existing networks and systems is a challenge. Companies face distracting, time consuming and misplaced investments when trying to address all these problems at once, often failing to deliver their solution to the market, not because of the technology itself but due to the need of supporting infrastructure.
A common scenario we will be looking into in this article consists in using OData in conjunction with a SQL-based backend, leveraging Odata Spatial Model and SQL Spatial Type.
One of the goals of OData and .Net underlying frameworks is to offer a robust end to end solution to fulfill these issues.
-According to OData, one of the key features of the next global solutions, is common spatial properties which include time and geography. To implement this feature, Odata v3 supports the Spatial Model.
+According to OData, one of the key features of the next global solutions, is common spatial properties which include time and geography. To implement this feature, Odata v3 supports the Spatial Model.
On the backend side, SQL Server provides a Spatial Type, which is well distributed and already widely used.
However, when using Spatial Model, a gap appears in the flow of service as the OData spatial types are not cross compatible with the SQL Spatial library. Any attempt to build a WCF service against Entity with SQL data will fail with gentle kind of “not compatible type” message.
diff --git a/_posts/2013-08-28-odataquerybuilder-a-cross-browser-javascript-library-for-building-odata-queries-3.html b/_posts/2013-08-28-odataquerybuilder-a-cross-browser-javascript-library-for-building-odata-queries-3.html index 7368a0e3..7c5f72b0 100644 --- a/_posts/2013-08-28-odataquerybuilder-a-cross-browser-javascript-library-for-building-odata-queries-3.html +++ b/_posts/2013-08-28-odataquerybuilder-a-cross-browser-javascript-library-for-building-odata-queries-3.html @@ -26,13 +26,13 @@A programmatic client might need all those details of the Atom format in order to interpret it, but I am not a program, I am a human being, and I want readable data! The same thing happens with a naïve question such as “What is this OData endpoint all about?” The OData answer is behind the $metadata URL https://services.odata.org/Northwind/Northwind.svc/$metadata:
[gist id="261b948a9d18562d600e" file="Metadata.xml"]
It might tell you about Customers, Products, Categories, and other related things… if you know how to read it! That exercise is left to the reader.
-Another problem: suppose I want to find the orders, dated earlier than last week and with shipping address containing “12”. Having thoroughly read all the http://odata.org documents (as we all do before even touching the keyboard ;-)), I may be tempted to compose a URL like this:
+Another problem: suppose I want to find the orders, dated earlier than last week and with shipping address containing “12”. Having thoroughly read all the {{site.url}} documents (as we all do before even touching the keyboard ;-)), I may be tempted to compose a URL like this:
That will return an error message because the Edm.DateTime literal is ill-formed; I should have entered OrderDate le datetime'2013-08-07'. However, even with the corrected date format:
The service returns an empty list:
[gist id="261b948a9d18562d600e" file="EmptyList.xml"]
-The list is empty because the order of the parameters for substringof was incorrect (see https://www.odata.org/documentation/odata-v2-documentation/uri-conventions/). The correct URL should in fact be https://services.odata.org/Northwind/Northwind.svc/Orders?$filter=OrderDate le datetime'2013-08-07' and substringof('12', ShipAddress) eq true which yields all the orders (click the URL to see them all).
+The list is empty because the order of the parameters for substringof was incorrect (see {{'/documentation/odata-version-2-0/uri-conventions/' | prepend: site.baseurl | prepend: site.url}}). The correct URL should in fact be https://services.odata.org/Northwind/Northwind.svc/Orders?$filter=OrderDate le datetime'2013-08-07' and substringof('12', ShipAddress) eq true which yields all the orders (click the URL to see them all).
[gist id="261b948a9d18562d600e" file="Results.xml"]
The last example of a difficult query for a naïve user to build is the following: “Who is the employee that placed the order number 10258?” The correct URL would be:
diff --git a/_posts/2014-03-20-status-updates-of-odata-libraries-that-support-odata-version-4-0.html b/_posts/2014-03-20-status-updates-of-odata-libraries-that-support-odata-version-4-0.html index b6803c4d..e89aba5b 100644 --- a/_posts/2014-03-20-status-updates-of-odata-libraries-that-support-odata-version-4-0.html +++ b/_posts/2014-03-20-status-updates-of-odata-libraries-that-support-odata-version-4-0.html @@ -11,7 +11,7 @@ published: true author: Yi Ding --- -OData Version 4.0 has officially been approved as a new OASIS standard recently. Compared to former versions, OData Version 4.0 offers exciting improvements to support OData consumers and producers. In order to help them adopt and benefit from OData Version 4.0, multiple efforts have been taken to build server and client libraries over different platforms.
+OData Version 4.0 has officially been approved as a new OASIS standard recently. Compared to former versions, OData Version 4.0 offers exciting improvements to support OData consumers and producers. In order to help them adopt and benefit from OData Version 4.0, multiple efforts have been taken to build server and client libraries over different platforms.
.NET
For .NET OData client developers, Microsoft has released the first version of the OData Client for .NET on January 27th, which is a .NET OData Client that supports OData Version 4.0 only. Together with the OData Client Code Generator delivered through the Visual Studio Gallery, a client experience of auto-generating codes to reference the target OData service is easy for client app builders to use. The OData core libraries such as the ODataLib, the EdmLib, and the Microsoft.Spatial are all updated to support OData Version 4.0 while the versions for OData V1-3 are still available. The libraries mentioned above will adopt a monthly release model to ensure a quick reaction to customer requirements for new features and bug fixes.
For .NET OData service developers, Microsoft is also working on updating existing solutions to OData Version 4.0 and has released nightly builds of ASP.NET Web API 2.2 for OData v4.0.
diff --git a/_posts/2014-04-22-contribute-to-odata-org-is-available-now.html b/_posts/2014-04-22-contribute-to-odata-org-is-available-now.html index d4046708..731ca680 100644 --- a/_posts/2014-04-22-contribute-to-odata-org-is-available-now.html +++ b/_posts/2014-04-22-contribute-to-odata-org-is-available-now.html @@ -10,10 +10,10 @@ published: true author: Qian Li --- -In order to make OData.org a more collaborative site, we are excited to announce that you can now easily contribute to OData.org at the Contribution page. Currently there are two ways for you to contribute
+In order to make OData.org a more collaborative site, we are excited to announce that you can now easily contribute to OData.org at the Contribution page. Currently there are two ways for you to contribute
Contribute to the OData Ecosystem
-You can publish your OData consumers, OData providers, OData live services, OData libraries and OData vocalbularies by navigating to the Contribution page and filling in the request form. Your request will be reviewed before publish. We will notify you through email in the process.
+You can publish your OData consumers, OData providers, OData live services, OData libraries and OData vocalbularies by navigating to the Contribution page and filling in the request form. Your request will be reviewed before publish. We will notify you through email in the process.
Post Blogs on OData.org
-To post blogs on OData.org, you first need to apply for a contributor account which can write and manage their own posts but cannot publish them. When you finish a blog post, please go to Contribution page to notify us for publishing it. We won’t set hard restrictions on blog posts. As long as the content is about OData and is good for the OData ecosytem, we will be very willing to publish them for you as soon as possible.
+To post blogs on OData.org, you first need to apply for a contributor account which can write and manage their own posts but cannot publish them. When you finish a blog post, please go to Contribution page to notify us for publishing it. We won’t set hard restrictions on blog posts. As long as the content is about OData and is good for the OData ecosytem, we will be very willing to publish them for you as soon as possible.
Call for action
If you have any suggestions or advice, please comment below to let us know. We are looking forward to your contribution to OData.org and thus to the OData ecosystem!
diff --git a/_posts/2014-06-02-odata-icons-guidelines-new-version-available.html b/_posts/2014-06-02-odata-icons-guidelines-new-version-available.html index ebbe6f8e..6da85c37 100644 --- a/_posts/2014-06-02-odata-icons-guidelines-new-version-available.html +++ b/_posts/2014-06-02-odata-icons-guidelines-new-version-available.html @@ -10,9 +10,9 @@ published: true author: Qian Li --- -We are happy to announce that the updated version of OData Icon Usage Guidelines now on OData.org. Users now can have access to standard OData icons and identify conforming implementations of the OData specification in accordance with these guidelines.
+We are happy to announce that the updated version of OData Icon Usage Guidelines now on OData.org. Users now can have access to standard OData icons and identify conforming implementations of the OData specification in accordance with these guidelines.
-Please go directly to OData Icon Usage Guidelines to read the guidelines. If you have problems related to these, please feel free to let us know.
+Please go directly to OData Icon Usage Guidelines to read the guidelines. If you have problems related to these, please feel free to let us know.
diff --git a/_posts/2014-06-30-new-odata-mailing-list.html b/_posts/2014-06-30-new-odata-mailing-list.html index 82d1ded7..95912595 100644 --- a/_posts/2014-06-30-new-odata-mailing-list.html +++ b/_posts/2014-06-30-new-odata-mailing-list.html @@ -15,4 +15,4 @@You can view more detailed instructions of how to join the new mailing list for OData. All kinds of issues and feedbacks for OData are welcomed in this mailing list. If any problems and concerns, please comments below to let us know.
+You can view more detailed instructions of how to join the new mailing list for OData. All kinds of issues and feedbacks for OData are welcomed in this mailing list. If any problems and concerns, please comments below to let us know.
diff --git a/_posts/2014-07-09-trippin-new-odata-v4-sample-service.html b/_posts/2014-07-09-trippin-new-odata-v4-sample-service.html index db70db6d..f700db62 100644 --- a/_posts/2014-07-09-trippin-new-odata-v4-sample-service.html +++ b/_posts/2014-07-09-trippin-new-odata-v4-sample-service.html @@ -18,7 +18,7 @@We are happy to announce that the source code of TripPin implemented using Web API OData is now available at GitHub. Please take a look and provide questions or feedback.
-Please play with this new sample service for OData V4. You can use it either to know more about OData or build an application upon that. If you have any problems, suggestions, bug reports for TripPin, you can join OData Mailing List to discuss about it.
+Please play with this new sample service for OData V4. You can use it either to know more about OData or build an application upon that. If you have any problems, suggestions, bug reports for TripPin, you can join OData Mailing List to discuss about it.
The class diagram below describes the model design for TripPin
diff --git a/_posts/2014-09-03-instant-odata-for-ibm-db2-on-zos-iseries-and-luw.html b/_posts/2014-09-03-instant-odata-for-ibm-db2-on-zos-iseries-and-luw.html index f1731c05..0de5e360 100644 --- a/_posts/2014-09-03-instant-odata-for-ibm-db2-on-zos-iseries-and-luw.html +++ b/_posts/2014-09-03-instant-odata-for-ibm-db2-on-zos-iseries-and-luw.html @@ -13,7 +13,7 @@ ---From my experience working with DB2 shops on .NET application development projects, I have learned that most .NET developers are less familiar with the different flavors of DB2. This is why they choose standards based connectivity from either IBM or Progress DataDirect.
The latest standard is OData, or “ODBC for the web”. DB2 is the core of many on-premise business systems, and this data has tremendous potential in the growing world of web and mobile. Not surprisingly, Progress DataDirect (world’s leading contributor to data API standards) introduced instant and secure OData production from any DB2 system in a self service way for everyone, including those without specific DB2 knowledge.
-A great example of OData’s power with DB2 is Salesforce.com that supports the consumption of OData sources for a new style of data federation using external objects (I will be speaking about this at Dreamforce ’14). For example, OData provides instant access to DB2 for i MRP/ERP systems from the Salesforce CRM customer data in the cloud. Here’s a list of OData consumers.
+A great example of OData’s power with DB2 is Salesforce.com that supports the consumption of OData sources for a new style of data federation using external objects (I will be speaking about this at Dreamforce ’14). For example, OData provides instant access to DB2 for i MRP/ERP systems from the Salesforce CRM customer data in the cloud. Here’s a list of OData consumers.
DataDirect Cloud OData production works with the following DB2 systems:
DB2 for LUW:
DB2 V10.1, V10.5 for Linux, UNIX, Windows
diff --git a/_posts/2014-11-14-salesforce-external-object-integration-using-lightning-connect-with-odata.html b/_posts/2014-11-14-salesforce-external-object-integration-using-lightning-connect-with-odata.html
index ed47a81b..5a654777 100644
--- a/_posts/2014-11-14-salesforce-external-object-integration-using-lightning-connect-with-odata.html
+++ b/_posts/2014-11-14-salesforce-external-object-integration-using-lightning-connect-with-odata.html
@@ -39,7 +39,7 @@
This article describes advanced OData scenario, both for the most recent OData protocol (V4) and earlier versions. The article was inspired by the Advanced OData Tutorial article published at the odata.org. The original article describes the HTTP communication level: it shows how to build URLs, which verbs to use and what response to expect. Most of developers prefer using some kind of library to encapsulate OData HTTP communication, and we are going to study how to solve the advanced OData scenarios using Simple.OData.Client. This library supports all OData protocol versions and can be installed as a NuGet package for either OData V1-3, V4 or as version-agnostic client. All library versions are packaged as Portable Class Library with support for .NET 4.x, Windows Store, Windows Phone 8, Silverlight 5, Xamarin iOS and Xamarin Android platforms.
+This article describes advanced OData scenario, both for the most recent OData protocol (V4) and earlier versions. The article was inspired by the Advanced OData Tutorial article published at the odata.org. The original article describes the HTTP communication level: it shows how to build URLs, which verbs to use and what response to expect. Most of developers prefer using some kind of library to encapsulate OData HTTP communication, and we are going to study how to solve the advanced OData scenarios using Simple.OData.Client. This library supports all OData protocol versions and can be installed as a NuGet package for either OData V1-3, V4 or as version-agnostic client. All library versions are packaged as Portable Class Library with support for .NET 4.x, Windows Store, Windows Phone 8, Silverlight 5, Xamarin iOS and Xamarin Android platforms.
To communicate with OData service we need an instance of ODataClient. It can be created either from its URL string or using ODataClientSettings. Here's the simplest version: {% highlight csharp%} diff --git a/_posts/2014-12-25-restier-a-turn-key-framework-to-build-restful-service.html b/_posts/2014-12-25-restier-a-turn-key-framework-to-build-restful-service.html index 49dad0b6..e25b0cdd 100644 --- a/_posts/2014-12-25-restier-a-turn-key-framework-to-build-restful-service.html +++ b/_posts/2014-12-25-restier-a-turn-key-framework-to-build-restful-service.html @@ -126,5 +126,5 @@
As mentioned above, RESTier is based on Web API OData, for some features not directly supported by RESTier, there are easy ways to fall back to Web API OData by using attribute routing. Please refer to RETier wiki for more detailed examples.
Feedbacks and bug reports. As mentioned previously, currently RESTier is an alpha version, for any feedbacks and bug report, please Open GitHub issues directly or Join OData Mailing List to discusss.
+Feedbacks and bug reports. As mentioned previously, currently RESTier is an alpha version, for any feedbacks and bug report, please Open GitHub issues directly or Join OData Mailing List to discusss.
Contribute to RETier. RESTier is fully open sourced, please refer to How to contribute to RESTier to contribute either code or documentation.
diff --git a/_posts/2015-01-22-ms-open-tech-china-releases-odata-producer-codegen-for-to-tap-the-gold-mine-of-corporate-data.html b/_posts/2015-01-22-ms-open-tech-china-releases-odata-producer-codegen-for-to-tap-the-gold-mine-of-corporate-data.html index ae837494..ec49b226 100644 --- a/_posts/2015-01-22-ms-open-tech-china-releases-odata-producer-codegen-for-to-tap-the-gold-mine-of-corporate-data.html +++ b/_posts/2015-01-22-ms-open-tech-china-releases-odata-producer-codegen-for-to-tap-the-gold-mine-of-corporate-data.html @@ -12,7 +12,7 @@ author: Microsoft Open Technologies (China) --- -According to a 2013 report issued by global consulting firm McKinsey & Company, The flow of “liquid”open data may contribute a total of three to five trillion dollars to the global economy. Committed to promote the free flow of data, Microsoft Open Tech (China) has become an active participant in the effort to build an Open Data Platform within the China market. MS Open Tech (China) not only contributed an OData plug-in to CKAN, the world’s leading open-source data portal platform to accelerate the China government Open Data initiative, but also to showcase the broader achievements of this effort at the Juhe Data Developers Conference, held on Oct 17 in 2014.
+According to a 2013 report issued by global consulting firm McKinsey & Company, The flow of “liquid”open data may contribute a total of three to five trillion dollars to the global economy. Committed to promote the free flow of data, Microsoft Open Tech (China) has become an active participant in the effort to build an Open Data Platform within the China market. MS Open Tech (China) not only contributed an OData plug-in to CKAN, the world’s leading open-source data portal platform to accelerate the China government Open Data initiative, but also to showcase the broader achievements of this effort at the Juhe Data Developers Conference, held on Oct 17 in 2014.
Today, MS Open Tech (China) has released an important update to this tool, formally called the OData Producer Codegen for JDBC plugin. This tool was designed to further enable the free flow and utilization of data between XX. With it, Chinese data service providers using JDBC will now be able to more easily add OData APIs for their own data to support interoperability with the data processing tools, such as Microsoft Office Excel and Power BI, familiar tool sets for data scientists, knowledge workers, researchers, and others.
“Open data standards and interoperability draw lots of attention from both local (Chinese) and global enterprises and government agencies.” said Yun Langsheng, Managing Director of Microsoft Open Technologies (China). “As a strong contributor to global open data standards and interoperability, Microsoft Open Tech has delivered a lot of support and made great contribution to OData and open source projects to help data providers, users and developers leverage various data sources more easily. OData Producer Codegen for JDBC aims help intellectual professionals leverage familiar tools such as Office and Power BI to more easily mine the data ‘buried’ behind JDBC. Eventually, we hope to see data flow more freely, both in China and around the world.”
“Microsoft OData protocol has infused new blood to Juhe Data,” said Zuo Lei, Juhe Data CEO. “Its JDBC interface function works especially well, which has helped greatly improve our development efficiency and save the time required. We plan to base more of our interface development work on OData in the future.”
diff --git a/_posts/2015-01-26-odata-org-weekly-news-letter-4th-week-2015.html b/_posts/2015-01-26-odata-org-weekly-news-letter-4th-week-2015.html index a7035481..49c90570 100644 --- a/_posts/2015-01-26-odata-org-weekly-news-letter-4th-week-2015.html +++ b/_posts/2015-01-26-odata-org-weekly-news-letter-4th-week-2015.html @@ -13,10 +13,10 @@-OData Producer Codegen for JDBC is designed in response to the requirements of data providers, to avail batches of data to users from JDBC enabled data service providers. The tool, upon one-key click after simple configuration, can largely reduce the workload of data service providers by adding data stored on the JDBC data sources to OData Restful APIs automatically. As a result, large amount of data becomes accessible immediately.
Read more at this blog post
+Read more at this blog post
-Ogee provides Eclipse based open source developer tools for the provisioning and consumption of OData services regardless of the service provisioning platform and service consuming technology. It comprises a graphical OData Model Editor for the creation of OData models that define the data structure required. The models can then be exported as service metadata document.
Read more at this blog post
+Read more at this blog post
Implementation of a module that provides OData protocol and then enables third parties to query (custom) creatable content types embedded in an Orchard CMS Site
Try this at Orchard Gallery
diff --git a/_posts/2015-03-04-odata-org-weekly-news-letter-2015-3-4.html b/_posts/2015-03-04-odata-org-weekly-news-letter-2015-3-4.html index 8faa966a..118a5520 100644 --- a/_posts/2015-03-04-odata-org-weekly-news-letter-2015-3-4.html +++ b/_posts/2015-03-04-odata-org-weekly-news-letter-2015-3-4.html @@ -19,6 +19,6 @@Read more at this blog post about how to visualize data in Power BI with Scorata OData.
Check the data feed here which is implemented using the turn-key OData server side library RESTier
+Check the data feed here which is implemented using the turn-key OData server side library RESTier
Read more at the blog.
diff --git a/_posts/2015-05-25-new-odata-org.md b/_posts/2015-05-25-new-odata-org.md index e929082d..3af2d505 100644 --- a/_posts/2015-05-25-new-odata-org.md +++ b/_posts/2015-05-25-new-odata-org.md @@ -22,7 +22,7 @@ The website is built with the following target audiences in mind: OData.org is very important for OData community. We have been working hard on improving both the contents and performance of the site and we will continually improving it according to your feedback. Below are current content structure of OData.org, and for future plans, please check [issues on GitHub](https://github.com/odataorg/odataorg.github.io/issues) -#### [Blog](https://www.odata.org/blog) +#### [Blog](/blog) Posts including subjects (but not limited) below, and except for site announcements, most posts are written by contributors. - Site announcement @@ -34,25 +34,25 @@ Posts including subjects (but not limited) below, and except for site announceme - Tools of OData - ... -#### [Getting Started (for developers)](https://www.odata.org/getting-started) +#### [Getting Started (for developers)](/getting-started) OData has specifications that cover almost every aspect of a RESTful API. But for starters, you don't need to go through all the details of OData specifications. In this part, we provide various tutorials for developers of OData. -#### [Documentation](https://www.odata.org/documentation) +#### [Documentation](/documentation) OData protocol specification. Including the latest OASIS standardized OData Version 4.0 as well as OData Version 3.0 and OData Version 2.0. -#### [Libraries](https://www.odata.org/libraries) +#### [Libraries](/libraries) Matrix of OData libraries of different platforms (.Net, JAVA, JavaScript, C++, Python, Ruby and etc.) for server and client. You are warmly welcomed to add your OData libraries here. -#### [Reference Services](https://www.odata.org/odata-services) +#### [Reference Services](/odata-services) Services built to demonstrate the features of OData. #### Tools Tools that can help you better understand OData services -#### [Ecosystem](https://www.odata.org/ecosystem) +#### [Ecosystem](/ecosystem) Consumers, providers and use cases of OData in the industry. We will improve the page with better UI experience and more up-to-date contents. -#### [Getting Involved](https://www.odata.org/contribution) +#### [Getting Involved](/contribution) Guidelines of how to getting involved in the OData community. #### Search @@ -60,7 +60,7 @@ Improved the search functionality in the navigation menu with full-text search. **Besides above, we are actively working on producing more contents for business decision makers and RESTfu API advocators and better organize contents for developers. Please let us know if you have any ideas.** -# [Call to action](https://www.odata.org/contribution) +# [Call to action](/contribution) ### Provide feedback As always, your feedback to OData.org is warmly welcomed. Please let us know your feedback either email to our mailing list or [create issues](https://github.com/odataorg/odataorg.github.io/issues) directly. diff --git a/_posts/2015-09-12-Lightning-Connect-New-in-OData-DF15.md b/_posts/2015-09-12-Lightning-Connect-New-in-OData-DF15.md index faf2fddc..6b083e63 100644 --- a/_posts/2015-09-12-Lightning-Connect-New-in-OData-DF15.md +++ b/_posts/2015-09-12-Lightning-Connect-New-in-OData-DF15.md @@ -5,7 +5,7 @@ date: 2015-09-23 17:59:43.000000000 +08:00 author: Sumit Sarkar --- -Salesforce introduced support for [Lightning Connect External Objects at Dreamforce '14](https://www.odata.org/blog/salesforce-external-object-integration-using-lightning-connect-with-odata/) powered by OData. Salesforce's Lightning Connect was initially released as an OData 2.0 read-only consumer. And new OData functionality is being added in each release based on demand from data hungry Salesforce applications. At Dreamforce '15, I learned about several large organizations running Lightning Connect in production including [Intuit](https://diginomica.com/2015/07/09/how-intuit-integrated-their-user-experience-with-progress/), [Warranty Group](https://success.salesforce.com/ev_sessions#/session/a2q30000001B6ilAAC), [Farmers Insurance](https://success.salesforce.com/ev_sessions#/session/a2q30000001B6ilAAC), to name a few. +Salesforce introduced support for [Lightning Connect External Objects at Dreamforce '14](/blog/salesforce-external-object-integration-using-lightning-connect-with-odata/) powered by OData. Salesforce's Lightning Connect was initially released as an OData 2.0 read-only consumer. And new OData functionality is being added in each release based on demand from data hungry Salesforce applications. At Dreamforce '15, I learned about several large organizations running Lightning Connect in production including [Intuit](https://diginomica.com/2015/07/09/how-intuit-integrated-their-user-experience-with-progress/), [Warranty Group](https://success.salesforce.com/ev_sessions#/session/a2q30000001B6ilAAC), [Farmers Insurance](https://success.salesforce.com/ev_sessions#/session/a2q30000001B6ilAAC), to name a few. For my friends in the OData tribe, this is the most interesting OData consumer among SaaS applications and it's very exciting to track the evolution of its OData support. @@ -40,7 +40,7 @@ My devzone session was on [Lightning Connect: Lessons Learned](https://success.s * Can you write back to external objects? This feature is currently in beta, and expected to be released in Winter '16. * Are there free options to produce OData? -The best place to learn more about the OData ecosystem is to visit [www.odata.org/ecosystem/](https://www.odata.org/ecosystem/) +The best place to learn more about the OData ecosystem is to visit [/ecosystem/](/ecosystem/) * How does the feature work with very large resources? When running common use cases for Lightning Connect through [DataDirect Cloud](https://www.progress.com/cloud-data-integration) OData endpoints, we see operators such as filters being efficiently implemented against the backend data source API resulting in fast and scalable performance. Performance benchmarks are being developed by DataDirect R&D for those interested in specific numbers. diff --git a/_posts/2015-09-29-olingo-releases-odata-V4-support-for-java.md b/_posts/2015-09-29-olingo-releases-odata-V4-support-for-java.md index 8d9f790c..83eb1d0f 100644 --- a/_posts/2015-09-29-olingo-releases-odata-V4-support-for-java.md +++ b/_posts/2015-09-29-olingo-releases-odata-V4-support-for-java.md @@ -7,8 +7,8 @@ author: Mike Pizzo The [Olingo](https://olingo.apache.org/) team [announced](https://twitter.com/ApacheOlingo?ref_src=twsrc%5Etfw) last week that they have released Apache Olingo 4.0 with support for building OData V4-compliant RESTful services and clients. -With support for OData V4's JSON format, Olingo makes building a modern RESTful service in Java easier than ever. Whether you are sharing data with [Salesforce Lightning Connect](https://developer.salesforce.com/blogs/developer-relations/2015/02/access-salesforce-data-external-sources-lightning-connect.html), building an on-line report using [combit Report Server 2.0](https://www.odata.org/blog/combit-report-server-odata4), using [PowerQuery](https://www.odata.org/blog/microsoft-power-query-for-excel-releases-support-for-odata-v4) to import data into Microsoft Excel, or just building a simple REST service that follows best patterns and practices, Olingo's OData Service for Java is for you! +With support for OData V4's JSON format, Olingo makes building a modern RESTful service in Java easier than ever. Whether you are sharing data with [Salesforce Lightning Connect](https://developer.salesforce.com/blogs/developer-relations/2015/02/access-salesforce-data-external-sources-lightning-connect.html), building an on-line report using [combit Report Server 2.0](/blog/combit-report-server-odata4), using [PowerQuery](/blog/microsoft-power-query-for-excel-releases-support-for-odata-v4) to import data into Microsoft Excel, or just building a simple REST service that follows best patterns and practices, Olingo's OData Service for Java is for you! -And for client application developers, Olingo's OData Client makes it easy to code against any OData-compliant service. Using the Olingo OData Client for Java gives you strongly typed access to over 7 million species sightings in NSW's new [Biodiversity Service](https://www.environment.nsw.gov.au/resources/MinMedia/MinMedia15083101.pdf), access to your mail, contacts and calendar information through the [Office 365 API](https://msdn.microsoft.com/en-us/office/office365/api/api-catalog), ERP data through [Acumatica](http://adn.acumatica.com/acumatica-liberates-erp-with-odata/), perform system management through [Redfish](https://www.dmtf.org/standards/redfish), or work with any other service written to follow [OData](https://www.odata.org) conventions. +And for client application developers, Olingo's OData Client makes it easy to code against any OData-compliant service. Using the Olingo OData Client for Java gives you strongly typed access to over 7 million species sightings in NSW's new [Biodiversity Service](https://www.environment.nsw.gov.au/resources/MinMedia/MinMedia15083101.pdf), access to your mail, contacts and calendar information through the [Office 365 API](https://msdn.microsoft.com/en-us/office/office365/api/api-catalog), ERP data through [Acumatica](http://adn.acumatica.com/acumatica-liberates-erp-with-odata/), perform system management through [Redfish](https://www.dmtf.org/standards/redfish), or work with any other service written to follow [OData](/) conventions. Olingo's newly released OData V4 Client and Server libraries join the [Olingo OData Client for Javascript](https://olingo.apache.org/doc/javascript/index.html), making it easy to consume all the same sources from your favorite browser-based applications and devices. diff --git a/_posts/2015-10-15-Next-major-SaaS-application-demonstrating-OData-support-OOW15.md b/_posts/2015-10-15-Next-major-SaaS-application-demonstrating-OData-support-OOW15.md index 7ede42bb..76f258eb 100644 --- a/_posts/2015-10-15-Next-major-SaaS-application-demonstrating-OData-support-OOW15.md +++ b/_posts/2015-10-15-Next-major-SaaS-application-demonstrating-OData-support-OOW15.md @@ -4,11 +4,11 @@ title: Next major SaaS application will be demonstrating OData support at OOW15 date: 2015-10-15 17:59:43.000000000 +08:00 author: Sumit Sarkar --- -I am very excited about co-presenting an “ecosystem-changing” session around OData at Oracle OpenWorld 2015 this year. This development represents the next major SaaS vendor to support accessing external data as an OData consumer. One of the early OData consumers in the SaaS space was Salesforce with the [introduction of Lightning Connect](https://www.odata.org/blog/salesforce-external-object-integration-using-lightning-connect-with-odata/), and I had the privilege of presenting a session at Dreamforce on, “Lightning Connect: Lessons Learned”. +I am very excited about co-presenting an “ecosystem-changing” session around OData at Oracle OpenWorld 2015 this year. This development represents the next major SaaS vendor to support accessing external data as an OData consumer. One of the early OData consumers in the SaaS space was Salesforce with the [introduction of Lightning Connect](/blog/salesforce-external-object-integration-using-lightning-connect-with-odata/), and I had the privilege of presenting a session at Dreamforce on, “Lightning Connect: Lessons Learned”.  -Lightning Connect is the new external data strategy for the Salesforce platform powered by OData and you can find the [latest news here](https://www.odata.org/blog/Lightning-Connect-New-in-OData-DF15/). +Lightning Connect is the new external data strategy for the Salesforce platform powered by OData and you can find the [latest news here](/blog/Lightning-Connect-New-in-OData-DF15/). One month later on a different stage at Moscone Center, I get to co-present with Roderick Peace in a session titled, “Get Ahead: Oracle Service Cloud Integration Strategy—Spectrum of Integrations”. Learn more about the spectrum of integration strategies to external data from Oracle Service Cloud, including OData read/w rite support. diff --git a/index.html b/index.html index 8098ae30..e34c32e2 100644 --- a/index.html +++ b/index.html @@ -92,7 +92,7 @@The Open Data Protocol (OData) is a data access protocol built on core protocols like HTTP and commonly accepted methodologies like REST for the web. There are various kinds of libraries and tools can be used to consume OData services. But for beginners and those who want to write their own libraries, the pure HTTP requests and responses are also very important. This documentation will not cover every feature details for OData V4 services but will try to cover various typical scenarios. If you want to have a more detailed understanding, please refer to OData Documentation.
+The Open Data Protocol (OData) is a data access protocol built on core protocols like HTTP and commonly accepted methodologies like REST for the web. There are various kinds of libraries and tools can be used to consume OData services. But for beginners and those who want to write their own libraries, the pure HTTP requests and responses are also very important. This documentation will not cover every feature details for OData V4 services but will try to cover various typical scenarios. If you want to have a more detailed understanding, please refer to OData Documentation.
You can now use the Postman collections to learn OData in an interactive way.
serviceRoot
below with the URL https://services.odata.org/V4/TripPinServiceRW
. TripPin now supports ETag, so for data modification topics, you should first using GET on TripPin (eg. GET serviceRoot/People) to get the section information in the payload then use the URL with section for data modification examples. (something looks like https://services.odata.org/V4/(S(flat4rgegiueineatspfdku1))/TripPinServiceRW)