RESO Product Updates is sponsored by

We’ll be at NAR NXT in just a few weeks! Visit us at Booth #1541 near the Global Pavilion to connect with the RESO team and learn more about our RED courses, RESO Analytics, Certification and more – and don’t forget to grab some RESO swag while you’re there! We can’t wait to see you!

Connect with RESO’s unmatched membership of industry leaders. Secure your spot as the RESO Monthly and/or RESO Product Updates sponsor: advertising@reso.org.

November 2025

Data Dictionary

Data Elements Approved for Data Dictionary Version 2.2 (Minor)
PoolCommunityYN Field (Boolean) – Approved new field to go along with the existing PoolPrivateYN field.

Study – Approved as a new lookup under the RoomType and FireplaceFeatures fields. Study also currently exists under ImageOf.

Survey – Approved as a new lookup under the LotSizeSource field. Adding Survey under LotSizeSource brings consistency to the lookups of the measurement source fields, as it currently exists under LotDimensionsSource and RoomLengthWidthSource.

Screened Porch – Approved as a new lookup under the ImageOf field.

Data Elements and Changes Approved for Data Dictionary Version 3.0 (Major)
Move the Humidifier lookup from Appliances to OtherEquipment – Humidifier and Dehumidifier are currently in two different fields. The decision to move one of them so that they are both under OtherEquipment increases consistency in the Data Dictionary.

Change the name of the HorseYN field to HorsesPermittedYN – The new name provides more clarity to the meaning of the field.

Global Subgroup
The group reviewed a worksheet that shows potential new data elements to enhance the Data Dictionary for international use. The sheet contains usage metrics derived from certification aggregate data and SNPI usage data from France. Several data elements were identified to be recommended to the Data Dictionary Workgroup.

Duplication Subgroup
The group continued classifying the different types of duplication that exist in the Data Dictionary and recorded recommendations to send to the main Data Dictionary Workgroup. The recommendations include deprecation of duplicate data elements and definition enhancements to further explain data elements that may appear to be duplicates but have a specific use in their respective fields.

New Construction Subgroup
The initial meeting of the New Construction Subgroup reviewed two business cases, New Construction Data Elements and New Construction Development Data Elements. The group identified potential targets and stakeholders for any recommendations that it will make.

Multi Family PropertyTyle Subgroup
This subgroup will be considering the potential of having a Multi Family lookup option at the PropertyType level. The first meeting was on Tuesday, November 4.

Interoperability

Standardization of Offer Management (OM) and Transaction Management (TM)
The group discussed the feasibility of creating a lightweight specification that would allow OM and TM products to exchange data using the ActivityPub protocol. The group is gathering feedback on the potential benefits of OM systems interoperating with each other more efficiently, whether offer data should be shared publicly and to what extent it needs to be limited.

The next steps for this case include:

• Get a general consensus that offering an efficient way to share offer information is desirable (workgroup meeting attendees were generally in favor).
• Gather volunteer OM providers willing to participate and host offer hubs.
• Gather subject matter experts to identify the Data Dictionary fields needed to exchange offer data (similar to the work done with Payload Tagging).

Research and Development

AI Fields – The group continued discussion on the potential need and use cases for fields to communicate permissions on whether AI can be used on listing data (e.g., whether a listing can be used in training AI models). The group would like to gather any implementation examples that currently exist to help drive the topic.

Environmental Hazards / Disaster Mitigation – The group is continuing to gauge the demand for and current use of fields to communicate preparedness and/or risk for natural and environmental disasters on properties.

To address potential reluctance to share this type of information, the group suggested these items be separated into legally required and nonlegally required categories.

Transport

• The Transport Workgroup reviewed recent votes on changes to RESO versioning policy. The changes allow minor, nonbreaking Data Dictionary versions to be released after being approved by the Data Dictionary and Transport workgroups, without need for RESO Board of Directors (BOD) ratification. Major versions, which contain breaking changes, still require BOD ratification, and providers will have one year to implement them. Please review the policy document.
• The Transport versioning policy page has been updated to reflect the recent changes. 
• 2025 Fall Conference Pain Points were captured and reviewed. They were discussed at the November 3 Transport meeting. 
• The Pain Points page will be continuously updated as new pain points are submitted and resolutions documented.
• FAQs will be created based on the Spring 2025 Conference Pain Points.
• The workgroup is developing its 2026 Roadmap and is seeking community feedback.
• RESO is consolidating a Data Dictionary entity-relationship diagram (ERD), created by Dan Troup, and a metadata relationship model, created by Sergio Del Rio, into a single ERD covering the entire Data Dictionary.
• Work is underway to clarify the definition of ModificationTimestamp with the goal of making providers aware that they should update the fields when a record is created, updated or “deleted.”
• RESO will discuss creating new fields for OriginatingSystemModificationTimestamp, SourceSystemModificationTimestamp and internal system updates outside of changes to the record.
• RESO will discuss creating new fields for: 
  • OriginatingSystemModificationTimestamp
  • SourceSystemModificationTimestamp
  • Internal system updates outside of changes to the record.
• DOM Increment Proposal – Review of the proposal is requested, and RESO is seeking additional implementations.
• Continued work on standards for exchanging offer and general transaction management information is being undertaken in the Interoperability and Transport workgroups.
• The ActivityPub Subgroup finalized a resolution protocol for the Unique Licensee Identifier (ULI).

New Subgroups in Support of 2026 Roadmap Items:

• Schools & Geographies – The goal is to standardize the schools, postal code and city fields.
• Identifiers – The goal is to standardize the Unique Organization Identifier (UOI) and the Unique System Identifier (USI) and to ultimately replace the Organization Unique Identifier (OUID) field. 
• Interested members should contact transport@reso.org to join.

New Project Focus Groups:

• DDWiki – RESO is seeking feedback from the community on the Data Dictionary Wiki.
• RESO Desktop Client – RESO is seeking input on important features for a new desktop client.
• Interested members should contact dev@reso.org to join.

October 2025

Data Dictionary

Data Elements Approved for Data Dictionary Version 2.2 (Minor)
Energy Performance Certificates for the EU – Approved new field and lookup additions to the PropertyGreenVerification Resource. This is designed to not only fit the original proposal for communicating Energy Performance Certificate (EPC) information for the European Union (EU) but also as a flexible option for other cases.

