1. RETS Working Group August 5, 2004Slide 1 RETS 2.0 – Bridging the Gap Sergio Del Rio Templates 4 Business Inc.

2. RETS Working Group August 5, 2004Slide 2 RETS 2.0 – Migration From 1.X RETS 2.0 Needs to Define a Migration Path from 1.X Justification Additional Benefits Proposed Solution Assumptions

3. RETS Working Group August 5, 2004Slide 3 Migration Path - Assumptions Web Services The current consensus is that RETS 2.0 will be based on Web Services Web Services is desirable to simplify the expansion of RETS into the Transaction Space

4. RETS Working Group August 5, 2004Slide 4 Migration Path - Justification Common to Both Server and Client Vendors Existing Investment in RETS 1.X Time Consuming to Rewrite to RETS 2.0 Costly to Rewrite to RETS 2.0 New Vendors – Don’t Want to Learn RETS 1.X Staff Re-Training Requirements

5. RETS Working Group August 5, 2004Slide 5 Migration Path - Justification Server Vendors Potential New Infrastructure Requirements Need to Support Two Separate Systems May Not Want to Deploy Web Services to All Customers  May Leave some systems at RETS 1.X for a very long time…

6. RETS Working Group August 5, 2004Slide 6 Migration Path - Justification Client Vendors Single Client – Connects to Multiple Server Vendors Existing Applications Are Working New Applications May Require Web Services

7. RETS Working Group August 5, 2004Slide 7 Migration Path – Proposed Solution Define RETS 1.X to 2.0 Translation Service Receives RETS 2.0 Web Services Calls Interfaces with any RETS 1.X Servers to get Answer Returns Answer in RETS 2.0 Format Provide Solution to Server Vendors  As Web Service  As Working Implementation (Source Code)

8. RETS Working Group August 5, 2004Slide 8 RETS 2.0 Translation Service Today’s Environment

9. RETS Working Group August 5, 2004Slide 9 RETS 2.0 Translation Service Introduce New Service

10. RETS Working Group August 5, 2004Slide 10 Proposed Solution - Overview Interface – Closely Matches Existing Transactions Implementation – Database Like (JDBC) retsOffices = retsConnection.logIn(“cornerstone.mris.com:6103/platinum”, “Application/1.0", “UserName", “Password"); retsConnection.setOffice(retsOffices[0]);

11. RETS Working Group August 5, 2004Slide 11 Proposed Solution – Details Now Execute a count and/or Search dmqlString = "(County=|MONTGOMERY-MD),(ListingStatus=|ACTIVE)"; numRecs = retsConnection.executeCount("Property", "RES“, 25, dmqlString); numRecs = retsConnection.executeSearch("Property", "RES“, 25, dmqlString);

12. RETS Working Group August 5, 2004Slide 12 Proposed Solution - Details Now Get the Results while (retsConnection.hasMoreSets()) { retsResultSet = retsConnection.getNextSet(); while (retsResultSet.hasMore()) { retsResultRow = retsResultSet.next(); // Process Row… }

13. RETS Working Group August 5, 2004Slide 13 Proposed Solution – Summary Build Web Service Based on RETS 1.X API Ease the Transition to RETS 2.0 Connects to any Existing RETS 1.X Server

14. RETS Working Group August 5, 2004Slide 14 Additional Benefits Working Implementation of RETS 2.0 Allows Server & Client Vendors to Immediately use Web Services Easily Move to the Real Estate Transaction Space by Adding Complementary Web Services Uses Web Services Security Model MISMO – Already Working on Web Services

15. RETS Working Group August 5, 2004Slide 15 Question For Working Group Do we include something like this in the RETS 2.0 specification?