realestate-propertydetail: Difference between revisions
Line 16: | Line 16: | ||
=== Discussion === | === Discussion === | ||
First we need to identify the property attributes that are common in all MLS systems. For instance number of bedrooms, number of bathrooms, fireplace y/n, if y then how many fireplaces, etc. As we define the common attributes we can start building the framework | First we need to identify the property attributes that are common in all MLS systems and then see which of these attributes can be satified by using an existing microformat. For instance number of bedrooms, number of bathrooms, fireplace y/n, if y then how many fireplaces, etc. As we define the common attributes and the microformats that satisfy them we can start building the framework. When we run into situations or data where there is no existing satisfactory microformat, we can discuss creating the best approach to satisfying those specific instances. | ||
=== | === Property Related Formats === | ||
This section is to identify any compatible microformats (i.e. hListing, adr, geo) and list them out. Also we can suggest formats, even if they don't exist or if you aren't certain they exist, add them to the list and hopefully one of us will be able to add a link to the appropriate microformat | This section is to identify any compatible microformats (i.e. hListing, adr, geo) and list them out. Also we can suggest formats, even if they don't exist or if you aren't certain they exist, add them to the list and hopefully one of us will be able to add a link to the appropriate microformat |
Revision as of 19:47, 19 April 2007
Introduction
The realestate_propertydetail page is an exploratory discussion on developing a microformat that could be used in conjunction with adr, hListing, geo, and maybe others, to provide a consistent format for real estate property listings.
One of my ultimate goals is to not only be able to provide a consistent industry specific format, but to also begin attaching data to properties in a way that has never been done before. So for instance, if a Realtor has a listing for sale and they post the listing and photos of the listing with geo data, that that information can be cataloged forever with the property. Then over time homeowners, home buyers, property assessors, etc. can look at snapshots of the same property over time and visually see upgrades, deterioration, etc.
Discussion Participants
Editor
- Brian Fidler
Authors
- Brian Fidler
Discussion
First we need to identify the property attributes that are common in all MLS systems and then see which of these attributes can be satified by using an existing microformat. For instance number of bedrooms, number of bathrooms, fireplace y/n, if y then how many fireplaces, etc. As we define the common attributes and the microformats that satisfy them we can start building the framework. When we run into situations or data where there is no existing satisfactory microformat, we can discuss creating the best approach to satisfying those specific instances.
Property Related Formats
This section is to identify any compatible microformats (i.e. hListing, adr, geo) and list them out. Also we can suggest formats, even if they don't exist or if you aren't certain they exist, add them to the list and hopefully one of us will be able to add a link to the appropriate microformat
Is there a format for:
- photo or photo gallery (a Realtor could upload one or more photos of a property with geo data associated too)