Municipality Field (String) – Approved a new field for Municipality. Previously, Municipality was approved to be removed as a synonym of Township.

MemberStateLicenseState Field (Collection) – New expansion field to connect the Member Resource and MemberStateLicense Resource. This would allow for efficient communication of multiple licenses for practitioners that are licensed in more than one state or have multiple types of licenses.

BedroomsAboveGrade and BedroomsBelowGrade (Number) – Two new fields to communicate bedroom counts per grade level.

Data Elements Approved for Data Dictionary Version 3.0 (Major)
Crawl Space to FoundationDetails – Approved moving the Crawl Space lookup from Basement to FoundationDetails.

WaterBodyRestrictions Field (String List, Multi) – Lookup field addition to the WaterBody Shape, approved for Data Dictionary 3.0.

WaterBodyRestrictionsYN (Boolean) – Addition to the WaterBody Shape, approved for Data Dictionary 3.0.

Global Subgroup
The group continued discussing property descriptions (e.g., architectural styles, water sources, location fields) that are common outside of North America but are not present in the Data Dictionary. The group is still seeking subject matter experts to provide international metadata or otherwise provide guidance on international needs for the Data Dictionary.

Duplication Subgroup
The group continued classifying the different types of duplication that exist in the Data Dictionary and recorded recommendations to send to the main Data Dictionary Workgroup.

New Construction Subgroup
Upcoming group scheduled for October 15 at 12:00 pm ET / 9:00 am PT. Bill Gaul is the chair.

Multi Family PropertyType Subgroup
Upcoming subgroup to consider the potential to have a Multi Family lookup option at the PropertyType level. It is currently in PropertySubType and StructureType but is highly used as a PropertyType. Chair needed.

Interoperability

Offer Management (OM) Interoperability – The group is discussing potential benefits of a standard that would allow OM products to efficiently exchange data with each other. More specifically, whether a lightweight specification utilizing the ActivityPub protocol, as is being discussed by the ActivityPub Subgroup, would be beneficial. Additionally, the group is gathering feedback from OM providers on whether offer information can be shared publicly and, if so, whether it should be limited. The group has action items to create a data model for exchanging offer data and to gather subject matter experts to identify which fields would be needed to do so.

Research and Development

AI Fields – The group is researching the demand for and current usage of AI-type fields that would communicate permissions on allowing AI to be used on listings. For example:

• Allow AI Learning Y/N (Property Resource) – Listings set to “No” would tell specific AI vendors to not use this listing in any training models.
• Allow AI Tracking/Learning Yes/No (Member and Office Resources) – For listing input and chat bots. 
  • May be used in agent/office controls for agents who prefer that their listing input doesn’t use any AI assistance (e.g. Lundy voice tools, Restb.ai photo enhancement).

Wildfire/Disaster Mitigation – The group is researching the demand for and current use of fields to communicate preparedness for natural disasters. For example:

• Disaster Mitigation / Preparedness – Fields on individual properties to describe what has been done to prepare for or respond to disasters.
• Disaster Risk – Fields to indicate the risk of disasters for individual properties (e.g., flood risk, fire risk).

Transport

The group reviewed the results of the recent policy votes and discussed the need to update the definitions of the ModificationTimestamp fields to clarify that they are reliable for use in data replication.

Additionally, the group discussed the potential for new timestamp fields such as an Internal Modification Timestamp and Originating/Source System Timestamp.

ActivityPub Subgroup
Voted to approve a consensus mechanism for resolving Unique Licensee Identifiers (ULI). This is a threshold that would need to be met during the ULI confirmation process by organizations acting as resolvers, in order to create a new ULI. It is essentially a check that a ULI does not already exist for the licensee.

RESO Analytics

The upcoming 4.0.0 release of RESO Analytics introduces an upgrade across multiple aspects of RESO’s certification and analytics offerings, including:

• User guides and help screens that add insights to the raw information.
• Tool tips that provide quick guidance to site functions.
• Six new virtual tours that offer easy-to-follow product explanations.

More details will be shared in a blog post sent to all members upon release.

September 2025

Data Dictionary

The following items were approved via virtual vote for Data Dictionary 2.1 or 2.2.

Data Dictionary Payload Additions (Data Dictionary 2.1) – Adding payload tags (similar to IDX) to fields that would typically be used in Association Management Systems and Offer Management.

webp MediaType (Data Dictionary 2.2) – Adding new lookup in the MediaType.

High-Speed Internet (Data Dictionary 2.2) – Communicates availability and details of broadband Internet service(s).

• InternetConnectivityYN (Boolean)
  • Indicates whether the property has access to a high-speed Internet service, which is an Internet connection delivered via broadband technologies (e.g., cable, fiber optic). As of 2024 in the United States, the FCC defines high-speed Internet as having minimum download speeds of 100 Mbps and upload speeds of 20 Mbps.
• InternetConnectivityType (String List, Multi)
  • Indicates the specific broadband service(s) available for delivering high-speed Internet to the property (e.g., cable, fiber optic).
• InternetConnectivityMaxDownloadSpeed (Number)
  • Refers to the highest rate at which data can be transferred from the Internet to a user’s device over a specific Internet connection, typically measured in megabits per second (Mbps) or gigabits per second (Gbps). See the InternetConnectivitySpeedUnits field for the unit used.
• InternetConnectivityMaxUploadSpeed (Number)
  • Refers to the highest rate at which data can be sent from a user’s device to the Internet, typically measured in megabits per second (Mbps) or gigabits per second (Gbps)
• InternetConnectivitySpeedUnits (String List, Single)
  • Indicates the standard measurements used to quantify how fast data is transferred over an Internet connection (e.g., Mbps, Gbps).

Geocode Fields and Lookups (Data Dictionary 2.2) – Communicates the source of geocode data and other information to downstream data consumers.

• GeocodeSource (String List, Single)
• Indicates the source of the geocode coordinates on a record (e.g., Bing, Google).
• GeocodeDisplayYN (Boolean)
• Indicates whether the geocode coordinates can be used for display.
• GeocodeManualYN (Boolean)
• Indicates whether the geocode coordinates were manually placed during listing input (i.e., not automatically provided by a mapping service).
• GeocodeDoNotAlterYN (Boolean)
• Indicates whether the geocode information should remain unchanged on the record.

