RETS Payload / New QUery Language

[Steve Clarke]

Since we broke RETS Schema out of RETS 2 in Chicago, I would think that it would be beneficial to actually try to hook Schema into RETS 1 in some useful way. Ideally, the Schema would actually replace the "Standard Names" concept entirely. I would think that as long as we can provide a flattened representation of the Schema, then we should be able to represent the references from the metadata and also reference schema elements from DMQL2 directly. Since RETS 1 already supports field selectability in the query language, I don't see any reason why this could not work rather nicely. Field selectability was something that we've been struggling with in RETS2 all along. I would say that a RETS 1 "Standard XML" payload that adheres to the new RETS Schema would be a very nice interim step. It also seems like relatively easy and practical, given the current RETS1 implementations.

[Jeff Brush]

Originally Posted by cgmckeever

just playing devils advocate here....

What benefit do MLS vendors get to move to RETS2 (SOAP) when they could achieve the same robust dataset (RETS Payload) using the RETS1 Server (as suggessted by SMC)

The Transaction Management Servers could implement RETS2 for their B2B and gain listing data from the MLS Vendor RETS Payload (transport indifferent)..similiarly if a MLS system needed this B2B connection, they could by simply connect via a SOAP client.

RETS2 had/has much more to offer than just a specific listing data payload. The first release was only the basics - just an equivalent to RETS1.

There are roadmaps that describe where RETS could grow - new functionality such as data replication including data pushes, background batch processing, negotiating of advanced login protocols, data security, digital signatures, standardization of RE data formats such as CMA and hotsheets. All of which would greatly enhance the Value-proposition for MLSs.

RETS can be and should be more than just an internet database.

[MattL]

snip:

Originally Posted by Jeff Brush

There are roadmaps that describe where RETS could grow

Who has these roadmaps?

-Matt

[Jeff Brush]

Originally Posted by MattL

snip:


Who has these roadmaps?

-Matt

RETS leadership, pre-BOD, had them. But with the new leadership and direction, they may not be as relavant. I believe a summary was presented to the community at a meeting more than a year ago, maybe two now. I think it was the same time as the Steve Verba governance model.

[x-sol]

RETS 2 FTW (for the win)

[pobrien]

RETS2 FTW, indeed! :)

I think, with the new roadmap discussions going on, it's time to haul the RETS2 concepts out and discuss them. Despite the disagreements people may have had with certain implementation details, I think the baby got thrown out with the bathwater. RETS could have been leading the way instead of playing catch-up in areas like syndication. And working as an API for things such as what's now known as RPR? RETS2 was made to handle that.

You know I am the world's biggest advocate of RETS compliance, but let's get real...why exactly did everything else in RETS have to grind to a halt in the two years since the MLS policy was announced?