From the Desk of the CTO: 10 Tech Topics to Engage in at the RESO Fall Conference

The pace of work in RESO’s workgroups and in its internal technology development continues to accelerate. Here’s what the crowd in Colorado Springs will be buzzing about:

1. Machine-Readable Usage Rights. A framework for hierarchical AI governance and machine-readable usage rights was approved in a Data Governance Subgroup launched by the Research & Development Workgroup in August. A Data Rights Register is collecting the licensing rules that data carries today.

2. Organization and System Identifiers. Alongside the Universal Parcel Identifier (UPI) and Unique Licensee Identifier (ULI), RESO is adding unique organization and system identifiers to standardize what differs between providers today. This will be optional in Data Dictionary (DD) 2.3 and enforced in DD 3.0.

3. Schools and Geographies. A new schools collection allows more than one school of each type on a listing, with district information, catchment, and state and NCES identifiers as the basis. Country and StateOrProvince were standardized on ISO in DD 2.0, and DD 2.3 adds CityGeoid and CountyOrParishGeoid to supplement City and CountyOrParish. This will be optional in DD 2.x and mandatory in DD 3.0 as linking identifiers, so a provider publishing City will need the matching CityGeoid.

4. Rebuilt Certification Suite. New testing for DD 2.1 and Web API Core 2.0.0 and 2.1.0 is in final testing with MLS providers, alongside a desktop and web client, a reference server with sample data, and SDKs. Testing moves onto your own machine, and searching your feed no longer requires a command line. If your organization is still working on DD 2.0, you’ll simply be moved up to testing on DD 2.1.

5. DD 3.0. Major changes are being settled for the Fall 2027 arrival of DD 3.0. Naming and casing conventions will be applied consistently, mapping suggestions from the Universal Mapping Initiative will be implemented, and duplication will be reduced. Where there are many ways to express enumerations at the transport level today, DD 3.0 standardizes on human-friendly enumerations only, so end users stop doing that translation.

6. Data Dictionary Minor Versions. Minor versions now ship quarterly, so the standard can keep pace with the industry. DD 2.1 added a Building Resource with 262 fields, 90 new fields on Property and 446 new lookup values. Nothing was removed. DD 2.2 brings new shapes and a standard metadata format that can advertise capabilities such as searchability. Nonbreaking means additions and soft deprecations, so you adopt on your own schedule.

7. RESO Tools Now Written by RESO’s Coding Assistant. The coding assistant has been trained to write specifications and generate clients, servers, testing tools and guides from end to end. That is why the entire toolset was rebuilt this year rather than over several years.

8. New Member Assistant Trained on RESO Material. The new assistant can do Data Dictionary research, draft proposals and answer questions about standards, policies, procedures, certification and how your data aligns with other providers. It is trained on the RED-T and RED-B course material, and members can request clarification or suggest edits. Once approved, those become part of the institutional knowledge.

9. Event-Based Replication. EntityEvent is the recommended path for keeping systems in sync, with the Queue Resource heading for deprecation. A reference server, client and testing tools are available now.

10. The Global Data Exchange (GDX). Built on the Web API and Data Dictionary, the exchange connects markets across borders while each participant keeps control of their local data and rules. RESO membership is required to participate in GDX, and the data producer nodes now span many countries.