Global Subgroup
The group continued discussing property descriptions (e.g., construction materials, water sources) that are common outside of North America but are not present in the Data Dictionary. The group is still seeking subject matter experts to provide international metadata or otherwise provide guidance on international needs for the Data Dictionary.

Duplication Subgroup
The group continued classifying the different types of duplication that exist in the Data Dictionary and recorded recommendations to send to the main Data Dictionary Workgroup.

Broker Advisory

The group discussed the potential for creating a formal Brokerage Data Standard, including a dedicated Data Dictionary schema, for the core systems used by residential real estate brokerages. The goal of such a standard is to address data fragmentation that exists among the many platforms in use by brokerages. Additionally, the standard would aim to enhance interoperability between platforms, provide clear definitions and make data more portable.

Transport

The group approved allowing RESO to fix false-positives in the current version of the SDK, in order to ensure consistency among systems. More specifically, the approval allows RESO to fix the false-positive for Media implemented as an OData Complex Type.

Certification Subgroup
The group discussed the Data Dictionary 2.1 release and its testing rules in preparation to move them to DRAFT status.

ActivityPub Subgroup
The group continued discussion of the Unique Licensee Identifier (ULI) Resolution Protocol and passed the following by vote:

• Adopt use of a consensus mechanism that must be met before creating a ULI.
• Adopt the following consensus formula: Consensus = floor(2/3 * Number of Resolvers) – This outlines the number of resolvers needed for a consensus.
  • For example, in a network of 7 total resolvers, the consensus would be C = floor(2/3 * 7) = 4.

August 2025

Workgroups have begun virtual (online) voting. See the RESO Workgroup Topics and Virtual Voting page, linked from the RESO Confluence homepage.

Data Dictionary

The following items were approved in the first official Data Dictionary virtual vote.

CurrencyType Field (String List, Single)

• Indicates the currency for the monetary values on the record, as input
• Lookup values populated from the ISO 4217 currency codes (e.g., USD for U.S. Dollar, CAD for Canadian Dollar, EUR for Euro)

Additional Living Quarters Proposal

• A data shape of fields and lookups to communicate information about additional or secondary living quarters/areas on a property
• Shape will be available in a later Data Dictionary version

Disaster Fields

• DisasterReliefAvailable (String List, Single)
  • Indicates whether disaster relief assistance is available for the property (e.g., Yes, No, Conditional); may include financial aid, government programs, insurance accommodations or other forms of relief related to declared disaster events
• DisasterReliefRemarks (String)
  • Provides additional details or context regarding disaster relief assistance available for the property

Delayed Marketing Fields

• DelayedMarketingYN (Boolean)
  • Indicates whether the property is subject to delayed marketing, meaning it will not be actively marketed or publicly advertised until a specified future date
• DelayedMarketingDate (Date)
  • Indicates the date when marketing will begin

PropertySubType – Half Duplex

• A residential building that shares one common wall with another unit, forming one half of a duplex structure
• Added as a new lookup under the PropertySubType field.

A new vote with items from the July 17 meeting is available on the RESO Workgroup Topics and Virtual Voting page, available until August 11.

Global Subgroup
The group looked at common property descriptions (e.g., location fields, architectural styles) that are common outside of North America but are not present in the Data Dictionary. Several action items were identified, including engaging with subject matter experts and using a data-driven approach to discover what additions to the Data Dictionary would help facilitate its use internationally.

Duplication Subgroup
The group continued classifying the different types of duplication that exist in the Data Dictionary and recorded recommendations to send to the main Data Dictionary Workgroup.

Interoperability

The workgroup received updates on using ActivityPub to support the RESO ULI and potentially to streamline listing workflows. They also discussed new interoperability ideas, including standards for AI bots to communicate with one another.

Research and Development

The group collected feedback on the need for standardized fields to manage AI permissions on listings – such as whether a listing can be used to train models or be enhanced with AI tools. The group also discussed the potential for fields to communicate property-specific disaster risk and mitigation, including fire and flood preparedness, and discussed the importance of leveraging existing standards (e.g., FEMA).

Transport and Certification

The Transport group initiated a vote on Additional Versioning and Certification Policies. Voting concluded on July 29 and results have been posted.

ActivityPub Subgroup
The group is continuing to discuss the details of a Unique Licensee Identifier (ULI) Resolution Protocol, including a consensus threshold among ULI Resolvers for confirming matches.

July 2025

Certification and MLS Map

RESO will soon update its Certification & MLS Map to reflect Data Dictionary 1.7 certifications as “Certified Legacy,” as it has been over a year since Data Dictionary 2.0 was ratified. RESO continues to certify applicants on Data Dictionary 2.0, and Data Dictionary 2.1 is in draft and under review for final approval. The few remaining Data Dictionary 1.6 certifications on the map will be marked as “Uncertified.” If you have any questions about specific certifications, please contact certification@reso.org.

Data Dictionary

Bulk Sale Subgroup
The group completed the planned meetings and approved the proposal for a PackageSale Resource and Property Resource field additions to support package sale listings. The proposal will need to be approved by the main Data Dictionary Workgroup.

Duplication Subgroup
The group began classifying the different types of duplication that exist in the Data Dictionary and created an action item to use RESO Analytics to determine how many organizations use both instances of a duplicate or only one or the other.

Global Subgroup
The group identified several research topics to find areas of the Data Dictionary that could be enhanced to better support international use – for example, identifying missing address/location components, property subtypes, architectural styles, ownership types and utilities – along with the regions of the world that may need them.

Research and Development

The group discussed interoperability and potential use of the ActivityPub protocol to improve transaction information during a listing lifecycle. Potential fields that communicate permissions about whether an organization’s data may be used in AI learning or training models were introduced.

Transport

The Transport Workgroup supported the proposal for workgroups to approve minor Data Dictionary versions without ratification from the RESO Board of Directors, provided that no breaking changes are introduced. The RESO board will ultimately weigh in on this policy.

ActivityPub Subgroup
The group discussed the Unique Licensee Identifier (ULI) Resolution Protocol and recommended that ULIs only be created when a set number of confirmations have been met, rather than creating them automatically and potentially having to remove them if consensus is not met. The group also discussed a consensus threshold needed from ULI resolvers for creating ULIs and the authentication and authorization method for the ULI network.

June 2025

Voting

