OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [odata] Basic OData question



Got it! Thanks so much.

I had a crack at promoting it to a broader audience, and to also identify where it may fit into another OASIS group I'm helping start: 'PACR' - For Government Cloud Computing.

As you know Open Data is a huge topic for the public sector, and my goal is to identify the overlap between Cloud and Open Data.

E.g. "OData Cloud Security" - For using it for enabling citizen access to government archives:

http://cloudbestpractices.net/2012/10/08/odata-cloud-security/

Neil.


On Mon, Oct 8, 2012 at 12:18 AM, Michael Pizzo <mikep@microsoft.com> wrote:

Correct; OData is a RESTful API, not just publishing files, and enables (but does not mandate) writability against services that choose to support writing data. It may also be useful to authorize users in the case of read-only access, for example, to customize data views based on user.

 

OData does not define a separate auth mechanism, but leverages existing authorization/authentication mechanisms. It is in the charter of the OData TC to give guidance as far as authorization/authentication for OData services.

 

You can read more about OData and current Authentication practices here: http://blogs.msdn.com/b/astoriateam/archive/tags/authentication/.

 

Thanks,

 

-Mike


From: Neil McEvoy [neil.mcevoy@ifossfoundation.org]
Sent: Sunday, October 07, 2012 2:21 AM
To: Michael Pizzo
Cc: odata@lists.oasis-open.org
Subject: Re: [odata] Basic OData question

Thanks Michael.

Yes I do have one main question. As I understand it, to date Open Data has been a process where the owners of the data extract and publish it from a legacy system, to some kind of file. Along with the open licence the developer can then take that data file and use it with a new app.

In contrast it seems that OData is more about an API to live data, still in its original source, achieved via RESTful methods? This would have obvious improved benefits, not least the ability to Write as well as Read?

If this is the case would it also embed the ability to handle authorization? I.e. if external parties are given the ability to update live data this would present security and access control requirements?

Kind regards, Neil.


On Sun, Oct 7, 2012 at 12:08 AM, Michael Pizzo <mikep@microsoft.com> wrote:

Yes, OData is short for "Open Data Protocol". It is "Open" because it was designed through an open process and open license, but also because it opens silos of data to the web. And it is a protocol; based on REST principles, it defines conventions, rules, and formats for exchanging data on the web.

 

More information on odata can be found at http://www.odata.org. There is also a nice write-up recently here: http://www.nuams.com/odata-communications-protocol-sharing-open-data.

 

Let me know if you need any more information.


Thanks,

 

-Mike

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Neil McEvoy
Sent: Saturday, October 6, 2012 9:09 AM
To: odata@lists.oasis-open.org
Subject: [odata] Basic OData question

 

Hi folks

 

New to the group so please excuse the newbie question.

 

Basically my question is that I previous thought of Open Data as being about the licence - It's made open by the appropriate licence to use it.

 

However OData seems to be more of a programmatic design of data access? 

 

--
Neil McEvoy
VP Business Development
iFOSSF.org




--
Neil McEvoy
VP Business Development
iFOSSF.org
Skype:neil.mcevoy1



--
Neil McEvoy
VP Business Development
iFOSSF.org
Skype:neil.mcevoy1


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]