Differences between revisions 40 and 41
Revision 40 as of 2011-03-28 18:25:47
Size: 5011
Editor: CoreyLeong
Comment:
Revision 41 as of 2011-03-29 13:18:25
Size: 5091
Editor: CoreyLeong
Comment:
Deletions are marked like this. Additions are marked like this.
Line 69: Line 69:
mlsn://2.4.100@32819.840 (Orlando, Florida, United States) mlsn://2.4.100@32819.840 (in Orlando, Florida, United States)
Line 71: Line 71:
mlsn://4.14.1970@36100.380/price (Venice, Italy, Europe) mlsn://4.14.1970@36100.380/price (in Venice, Italy, Europe)
Line 73: Line 73:
mlsn://50.2.16169@7000.036/beds (Hobart, Tasmania, Australia) mlsn://50.2.16169@7000.036/beds (in Hobart, Tasmania, Australia)
Line 75: Line 75:
mlsn://101.1006.3@x.x/baths mlsn://101.1006.3@10117.276/baths (in Berlin, Germany, Europe)
Line 77: Line 77:
mlsn://8.15.23@x.x/squaremeters mlsn://8.15.23@1102.608/squaremeters (in Claro, Philippines, Asia)

Graduate Research

2011 Graduate Research Project

Multiple Listing Service Network Protocol (MLSN)

introduction://


Sellers list their properties with real estate professionals who enter property information into private databases called Multiple Listing Services (MLS).

These MLSs attempt to index listings with serialized numbers that only members of the local real estate association have access to query, insert, and update.

In the United States alone, there are over 900 MLSs which unfortunately create redundant, localized MLS numbers causing confusion over specific properties and their respective listing information on the Internet.

These duplicated MLS numbers can be anywhere from eight digits or more relaying no meaningful or geographical information to real estate professionals and real estate buyers alike.

Random Sample of 100 MLS Numbers from the Web:

110013426, R3185082, 294286, 1107300, 10258465, 1101093, 1028948, 10003617, 24601, 110003812, T2288434, 114240, 740867, 4011070, AX5449172, 171857, FQ5004108, 50101, 172919, 703272, A3932341, 112524, 318566, R3176912, 901410, 972237, 54345, 10009866, 33059, 318616, 210133124, 56291, F1119366, 470733, 470740, 4467536, 4469831, 33069, 24601, 110003812, T2288434, 114240, 740867, AX5449172, 171857, FQ5004108, 172919, 825421, 22129714, 134938, 4202456, 4321153, 956187, 100000106, 094159, 825448, T2399881, 4248855, T2329062, 617893, 10003381, 100002838, 092198, 4275714, 54925, S602879, 1002882, 092153, 791305, 135153, 4327780, 583729, 54924, FX6605832, 2741772, 4331327, 1580548, 100004268, 995033, 81001387, 611838, 88754874, 90055460, 849250, H741473, 4334517, 4334588, 4351841, 845085, 10002523, M5809445, T2396258, T2375453, T2398293, T2404925, 29117969, T2406949, T2384782, 100009994, B352181

Collection Method: Daily Google Alerts

methodologies://


  • Accessibility
    • Registered Internet Port 32801: TCP/UDP.
  • Internationalization (I18N)
    • Reuses ISO 3166-1 for Country Codes.
  • Reusability
    • Triple-dotted numbers are reused creating new mlsn addresses.
  • Standardization
    • Uses IETF RFC 3986 Uniform Resouce Identifier (URI): Generic Syntax.
  • Usability
    • Geographical locations visually embedded within mlsn protocol.

results://


  • Simple request-reply messaging implementation.
  • Messaging content implements Extensible Markup Language (XML) defined by W3C.
  • Mimics Whois Protocol Specification: IETF RFC 3912.
  • Offers users Uniform Resource Locators (URLs).
  • Usable for all types of properties: Residential, Commercial, Land, Timeshares, etc.
  • Implements Representational State Transfer (REST).
  • 281 trillion reusable possible combinations (281,457,797,169,150).

examples://

mlsn://2.4.100@32819.840 (in Orlando, Florida, United States) 

mlsn://4.14.1970@36100.380/price (in Venice, Italy, Europe)

mlsn://50.2.16169@7000.036/beds (in Hobart, Tasmania, Australia)

mlsn://101.1006.3@10117.276/baths (in Berlin, Germany, Europe) 

mlsn://8.15.23@1102.608/squaremeters (in Claro, Philippines, Asia)

mlsn://33.3.7789@x.x/yearbuilt

mlsn://8080.56.921@x.x/contact

mlsn://10742.300.1@x.x/type

mlsn://585.467.239@x.x/status

mlsn://97.33933.47@x.x/description

mlsn://22.747.9387@x.x/style

Postal Codes from GeoNames.org.

http://en.wikipedia.org/wiki/3166-1

future_directions://


  • Protocol maintained by GR8C nonprofit organization for public use.
  • Developers develop mlsn clients in languages such as C, Python, Java, Ruby, etc.
  • Registry/Registrars offer web-based services for registering property listings.
  • Resolving domains to MLSN URL's via a registered Top-Level Domain (TLD).

conclusion://


From my research, I introduced a public, standardized numbering system and protocol called Multiple Listing Service Network (MLSN).

Similar to the Web, MLSN is an application publicly available on the Internet, but instead of port 80, MLSN is accessible from port 32801.

The numbering scheme is comprised of two parts separated by an ‘@’ symbol: (1) a triple-dotted notation of three decimal integers ranging from 1 to 65,535 and (2) a double-dotted notation number composed of a postal code and country code defined by ISO 3166-1.

Taking in consideration for expired listings, MLSN numbers have a reusable feature which allows assigning a new, double-dotted notation number to a preexisting triple-dotted number thereby creating a new MLSN number.

Together with a standard protocol and unique numbering schema, a Uniform Resource Locator (URL) is available to users for searching for property listings on the Internet.

appendix://


Messaging on the Wire

Specification

references://


Academics/Research/2011/MLSN (last edited 2011-04-01 14:15:16 by CoreyLeong)