<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Why OData? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-odata/m-p/12259774#M1986966</link>
    <description>&lt;P&gt;Hi community,&lt;/P&gt;
  &lt;P&gt;this may sound like a very dumb question, and I am sorry for that, but I have failed to find a satisfying answer to why is SAP so adamant on using OData? &lt;/P&gt;
  &lt;P&gt;I understand what OData is and what features are defined with it.&lt;/P&gt;
  &lt;P&gt;What I do not understand is why it's adoption is basically limited to SAP and they seem to keep sticking to it no matter how API implementations of other IT companies look like ( I am not talking about providing it as an optional rendering, like Sharepoint, but OData being the only available choice )&lt;/P&gt;</description>
    <pubDate>Wed, 26 Aug 2020 06:56:03 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2020-08-26T06:56:03Z</dc:date>
    <item>
      <title>Why OData?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-odata/m-p/12259774#M1986966</link>
      <description>&lt;P&gt;Hi community,&lt;/P&gt;
  &lt;P&gt;this may sound like a very dumb question, and I am sorry for that, but I have failed to find a satisfying answer to why is SAP so adamant on using OData? &lt;/P&gt;
  &lt;P&gt;I understand what OData is and what features are defined with it.&lt;/P&gt;
  &lt;P&gt;What I do not understand is why it's adoption is basically limited to SAP and they seem to keep sticking to it no matter how API implementations of other IT companies look like ( I am not talking about providing it as an optional rendering, like Sharepoint, but OData being the only available choice )&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 06:56:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-odata/m-p/12259774#M1986966</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2020-08-26T06:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: Why OData?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-odata/m-p/12259775#M1986967</link>
      <description>&lt;P&gt;Hi Sebastian&lt;/P&gt;&lt;P&gt;That's not a dumb question at all - far from it.&lt;/P&gt;&lt;P&gt;First off, I think some of it has to do with OData being very query-centric and the database being at the heart of the on-premise SAP system. Accessing the database is also at the core of the ABAP language, contrary to many other languages out there.&lt;/P&gt;&lt;P&gt;Second, OData has been in use at SAP for a &lt;EM&gt;long&lt;/EM&gt; time. Alternatives like GraphQL and OpenAPI just weren't around at the time. And there is already one legacy web service technology still in use in the SAP world (SOAP), so I can understand any reluctance to introducing a new technology.&lt;/P&gt;&lt;P&gt;Third, using a protocol/language with programmatically accessible metadata is essential for e.g. tool support.&lt;/P&gt;&lt;P&gt;Just my two euro cents &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Morten&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 10:50:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-odata/m-p/12259775#M1986967</guid>
      <dc:creator>MortenWittrock</dc:creator>
      <dc:date>2020-08-26T10:50:36Z</dc:date>
    </item>
  </channel>
</rss>