Going forward, the Data Dictionary Workgroup approved moving in-meeting voting to online voting. Additionally, the group voted that all proposals, requests, initiatives, etc. must be brought up in a meeting prior to voting. This retains the policy of requiring a motion, a second and an opportunity for discussion on all topics before they are brought to a vote.

A new Confluence page (not specific to any one workgroup) is being created to show all topics currently available for a vote, as well as topics that are upcoming for a discussion and vote.

Data Dictionary

Data Dictionary 2.1
The draft for Data Dictionary 2.1 has been posted for review. Reviewers may comment on the sheet or email dd@reso.org to report any items that may need attention.

Global Subgroup
A survey was sent out to workgroup members asking which areas of the Data Dictionary could benefit the most from additions and changes with an international focus. Collected feedback will be used to create an outline of tasks for the Global Subgroup to work through. If you are interested in joining this or any other subgroup, email dd@reso.org.

Duplication Subgroup
The goal of this subgroup is to identify, classify and define duplication in the Data Dictionary.

New Construction Subgroup
New metadata has been added for consideration in developing standards conveying new construction and new construction development information. The upcoming group will address the New Construction Development Data Elements and New Construction Data Fields business cases from the R&D Workgroup.

Transport

Data Dictionary 2.1 and Updates on Versioning Policies
The workgroup discussed Data Dictionary Policy Voting Results as they relate to Data Dictionary 2.1.

ActivityPub Subgroup
ActivityPub is a federated, decentralized communication standard. It can be used in scenarios where threaded conversations exist between many different users and nodes, which is common in the real estate data ecosystem. The group has the following two goals regarding the use of ActivityPub:

• Improve communication and standardization during the transaction management process. See: RESO Listing Advertisement Proposal.
• Implement a resolution protocol for the RESO Unique Licensee Identifier (ULI). See: ULI White Paper and ULI Resolution Protocol.

May 2025

New Subgroups

Several new subgroups have sprung up this spring. Email dd@reso.org if you would like to participate in any of these subgroups.

ActivityPub Subgroup
This group (under the Transport Workgroup) will evaluate how to use ActivityPub to implement a resolution protocol for the RESO Unique Licensee Identifier (ULI), as well as how it can be used to provide interoperability throughout the listing lifecycle. ActivityPub has recently been discussed in the Interoperability Workgroup, including its emphasis on protocol over platform – a focus on open, decentralized systems built upon protocols. This shift in focus offers greater flexibility by allowing different systems to interact with each other with less customization required.

Duplication Subgroup
The goal of this subgroup is to identify, classify and define duplication in the Data Dictionary. The group will also identify duplication that remains useful to retain, the existence of which should be clearly communicated to users. Any recommendations for deduplication, a method to communicate duplication or other changes will be sent to the Data Dictionary Workgroup.

Global Subgroup
This group will identify areas of the Data Dictionary where enhancements to facilitate international use may be made. The group will then submit a proposal for any additions or changes to the main workgroup for approval. See Data Dictionary Global Subgroup Proposal for further information.

Here are two current requests related to international use of the Data Dictionary:

• Currency Types and Currency Conversion for International Markets
• Proposal for Energy Performance Certificates for the EU in the Data Dictionary

Multi-Select Lookups Subgroup
Many fields have lookups that could go together or stand on their own. Example fields include PatioAndPorchFeatures and Flooring. Example lookups include Porch, Patio, Screened which could be Screened Porch or Screened Patio. Data consumers do not know whether individual lookups go together.

This subgroup will identify all fields with these instances and make recommendations to address them.

Multi-Select Lookups Subgroup
The goal of this reformed subgroup will be to add data elements to better convey new construction-specific information. The group will address the New Construction Development Data Elements and New Construction Data Fields business cases from the R&D Workgroup. Metadata from construction-focused organizations has been obtained.

Move to Online Voting

A system to vote asynchronously on Data Dictionary proposals is being developed. This will replace or be an addition to the typical Zoom voting done during meetings or live conferences.

April 2025

Data Dictionary

• Cottage
  • Approved Cottage as an addition to ArchitecturalStyle
  • “Also known as cottage” verbiage to be removed from the definition of Bungalow.

March 2025

Data Dictionary

• Transition of the “Master” Term to “Primary”
  • Approved “soft deprecation” of “Master”
  • Soft deprecation means that systems can still be in compliance by using Master as a local field, they have the option of also adopting Primary now, and adopting Primary will be required at a date and version to be determined in the future
• Municipality vs. Township
  • Approved removal of “Municipality” from the disallowed synonyms list of the Township field.
• Legacy and Deprecated Data Elements (RCP-45) Proposal
  • Approved three new fields each for the Field and Lookup resources
• Power Production Source
  • Approved a PowerProductionSource field to indicate the source of information about the property’s energy generation.
    • Addition to the PropertyPowerProduction Resource

Data Dictionary Subgroups

• Bulk Sale – Based on feedback from data providers, the group decided to pursue a Package Sale Resource to communicate bulk/package sales.

February 2025

Data Dictionary

• Proposals for “Primary” Replacing “Master”
  • Add “Primary” lookups (e.g., Primary Bedroom, Primary Bathroom) to all fields that contain “Master”
  • Deprecate lookups that use “Master”

• FrontageLength Numeric Fields
  • Approved FrontageLengthNumeric field
  • Approved FrontageLengthNumericUnit field
  • Deprecate FrontageLength String field

• New ParkingFeatures Lookups
  • Add Attached Garage
  • Add Detached Garage
  • Will be consistent with Attached Carport and Detached Carport

January 2025

Data Dictionary

The following topics are due for a vote in the next Data Dictionary Workgroup meeting:

• Attached and Detached Garage Proposal (motion and vote needed)
• “Master” Term in Data Dictionary
• Legacy and Deprecated Data Elements (RCP-45) Proposal
• Municipality vs. Township
• Frontage Length Numeric Field Request

Data Dictionary Subgroups

Bulk Sale: A Package Sale Shape is taking shape.

Accessory Dwelling Unit (ADU): The Additional Living Quarters (ALQ) Shape is being finalized and will be emailed to the subgroup for review and virtual vote.

Fast Track: Review of the Fast Track Potential Data Dictionary Additions sheet is complete, and several new lookups will be suggested to the Data Dictionary Workgroup as part of New Lookup Considerations from Fast Track Subgroup.

