1. OData Futures: creating the web of data
2/28/ :05 AM
SAC-824T
OData Futures: creating the web of data
Pablo Castro
Software Architect
Microsoft Corporation
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Agenda OData enhancements in upcoming version
Using OData from Windows 8
Roadmap

3. Functionality. Efficiency. Versatility.

4. Functionality. Efficiency. Versatility.

5. Modeling and Querying: Location
First-class types in the model
Point, lines, line strings, polygon types
General geography and geometric types
“Distance” queries support
Extensible query capabilities
Represented using standard formats
GeoJSON, GML

6. Modeling and Querying: Collections
Before collections were top-level or associations only
Properties can now be collections
Primitives or complex types
New “any” and “all” operators
Predicates that work on collections
Through properties or associations

7. Modeling and Querying: Inheritance
Full inheritance support
No more obscure fine-print
Enables associations in subtypes
Use types in segments to refer to members of subtypes
Applies in path and all query operators

8. Functionality. Efficiency. Versatility.

9. Efficiency: Deltas Incrementally refresh cached data
Adds “delta” link to responses
Server encodes what it needs there
Responses include new, updated and deleted entities
Backwards compatible

10. Efficiency: Wire Format

11. Efficiency: Cleaner and Leaner JSON
Optimize for network I/O
Payload size matters above all
Parsing time typically not a problem
Don’t get too weird
Plain JSON
Strategy
Templates for redundant information
Streamline compression in HTTP

12. Functionality. Efficiency. Versatility.

13. Modeling Behavior “HATEOAS” “Actions” have a name and a link
Server encodes what it needs in URLs
Availability depends on state
Server drives

14. Annotations and Semantics
Annotate any model construct
Annotations
Target
Term
Value
Terms can use global names
Shared vocabularies

15. Roadmap

16. Roadmap OData protocol WCF Data Services
New version draft by end of 2011
WCF Data Services
New release in Q1 2012, covering most of next OData draft
Refresh with next version of Visual Studio

17. For more information RELATED SESSIONS DOCUMENTATION & ARTICLES CONTACT
Building data-driven HTML5 Applications with WCF RIA Services
Your Devices + OData + Azure == Happiness
F# 3.0: data, services, Web, cloud, at your fingertips
CONTACT

18. thank you Feedback and questions http://forums.dev.windows.com
Session feedback

19. 2/28/ :05 AM
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.