Direct Response to Re: [Rets-dev] Google Base Housing vs. RETS

Fri Mar 16 13:38:29 CDT 2007

Yeah- I’m done

  _____  

From: john.rayburn at gmail.com [mailto:john.rayburn at gmail.com] 
Sent: Friday, March 16, 2007 12:36 PM
To: Stuart Schuessler
Cc: fwanicka at ezlistmls.com; Rets-dev at rets.org
Subject: Re: Direct Response to Re: [Rets-dev] Google Base Housing vs. RETS

I would suggest that allowing the rets-dev list to degrade into a flame war
is not what we, as a RETS community, are seeking.  As such, maybe all
involved can be considerate of each other as we discuss different
technologies, methodologies, systems, et cetera.  If we need to speak
without respect for each other, please take it off list. 

Sincerely,
John Rayburn

On 3/16/07, Stuart Schuessler <sschuessler at tds.net> wrote:

Yeah sometimes I come across that way when someone is being ridiculous.  For
example the comment you just made.  Do you think it was necessary to post it
to the entire group?  Now that you have would you like to point out the 
parts you find are insulting?  Which part insulted you the most?  Which
statement was snide?

I will admit that I may have been a little sarcastic and I did question any
actual experience using RETS or Real Estate based on the comments, but come 
on- replace RETS with a simpler format like GoogleBase.  It is naïve.

Stuart

-----Original Message-----
From: rets-dev-bounces at rets.org [mailto: rets-dev-bounces at rets.org
<mailto:rets-dev-bounces at rets.org> ] On Behalf
Of Frank Wanicka
Sent: Friday, March 16, 2007 10:33 AM
To: Rets-dev at rets.org
Subject: RE: Direct Response to Re: [Rets-dev] Google Base Housing vs. RETS 

Maybe you should refrain from any further replies to this thread if you
can't do it without being snide and insulting. There seem to be plenty of
others on the list that share your position that are able to respond 
politely.

_________________
Frank Wanicka
Real Estate Technologies, Inc.

> -----Original Message-----
> From: rets-dev-bounces at rets.org [mailto: rets-dev-bounces at rets.org] On
Behalf Of
> Stuart Schuessler
> Sent: Friday, March 16, 2007 11:59 AM
> To: dsrockets at gmail.com  <mailto:dsrockets at gmail.com> 
> Cc: Rets-dev at rets.org
> Subject: RE: Direct Response to Re: [Rets-dev] Google Base Housing vs.
RETS
>
> >>I can use an ATM, as well as most people.  Thats the vessel for 
> >>communication.  I dont need to know how it communicates and-or   what
> >>standard it uses.
>
> When you use that ATM you are using a client application that speaks to a
> server following a standard.  You as the end user do not know you are 
using
> a standard.  I am sure during the development of the ATM standard someone
> wanted to put it all on GoogleBase, but that would be crazy right?  I am
> sure that some thought the standard was too complicated. 
>
> So now you are saying you do not want it on Googlebase.  Ok.  You want the
> Googlebase metadata- right?  NP:  RETS2 supports different payloads.
> Propose a payload to the group that follows the Googlebase layout.  Did 
you
> want someone else to propose it?
>
> >>you completely missed the point of every email thus far from me.  I
>
> >>dont want to use googlebase.  I was merely comparing that two things, 
>
> >>same end result - one easy and one not
>
> There is nothing in RETS that would prevent a simpler data feed.  You are
> not even required to have a login.  You could just have a search.  It is 
the
> implementation of RETS to serve different business needs that complicates
> it.
>
> >>you completely missed the point of every email thus far from me.
>
> No, I think I completely understand your point.  Yes I do think that if 
you
> had your choice all real estate data would be in GoogleBase.  I think that
> there is a lack of understanding about what happens in real estate and you
> are frustrated because you cannot get access to data so you are blaming 
RETS
> without reading the RETS specification.
>
> >>the client and the standard SHOULD NOT define business rules.  What
> >>open industry standard defines business rules?
>
> I agree and RETS does not.  It provides a way to support the business
rules
> that are defined.  It even provides a way to publish some of those rules
> back to the client.
>
> >> What is this Mismo 
>
> You are actually working in Real Estate - right?  MISMO is the mortgage
> industry standard.  Paul had an earlier email about that.
>
> >>my friend, you have just defined everything you do AFTER THE FACT of 
>
> >>RETS when the data has been repurposed onto a different system.  Is
>
> >>RETS now supposed to be a complete tool to provide every view of the
>
> >>data sliced and diced that you want?  Or is it supposed to communicate 
>
> >>with an abstracted SERVER to get the data.  Oh and we are still only
>
> >>talking about listing data!
>
> Uh - wrong.  I am defining concerns that a server provider has before the 
> data is even obtained.  The business rules and fields need to be in place
to
> support various "repuposing".  Yes RETS can provide different views of
data.
> A client is suppose to communicate with a server to get the data and based

> on a number of factors that are defined by the MLS the view of data the
> client gets may be different and support the use of the data that follows
> the client's purpose for existing.  There is really nothing abstract about

> it.
>
> >> with RETS2 ?
>
> I have not used wget on RETS2.  RETS2 does follow the HTTP protocol so
there
> is not reason it cannot be done.  SOAP is just a standard on HTTP
(probably
> be better on Googlebase) so if you would like to got to the trouble of
> making the API calls using wget then I am sure you could do that.  You do
> know that the tools that generate everything for you in SOAP are just 
tools
> right?  They make the same HTTP calls.
>
> Stuart

_______________________________________________
Rets-dev mailing list
Rets-dev at rets.org 
http://lists.rets.org/mailman/listinfo/rets-dev

_______________________________________________
Rets-dev mailing list
Rets-dev at rets.org
http://lists.rets.org/mailman/listinfo/rets-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rets.org/pipermail/rets-dev/attachments/20070316/71bc2da8/attachment.html