Export to

• Google Calendar
• iCalendar file
• hCalendar markup
  <div class="vevent h-event"> <h1 class="summary p-name">PLUG: OData Open Data and Interoperability</h1> <div class='date'><time class="dtstart dt-start" title="2012-03-01T19:00:00" datetime="2012-03-01T19:00:00">Thursday, March 1, 2012 from 7</time>–<time class="dtend dt-end" title="2012-03-01T21:00:00" datetime="2012-03-01T21:00:00">9pm</time></div> <div class="location vcard p-location h-card"> <a class="url" href='http://calagator.org/venues/202391953'><span class='fn org p-name'>Portland State University FAB, Room 86-09</span></a> <div class="adr p-adr h-adr"> <div class="street-address p-street-address">1900 SW Fourth Avenue</div> <span class="locality p-locality">Portland</span> , <span class="region p-region">Oregon</span> <span class="postal-code p-postal-code">97201</span> <div class="country-name p-country-name">US</div> (<a href='https://maps.google.com/maps?q=1900%20SW%20Fourth%20Avenue,%20Portland%20Oregon%2097201%20US'>map</a>) </div> </div> <div class="description p-description"> <p>Open Data and Interoperability by Arlo Belshee</p> <p>Lots of us want to expose our data via RESTful web APIs. We also want to consume data exposed via such APIs. REST + Json works well for this. However, we'd also like to mash up multiple data sources and build higher level tools. For example, it would be nice to create Business Intelligence (BI) tools that can point to any API and start charting the data, or create JavaScript control libraries that can be bound directly to data sources.</p> <p>Unfortunately, that isn't possible with just REST + Json.</p> <p>The problem is that each service is custom. No two services follow exactly the same rules. Sure, everything exposes sets of resources. But how do you get from a resource to its related resources? How do you ask the server to tell you about related resources? What, exactly should the server do when it gets a PATCH verb? Each server interprets these differently, which prevents making general tools.</p> <p>I'm going to talk about the OData protocol. This is an open standard that defines uniform semantics and modeling for RESTful web services. I'll show how this allows general tools to be built, and data from multiple sources to be combined together in interesting ways - without requiring custom code for each server. I'll also show how this enables people working in different languages. A single library can be written for each language which can then support all OData-compliant RESTful web services.</p> <p>Most of the examples will be with open source frameworks and tools, but I'll also show ways that you can use OData to break out data that is trapped in closed-source systems and expose it to the open source ecosystem.</p> <p>Agenda:</p> <p>7:00 - 7:30 Business We will discuss the status of our ongoing projects including PLUG's monthly Advanced Topics meetings, PLUG's monthly hands on clinics etc.</p> <p>7:30 - 8:30 Presentation and Questions</p> <p>See above</p> <p>9:00 - ... Beer The Lucky Lab Northwest Beer Hall 1945 NW Quimby Portland, Oregon</p> </div> <h3>Links</h3> <ul> <li><a class="url u-url" href="http://pdxlinux.org/">Website</a></li> </ul> </div>