Versioning Policy: A subgroup will be formed to review Data Dictionary versioning, handling duplication and deprecation of duplicate data elements. Posts will be created in the Data Dictionary Workgroup and Transport Workgroup discussion forums to solicit participation.

Alignment Reports

RESO Provider and Market Alignment Reports are officially for sale. Industry Alignment Reports are free to RESO members within RESO Analytics, and Consumer Alignment Reports are coming soon. | DETAILS

December 2024

Data Dictionary

Community Pool Features Proposal – A new multi-select lookup-type field called CommunityPoolFeatures was approved.

• Lookups are based on PoolFeatures lookups with options not pertaining to community pools omitted.
• CommunityPoolFeatures will exist alongside the existing PoolFeatures field.
• The PoolFeatures field will remain unchanged.

Data Dictionary Subgroups

• ADU Subgroup – Work continues on an Additional Living Quarters Proposal.
• Bulk Sale Subgroup – Work continues on selecting a structure to communicate bulk or package sales.

Alignment Reports

This is a reminder that RESO Provider and Market Alignment Reports are officially for sale. Industry Alignment Reports are free to RESO members, and Consumer Alignment Reports are coming soon. | DETAILS

November 2024

Data Dictionary 2.0

Retroactive Consistency Changes (Fields changed from String to Lookup)

• OfficeCountry
• OfficeMailCountry
• OfficeMailStateOrProvince
• OfficeMailCountyOrParish

Fields changed to use “Id” instead of “ID” per PascalCase convention (with more to come)

• LockOrBoxOriginatingSystemID
• LockOrBoxSourceSystemID
• OriginatingSystemResourceRecordID
• OriginatingSystemResourceRecordSystemID
• SourceSystemResourceRecordID
• SourceSystemResourceRecordSystemID
• FranchiseNationalAssociationID
• OfficeBrokerNationalAssociationID

Approved enumerating Time Zone fields with lookups of the tz database from IANA

 Data Dictionary 2.1

• Approved Commercial (CRE) Subgroup Proposal
• Approved HasStreamYN addition to Add/Edit with Media
• Approved FeedTypes/FeedRules Fields Proposal
• Closed by the Data Dictionary Workgroup at the RESO 2024 Fall Conference, is currently in DRAFT status and will await Board of Directors ratification at its next meeting

October 2024

Data Dictionary Subgroups

Commercial Real Estate (CRE) Subgroup – The group wrapped up their final meeting and submitted a CRE Proposal to the Data Dictionary Workgroup. The updates would convey commercial-focused property data outside of the existing data elements. The main points are:

• A new Property Type named Commercial Real Estate (CRE)
• Two new lookup fields named PropertyCategory and PropertySubcategory (commercial having a greater level of tiered property classifications than residential)
• Identification of existing fields and lookups to be given the CRE Property Type attribute/reference

ADU Subgroup – The group held its first meeting with the goal of developing a standard for conveying information about additional living quarters outside of the main residence.

R&D Workgroup

• The group went over a New Construction Development Data Elements business case, which aims to create standards that express what is available at a development level vs. resale home specs (e.g., a list of available floor plans, builder information and ranges for price, square footage, bedrooms and bathrooms).

Interoperability Workgroup 

• A proposal to tag existing Data Dictionary fields with Association Management Systems (AMS) and Offer Management (OM) payloads was approved and submitted to the Data Dictionary Workgroup.

September 2024

RESO Alignment Reports

RESO Alignment Reports from RESO Analytics take published data from the RESO certification process and organize it into practical, actionable visualizations and comparisons.

The Industry Alignment Report is complimentary for all RESO members, through their process of becoming certified.

The Provider Alignment Report and Market Alignment Report are live in beta. These premium products are available for purchase. An automated way to buy reports is on the way. For now, please inquire with dev@reso.org.

Alignment reports save organizations significant time in constructing comparative data frameworks, allowing technical staff, data analysts and business management to focus on the critical details necessary to make their data collaborations work. | READ MORE

Data Dictionary

Features That Help with Accessibility

• Approved several accessibility-related lookups under various fields – General Accessibility Features Lookups.
• The new lookups are less specific, without exact measurement requirements and other conditions as laid out in the HUD-driven AccessibilityFeatures field.

Waterfront Subgroup Proposal

• Approved a new data “shape” named WaterBody to convey information about bodies of water related to the property.
• Allows for a property to describe one or more related bodies of water including type, access, features and ownership.

Rental Subgroup Proposal

• Approved new data elements to improve the existing Residential Lease (RLSE) Property Type for rental use cases.

Metadata Resources and DD 2.1

• Approved further support for metadata resources in the Data Dictionary, including changes to the Data Dictionary Reference Sheet Format and Data Dictionary Wiki.

August 2024

Data Dictionary

Add/Edit with Media Fields – The following additions and changes were approved for the Media Resource in order to support the Add/Edit with Media specification:

• MediaStatusDescription (New String Field)
• Change the existing MediaStatus field from “Open” to “Open with Enumerations” and add the following lookups:
  • Incomplete
  • Processing
  • Deleted
  • Rejected
  • Complete

UPI v2.0 Fields
The following fields were approved to support the next version of the Universal Parcel Identifier (UPI, note the updated naming):

• UniversalParcelId
• CountrySubdivision
• ParcelSubcomponent

Approved a new Appliances lookup named Refrigerator with Ice Maker.

July 2024

Data Dictionary

Building Subgroup Proposal – The fields of the proposed Building Resource were approved by the Data Dictionary Workgroup.

Waterfront Data Elements Subgroup

A proposal for a new resource for conveying information about nearby bodies of water was approved to be sent to the main Data Dictionary Workgroup.

RESO Analytics Version 3.1.0 Release Notes – New Testing Configuration Generator

• Providers may now export their prefilled Certification Environment File from the My Account section of the toolbar.
• The exported file will contain the user’s credentials and Certification API Key.

June 2024

Data Dictionary 2.0

The RESO Data Dictionary 2.0 standard represents a large improvement in standardization, particularly in lookups (aka enumerations) and data quality. Users of RESO-certified systems can expect increased predictability and consistency, as all payload data elements will be correctly advertised in their metadata, and all payload data will match what is advertised. | VIEW RELEASE GUIDE

All current Data Dictionary 1.7 certifications will be downgraded to “Certified Legacy” on April 15, 2025. MLSs and other data providers should upgrade their certifications to Data Dictionary 2.0 prior to that date.

