Accredited OpenMLS Registrar Process

This past week, I finished one of my ucf graduate courses covering evaluation of nonprofit programs and activities. The textbook was called Evaluation: A Systematic Approach.

From my research and course work, I developed the above diagram which depicts the process for accrediting OpenMLS® Registrars in the near future. This is a beta version, however, it does encompass and satisfy evaluating requirements, documents, and supporting information for accrediting third-party organizations for becoming a fully, functional OpenMLS® connecting to the World Wide MLS (WWMLS) over the Internet.

I intend to publish the paper I submitted for this course on my papers website. The paper's title is GR8C Accredited: Developing an Accreditation Program for OpenMLS® Registrars.

--Corey

Happy First Birthday WWMLS

Last Saturday marked the first birthday for the World Wide MLS (WWMLS). Since then, the follow progress has been made towards WWMLS:

• Presented Multiple Listing Service Network (MLSN) Protocol at the University of Central Florida 2011 Research Fair


• Ongoing data research and collection of legacy mls numbers on the World Wide Web (WWW)


• Development integration with Red Hat's Openshift Platform as a Service (PaaS)


• Accepted Exhibition of MLSN Protocol at Nonprofit Technology's (NTEN) 2012 Confernece and Science Fair in San Francisco
  
• Accepted MLSN Abstract Paper for presenting at American Real Estate Society (ARES) in April of 2012

As MLSN is presented to different groups such as academics and technologists, I am confident with the two upcoming presentations in 2012, especially in St. Petersburg at ARES, that the MLSN Protocol and WWMLS framework will alter others' thought processes of not only the dysfunctional aspect of today's legacy MLS, but also future directions in how real estate consumers interact and expect a specific quality of service (QoS) from real estate professionals. The main intention is integrate WWMLS in every aspect of the future of real estate.

Moving foward, the second phase for WWMLS will be the introduction of the messaging language called Real Estate Metadata Language (Remetal). This XML language will be used to markup properties in a self-describing, yet simple language for sending and receiving between the main OpenMLS Registry and accredited OpenMLS Registrars. I plan to propose Remetal to additional call for papers (CFP) on the academic and technical levels in 2012.

The third yet most important phase will be for the Real Estate Transport Protocol (RETP). This protocol defines the type of messaging, the distribution channels, error correction system, etc. Again, RETP papers will be proposed along with exhibitions at national and if necessary global science fairs.

The future of real estate is bright and changing.

And as the cliche goes, please stay tuned...

--Corey

PubSubListing Protocol v0.1

One of the challenges for buyers in real estate is knowing the most current listing information. The MLSN Protocol resolves this issue for public access to listing information, but it is based upon a request/response protocol. A user must manually query an mlsn server to find out the latest increase or decrease price for a listing. Whereas, the publish/subscribe could be used to receive listing information automatically over the Internet.

In the diagram above, users subscribe to topic message queues using the PubSubListing Protocol. When a listing's price changes, this update is sent to the messaging server which updates the subscribed topic queues, respectively. The pricing update is broadcasted over the PubSubListing Protocol to the users who then view the new price on their laptop, desktop machine, or mobile device. This broadcast pattern continues whenever the listing's price changes. Users have the ability to continue to receive future broadcasted messages by remaining subscribed or unsubscribing to the topic queues.

In summary, the obvious benefits of the PubSubListing protocol are the automated messages of changes and the ability to subscribe or unsubscribe to topic queues. The next step for the protocol is to apply for a reserved port with IANA.

MLSN URL's Reusability

One of the major benefits of MLSN URL's is the ability to reuse assigned MLS Numbers. Using an simple scenario, I'll go in detail of how reusability works with MLSN URL's.

In the diagram above, Alice is an owner of an accredited OpenMLS registrar. Her service is located at alicesmls.com.

Bob the seller, needs to sell his house in Orlando, Florida. He registers it on Alice's MLS for 60 days and receives a unique MLSN URL, mlsn://1.1.1@3203.840.

Unfortunately, Bob's house does not sell within the 60 days and expires. When this happens, the assigned 1.1.1 or triple short number returns to Alice's block of MLS numbers to be reused again.

A new seller, Cristy, registers her house in Atlanta, Georgia on alicesmls.com and receives her unique MLSN URL, mlsn://1.1.1@30329.840.

As you can see, 1.1.1 was used once with Bob's listing and then again with Cristy's. Each MLSN URL represents two completely different listings, which demonstrates reusability.

By the way, the number 840 in the MLSN URL's represents the iso country code for the United States.

--Corey

MLSN Protocol User Session Diagram

A Simple User Session

Scenario: User wants to know the status of a property listing in the downtown Orlando zip code, 32801, located in the United States.

A user starts a session on a client desktop. He enters the following MLS Number URL at the prompt:

user>mlsn 1.1.1@32801.840/status

The mlsn client application sends the MLSN URL via port 32801 over tcp through the internet to an MLSN Messaging Server which accepts the text string via port 32801.

The MLSN Server routes the URL text string to an application server which parses and creates a query for the database which returns a result.

The result is sent from the application server back to the MLSN Messaging Server which sends the result via port 32801 over tcp back through the Internet cloud.

Finally, the client desktop receives the result via port 32801 and displays the results to the user:

user>active

--Corey