[Rets-dev] The MLS Transaction Set

[Paul Stusiak]

In-line

Dave Sullivan wrote:
> MLSs originated in a time when there was NO information available 
> about real properties for sale.  The MLS book provided REALTORS with a 
> twice-monthly list of properties for which they could earn a 
> commission if sold, a brief description of the property and a small 
> B&W photo.  For decades, the MLS was the _best_ source for information 
> on a real property, as it added photos, then color, then links to 
> video; but the advent of the Internet is rapidly making this less true.
>
That is not my definition of the how or the why MLS operations occurred. 
Properties for sale clearly predate the MLS and the information also 
must predate the MLS. I think that the closest analogy is the Commercial 
market where the information is closely held or at the least, multiple 
sources of information must be accessed to understand what is available 
in the current inventory in an area. I think that other countries may 
follow this multiple sources of information necessary to determine the 
inventory. To my thinking, the MLS is a way to share those listings 
between potentially competing vendors to provide a more complete view of 
the market. Whether it is a shoe-box, book or on-line system, it is this 
common information market that is close to my sense of the MLS.

Wikipedia has a some information here
http://en.wikipedia.org/wiki/Multiple_Listing_Service
(As with all Wikipedia entries, you are cautioned as to the source and 
veracity of information)

As well, there is some information on the MRIS website.
http://www.mris.com/about/history/index.cfm
(Of course, this history may only be relevant to the MRIS service and 
region.)

You're missing the (R) on REALTOR(R).
> For the sake of discussion, let's say someone starts a service to 
> provide comprehensive information, pictures, and video of a property 
> for REALTORS which they can link to in their listing.  This would let 
> them avoid filling out the entire MLS form and just enter the factual 
> data of property address, legal description, price, terms, exclusions, 
> etc.  The MLS would no longer carry the property description, but 
> merely a link to it.
>
> In this environment, what does RETS convey?
In an integrated client facing application, I would expect that the 
comprehensive service would provide a RETS feed of their information 
using the defined transport and the defined schema. The client 
application can then use modern tools to build a composite view for the 
application, from the property information, the listing information, the 
media information and the public record information. I can further see 
RETS providing the mechanism for exchanging the information to populate 
Appraisal forms, Inspection forms and other pieces of the transaction.

I'm assuming that your question hides a different observation on your part.
>
> =====================================
>
> Regarding the Listings.xsd, the schema propagates existing MLS table 
> structures that use STATUS to convey several different dimensions of 
> the business status of the Listing.  Is it offered for sale or not?  
> If offered, has a contract been accepted by the Seller?  Is the 
> contract contingent on anything?  Is so, what are the contingencies 
> and when do they expire?  (/I notice quite a lack of patience with 
> those MLSs that try to include all this information in their STATUS 
> field, which then makes it incompatible with the RETS standard)
>
> /
I don't understand your observation. The Listings schema is a hierarchal 
structure and not a tabular structure. Can you explain how this 
propagates a tabular structure?

I think you need to look here
/Listings/Listing/ContingencyInformation/
/Listings/Listing/ContractInformation/
as well as the enumeration for ListingStatuses in RETSCommons.xsd

Again, if you feel that there is missing information, please let me know 
and I'll bring it to the group for discussion and inclusion.

I don't understand your comment about the 'lack of patience...' or how 
you could include all this in a single field when it represents many 
diverse business conditions.
> //======================================
>
> As far as attending meetings goes, that would only be effective if 
> stakeholders are receptive to a significant change in perspective.  In 
> my experience since 1999, stakeholders represent the business 
> positions of their employers.  There is a natural tension between the 
> client-side businesses which would like to receive lots of services, 
> and server-side organizations who must bear the cost of providing 
> them.  In this environment, achieving a standard is a much lower 
> priority than negotiating the scope of functionality.
>
I don't follow you here. I was suggesting that you could attend a 
meeting to present your experience to the Schema group. As any one who 
has attended these meetings in the last few months will agree, the group 
has had many arguments presented about how the schemas can represent the 
information. Those who have presented supported and reasoned arguments 
have had their ideas incorporated into the standard. Even good arguments 
can be rejected or modified when additional facts are provided.

My experience extends before 1999 to 1982 in the business world and, 
while in general, people as stakeholders see the world through their own 
perspective, most people are willing to accept compromise when presented 
with an argument that outlines group benefits - a 'greater good' if you 
will.

There are certainly more stakeholders represented at these meetings, 
including strong representation from MLS and Associations as well as 
from the Broker community than you describe.

I would further point out, that while core to the community, the 
existing listing inventory data is not the only facet in RETS2. This 
seems to be a common misconception. RETS2 is attempting to broaden the 
standard into new business needs like workflow management embodied in 
Transaction Management Systems, association membership and other areas 
around the complete real estate transaction - from contract to keys.

Paul
> Dave
>
>
> At 03:59 PM 8/5/2007, Paul Stusiak wrote:
>> Thank you for your comments.
[snip]

-- 
Paul Stusiak
Falcon Technologies Corp.