May 2024

Data Dictionary

The Data Dictionary Workgroup voted to add fields named BackOnMarketTimestamp and CurrentPrice. Additionally, CurrentPrice will be removed as a synonym of ListPrice.

Transport

The Transport Workgroup voted to create a RESO Change Proposal (RCP) for the Add/Edit with Media addition to the ratified Web API Add/Edit.

Universal Property Identifier (UPI)

The UPI Workgroup approved to adopt a URN-based UPI Version 2.0.

Certification

Minor changes to certification testing created a new effective ratification date for Data Dictionary 2.0 of April 15, 2024.

April 2024

Data Dictionary

• Approved revisions to the definitions of the Standard Status lookups as proposed by a RESO focus group.
• Approved an initiative to create a stand-alone WaterHeater field to convey information about water heaters. Water heater information is currently contained in the Appliances lookups.
• Approved two new lookups under HorseAmenities: Indoor Arena and Outdoor Arena.

March 2024

Data Dictionary 2.1

Data Dictionary Naming Conventions – Approved the motion to change the following resources to singular form in the next version release:

• ContactListingNotes to ContactListingNote
• ContactListings to ContactListing
• Contacts to Contact
• PropertyRooms to PropertyRoom
• PropertyUnitTypes to PropertyUnitType
• Rules to Rule
• TeamMembers to TeamMember
• Teams to Team

Approved the motion to add a field called OpenHouseModificationTimestamp to the Property Resource.

Data Dictionary Naming Conventions – Approved the motion to change the following resources to singular form in the next version release:

• ContactListingNotes to ContactListingNote
• ContactListings to ContactListing
• Contacts to Contact
• PropertyRooms to PropertyRoom
• PropertyUnitTypes to PropertyUnitType
• Rules to Rule
• TeamMembers to TeamMember
• Teams to Team

Approved the motion to add a field called OpenHouseModificationTimestamp to the Property Resource.

Approved two new lookups for the GreenVerificationStatus field: 

• Proposed – Indicates that the verification process has not yet started. Plans or specifications have been proposed as part of a new construction building plan. No construction has started.
• Expired – Indicates that the verification process is complete. All requirements are complete and official verification documentation is on file or published but the verification has expired per specific mandatory energy labeling program disclosure requirements.

Approved changes to definitions of existing GreenVerificationStatus lookups, removing mention of occupancy:

• Complete – Indicates that the verification process is complete. All requirements are complete and official verification documentation is on file or published.
• In Process – Indicates that the verification process is underway but not complete. Application, plans testing or specifications are in process.

Approved two new lookup additions to the EventType field of the InternetTracking Resource:

• Sign In
• Sign Out

Approved retroactively renaming the PowerStorage Resource to PropertyPowerStorage to align with PropertyPowerProduction Resource.

Approved retroactively renaming the following fields of the Media resource to end in “ID” instead of “Id”:

• OriginatingSystemResourceRecordId
• SourceSystemResourceRecordId
• OriginatingSystemResourceRecordSystemId
• SourceSystemResourceRecordSystemId

Transport/Certification

Approved disabling payload validation during certification testing for the following enumerated fields in Data Dictionary 2.0:

• MLSAreaMinor
• MLSAreaMajor
• MiddleOrJuniorSchoolDistrict
• ElementarySchool
• HighSchoolDistrict
• HighSchool
• ElementarySchoolDistrict
• MiddleOrJuniorSchool
• ImageSizeDescription

This change in testing requirements means that those using string enumerations aren’t required to advertise the corresponding lookups for the included fields in metadata.

RESO Analytics

• Added a report switcher dropdown to the Data Dictionary Report for organizations with more than one provider, matching the dropdown on the Certification Summary Report.

February 2024

RESO Web API Add/Edit is Official

The newly ratified standard is now available for certification. | LEARN MORE

January 2024

Standards

The board ratified four RESO Change Proposals (RCPs):

• Add/Edit (RCP-010)
• Add/Edit Rules (RCP-019)
• EntityEvent Model (RCP-027)
• EntityEvent Model and Web Hooks (RCP-028)

Data Dictionary

Data Dictionary Naming Conventions – Approved the motion to change the following resources to singular form in the next version release (Data Dictionary 2.1):

• ContactListingNotes to ContactListingNote
• ContactListings to ContactListing
• Contacts to Contact
• PropertyRooms to PropertyRoom
• PropertyUnitTypes to PropertyUnitType
• Rules to Rule
• TeamMembers to TeamMember
• Teams to Team

The motion to add a field called OpenHouseModificationTimestamp to the Property Resource has been approved.

December 2023

Data Dictionary

The Data Dictionary Workgroup moved forward with enumerating Architectural Style, including values from well-recognized industry lists and high-usage items from RESO Analytics. The following lookups passed:

Alphabetical List of Certified Organizations

Our alphabetized certification status list has returned and is now tied directly to RESO Analytics, as is the RESO Certification Map. The list is now driven by the RESO Unique Organization Identifier (UOI) Service and the Public Organizations feed. Organizations on the list may be expanded to show their certification status and a link to their certification summary on RESO Analytics.

RESO Certification Map

The map is now driven by certification data from RESO Analytics and the RESO UOI Service. Certification statuses for the organizations represented on the map are updated in real time, based on certification self-testing done by data providers.

Map Tooltips

Map tooltips have been updated with the latest certification data from RESO Analytics, along with a link to the certification details for the organization represented.

Certification Status Charts

Pie charts have been added to show the breakdown of certification statuses by organization. There are three charts: Combined (all types of data providers), MLSs and Pooled Platforms. The chart sections are hoverable, showing the exact count of organizations in the selected section.

 

Certified Current Definition

In order to be considered “Certified Current,” organizations must now be certified for both Web API Core 2.0.0 and Data Dictionary 1.7.

 

November 2023

Certification

The RESO Board of Directors ratified Data Dictionary 2.0, Web API 2.1.0 and RESO Common Format at the RESO 2023 Fall Conference.

More will be shared about these exciting developments on RESO’s website, in the RESO Workgroup Collaboration System, on RESO’s GitHub and in future issues of RESO Monthly. You can also expect to see updates on the Data Dictionary Wiki before the end of 2023, as Data Dictionary 2.0 exits “draft” status and becomes the prevailing standard.

