[Rets-dev] StandardNames mapping for Class

[Libor Viktorin]

Your "another vendor" will hit a big problem: If a client wants to
search using standard names, then the SearchType and Class must be
standard names (see RETS 1.7, 7.4.7). How does the server decide which
table to search if two tables have the same name?
The specification SHOULD explicitly say the standard names are unique,
but even if it does not, there is no correct way to implement classes
with shared names.

I would rephrase the issue and move it to another place: What if a
client searches using StandardNames=0, but Format=Standard-XML? Is it
then possible to use one of the standard DTDs to format the results,
even if the requested class did not have a standard name? 

Libor



-----Original Message-----
From: rets-dev-bounces at rets.org [mailto:rets-dev-bounces at rets.org] On
Behalf Of Keith T. Garner
Sent: Thursday, December 15, 2005 1:37 PM
To: rets-dev at rets.org
Subject: [Rets-dev] StandardNames mapping for Class

Another 1.5/1.7 fun question.

Another ezRETS user going against another MLS Vendor reports that the
MLS
Vendor has mapped a StandardName for a class to more than one class.

Let's say they have the following situation (the following table only
guaranteed to look good in a monospace font):
   StandardName         SystemName
   ------------         ----------
   LotsAndLand          LAND
   ResidentialProperty  RES
   ResidentialProperty  CONDO

(Those aren't the actual values, to protect the innocent, but you get
the idea.)

The MLS Vendor replied to my user (so this is totally 3rd hand): "We
must
assign one of the four labels to each class.  Many of our customers have
more than four classes and as such we must reuse the labels."  They also
recommend something to the effect of "just use system names."

I was digging through the spec and I didn't see anything about the
uniqueness of a StandardName.  The way I have things is I assumed the
StandardName to be unique within its context.  Unfortunately for me, the
spec doesn't support this.

Any opinions on this?  I'm playing around with a few different fixes as
asked about by the user, but I'm not sure if ezRETS is at fault here.  I
ended up giving the user the same reply "just use standard names" but
I'd
like to make ezRETS more compliant if it is in fact the problem.

Also, a question for Paul and Steve.  It looks like give my recent
mails,
we've found a few more points of confusion in the 1.x spec.  What are
our
plans on fixing/clarifying this items in 1.x?

Keith

-- 
   Keith T. Garner - Strategic Architect - Center for REALTOR(r)
Technology
     kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt

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