What’s it going to take to get real estate technology vendors to transition away from RETS to the Web API? Much like luring a donkey with the promise of a juicy carrot, the Real Estate Standards Organization (RESO) is hoping that both a carrot (providing easy-to-use replication tools) and a stick (large MLSs putting a “death date” on RETS feeds) will facilitate the move.
Art Carter is the chair of the 2019 RESO board of directors and CEO of California Regional MLS. Josh Darnell is the chief architect at RESO and founder and CEO of kurotek, a real estate tech consultancy.
Both Carter and Darnell are committed to RESO’s mission around creating and promoting the adoption of data standards to drive efficiency in the real estate industry.
Today, Carter and Darnell discuss the transition from RETS to the Web API and discuss what RESO is doing to rectify the replication issue. Carter gives us an update on the progress of RESO’s search for a new CEO, describing the combination of technical skill and evangelism the organization is looking for in a leader.
Darnell shares his take on independent systems like Trestle and the Spark API and walks us through the RESO initiatives that address the separation of listing input.
Listen in for insight into the ongoing evolution of real estate standards and learn how you can support RESO’s work to give agents access to the data they need.
- The progress of RESO’s search for a new CEO
- What RESO is looking for in a leader for the organization
- What the RESO board is doing to rectify the replication issue
- RESO’s understanding that standards will continue to evolve
- RESO’s focus on giving agents access to the data they need
- Darnell’s take on independent systems like Trestle, Spark API
- The intent behind RESO’s RCP010 and RCP019 initiatives
- Why we will eventually rely on MLSs to handle compliance
- The value of working together in an open-source model
- Carter’s insight on how proprietary systems impact innovation
- Why vendors need to accept that RETS is going away
- Who Darnell would like to see at RESO’s workgroup meetings
- What it will take to get vendors to transition to the Web API