What’s important to know about RESO Common Format is that it will allow for more certifications for non-MLS technology.

 

October 2023

Data Dictionary

• Heat Pump Water Heater was approved as a lookup under Appliances.
• Data Dictionary 2.0 will be closed to new changes on October 31, 2023.

The following resources voted in as plural for version 2.0 will be updated to singular:

• CaravanStops – Change to CaravanStop
• MemberStateLicenses – Change to MemberStateLicense
• OfficeCorporateLicenses – Change to OfficeCorporateLicense

The following LookupNames will also be changed to singular:

• CaravanStopsResourceNames – Change to CaravanStopResourceName
• CaravanStopsClassName – Change to CaravanStopClassName

Data Dictionary Subgroups

Fast Track
The group is reviewing suggested mappings for nonstandard enumerations collected via certification testing in RESO Analytics, starting with the most commonly used fields, and they recommended to restrict enumerations for Country and StateOrProvince fields to ISO standards and to cross-validate them.

Commercial Real Estate (CRE)
The group recommended that the CRE standard takes the direction of a new Data Dictionary class as opposed to new resource(s).

Rental
The group recommended a new multiselect lookup field called LeaseTermOptions with the same lookup options as LeaseTerm, plus the addition of options for 3 Months and 9 Months. These options are meant to better convey rental listing information.

Transport

• Supporting Single Feeds (RCP-035) – The group approved the creation of a specification and testing rules based on the Single Feeds GitHub discussion.
• RESO Common Format (RCP-025) – The specification was approved.
  • Testing rules approved by Certification Subgroup were added to the RESO Common Format proposal. 
  • Two implementations have been verified.
  • Beta testing tools have been created.
• Deprecated Data Elements (RCP-045) – The creation of a specification to indicate when a data element has been deprecated has been approved. This could be a resource, field or lookup.
• Conventions for Data Dictionary Resource and Route Naming – Naming conventions for Data Dictionary data elements were approved, including a change to make all resource names singular.

UPI

The UPI Workgroup has proposed a UPI Version 2.0, which involves retaining the formatting of the parcel identifier from the county or other relevant authority.

 

September 2023

Data Dictionary

• ShowingServiceName was approved. | FULL DETAILS
• Engineered Hardwood was approved as a lookup under Flooring.
• ClosetType was approved for the PropertyRooms Resource. | FULL DETAILS
• A new set of REALTOR® Safety Fields was approved. Four items will move from ShowingRequirements to a new ShowingConsiderations field that will also contain ten other items.Three items will move from ShowingRequirements to PropertyCondition. The final result of the REALTOR® Safety Fields Proposal is shown below.

 

August 2023

Data Dictionary

Co-Ownership
Co-Ownership was previously voted in as a lookup under the PropertySubType field for Data Dictionary 2.1. There was a request to move the Co-Ownership option under PropertyType instead, but the Data Dictionary Workgroup voted against this measure. Co-Ownership will continue to be a lookup under PropertySubType.

FrontageType vs. WaterfrontFeatures
This proposal would streamline the lookups of FrontageType and WaterfrontFeatures. The Data Dictionary Workgroup is exploring moving certain lookups to CommunityFeatures. Further research into certification data is underway to see how many providers offer just one or both FrontageType and WaterfrontFeatures fields.

ImageContains
The direction of ImageContains is a new multi-select lookup field that will convey multiple subjects in an image. Some of the more specific items from ImageOf will be put in ImageContains. Additional appropriate items for ImageContains will be gathered with help from fields like Appliances and InteriorFeatures.

ImageOf would be broad items like Backyard and ImageContains would be Fence and Patio. One ImageOf can have many ImageContains. For example: “This is an image of a backyard that has a patio and fence in it.” A proposal for the actual lookups will be out soon.

 

July 2023

RESO Analytics, v1.3.4

Certification status icons have been added to the provider drop-down list on the Certification Summary page.

The icons are hoverable, showing the status for each certification, including in-process certifications.

The icons may also be useful to providers who have an existing certification and are retesting after making changes or testing a new system.

 

June 2023

Data Dictionary

Two new subgroups are forming under the Data Dictionary Workgroup.

Fast-Track Subgroup
The release of Data Dictionary 2.0 will bring new tests on enumerations. The self-testing system will allow data providers to make suggestions for additions or changes to the Data Dictionary. The workgroup is proposing a new model to fast-track the release of high-priority changes without having to wait for major dictionary version changes that could take a year or more to ratify.

This subgroup would create the process to release those changes into the Data Dictionary at a quicker pace. If you would like to participate, please email dd@reso.org.

Building Subgroup
A proposal initiated by the Real Estate Board of New York (REBNY) suggests that a new resource called Building should be added to the Data Dictionary. The goal is a more accurate description of vertical residential properties. Property features for a building can be different from those of a unit. For example, in a rental listing, the building allows dogs, but the condo owner does not.

Metadata has been collected from several providers, including REBNY’s Residential Listing Service (RLS), and will be aligned with the Data Dictionary to identify candidate fields for a new resource.

Please comment on this post if you are interested in helping to shape the fields of a potential Building Resource.

RESO Analytics

Providers may now archive endorsements and should do so for any organizations that they are no longer serving or contain results that are otherwise unwanted.

Archiving is available for endorsements in Passed, Notified, Certified, Canceled or Withdrawn status and is performed by selecting the status button for the endorsement to be archived and then selecting Archive.

Auto-Archiving Certification Endorsements: Endorsements in the statuses of Passed, Notified, Canceled or Withdrawn are automatically archived and replaced if a new endorsement of the same type is submitted by the provider. A new Performance Report will also be generated for any endorsement that is auto-archived and replaced. Endorsements in the Certified and Revoked status are not archived and replaced.

Multiple Statuses of Endorsements: Providers are able to retain existing endorsements that are in a permanent status (Certified, Revoked) alongside new in-progress endorsements of the same type.

Provider System Names: Provider system names have been added to certification reports. Providers may offer more than one system, and the addition of the name allows them to be distinguished from one another. System names have been added to the following reports: Data Dictionary and Web API Reports, Certification Summary Report, and Performance Report. Providers that would like to change their system name may reach out to certification@reso.org, and it will be updated by RESO staff.

Sort Options Improved: The name and time sort on the endorsements page has been streamlined to a single menu, requiring fewer clicks.

Improved Clipboard Functionality: The page header bar, endorsements and summary pages allow for copying an organization’s Unique Organization Identifier (UOI) by selecting the clipboard icon.

May 2023

Data Dictionary

Coming Soon approved as a new lookup under the ChangeType field
Workgroup voted to create Agent/Office biography and media fields (business case from R&D Workgroup)

Web API Transition Guide

RESO has produced a Web API Transition Guide to help organizations along on their own journey toward the API standard. We encourage everyone reading this who has not transitioned fully to RESO Web API to add this to your 2023 reading list.

 

April 2023

Data Dictionary

Lookups Approved for PowerStorageType

• Lithium Ion Battery
• Lead Acid Battery
• Lithium Iron Phosphate
• Other
• Unknown

2023 RESO Winter Developer Conference

MEETING NOTES

Items that were discussed at the 2023 Winter RESO Developer Conference include:

• More user-friendly and extensible metadata resources for models, fields and lookups
• The ability to advertise capabilities, like whether a field is searchable, updatable or expandable
• Support for locale, internationalization and local data elements
• Pushing payloads to data consumers using web hooks and RESO Common Format
• Add/Edit for Media resources using streams to update photos or videos

 

March 2023

Data Dictionary

Current and future versions of Data Dictionary in spreadsheet format have been added to the home page of the Data Dictionary Workgroup on RESO’s workgroup collaboration system, Confluence, and to RESO’s website.

RESO Web API Transition Guide

We are excited to share an initial draft of Transitioning Your Customers to RESO Web API: A Guide For MLS Leaders. This guide will help you get started and see the transition through to completion.

This is just version 1.0. We welcome suggestions/edits from the community before we unveil a printed version 2.0 at the upcoming RESO 2023 Spring Conference in San Antonio, TX, April 18–20.

Feel free to contact us at support@reso.org with any suggestions. This is a team effort, and we are grateful for your contributions.

 

February 2023

Data Dictionary

A new resource and accompanying fields were approved for Data Dictionary 2.0.

• PowerStorage
  • PowerStorageType
  • NameplateCapacity
  • DateOfInstallation
  • InformationSource

Transport

Data Dictionary JSON Payloads (RCP-025) has been renamed RESO Common Format.

Transitioning Your Customers to RESO Web API, A Guide for MLS Leaders has been produced with feedback from dozens of member organizations.

MLSs, technology vendors and brokerage companies contributed their experiences in preparation, communications, scheduling and distribution for a successful transition from RETS to Web API.

Version 1.0 of this guide will be distributed in Q1 to all MLSs via email. RESO is seeking your feedback to continue improving the guide.

A final version will be printed and shared with attendees at RESO’s Spring Conference in San Antonio, TX.

 

January 2023

Data Dictionary

A field to contain a listing’s participant-provided contact phone or email called AttributionContact was voted into Data Dictionary 2.0.

A field called CompensationComments was voted into Data Dictionary 2.0.

A field called GrossLivingAreaAnsi was voted into Data Dictionary 2.0.

A lookup called Affiliate under the MemberType field was voted into Data Dictionary 2.0.

A lookup called Steel Frame under the ConstructionMaterials field was voted into Data Dictionary 2.0.

The Owner Will Carry lookup of the ListingTerms field’s definition was corrected to read, “The seller will carry the mortgage note.”

A new Resource called InternetTrackingSummary, as well as new fields and lookups, were voted into Data Dictionary 2.0.

Transport

The Lookup Resource additions to the Data Dictionary 1.7 specification were approved.

Changes were made to the proposal for Metadata Localization, and the group approved moving forward with producing a specification.

Two implementations of the RESO Common Format proposal have been identified. The group will review the specification and testing rules next.

The draft Add/Edit (RCP-010) proposal has been updated to reflect the changes from the original proposal. One implementation has been validated.

RESO Analytics

The v1.3.0 release of RESO Analytics contains the following features:

Performance Metrics Improvement – Estimated Seconds per 1,000 Records
Estimated Seconds per 1,000 Records as a large number metric, including industry averages.

Example:

See: https://certification.reso.org/summary/M00000146

Addition of Sort by Time in Endorsements List
Users can now sort by time in the endorsements list.

This will show each endorsement individually rather than grouped because they could have been tested/approved at different times.

Archive Reports Feature
Added the ability to archive reports for providers and admins.

Providers should archive their reports when they have results they no longer want or if they have a customer that they no longer are doing business with.

The public feed will be updated automatically if a provider archives their reports, and their “pair” will not be counted as certified for an MLS with only one of the two required endorsements in cases where they only archive one endorsement (e.g. Data Dictionary) and not the other (e.g. Web API).

Notifications will be sent to the provider of the endorsement, not the recipient, when an item is archived.

RESO admins can also archive reports, which is a softer option than to revoke them. The provider will be notified if RESO archives an endorsement.

High-level statistics will be saved when reports are archived, as RESO will be offering provider metrics in the future. This will allow providers to see whether they have improved against their historical averages, including standardization and performance statistics.

RESO Public Feeds
A new organization service is available for those wanting the authoritative source for Unique Organization Identifiers (UOIs). It matches the schema of the OUID Resource in the Data Dictionary.

The data reflects current organization and endorsements feeds also used for certification and provides a formatted view of high-level statistics.

1. Organization Feed
The orgs service shows the data from the production UOI service in JSON format, matching the OUID Resource. https://services.reso.org/orgs

2. Orgs Plus Endorsements Feed
Parameters may be passed to show the endorsements for each org as well. https://services.reso.org/orgs?showEndorsements=true

3. Formatted Stats Feed
There is also a service that shows formatted metrics in JSON format. https://services.reso.org/orgs?statsOnly=true

The response looks like the following:

Each bucket we certify is represented, as well as an “All” category, showing everything.

For MLSs to be counted as “Certified Current,” they MUST have approved Data Dictionary and Web API Core Endorsements. As of this afternoon, there are 233 Certified Current MLSs and 184 Passed Current. We should perhaps reach out to the Certified Legacy and Uncertified.

This information will be the same that drives the map and the other lists on the public RESO site, and a working demo of that can be found here: https://resostg.wpengine.com/certification/

Coming in Certification v1.4.0
Provider and Market Alignment Tools, including comparisons against Industry Aggregates.

Those interested in beta testing this product should reach out to dev@reso.org.